[
https://issues.apache.org/activemq/browse/SM-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48154#action_48154
]
Soumya Pal commented on SM-1729:
--------------------------------
Hi Lars,
Thanks for ur input.
Actually we don't really have a Master slave set up as such. The secondary
servers I mentioned either sends direct JBI requests over the AMQ to .45
primary Smix server, or an http request comes over to a HTTP unit deployed in
the .45 servicemix. Not exactly clustered approach. By secondary servers I
meant sort of clients to the main servicemix process on .45. Sorry for the
confusion that I might have created.
Yes you are correct this is probably a ActiveMQ problem as it appears from the
error logs.
> 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.
