You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Soumya Pal (JIRA)" <ji...@apache.org> on 2008/12/12 10:28:05 UTC
[jira] Commented: (SM-1729) java.io.IOException: Wire format
negociation timeout: peer did not send his wire format.
[ https://issues.apache.org/activemq/browse/SM-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48145#action_48145 ]
Soumya Pal commented on SM-1729:
--------------------------------
Hi,
I was able to fix this problem by stopping all the smix processes on all servers. Then starting the primary Smix server process on 192.10.10.45. It started fine. Then I started the 2 secondary server smix processes i.e. the ones on 192.10.10.46 and 192.10.10.49. They work fine now.
But still I would not say the issue is "fixed". If anyone can give an insight to why this might have arised might help others in future to get an idea of what they should avoid or how to get a permanant fix.
Rgds,
Soumya
> java.io.IOException: Wire format negociation timeout: peer did not send his wire format.
> ----------------------------------------------------------------------------------------
>
> Key: SM-1729
> URL: https://issues.apache.org/activemq/browse/SM-1729
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-lwcontainer
> Affects Versions: 3.2.1
> Environment: Windows
> Reporter: Soumya Pal
> Assignee: Hiram Chirino
>
> I have been using Servicemix professionally in our
> company.
> There is a strange issue we have.
> We have a Servicemix server running on say
> 192.10.10.45. and we have lwc components deployed over
> there.
> Now we have 2 more client applciations (on
> 192.10.10.46 abd 192.10.10.49) which are also
> servicemix but listen on AMQ url on 192.10.10.45 i.e.
> th eprimary server.
> Now we made restart of the primary and secondary
> servers. Now teh order of restart so happened that
> when the primary 192.10.10.45 server was restarted the
> other 2 secondary server processes were already
> running.
> Sicne then we are gettibng
> ActiveMQ Transport Server: tcp://localhost:61616 |
> TransportConnector |
> org.apache.activemq.broker.TransportConnector$1
> 162 | Could not accept connection from
> /192.10.10.46:4778: java.net.SocketException: Software
> caused connection abort: socket write error
> java.net.SocketException: Software caused connection
> abort: socket write error
> and
> 2008-12-11 10:46:53,319 | ERROR | ActiveMQ Transport
> Server: tcp://localhost:61616 | TransportConnector
> | org.apache.activemq.broker.TransportConnector$1
> 162 | Could not accept connection from
> /192.10.10.46:4780: java.io.IOException: Wire format
> negociation timeout: peer did not send his wire
> format.
> java.io.IOException: Wire format negociation timeout:
> peer did not send his wire format.
> at
> org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:88)
> --------------------
> Endpoint connection to JMS broker failed: Could not
> connect to broker URL: tcp://localhost:61616. Reason:
> java.net.SocketException: Connection reset by peer:
> socket write error
> ---------------------
> Endpoint connection to JMS broker failed: Could not
> connect to broker URL: tcp://localhost:61616. Reason:
> java.net.SocketException: Connection reset by peer:
> socket write error
> Can you kindly sugest why thsi may be occuring?
> Thanks in advance
> Soumya
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.