[
https://issues.apache.org/jira/browse/AXIS2-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-4198.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.5
Fixed in trunk and 1.5 branch
> Can not stop the ListenerManager when transports are added with the
> addListener() method
> ----------------------------------------------------------------------------------------
>
> Key: AXIS2-4198
> URL: https://issues.apache.org/jira/browse/AXIS2-4198
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: nightly
> Environment: Linux OS
> Reporter: Richard Slade
> Assignee: Jeff Barrett
> Fix For: 1.5, nightly
>
> Attachments: patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> With recent changes to the ListenerManager with revisions 726705 and 728440.
> The ListenerManager stop() method can now only be invoked after the start()
> method is called because of the proper use of the 'stopped' boolean flag. But
> when transports are added with the addListener() method and the 'started'
> parameter is set to false, the addListener() method starts the transport
> (just like invoking the start() method), but the stopped boolean is not set
> to 'false'. Currently the only was to set the 'stopped' boolean flag is my
> invoking the start() method. The code should be changed to set the 'stopped'
> boolean flag during the addListener() method if the 'started' parameter is
> set to false.
> Prior to these recent changes the stop() method could be invoked with
> transports added with the addListener() method.
> This problem was uncovered running the sandesha2 unit tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
