I am trying to use the transactional receive service on my msmq topics. The reason i am trying to use it is that if you don't turn it on, sometimes messages can get processed twice. Turning it on alleviates this problem, but has some unwanted side effects.
When the ESB service starts up i get this error in the event log:
Event Info: An communication error occured on the server when checking for messages: Party UrjanetResponseSubscriber Topic UrjanetResponseTopic Exception: Could not connect to net.tcp://<machine:port>/MsmqReceiveService/. The connection attempt lasted for a time span of 00:00:02.0008339. TCP error code 10061: No connection could be made because the target machine actively refused it <ip address:port>. Inner Exception: No connection could be made because the target machine actively refused it <ip address:port> Method: DoConnect Stack: Server stack trace: at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade) at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Neuron.Esb.Channels.Msmq.IMsmqChannelReceiveService.Receive(String queuePath, NameValuePair[] properties) at Neuron.Esb.Channels.Msmq.MsmqChannel.ServerCacheReceiveThread() at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
Then every 5 seconds thereafter, the receive service logs an ERROR in the event log like this one:
Event Info: Exception occurred during Receive Exception: Receive on local address net.msmq://localhost/private/<subscriber>_<topic> timed out after 00:00:05. The time allotted to this operation may have been a portion of a longer timeout. Method: Receive Stack: at System.ServiceModel.Channels.MsmqInputChannelBase.Receive(TimeSpan timeout) at Neuron.Esb.Channels.Msmq.MsmqChannelReceiveService.Receive(String queuePath, NameValuePair[] values)
There are no actual functional errors in the processing. It just keeps logging.This is happening even when there is no processing going on in the queues. This is filling up our event logs to the point where we are losing any "real" errors because of the flood of these non-errors.
How do i turn this off or configure it differently without turning off the transactional receive service on the topic? I can't find anywhere in neuron to configure this. Any help appreciated.
Tags: msmq
can you please enter this as a support request. just send an email to neuronsupport@neudesic.com. also include the neuron logs and what version of Neuron you are seeing this on.
as a general rule, you should not be using this. Its been removed in later versions of neuron as it was only applicable to msmq 3.0, which we no longer support in later versions of Neuron
if you are receiving duplicate messages, then something else is mis configured. We should work with you to determine what needs to be correctly configured.
kind regards,
marty
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin. Powered by