You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Albert Strasheim (JIRA)" <ji...@apache.org> on 2006/12/26 02:24:02 UTC

[jira] Created: (AMQCPP-38) Async error on broker when running integration tests

Async error on broker when running integration tests
----------------------------------------------------

                 Key: AMQCPP-38
                 URL: https://issues.apache.org/activemq/browse/AMQCPP-38
             Project: ActiveMQ C++ Client
          Issue Type: Bug
    Affects Versions: 1.1
            Reporter: Albert Strasheim
         Assigned To: Nathan Mittler


Brought over from the comments in AMQCPP-28.

Sometimes when running the integration tests against the AMQ broker from trunk, ones sees the following message from the broker:

ERROR Service - Async error occurred:
java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-36153-1166305227288-5:16:-1:1
at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
at java.lang.Thread.run(Thread.java:595)



Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily:

1. Start a fresh copy of the broker (4.2 from yesterday's trunk)
2. Run the integration test under Valgrind
3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired.

Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent - if it is, it could explain why I only see it when running under Valgrind.

On Linux, I also just got the following test failure for the first time (not running under Valgrind):

1) test: integration::durable::DurableTester::test (E)
uncaught exception of unknown type


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (AMQCPP-38) Async error on broker when running integration tests

Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Mittler updated AMQCPP-38:
---------------------------------

    Fix Version/s: 1.1

> Async error on broker when running integration tests
> ----------------------------------------------------
>
>                 Key: AMQCPP-38
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-38
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Albert Strasheim
>         Assigned To: Nathan Mittler
>             Fix For: 1.1
>
>
> Brought over from the comments in AMQCPP-28.
> Sometimes when running the integration tests against the AMQ broker from trunk, ones sees the following message from the broker:
> ERROR Service - Async error occurred:
> java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-36153-1166305227288-5:16:-1:1
> at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
> at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
> at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
> at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
> at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
> at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
> at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
> at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
> at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
> at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
> at java.lang.Thread.run(Thread.java:595)
> Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily:
> 1. Start a fresh copy of the broker (4.2 from yesterday's trunk)
> 2. Run the integration test under Valgrind
> 3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired.
> Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent - if it is, it could explain why I only see it when running under Valgrind.
> On Linux, I also just got the following test failure for the first time (not running under Valgrind):
> 1) test: integration::durable::DurableTester::test (E)
> uncaught exception of unknown type

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (AMQCPP-38) Async error on broker when running integration tests

Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Mittler updated AMQCPP-38:
---------------------------------

    Fix Version/s:     (was: 1.1)
                   2.0

Moving to release 2.0 - the current thought is that this may be an issue with the broker.

> Async error on broker when running integration tests
> ----------------------------------------------------
>
>                 Key: AMQCPP-38
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-38
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Albert Strasheim
>         Assigned To: Nathan Mittler
>             Fix For: 2.0
>
>
> Brought over from the comments in AMQCPP-28.
> Sometimes when running the integration tests against the AMQ broker from trunk, ones sees the following message from the broker:
> ERROR Service - Async error occurred:
> java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-36153-1166305227288-5:16:-1:1
> at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
> at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
> at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
> at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
> at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
> at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
> at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
> at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
> at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
> at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
> at java.lang.Thread.run(Thread.java:595)
> Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily:
> 1. Start a fresh copy of the broker (4.2 from yesterday's trunk)
> 2. Run the integration test under Valgrind
> 3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired.
> Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent - if it is, it could explain why I only see it when running under Valgrind.
> On Linux, I also just got the following test failure for the first time (not running under Valgrind):
> 1) test: integration::durable::DurableTester::test (E)
> uncaught exception of unknown type

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (AMQCPP-38) Async error on broker when running integration tests

Posted by "Albert Strasheim (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37830 ] 

Albert Strasheim commented on AMQCPP-38:
----------------------------------------

Here's the stacktrace on the broker that turns up when running the integration tests repeatedly with both the broker and the integration tests running on Windows XP SP2 with Sun Java 1.5.0_10 on a Core 2 Duo:

{noformat}
java.lang.IllegalArgumentException: The subscription does not exist: ID:xxx-4402-1168189818390-5:210:-1:1
	at org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:311)
	at org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:401)
	at org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:181)
	at org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:74)
	at org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:74)
	at org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:88)
	at org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:456)
	at org.apache.activemq.command.MessageAck.visit(MessageAck.java:179)
	at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:258)
	at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:164)
	at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
	at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
	at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
	at org.apache.activemq.transport.stomp.StompSubscription.onMessageDispatch(StompSubscription.java:71)
	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:47)
	at org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:972)
	at org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:709)
	at org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:725)
	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)
{noformat}

