[
https://issues.apache.org/jira/browse/AXIS2-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778850#action_12778850
]
Ruwan Linton commented on AXIS2-4552:
-------------------------------------
Amila, if you carefully look at the addListener method there is a boolean flag
called started, which is used when adding a listener which has already been
initialized and started. That is why I was saying that you cannot just init and
add the listener without starting, if you init it you need to start it before
adding and pass started as true to the addListener method.
This change has been done purposely... for a synapse requirement. Anyway
initializing the listeners when the listener manager is initializing a logical
then doing it at the start method.
Thanks,
Ruwan
> TransportListener#init called twice on the same instance
> --------------------------------------------------------
>
> Key: AXIS2-4552
> URL: https://issues.apache.org/jira/browse/AXIS2-4552
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: nightly
> Reporter: Andreas Veithen
> Fix For: 1.6
>
>
> It seems that under some circumstances, the init method of the same
> TransportListener instance is called twice during the lifecycle of the
> listener. Evidence can be found here:
> http://markmail.org/thread/25ksz5k2pnunxkpd
> http://svn.apache.org/viewvc?rev=835750&view=rev
> This is of course incorrect: the init method must be called only once on a
> given instance. This is probably a regression caused by Ruwan's patch (or
> Glen's corrections to that patch) for AXIS2-4304 [Note: if this is the case
> then probably Axis2 1.5 is also affected]. This is a major issue since it
> causes uncontrollable resource leakage (thread pools, timers, etc.).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
