You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2010/05/06 11:20:37 UTC
[jira] Created: (SMX4NMR-190) can't refresh JBI deployer bundle
can't refresh JBI deployer bundle
---------------------------------
Key: SMX4NMR-190
URL: https://issues.apache.org/activemq/browse/SMX4NMR-190
Project: ServiceMix NMR
Issue Type: Bug
Reporter: Freeman Fang
Assignee: Freeman Fang
Fix For: 1.4.0
if we refresh JBI deployer bundle, then the blueprint container for this bundle doesn't start up correctly,
we will see
[ 66] [Active ] [Failure ] [ ] [ 60] Apache ServiceMix JBI Deployer (1.2.0)
and from the log, we get exception like
17:15:59,873 | ERROR | pool-2-thread-1 | BlueprintContainerImpl | container.BlueprintContainerImpl 337 | Unable to start blueprint container for bundle org.apache.servicemix.jbi.deployer
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to intialize bean adminCommandsService
at org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:519)
at org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)
at org.apache.geronimo.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:212)
at org.apache.geronimo.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:140)
at org.apache.geronimo.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:603)
at org.apache.geronimo.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:310)
at org.apache.geronimo.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:211)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
This could cause problem when JBI Deployer bundle get refreshed (it could be caused by refresh other bundles which JBI Deployer bundle import package from) , and afterwords JBI artifacts deployment doesn't work at all
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SMX4NMR-190) can't refresh JBI deployer bundle
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4NMR-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved SMX4NMR-190.
----------------------------------
Resolution: Fixed
commit fix
http://svn.apache.org/viewvc?rev=941622&view=rev
> can't refresh JBI deployer bundle
> ---------------------------------
>
> Key: SMX4NMR-190
> URL: https://issues.apache.org/activemq/browse/SMX4NMR-190
> Project: ServiceMix NMR
> Issue Type: Bug
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 1.4.0
>
>
> if we refresh JBI deployer bundle, then the blueprint container for this bundle doesn't start up correctly,
> we will see
> [ 66] [Active ] [Failure ] [ ] [ 60] Apache ServiceMix JBI Deployer (1.2.0)
> and from the log, we get exception like
> 17:15:59,873 | ERROR | pool-2-thread-1 | BlueprintContainerImpl | container.BlueprintContainerImpl 337 | Unable to start blueprint container for bundle org.apache.servicemix.jbi.deployer
> org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to intialize bean adminCommandsService
> at org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:519)
> at org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)
> at org.apache.geronimo.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:212)
> at org.apache.geronimo.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:140)
> at org.apache.geronimo.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:603)
> at org.apache.geronimo.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:310)
> at org.apache.geronimo.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:211)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> This could cause problem when JBI Deployer bundle get refreshed (it could be caused by refresh other bundles which JBI Deployer bundle import package from) , and afterwords JBI artifacts deployment doesn't work at all
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (SMX4NMR-190) can't refresh JBI deployer
bundle
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4NMR-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SMX4NMR-190 started by Freeman Fang.
> can't refresh JBI deployer bundle
> ---------------------------------
>
> Key: SMX4NMR-190
> URL: https://issues.apache.org/activemq/browse/SMX4NMR-190
> Project: ServiceMix NMR
> Issue Type: Bug
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 1.4.0
>
>
> if we refresh JBI deployer bundle, then the blueprint container for this bundle doesn't start up correctly,
> we will see
> [ 66] [Active ] [Failure ] [ ] [ 60] Apache ServiceMix JBI Deployer (1.2.0)
> and from the log, we get exception like
> 17:15:59,873 | ERROR | pool-2-thread-1 | BlueprintContainerImpl | container.BlueprintContainerImpl 337 | Unable to start blueprint container for bundle org.apache.servicemix.jbi.deployer
> org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to intialize bean adminCommandsService
> at org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:519)
> at org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)
> at org.apache.geronimo.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:212)
> at org.apache.geronimo.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:140)
> at org.apache.geronimo.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:603)
> at org.apache.geronimo.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:310)
> at org.apache.geronimo.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:211)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> This could cause problem when JBI Deployer bundle get refreshed (it could be caused by refresh other bundles which JBI Deployer bundle import package from) , and afterwords JBI artifacts deployment doesn't work at all
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.