activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johan Ekesparr (JIRA)" <>
Subject [jira] Created: (AMQ-1719) Resource adapter stops consuming messages after broker is forcefully stopped/restarted during XA transaction.
Date Mon, 12 May 2008 12:47:43 GMT
Resource adapter stops consuming messages after broker is forcefully stopped/restarted during
XA transaction.

                 Key: AMQ-1719
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker, Connector
    Affects Versions: 5.1.0
         Environment: Windows XP, IBM WebSphere, Oracle, Java 1.5.0 ( IBM
J9 VM), ActiveMQ 5.1.0 downloaded 2008-May-12.
            Reporter: Johan Ekesparr
         Attachments:, DemoEAR.ear, websphere_trace.log

Have attached logs from websphere, activeMQ and also the content of the datadirectory for
details of data state ( plus the smal program used to create the scenario).

#1. Installed the resource adapter that came with ActiveMQ into the websperhe applicationserver
and configured it to connect to external broker using failover.
#2. Setup a JDBC XA datasource ( Oracle ) and JMS XA destination ( ActiveMQ ).
#3. Created a small Message Driven bean that receives a JMS message that it tries to store
in the database after which it sleeps for 5 secs. And deployed it to the WebSphere appserver.
#4. Started the activemq broker without doing any modifications since the download and extract
into the filesystem.
#5. Started applicationserver. 
#6. Started publishing messages to the broker
#7. As expected the Message driven bean received the messages one-by-one and processed them.
#8. Used to ctrl-C on the broker to halt it in the middle of the processing. Resulting in
a failed commit of XA transaction.
#9. Waited a while and then started broker again.
#10. Received Exception on client side and nothing more happened. 

Exception in thread "ActiveMQ Transport: tcp://localhost/" java.lang.NullPointerException
    at org.apache.activemq.state.ConnectionStateTracker$
    at org.apache.activemq.state.Tracked.onResponses(
    at org.apache.activemq.transport.failover.FailoverTransport$3.onCommand(
    at org.apache.activemq.transport.WireFormatNegotiator.onCommand(
    at org.apache.activemq.transport.InactivityMonitor.onCommand(
    at org.apache.activemq.transport.TransportSupport.doConsume(
    at org.apache.activemq.transport.tcp.TcpTransport.doRun(

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

View raw message