Uploaded image for project: 'ServiceMix'
  1. ServiceMix
  2. SM-1729

java.io.IOException: Wire format negociation timeout: peer did not send his wire format.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 3.2.1
    • None
    • servicemix-lwcontainer
    • None
    • Windows

    Description

      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

      Attachments

        Activity

          People

            chirino Hiram R. Chirino
            soumya Soumya Pal
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: