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/01/21 16:47:59 UTC
[jira] Created: (AXIS2-4218) Calling a remote web service from
Axis2 generated stub results allocates a handle that does not get released
Calling a remote web service from Axis2 generated stub results 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
Affects Versions: 1.2, 1.3, 1.4, 1.4.1, 1.5
Environment: WIndows XP, Java 1.6_7 (and higher). Quad-core Intel system with 4Gb memory
Reporter: Dennis Urech
Priority: Critical
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.
[jira] Resolved: (AXIS2-4218) Calling a remote web service from
Axis2 generated stub allocates a handle that does not get released
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4218.
------------------------------------
Resolution: Invalid
Of course, otherwise I wouldn't have asked the question :-)
This is how I figured this out: The only thing that a Java process would ever want to get from the registry location "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" are the proxy settings configured in Windows/Explorer, so I tried to find out which component would be responsible for doing this. Since you traced the problem down to httpClient.executeMethod, the only candidates were commons-httpclient and the JRE. Actually commons-httpclient has some code to access the registry, but it is only in the "contrib" section and not part of the distribution, so this left only the JRE as a suspect. After searching a bit, I stumbled over a page that explains that Java 5 supports retrieving the proxy settings from the registry (in previous versions this was only supported inside applets) and that this is enabled by the system property I asked you to check.
Conclusion: you should switch that feature off and submit a bug report to the JRE vendor.
> 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.
[jira] Updated: (AXIS2-4218) Calling a remote web service from
Axis2 generated stub allocates a handle that does not get released
Posted by "Dennis Urech (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Urech updated AXIS2-4218:
--------------------------------
Summary: Calling a remote web service from Axis2 generated stub allocates a handle that does not get released (was: Calling a remote web service from Axis2 generated stub results allocates a handle that does not get released)
> 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
> 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: Critical
>
> 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.
[jira] Commented: (AXIS2-4218) Calling a remote web service from
Axis2 generated stub allocates a handle that does not get released
Posted by "Dennis Urech (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AXIS2-4218) Calling a remote web service from
Axis2 generated stub allocates a handle that does not get released
Posted by "Dennis Urech (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734276#action_12734276 ]
Dennis Urech commented on AXIS2-4218:
-------------------------------------
java.net.useSystemProxies=true
> 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.
[jira] Updated: (AXIS2-4218) Calling a remote web service from
Axis2 generated stub allocates a handle that does not get released
Posted by "Dennis Urech (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Urech updated AXIS2-4218:
--------------------------------
Component/s: transports
Priority: Blocker (was: Critical)
> 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.
[jira] Commented: (AXIS2-4218) Calling a remote web service from
Axis2 generated stub allocates a handle that does not get released
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734244#action_12734244 ]
Andreas Veithen commented on AXIS2-4218:
----------------------------------------
Can you please check what the value of the "java.net.useSystemProxies" system property inside the process that leaks the handles?
> 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.
[jira] Commented: (AXIS2-4218) Calling a remote web service from
Axis2 generated stub allocates a handle that does not get released
Posted by "Dennis Urech (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734282#action_12734282 ]
Dennis Urech commented on AXIS2-4218:
-------------------------------------
I just experimented with setting this property to false ans the leak APPEARS to be GONE!! Does this make sense to you.
> 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.