> Async error on broker when running integration tests
> ----------------------------------------------------
>
>                 Key: AMQCPP-38
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-38
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Albert Strasheim
>         Assigned To: Nathan Mittler
>             Fix For: 1.1
>
>
> Brought over from the comments in AMQCPP-28.
> Sometimes when running the integration tests against the AMQ broker from trunk, ones sees the following message from the broker:
> ERROR Service - Async error occurred:
> java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-36153-1166305227288-5:16:-1:1
> at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
> at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
> at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
> at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
> at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
> at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
> at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
> at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
> at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
> at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
> at java.lang.Thread.run(Thread.java:595)
> Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily:
> 1. Start a fresh copy of the broker (4.2 from yesterday's trunk)
> 2. Run the integration test under Valgrind
> 3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired.
> Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent - if it is, it could explain why I only see it when running under Valgrind.
> On Linux, I also just got the following test failure for the first time (not running under Valgrind):
> 1) test: integration::durable::DurableTester::test (E)
> uncaught exception of unknown type

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (AMQCPP-38) Async error on broker when running integration tests

Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37827 ] 

Nathan Mittler commented on AMQCPP-38:
--------------------------------------

Running the integration tests several times in a row against the latest trunk of the broker (everything co-located on the same OS X machine), I do not get this error.  Could you please provide your environment? 

Also, try running against the broker's latest trunk and see if you still have problems.

> Async error on broker when running integration tests
> ----------------------------------------------------
>
>                 Key: AMQCPP-38
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-38
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Albert Strasheim
>         Assigned To: Nathan Mittler
>             Fix For: 1.1
>
>
> Brought over from the comments in AMQCPP-28.
> Sometimes when running the integration tests against the AMQ broker from trunk, ones sees the following message from the broker:
> ERROR Service - Async error occurred:
> java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-36153-1166305227288-5:16:-1:1
> at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
> at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
> at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
> at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
> at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
> at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
> at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
> at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
> at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
> at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
> at java.lang.Thread.run(Thread.java:595)
> Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily:
> 1. Start a fresh copy of the broker (4.2 from yesterday's trunk)
> 2. Run the integration test under Valgrind
> 3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired.
> Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent - if it is, it could explain why I only see it when running under Valgrind.
> On Linux, I also just got the following test failure for the first time (not running under Valgrind):
> 1) test: integration::durable::DurableTester::test (E)
> uncaught exception of unknown type

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (AMQCPP-38) Async error on broker when running integration tests

Posted by "Albert Strasheim (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37829 ] 

Albert Strasheim commented on AMQCPP-38:
----------------------------------------

I've been running the integration tests repeatedly on Windows.

DurableTester fails most of the time. Also seeing exceptions in the broker in new places. Also got this crash, which is quite interesting:

{noformat}
1) test: inR6025
- pure virtual function call
tegration::durable::DurableTester::test (E)
uncaught exception of unknown type


2) test: integration::simple::SimpleTester::test (E)
uncaught exception of unknown type
{noformat}

> Async error on broker when running integration tests
> ----------------------------------------------------
>
>                 Key: AMQCPP-38
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-38
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Albert Strasheim
>         Assigned To: Nathan Mittler
>             Fix For: 1.1
>
>
> Brought over from the comments in AMQCPP-28.
> Sometimes when running the integration tests against the AMQ broker from trunk, ones sees the following message from the broker:
> ERROR Service - Async error occurred:
> java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-36153-1166305227288-5:16:-1:1
> at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
> at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
> at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
> at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
> at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
> at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
> at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
> at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
> at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
> at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
> at java.lang.Thread.run(Thread.java:595)
> Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily:
> 1. Start a fresh copy of the broker (4.2 from yesterday's trunk)
> 2. Run the integration test under Valgrind
> 3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired.
> Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent - if it is, it could explain why I only see it when running under Valgrind.
> On Linux, I also just got the following test failure for the first time (not running under Valgrind):
> 1) test: integration::durable::DurableTester::test (E)
> uncaught exception of unknown type

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (AMQCPP-38) Async error on broker when running integration tests

Posted by "Albert Strasheim (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37828 ] 

Albert Strasheim commented on AMQCPP-38:
----------------------------------------

Built a brand new AMQ 4.2, revision 493766. Also running AMQCPP from revision 493766. Using the default activemq.xml that gets included in the tarball made by the AMQ build.

Running on Fedora Core 6 x86 Linux with Sun Java SDK 1.5.0_10. Hardware wise I'm running a Intel P4 2.8 GHz with HT enabled with 2 GB RAM.

All the unit tests pass. The integration tests also pass, but I still get the error on the broker the first time I run the integration tests after broker startup. Not running under Valgrind or anything like that.

Stacktrace says:

