You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2009/05/28 22:35:45 UTC
[jira] Updated: (GERONIMO-3928) Exception on stopping server after
sending a non persistent message
[ https://issues.apache.org/jira/browse/GERONIMO-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-3928:
-----------------------------------
Priority: Minor (was: Major)
Fix Version/s: (was: 2.2)
Verification Required
Need to see if it's still happening with current amq before spending any time on this. Note behavior seems correct, just annoying.
> Exception on stopping server after sending a non persistent message
> -------------------------------------------------------------------
>
> Key: GERONIMO-3928
> URL: https://issues.apache.org/jira/browse/GERONIMO-3928
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Reporter: Anish Pathadan
> Priority: Minor
> Fix For: Verification Required
>
> Attachments: sendMessage.war
>
>
> Hi,
> I am getting the following exception on stopping the server after sending a non persistent message to a queue.
> I have attached a test case for this.
> Steps to reproduce the issue:-
> 1).Deploy the attached sendMessage.war
> 2).Access http://localhost:8080/sendMessage/SendMessage to send a non persistent message.
> 3).Stop the server using Ctrl-C
> Following is the stack trace
> 07:39:08,828 WARN [ActiveMQManagedConnection] Connection failed: javax.jms.JMSE
> xception: java.io.EOFException
> 07:39:08,843 WARN [GeronimoConnectionEventListener] connectionErrorOccurred cal
> led with null
> javax.jms.JMSException: java.io.EOFException
> at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSuppo
> rt.java:46)
> at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConne
> ction.java:1519)
> at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection
> .java:1535)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFi
> lter.java:96)
> at org.apache.activemq.transport.ResponseCorrelator.onException(Response
> Correlator.java:114)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFi
> lter.java:96)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFi
> lter.java:96)
> at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFo
> rmatNegotiator.java:147)
> at org.apache.activemq.transport.InactivityMonitor.onException(Inactivit
> yMonitor.java:150)
> at org.apache.activemq.transport.TransportSupport.onException(TransportS
> upport.java:97)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
> 150)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.io.EOFException
> at java.io.DataInputStream.readInt(DataInputStream.java:358)
> at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.
> java:267)
> at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTranspo
> rt.java:156)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
> 136)
> ... 1 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.