activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-1219) If a STOMP client does not disconnect or there is an error in the DISCONNECT frame the next message produced is lost
Date Mon, 08 Sep 2008 14:55:56 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully updated AMQ-1219:
----------------------------

    Fix Version/s: 5.3.0
                       (was: 5.2.0)

> If a STOMP client does not disconnect or there is an error in the DISCONNECT frame the
next message produced is lost
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1219
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1219
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 4.1.0
>         Environment: SuSE SLES10 java 1.5 and java 1.6
>            Reporter: Jay van der Meer
>             Fix For: 5.3.0
>
>
> Using the provided example programs I created a durable queue and then used STOMP to
read the messages.  If the STOMP client does not send a DISCONNECT frame or the DISCONNECT
frame is missing \n the next message sent will produce the following stack trace in activemq.log
and will not be sent:
> 2007-04-03 13:50:00,987 [ception Handler] DEBUG Transport                      - Transport
failed: java.io.IOException: The transport is no
> t running.
> java.io.IOException: The transport is not running.
>         at org.apache.activemq.transport.TransportSupport.checkStarted(TransportSupport.java:103)
>         at org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:117)
>         at org.apache.activemq.transport.stomp.StompTransportFilter.sendToStomp(StompTransportFilter.java:80)
>         at org.apache.activemq.transport.stomp.StompSubscription.onMessageDispatch(StompSubscription.java:81)
>         at org.apache.activemq.transport.stomp.ProtocolConverter.onActiveMQCommad(ProtocolConverter.java:479)
>         at org.apache.activemq.transport.stomp.StompTransportFilter.oneway(StompTransportFilter.java:56)
>         at org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:141)
>         at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:43)
>         at org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1051)
>         at org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:772)
>         at org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:788)
>         at org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
>         at org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
>         at org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
> To reproduce the error:
> 1. Using the provided examples modify the build.xml to set durable = true max = 1
> 2. ant producer
> 3. Using a stomp client read the message but do not send a DISCONNECT.
> 4. ant producer
> 5. Using a stomp client or ant consumer the message produced in step 4 will not be in
the queue.
> Thanks.

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


Mime
View raw message