You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Nikos Berdos (JIRA)" <ji...@apache.org> on 2013/02/11 14:27:12 UTC
[jira] [Commented] (SMX4-1245) activemq-broker.xml stays in
Blueprint "GracePeriod" state forever
[ https://issues.apache.org/jira/browse/SMX4-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575777#comment-13575777 ]
Nikos Berdos commented on SMX4-1245:
------------------------------------
I have a new installation of SMX 4.4.2 on a Windows 7 64bit and the problem persists. I have modified the org.apache.karaf.features file in order to add new features and move the activemq-broker.xml at the end, so my new featuresBoot is:
featuresBoot=karaf-framework,config,activemq-spring,cxf-specs,camel,camel-activemq,camel-cxf,camel-blueprint,war,camel-jaxb,camel-bindy,jpa,webconsole,activemq-broker
SMX starts but the activemq-broker never appears in the list:
karaf@root> list | grep activemq
[ 58] [Active ] [ ] [ ] [ 60] activemq-pool (5.5.1)
[ 59] [Active ] [ ] [ ] [ 60] activemq-console (5.5.1)
[ 61] [Active ] [ ] [ ] [ 60] activemq-ra (5.5.1)
[ 62] [Active ] [Created ] [ ] [ 60] activemq-core (5.5.1)
[ 63] [Active ] [Created ] [ ] [ 60] activemq-karaf (5.5.1)
[ 73] [Active ] [ ] [ ] [ 60] activemq-spring (5.5.1)
[ 114] [Active ] [ ] [ ] [ 50] activemq-camel (5.5.1)
[ 165] [Resolved ] [ ] [ ] [ 60] activemq-blueprint (5.5.1)
karaf@root>
After restarting the SMX (osgi:shutdown and start SMX) I see it on the list:
karaf@root> list | grep activemq
[ 58] [Active ] [ ] [ ] [ 60] activemq-pool (5.5.1)
[ 59] [Active ] [ ] [ ] [ 60] activemq-console (5.5.1)
[ 61] [Active ] [ ] [ ] [ 60] activemq-ra (5.5.1)
[ 62] [Active ] [Created ] [ ] [ 60] activemq-core (5.5.1)
[ 63] [Active ] [Created ] [ ] [ 60] activemq-karaf (5.5.1)
[ 73] [Active ] [ ] [ ] [ 60] activemq-spring (5.5.1)
[ 114] [Active ] [ ] [ ] [ 50] activemq-camel (5.5.1)
[ 165] [Resolved ] [ ] [ ] [ 60] activemq-blueprint (5.5.1)
[ 169] [Active ] [Created ] [ ] [ 60] activemq-broker.xml (0.0.0)
In the subsequent restarts I see that it is in GracePeriod but then it starts successfully:
karaf@root> list | grep activemq
karaf@root> list | grep activemq
[ 43] [Active ] [GracePeriod ] [ ] [ 60] activemq-broker.xml (0.0.0)
[ 59] [Active ] [ ] [ ] [ 60] activemq-pool (5.5.1)
[ 60] [Active ] [ ] [ ] [ 60] activemq-console (5.5.1)
[ 62] [Active ] [ ] [ ] [ 60] activemq-ra (5.5.1)
[ 63] [Active ] [Created ] [ ] [ 60] activemq-core (5.5.1)
[ 64] [Active ] [Created ] [ ] [ 60] activemq-karaf (5.5.1)
[ 74] [Active ] [ ] [ ] [ 60] activemq-spring (5.5.1)
[ 115] [Active ] [ ] [ ] [ 50] activemq-camel (5.5.1)
[ 166] [Resolved ] [ ] [ ] [ 60] activemq-blueprint (5.5.1)
karaf@root> list | grep activemq
[ 43] [Active ] [Created ] [ ] [ 60] activemq-broker.xml (0.0.0)
[ 59] [Active ] [ ] [ ] [ 60] activemq-pool (5.5.1)
[ 60] [Active ] [ ] [ ] [ 60] activemq-console (5.5.1)
[ 62] [Active ] [ ] [ ] [ 60] activemq-ra (5.5.1)
[ 63] [Active ] [Created ] [ ] [ 60] activemq-core (5.5.1)
[ 64] [Active ] [Created ] [ ] [ 60] activemq-karaf (5.5.1)
[ 74] [Active ] [ ] [ ] [ 60] activemq-spring (5.5.1)
[ 115] [Active ] [ ] [ ] [ 50] activemq-camel (5.5.1)
[ 166] [Resolved ] [ ] [ ] [ 60] activemq-blueprint (5.5.1)
Shall we expect a quick fix on this or any other elegant workaround since this behavior could jeopardize the operation of the system.
> activemq-broker.xml stays in Blueprint "GracePeriod" state forever
> ------------------------------------------------------------------
>
> Key: SMX4-1245
> URL: https://issues.apache.org/jira/browse/SMX4-1245
> Project: ServiceMix 4
> Issue Type: Bug
> Environment: ServiceMix 4.3
> Reporter: metatech
>
> In a small proportion of the time (about 20%) of first starting ServiceMix, the bundle "activemq-broker.xml" stays in the "GracePeriod" forever (ie no timeout after 5 minutes). It is waiting for a namespace handler for the namespace "http://activemq.apache.org/schema/core", which should be exported by the bundle "activemq-blueprint", which is declared as a OSGi fragment of the "activemq-core" bundle. When the problem occurs, the fragment is not properly attached to the host bundle. See the extract of the Karaf console :
> {code}
> [ 46] [Active ] [ ] [ ] [ 60] activemq-core (5.4.2)
> [ 56] [Installed ] [ ] [ ] [ 60] activemq-blueprint (5.4.2)
> [ 59] [Active ] [GracePeriod ] [ ] [ 60] activemq-broker.xml (0.0.0)
> {code}
> There are no "Hosts:" and "Fragments:" lines.
> The activemq-blueprint stays in "Installed" state instead of "Resolved", and cannot be started manually because it is a fragment bundle.
> Proposed short-term workaround (untested) : merge both bundles "activemq-core" and "activemq-blueprint".
> Long-term solution : I guess the problem is due to a race condition between the starting of the bundles and the discovery of the "host-fragment" relationship : maybe a 2-phase mechanism is needed.
--
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