[
https://issues.apache.org/jira/browse/AXIS2-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Schmidt updated AXIS2-5329:
--------------------------------
Attachment: Patch_5329.7z
I dived deeper into that issue. I will use the Axis 2 OSGi bundle to run Axis 2
in my OSGi-Runtime, but that doesn't work with the current release of 1.6.2 and
also with previous releases. This issue is very complicated. The startup
process runs synchronous to the bundle activation, but the startup process
needs the configuration context to register the Axis2 servlet at the
Http-Service. The configuration context will be instantiated with the managed
service and register as a service, but this cannot be work because of issue
4847.
The mistake is that the startup process doesn't not work, because there is no
configuration context and the configuration context can not be registered
because the bundle is not active or activating.
I fixed that issue. I implemented to register the Axis2 servlet at the
Http-Service asynchronously from the bundle activation process. For that
implementation I used declarative services to bind the Http-Service and Axis2
configuration context to do the registration only if that two things are
available. After that the Axis2 bundle runs very well in my OSGi-Runtime, also
with active configuration manager (look at previous comment).
Please take a look into my patch and merge it into branch 1.6.x and 1.7.x. Can
i get an release of 1.6.3 after merging that patch?
My OSGi-Runtime:
START LEVEL 1
ID|State |Level|Name
0|Active | 0|System Bundle (4.2.1)
5|Active | 1|Apache JAMES Mime4j (Core) (0.7.2)
6|Active | 1|Axiom API (1.2.14)
7|Active | 1|Axiom DOM (1.2.14)
8|Active | 1|Axiom Impl (1.2.14)
9|Active | 1|Apache Commons Codec (1.9.0)
10|Active | 1|Commons FileUpload (1.3.0)
11|Active | 1|Apache Geronimo Bundles: commons-httpclient-3.1
(3.1.0.2)
12|Active | 1|Commons IO (2.4.0)
13|Active | 1|Commons Logging (1.1.3)
14|Active | 1|de.kisters.wab.amigw.hello (5.80.0.SNAPSHOT)
15|Active | 1|Activation 1.1 (1.1.0)
16|Active | 1|JavaMail 1.4 (1.7.1)
17|Active | 1|geronimo-jms_1.1_spec (1.1.1)
18|Active | 1|geronimo-stax-api_1.0_spec (1.0.1)
19|Active | 1|Web Services Metadata 2.0 (1.1.3)
20|Active | 1|Apache HttpClient OSGi bundle (4.2.4)
21|Active | 1|Apache HttpCore OSGi bundle (4.2.4)
22|Active | 1|jsr311-api (1.1.1)
23|Active | 1|Apache Neethi (3.0.2)
24|Active | 1|org.apache.axis2.osgi (1.0.0.2)
25|Active | 1|Apache Felix Bundle Repository (1.6.6)
26|Active | 1|Apache Felix Configuration Admin Service (1.8.0)
27|Active | 1|Apache Felix EventAdmin (1.3.2)
28|Active | 1|Apache Felix Gogo Command (0.12.0)
29|Active | 1|Apache Felix Gogo Runtime (0.10.0)
30|Active | 1|Apache Felix Gogo Shell (0.10.0)
31|Active | 1|Apache Felix Http Jetty (2.2.2)
32|Active | 1|Apache Felix (4.2.1)
33|Active | 1|Apache Felix Metatype Service (1.0.10)
34|Active | 1|Apache Felix Declarative Services (1.8.2)
35|Active | 1|Apache ServiceMix :: Bundles :: wsdl4j (1.6.2.6)
36|Active | 1|Stax2 API (3.1.1)
37|Active | 1|Woden - API (1.0.0)
38|Active | 1|Woden - Commons (1.0.0)
39|Active | 1|Woden - DOM (1.0.0)
40|Active | 1|Woodstox XML-processor (4.2.0)
41|Active | 1|XmlSchema (1.4.7)
> ConcurrentModificationException from org.apache.axis2.osgi during startup
> -------------------------------------------------------------------------
>
> Key: AXIS2-5329
> URL: https://issues.apache.org/jira/browse/AXIS2-5329
> Project: Axis2
> Issue Type: Bug
> Components: modules
> Affects Versions: 1.6.2
> Environment: Linux, Karaf using felix,
> Reporter: Tomas Forsman
> Attachments: Patch_5329.7z, axis2-karaf-example.zip
>
>
> I receive the following exception during startup of the axis2 osgi bundle:
> ERROR: Bundle org.apache.axis2.osgi [77] EventDispatcher: Error during
> dispatch. (java.util.ConcurrentModificationException)
> java.util.ConcurrentModificationException
> at
> java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
> at java.util.AbstractList$Itr.next(AbstractList.java:343)
> at
> org.apache.axis2.osgi.deployment.tracker.BundleTracker$1.bundleChanged(BundleTracker.java:68)
> at
> org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:807)
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:729)
> at
> org.apache.felix.framework.util.EventDispatcher.run(EventDispatcher.java:949)
> at
> org.apache.felix.framework.util.EventDispatcher.access$000(EventDispatcher.java:54)
> at
> org.apache.felix.framework.util.EventDispatcher$1.run(EventDispatcher.java:106)
> at java.lang.Thread.run(Thread.java:662)
> From looking at the code, I guess that a quick fix would be to make the
> following method synchronized:
> OSGiConfigurationContextFactory.updated(Dictionary dictionary)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
