activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Mittler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-38) Async error on broker when running integration tests
Date Sun, 07 Jan 2007 15:28:48 GMT

    [ 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

        

Mime
View raw message