Connection reset by peer Exception in Stomp in Linux (in Windows Ok...) wenn 
Client führt connection.disconnect() sofort nach connection.send(..); 
connection.commit(..)  ohne Pause
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: AMQ-2951
                 URL: https://issues.apache.org/activemq/browse/AMQ-2951
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.4.0
         Environment: Linux version 2.6.32.12-0.7 SUSE Linux
            Reporter: Sergey Rem


Exception kommt Connection reset by peer.
Bei Senden einer Nachricht vom Client zum Broker Stomp in Linux (in Windows ist 
alles in Ordnung...)  kommt Exception, wenn Client führt 
connection.disconnect() sofort nach connection.send(..); connection.commit(..)  
ohne eine Pause nach commit zu machen. Mit Pause nach commit(...) ist alles in 
Ordnung.

INFO | Transport failed: java.io.IOException: Connection reset by peer
java.io.IOException: Connection reset by peer
        at sun.nio.ch.FileDispatcher.read0(Native Method)
        at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21)
        at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
        at sun.nio.ch.IOUtil.read(IOUtil.java:206)
        at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:207)
        at 
org.apache.activemq.transport.stomp.StompNIOTransport.serviceRead(StompNIOTransport.java:103)
        at 
org.apache.activemq.transport.stomp.StompNIOTransport.access$000(StompNIOTransport.java:51)
        at 
org.apache.activemq.transport.stomp.StompNIOTransport$1.onSelect(StompNIOTransport.java:80)
        at 
org.apache.activemq.transport.nio.SelectorSelection.onSelect(SelectorSelection.java:94)
        at 
org.apache.activemq.transport.nio.SelectorWorker$1.run(SelectorWorker.java:119)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
        at java.lang.Thread.run(Thread.java:595)


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to