{noformat}
java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-40938-1168188574402-5:0:-1:1
        at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:552)
        at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
        at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:258)
        at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:164)
        at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
        at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
        at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
        at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
        at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
        at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
        at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
        at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
        at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
        at java.lang.Thread.run(Thread.java:595)
{noformat}

As you can see, the line numbers have changed slightly from the previous stacktrace.

The second time I run the integration tests (without restarting the broker), I get this:

{noformat}
[albert@dogbert test-integration]$ ./activemq-test-integration 
integration::durable::DurableTester::test. : errorE
integration::expiration::ExpirationTest::testExpired.b928ada1-656d-47c3-b1ee-5e6b5eb6954b
 : OK
integration::expiration::ExpirationTest::testNotExpired.943b9129-9147-46f0-8016-414389f0ca5e
 : OK
integration::simple::SimpleTester::test. : OK
integration::transactional::TransactionTester::test. : OK
integration::various::SimpleRollbackTest::test. : OK



!!!FAILURES!!!
Test Results:
Run:  6   Failures: 0   Errors: 1


1) test: integration::durable::DurableTester::test (E) 
uncaught exception of unknown type
{noformat}

No stacktrace on the broker though. The third time I run the tests, another failure appears:

{noformat}
[albert@dogbert test-integration]$ ./activemq-test-integration 
integration::durable::DurableTester::test. : errorE
integration::expiration::ExpirationTest::testExpired.3036ea6e-b22c-4daf-8446-53c17e6995f4
 : OK
integration::expiration::ExpirationTest::testNotExpired.0577f611-aa2b-452f-9aa4-42d654375b78
 : OK
integration::simple::SimpleTester::test. : OK
integration::transactional::TransactionTester::test. : errorE
integration::various::SimpleRollbackTest::test. : OK



!!!FAILURES!!!
Test Results:
Run:  6   Failures: 0   Errors: 2


1) test: integration::durable::DurableTester::test (E) 
uncaught exception of unknown type


2) test: integration::transactional::TransactionTester::test (E) 
uncaught exception of unknown type
{noformat}

On the next run, TransactionTester passes again.

Just restarted the broker and ran the integration tests again -- no IllegalStateException stacktrace this time. Noticed this in the broker log on startup the second time round:

{noformat}
INFO  JournalPersistenceAdapter      - Journal Recovered: 1 message(s) in transactions recovered.
{noformat}

Ran the tests again against the second instance of the broker. Everything went fine again. Next run after that yielded a DurableTester failure again, but no stacktrace on the broker.

> Async error on broker when running integration tests
> ----------------------------------------------------
>
>                 Key: AMQCPP-38
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-38
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Albert Strasheim
>         Assigned To: Nathan Mittler
>             Fix For: 1.1
>
>
> Brought over from the comments in AMQCPP-28.
> Sometimes when running the integration tests against the AMQ broker from trunk, ones sees the following message from the broker:
> ERROR Service - Async error occurred:
> java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-36153-1166305227288-5:16:-1:1
> at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
> at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
> at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
> at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
> at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
> at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
> at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
> at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
> at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
> at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
> at java.lang.Thread.run(Thread.java:595)
> Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily:
> 1. Start a fresh copy of the broker (4.2 from yesterday's trunk)
> 2. Run the integration test under Valgrind
> 3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired.
> Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent - if it is, it could explain why I only see it when running under Valgrind.
> On Linux, I also just got the following test failure for the first time (not running under Valgrind):
> 1) test: integration::durable::DurableTester::test (E)
> uncaught exception of unknown type

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (AMQCPP-38) Async error on broker when running integration tests

Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Mittler closed AMQCPP-38.
--------------------------------

    Resolution: Fixed

I believe this to be a broker side issue captured in AMQ-1077

> Async error on broker when running integration tests
> ----------------------------------------------------
>
>                 Key: AMQCPP-38
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-38
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Albert Strasheim
>         Assigned To: Nathan Mittler
>             Fix For: 2.0
>
>
> Brought over from the comments in AMQCPP-28.
> Sometimes when running the integration tests against the AMQ broker from trunk, ones sees the following message from the broker:
> ERROR Service - Async error occurred:
> java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-36153-1166305227288-5:16:-1:1
> at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
> at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
> at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
> at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
> at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
> at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
> at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
> at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
> at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
> at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
> at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
> at java.lang.Thread.run(Thread.java:595)
> Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily:
> 1. Start a fresh copy of the broker (4.2 from yesterday's trunk)
> 2. Run the integration test under Valgrind
> 3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired.
> Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent - if it is, it could explain why I only see it when running under Valgrind.
> On Linux, I also just got the following test failure for the first time (not running under Valgrind):
> 1) test: integration::durable::DurableTester::test (E)
> uncaught exception of unknown type

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