Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 29 Jun 2011 22:45:29 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1442426299.4025.1309387529239.JavaMail.tomcat@hel.zones.apache.org>
Subject: =?utf-8?Q?[jira]_[Closed]_(AMQ-2951)_Connection_reset_by_peer?=
 =?utf-8?Q?_Exception_in_Stomp_in_Linux_(in_Windows_Ok...)_wenn?=
 =?utf-8?Q?_Client_f=C3=BChrt_connection.disconnect()_sofort_nach_co?=
 =?utf-8?Q?nnection.send(..);_connection.commit(..)__ohne_Pause?=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/AMQ-2951?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-2951.
-----------------------------

    Resolution: Not A Problem

Given the description it sounds like a timing issue where the broker is sti=
ll reading the last bit of data when the socket is closed.  If you have a t=
est case to reproduce please attach and reopen the issue.

> Connection reset by peer Exception in Stomp in Linux (in Windows Ok...) w=
enn Client f=C3=BChrt connection.disconnect() sofort nach connection.send(.=
.); connection.commit(..)  ohne Pause
> -------------------------------------------------------------------------=
---------------------------------------------------------------------------=
--------------------------------
>
>                 Key: AMQ-2951
>                 URL: https://issues.apache.org/jira/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 Windo=
ws ist alles in Ordnung...)  kommt Exception, wenn Client f=C3=BChrt connec=
tion.disconnect() sofort nach connection.send(..); connection.commit(..)  o=
hne 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.serviceR=
ead(StompNIOTransport.java:103)
>         at org.apache.activemq.transport.stomp.StompNIOTransport.access$0=
00(StompNIOTransport.java:51)
>         at org.apache.activemq.transport.stomp.StompNIOTransport$1.onSele=
ct(StompNIOTransport.java:80)
>         at org.apache.activemq.transport.nio.SelectorSelection.onSelect(S=
electorSelection.java:94)
>         at org.apache.activemq.transport.nio.SelectorWorker$1.run(Selecto=
rWorker.java:119)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadP=
oolExecutor.java:651)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE=
xecutor.java:676)
>         at java.lang.Thread.run(Thread.java:595)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira