You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2010/06/10 15:13:51 UTC
[jira] Created: (SMX4NMR-194) JBI cluster exception on console at
shutdown
JBI cluster exception on console at shutdown
---------------------------------------------
Key: SMX4NMR-194
URL: https://issues.apache.org/activemq/browse/SMX4NMR-194
Project: ServiceMix NMR
Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: 1.2.0
When the JBI cluster engine is deployed, you can see this exception at shutdown when the ActiveMQ broker is on the same container and is being shut down before the cluster engine:
{noformat}
Exception in thread "ActiveMQ Connection Worker: tcp://localhost/127.0.0.1:61616" org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint container is being or has been destroyed
at org.apache.geronimo.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:175)
at org.apache.geronimo.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:49)
at org.apache.geronimo.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:200)
at org.apache.geronimo.blueprint.container.AbstractServiceReferenceRecipe$JdkProxyFactory$1.invoke(AbstractServiceReferenceRecipe.java:561)
at $Proxy95.createConnection(Unknown Source)
at org.apache.servicemix.jbi.cluster.requestor.ActiveMQJmsRequestorPool.createConnection(ActiveMQJmsRequestorPool.java:111)
at org.springframework.jms.listener.AbstractJmsListeningContainer.createSharedConnection(AbstractJmsListeningContainer.java:378)
at org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:363)
at org.apache.servicemix.jbi.cluster.requestor.ActiveMQJmsRequestorPool.onException(ActiveMQJmsRequestorPool.java:102)
at org.apache.activemq.ActiveMQConnection$4.run(ActiveMQConnection.java:1809)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SMX4NMR-194) JBI cluster exception on console at
shutdown
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4NMR-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved SMX4NMR-194.
-------------------------------------
Resolution: Fixed
Fixed in http://svn.apache.org/viewvc?view=revision&revision=953318 by logging the exception instead of showing it on the console.
Ideally, we should make the Cluster Engine more aware of the environment and dynamically disable itself when the ConnectionFactory is being unregistered as explained in SMX4NMR-195
> JBI cluster exception on console at shutdown
> ---------------------------------------------
>
> Key: SMX4NMR-194
> URL: https://issues.apache.org/activemq/browse/SMX4NMR-194
> Project: ServiceMix NMR
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: 1.4.0
>
>
> When the JBI cluster engine is deployed, you can see this exception at shutdown when the ActiveMQ broker is on the same container and is being shut down before the cluster engine:
> {noformat}
> Exception in thread "ActiveMQ Connection Worker: tcp://localhost/127.0.0.1:61616" org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint container is being or has been destroyed
> at org.apache.geronimo.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:175)
> at org.apache.geronimo.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:49)
> at org.apache.geronimo.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:200)
> at org.apache.geronimo.blueprint.container.AbstractServiceReferenceRecipe$JdkProxyFactory$1.invoke(AbstractServiceReferenceRecipe.java:561)
> at $Proxy95.createConnection(Unknown Source)
> at org.apache.servicemix.jbi.cluster.requestor.ActiveMQJmsRequestorPool.createConnection(ActiveMQJmsRequestorPool.java:111)
> at org.springframework.jms.listener.AbstractJmsListeningContainer.createSharedConnection(AbstractJmsListeningContainer.java:378)
> at org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:363)
> at org.apache.servicemix.jbi.cluster.requestor.ActiveMQJmsRequestorPool.onException(ActiveMQJmsRequestorPool.java:102)
> at org.apache.activemq.ActiveMQConnection$4.run(ActiveMQConnection.java:1809)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:637)
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMX4NMR-194) JBI cluster exception on console at
shutdown
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4NMR-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen updated SMX4NMR-194:
------------------------------------
Fix Version/s: 1.4.0
(was: 1.2.0)
Affects Version/s: 1.2.0
(was: 1.0.0)
> JBI cluster exception on console at shutdown
> ---------------------------------------------
>
> Key: SMX4NMR-194
> URL: https://issues.apache.org/activemq/browse/SMX4NMR-194
> Project: ServiceMix NMR
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: 1.4.0
>
>
> When the JBI cluster engine is deployed, you can see this exception at shutdown when the ActiveMQ broker is on the same container and is being shut down before the cluster engine:
> {noformat}
> Exception in thread "ActiveMQ Connection Worker: tcp://localhost/127.0.0.1:61616" org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint container is being or has been destroyed
> at org.apache.geronimo.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:175)
> at org.apache.geronimo.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:49)
> at org.apache.geronimo.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:200)
> at org.apache.geronimo.blueprint.container.AbstractServiceReferenceRecipe$JdkProxyFactory$1.invoke(AbstractServiceReferenceRecipe.java:561)
> at $Proxy95.createConnection(Unknown Source)
> at org.apache.servicemix.jbi.cluster.requestor.ActiveMQJmsRequestorPool.createConnection(ActiveMQJmsRequestorPool.java:111)
> at org.springframework.jms.listener.AbstractJmsListeningContainer.createSharedConnection(AbstractJmsListeningContainer.java:378)
> at org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:363)
> at org.apache.servicemix.jbi.cluster.requestor.ActiveMQJmsRequestorPool.onException(ActiveMQJmsRequestorPool.java:102)
> at org.apache.activemq.ActiveMQConnection$4.run(ActiveMQConnection.java:1809)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:637)
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.