axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-4552) TransportListener#init called twice on the same instance
Date Tue, 17 Nov 2009 16:19:39 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778966#action_12778966
] 

Amila Chinthaka Suriarachchi commented on AXIS2-4552:
-----------------------------------------------------

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

Are you sure? I think this method was there before your change. So at that time it assumes
init is not called if the start is not called.


That is why I was saying that you cannot just init and add the listener without starting

I think the init method is called because of your change. At the ListnerManager init method
it calls init for all transport listners.


> 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.


Mime
View raw message