[
https://issues.apache.org/jira/browse/AXIS2-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691142#comment-13691142
]
Sven Strohschein commented on AXIS2-4847:
-----------------------------------------
It still occurs with Axis2 1.6.2:
Jun 22, 2013 1:20:07 PM org.apache.axis2.osgi.deployment.tracker.BundleTracker
open
INFO: Bundle tracker is opened
Jun 22, 2013 1:20:07 PM org.apache.axis2.deployment.DeploymentEngine
addServiceGroup
INFO: Deploying Web service: test.access-webservice_0 -
Jun 22, 2013 1:20:07 PM org.apache.axis2.osgi.deployment.ServiceRegistry
addServices
INFO: [Axis2/OSGi] Deployed axis2 service group:test.access-webservice_0 in
Bundle: test.access-webservice
Jun 22, 2013 1:20:07 PM
org.apache.axis2.osgi.deployment.OSGiConfigurationContextFactory updated
INFO: Axis2 environment has started.
ERROR: Bundle org.apache.axis2.osgi [2] Error starting
file:/C:/Users/Sven/.m2/repository/org/apache/axis2/org.apache.axis2.osgi/1.6.2/org.apache.axis2.osgi-1.6.2.jar
(org.osgi.framework.BundleException: Activator start error in bundle
org.apache.axis2.osgi [2].)
*ERROR* [org.osgi.service.cm.ManagedService, id=27,
bundle=2/file:/C:/Users/Sven/.m2/repository/org/apache/axis2/org.apache.axis2.osgi/1.6.2/org.apache.axis2.osgi-1.6.2.jar]:
Unexpected problem updating configuration null
java.lang.IllegalStateException: Can only register services while bundle is
active or activating.
at org.apache.felix.framework.Felix.registerService(Felix.java:3209)
at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:320)
at
org.apache.axis2.osgi.deployment.OSGiConfigurationContextFactory.updated(OSGiConfigurationContextFactory.java:106)
at
org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1467)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)
at java.lang.Thread.run(Thread.java:722)
java.lang.NullPointerException: Specified service reference cannot be null.
at
org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:458)
at
org.apache.axis2.osgi.internal.Activator$HttpServiceTracker.addingService(Activator.java:79)
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:980)
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:906)
at
org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:262)
at
org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:185)
at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:348)
at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:283)
at org.apache.axis2.osgi.internal.Activator.start(Activator.java:50)
at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:641)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1977)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1895)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)
at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)
at java.lang.Thread.run(Thread.java:722)
> IllegalStateException: Can only register services while bundle is active or
> activating.
> ---------------------------------------------------------------------------------------
>
> Key: AXIS2-4847
> URL: https://issues.apache.org/jira/browse/AXIS2-4847
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: Apache Felix Framework 3.0.2
> Reporter: Ancoron Luciferis
>
> I'm trying to run the axis2 OSGi version 1.5.1 inside a GlassFish 3.1
> (promoted build 23 currently) and facing the following problem:
> *ERROR* [org.osgi.service.cm.ManagedService, id=68, bundle=280]: Unexpected
> problem updating null
> java.lang.IllegalStateException: Can only register services while bundle is
> active or activating.
> at org.apache.felix.framework.Felix.registerService(Felix.java:2817)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:229)
> at
> org.apache.axis2.osgi.deployment.OSGiConfigurationContextFactory.updated(OSGiConfigurationContextFactory.java:107)
> at
> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1112)
> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:88)
> And because of that I then get:
> org.osgi.framework.BundleException: Activator start error in bundle
> org.apache.axis2.osgi [280].
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1864)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1734)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:892)
> at com.profitbricks.osgi.test.FelixTest.testModules(FelixTest.java:241)
> Caused by: java.lang.NullPointerException: Specified service reference cannot
> be null.
> at
> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:319)
> at
> org.apache.axis2.osgi.internal.Activator$HttpServiceTracker.addingService(Activator.java:79)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
> at
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
> at
> org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:184)
> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339)
> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273)
> at org.apache.axis2.osgi.internal.Activator.start(Activator.java:50)
> at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:633)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1817)
> ... 33 more
> When I read the code I don't really understand why the implementor chose
> "ManagedService" for the "OSGiConfigurationContextFactory" as it really
> should be a "ManagedServiceFactory". Additionally manually invoking the
> "updated" method within the activator code is counter-productive, as it is
> called automatically (and must be called asynchronously) by the OSGi
> Config-Admin.
> See sections 104.15.9 and 104.15.10 of the OSGi Compendium spec v4.2.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
