activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APLO-156) AssertionError on queue browser creation
Date Wed, 08 Feb 2012 23:49:59 GMT

    [ https://issues.apache.org/jira/browse/APLO-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204122#comment-13204122
] 

Hiram Chirino commented on APLO-156:
------------------------------------

Thanks for the report.  Fix should make it into the next SNAPSHOT.
                
> AssertionError on queue browser creation
> ----------------------------------------
>
>                 Key: APLO-156
>                 URL: https://issues.apache.org/jira/browse/APLO-156
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-stomp
>    Affects Versions: 1.0
>         Environment: Windows Vista SP 2
>            Reporter: Michael Justin
>             Fix For: 1.1
>
>
> When the Stomp client opens a queue browser, the broker logs an AssertionError:
> send:
> CONNECT
> login:admin
> passcode:password
> accept-version:1.0,1.1
> server:localhost
> heart-beat:0,0
> received:
> CONNECTED
> version:1.1
> server:apache-apollo/1.0
> session:mybroker-1238
> heart-beat:100,10000
> user-id:admin
> send:
> SUBSCRIBE
> destination:/queue/TOOL.DEFAULT
> id:{28C1F8E4-3125-4FDD-B2A6-CC14DCDE9EE3}
> send:
> SEND
> destination:/queue/TOOL.DEFAULT
> send:
> SEND
> destination:/queue/TOOL.DEFAULT
> send:
> SUBSCRIBE
> destination:/queue/TOOL.DEFAULT
> id:{5A963ED4-9799-4FD0-B6DC-96E3C9446401}
> browser:true
> -> when this subscribe frame has been sent, the broker logs:
> WARN  | java.lang.AssertionError: assertion failed: this.rejection_handler.$eq$eq(null)
> A minor problem is in the browser:end message frame, the subscription id is repeated:
> received:
> MESSAGE
> subscription:{5A963ED4-9799-4FD0-B6DC-96E3C9446401}
> subscription:{5A963ED4-9799-4FD0-B6DC-96E3C9446401}
> destination:
> message-id:
> browser:end
> And there is an exception when the client disconnects after it has read the queue browser
until the end:
> java.lang.AssertionError: stomp subscription id: {5A963ED4-9799-4FD0-B6DC-96E3C9
> 446401}, remote address: /127.0.0.1:50646: Use of object not allowed after it ha
> s been released.
>         at org.fusesource.hawtdispatch.BaseRetained.assertRetained(BaseRetained.
> java:157)
>         at org.fusesource.hawtdispatch.BaseRetained.retain(BaseRetained.java:79)
>         at org.apache.activemq.apollo.broker.LocalRouter.unbind(LocalRouter.scal
> a:1058)
>         at org.apache.activemq.apollo.stomp.StompProtocolHandler$$anonfun$on_tra
> nsport_disconnected$2.apply(StompProtocolHandler.scala:722)
>         at org.apache.activemq.apollo.stomp.StompProtocolHandler$$anonfun$on_tra
> nsport_disconnected$2.apply(StompProtocolHandler.scala:720)
>         at scala.collection.immutable.Map$Map2.foreach(Map.scala:139)
>         at org.apache.activemq.apollo.stomp.StompProtocolHandler.on_transport_di
> sconnected(StompProtocolHandler.scala:720)
>         at org.apache.activemq.apollo.stomp.StompProtocolHandler.on_transport_co
> mmand(StompProtocolHandler.scala:787)
>         at org.apache.activemq.apollo.broker.BrokerConnection.on_transport_comma
> nd(Connection.scala:125)
>         at org.apache.activemq.apollo.broker.Connection$$anon$1.onTransportComma
> nd(Connection.scala:51)
>         at org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTr
> ansport.java:597)
>         at org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport
> .java:472)
>         at org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispa
> tchSource.java:226)
>         at org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDi
> spatchQueue.java:83)
>         at org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThre
> ad.java:61)
> I can reproduce it on every broker run, using Apollo 1.0 final

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message