You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Dennis Urech (JIRA)" <ji...@apache.org> on 2009/07/22 16:29:14 UTC

[jira] Commented: (AXIS2-4218) Calling a remote web service from Axis2 generated stub allocates a handle that does not get released

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

Dennis Urech commented on AXIS2-4218:
-------------------------------------

Can you guys please look into this problem!  If you cannot fix it, can you at least provide a workaround (I don't care how convoluted it may be).  I need this resolved.  Am I just doing something wrong??

Please respond

Thanks

> Calling a remote web service from Axis2 generated stub allocates a handle that does not get released
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-4218
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4218
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.5, 1.4.1, 1.4, 1.3, 1.2
>         Environment: WIndows XP, Java 1.6_7 (and higher). Quad-core Intel system with 4Gb memory
>            Reporter: Dennis Urech
>            Priority: Blocker
>
> When I make a call to an Axis2 generated stub to access a remote web service, several Windows handles are allocated (approximately 5).  All but 1 of these is released.  The one that remains (and is not released) is a handle to a Registry Key "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings".  I have traced it down the allocation of all the handles to the call to the httpClient.executeMethod(config, method); in AbstractHTTPSender (line 542).
> We call this web service every 5 seconds and therefore my code is leaking about 700 of these handles every hour.  After about a 3 days we have to kill our applications since it has consumed too many handles.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.