Hi,
I'm getting following error when try to send the messages (even from test clients). This happens only the Transport set to TCP.
Event Info: Party Subscriber2 / session 09c6c6c2-1872-480e-83a3-29b8d423333f. The message was not delivered. MessageId: 66727f46-98c6-429e-a843-f2be0c874822
Exception: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'.
Inner Exception: An existing connection was forcibly closed by the remote host
Method: Send
Stack:
Server stack trace:
at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, BufferManager bufferManager)
at System.ServiceModel.Channels.BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager
Any one experienced this and resolved?
Cheers,
Gihan.
Tags:
are you testing on the same machine or remote? when you hit connect, did the topics report being online, or where they still offline?
The TCP transports requires ports to be open. Their is a port associated with the topic...then the client port range. All are specified in the network properties. Please make sure that there is nothing, like the local firewall, interfering/blocking the ports. Also, check either the Neuron ESB logs for the specific topic or look at the neuron esb event log on the server to see if the Topic actually started up. It may not have due to blocked port...or it may have shut down
Hi Marty,
Thanks for the replies.
I'm using the same machine with two test clients Publisher and Subscriber, status on both are Online.
Publisher sent the message but no message received at Subscriber. On the Endpoint Health, under the topic, it says message is processed but there is an error and error is same as what I posted early. Also 2 warnings.
Event Info: Attempting to reconnect Party to Topic. Party Publisher2, session 56267f23-fbd2-4500-842e-959c4337bc00, server address net.tcp://localhost:50013/ESBTcpPubSub/, topic Topic2
Method: Reconnect
Event Info: Client has not received ping from sever in the last 20.0478391 seconds. Reconnecting... Party: Publisher2 Session: 56267f23-fbd2-4500-842e-959c4337bc00 Topic: Topic2 Server Address net.tcp://localhost:50013/ESBTcpPubSub/
Method: TimerElapsed
Also this warnings are keep appearing on the topic log which cause to fill up the disk space eventually.
Fire wall is off.
I tried a new topic with new publisher and subscriber without luck.
Cheers,
Gihan
can you please send us the neuron log files so we can inspect them. you can email them to neuronsupport@neudesic.com. The email will auto generate a support ticket for you.
A new set of log files gets created each time you restart the esb service. the default location is :
c:\Program Files\Neudesic\Neuron ESB v3\Logs\Default
Hi Marty,
Just sent the log files to neuronsupport@neudesic.com
Cheers,
Gihan.
Hi Marty,
Any further update on this? Have you had a chance to look at the log files?
This issue stopping us doing further development/configuration and testing on Neuron ESB in our Dev environment.
Cheers,
Gihan.
just sent you an update
For any one having this problem, check the Networking property under TCP transport make sure Reliable set to False.
Cheers,
Gihan.
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin. Powered by