[
https://issues.apache.org/jira/browse/AXIS2-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154858#comment-14154858
]
Andy Schmidt commented on AXIS2-5671:
-------------------------------------
I dived deeper into this issue and fixed it. I created the patch file
'AXIS2-5671.patch' which fix this issue in file
'org.apache.axis2.osgi.deployment.tracker.BundleTracker'. This issue sometimes
happens because of some bundles could be switch their state from starting to
active after the open method handled all current active bundles and before the
'BundleListener' are registered. I fixed it to register the 'BundleListener'
before running over all active bundles ate startup process. The
'BundleListener' will handle bundles which are starting to slow or lazy.
> Axis OSGi Bundle doesn't handle all bundles at startup process to register
> Axis Services
> ----------------------------------------------------------------------------------------
>
> Key: AXIS2-5671
> URL: https://issues.apache.org/jira/browse/AXIS2-5671
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.6.2
> Reporter: Andy Schmidt
> Fix For: 1.7.0, 1.6.3
>
> Attachments: AXIS2-5671.patch
>
>
> Sometimes the Axis OSGi Bundle doesn't handle all bundles at startup process
> to register there Axis Services from WSDL and service XML files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
