You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (JIRA)" <ji...@apache.org> on 2012/10/01 07:39:08 UTC
[jira] [Commented] (APLO-207) "Use of object not allowed after it
has been released" error then broker stuck
[ https://issues.apache.org/jira/browse/APLO-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466650#comment-13466650 ]
Lionel Cons commented on APLO-207:
----------------------------------
Unfortunately, no. This happens very infrequently.
> "Use of object not allowed after it has been released" error then broker stuck
> ------------------------------------------------------------------------------
>
> Key: APLO-207
> URL: https://issues.apache.org/jira/browse/APLO-207
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-99-trunk-20120519.032132-42
> Reporter: Lionel Cons
> Attachments: APLO-207.log
>
>
> Using apollo-99-trunk-20120519.032132-42, we saw once in our logs:
> 2012-05-25 17:46:02,285 | WARN | java.lang.AssertionError: stomp subscription id: our-id, remote address: /127.0.0.1:49582: Use of object not allowed after it has been released. | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-4
> Then the broker was unusable, stuck on "virtual host shutdown is waiting on stop". The broker could not be stopped via "service apollo stop", only "kill -9" has been able stop it.
> See the attached logs for more information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira