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 "LEE (JIRA)" <ji...@apache.org> on 2008/07/01 14:13:44 UTC

[jira] Created: (AXIS2-3883) file handles not being closed after successful call to webservice

file handles not being closed after successful call to webservice
-----------------------------------------------------------------

                 Key: AXIS2-3883
                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
    Affects Versions: 1.3
         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
            Reporter: LEE
            Priority: Blocker


We have been regularly experiencing the following problem when trying to call an axis 2 webservice:

Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
	at java.util.zip.ZipFile.open(Native Method)
	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
	at java.security.AccessController.doPrivileged(AccessController.java:192)
	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
	

On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.

The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "LEE (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609574#action_12609574 ] 

LEE commented on AXIS2-3883:
----------------------------

All the webservices we are currently using have java2 security on.

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Priority: Blocker
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "LEE (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609593#action_12609593 ] 

LEE commented on AXIS2-3883:
----------------------------

The fact that I don't know what that is suggests not - however, I didn't set these up so can you tell me whereI would find these settings and then I'll let you know what else is on.

Cheers

Lee

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Priority: Blocker
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609576#action_12609576 ] 

Davanum Srinivas commented on AXIS2-3883:
-----------------------------------------

What else is on? PARENT_LAST class loading?

thanks,
dims

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Priority: Blocker
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Updated: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Glen Daniels updated AXIS2-3883:
--------------------------------

    Fix Version/s: 1.5

Can we look into this for 1.5?

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Blocker
>             Fix For: 1.5
>
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655200#action_12655200 ] 

Glen Daniels commented on AXIS2-3883:
-------------------------------------

Found some code which might help us here - at least for the client side or servers that are recycling.

http://www.devx.com/Java/Article/22018/ has a TempFileManager class which a) puts each instance's files in a unique directory making it easier to clean up, and b) reaps old files (ones not locked by a running process) each time it starts up.  It's not the right long-term solution for the long-running server problem, but it's a start.  I've asked the author if we can use it and he'll hopefully submit it here soon so we have the right licensing.

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Blocker
>             Fix For: 1.5
>
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


[jira] Updated: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Michael Pilone (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pilone updated AXIS2-3883:
----------------------------------

    Attachment: TempFileManager.java

The TempFileManager which will put temporary files in a single folder and then cleanup old folders when the application is restarted. Please cite the DevX article and myself if the code is used in production. There is no official license on the code so Apache is free to do what they like with it.

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Blocker
>             Fix For: 1.5
>
>         Attachments: TempFileManager.java
>
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


[jira] Issue Comment Edited: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Sujay Chauhan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613955#action_12613955 ] 

sujay.chauhan edited comment on AXIS2-3883 at 7/16/08 6:49 AM:
---------------------------------------------------------------

Hi 

We are seeing the same issue and it is holding us up from moving to production as out production servers would run out of disk space.

This is in regards to a client that we are trying to implement using axis2-1.4 and rampart-1.3. 

We have a folder structure

clientProjectFolder
      --otherFolders
      --....
      --....
      --axis2
          --conf
                --axis2.xml
           --modules
                 --rampart1.3.mar


our axis2.xml file contains the global module <module ref="rampart"/>
In our client code, we make use of the fileSytemConfigurator to configure the client stub before making the call to our service.

Every time we are calling the service, files are added to the TEMP folder (see below)

C:\TEMP\_axis2>dir
 Volume in drive C has no label.
 Volume Serial Number is 0CE7-7F35

 Directory of C:\TEMP\_axis2

07/16/2008  08:36 AM    <DIR>          .
07/16/2008  08:36 AM    <DIR>          ..
07/16/2008  08:36 AM             2,704 axis2473rampart-1.3.mar
               1 File(s)          2,704 bytes
               2 Dir(s)  103,722,340,352 bytes free

The same issue is being duplicated on our prod servers which are not windows based but linux based. the files get put in /tmp/_axis2 folder.

Any advice on if there is a workaround for this?

Thanks,
Sujay

      was (Author: sujay.chauhan):
    Hi 

We are seeing the same issue and it is holding us up from moving to production as out production servers would run out of disk space.

This is in regards to a client that we are trying to implement using axis2. We have a folder structure

clientProjectFolder
      --otherFolders
      --....
      --....
      --axis2
          --conf
                --axis2.xml
           --modules
                 --rampart1.3.mar


our axis2.xml file contains the global module <module ref="rampart"/>
In our client code, we make use of the fileSytemConfigurator to configure the client stub before making the call to our service.

Every time we are calling the service, files are added to the TEMP folder (see below)

C:\TEMP\_axis2>dir
 Volume in drive C has no label.
 Volume Serial Number is 0CE7-7F35

 Directory of C:\TEMP\_axis2

07/16/2008  08:36 AM    <DIR>          .
07/16/2008  08:36 AM    <DIR>          ..
07/16/2008  08:36 AM             2,704 axis2473rampart-1.3.mar
               1 File(s)          2,704 bytes
               2 Dir(s)  103,722,340,352 bytes free

The same issue is being duplicated on our prod servers which are not windows based but linux based. the files get put in /tmp/_axis2 folder.

Any advice on if there is a workaround for this?

Thanks,
Sujay
  
> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Priority: Blocker
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Sujay Chauhan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613955#action_12613955 ] 

Sujay Chauhan commented on AXIS2-3883:
--------------------------------------

Hi 

We are seeing the same issue and it is holding us up from moving to production as out production servers would run out of disk space.

This is in regards to a client that tries to use axis2. We have a folder structure

projectFolder
      --otherFolders
      --axis2
          --conf
                --axis2.xml
           --modules
                 --rampart1.3.mar


our axis2.xml file contains the global module <module ref="rampart"/>
In our client code, we make use of the fileSytemConfigurator to configure the client stub before making the call to our service.

Every time we are calling the service, files are added to the TEMP folder (see below)

C:\TEMP\_axis2>dir
 Volume in drive C has no label.
 Volume Serial Number is 0CE7-7F35

 Directory of C:\TEMP\_axis2

07/16/2008  08:36 AM    <DIR>          .
07/16/2008  08:36 AM    <DIR>          ..
07/16/2008  08:36 AM             2,704 axis2473rampart-1.3.mar
               1 File(s)          2,704 bytes
               2 Dir(s)  103,722,340,352 bytes free

The same issue is being duplicated on our prod servers which are not windows based but linux based. the files get put in /tmp/_axis2 folder.

Any advice on if there is a workaround for this?

Thanks,
Sujay

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Priority: Blocker
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675800#action_12675800 ] 

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

I had a chance to look at this issue.

If you deploy a mar (or aar) file first Axis2 copy this file to a temp file location. Then extract each and every jar file in this mar (or aar) file in the the same folder. The reason for doing this is it has to create a class loader for this archive file.

If you deployed in extracted form then it does not create any temp files and create the class loader from there.

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Blocker
>             Fix For: 1.5
>
>         Attachments: TempFileManager.java
>
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


[jira] Commented: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609557#action_12609557 ] 

Davanum Srinivas commented on AXIS2-3883:
-----------------------------------------

Also looks like rampart code needs to cache the DocumentBuilderFactory (getDocumentFromSOAPEnvelope)

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Priority: Blocker
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Updated: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Deepal Jayasinghe updated AXIS2-3883:
-------------------------------------

    Fix Version/s:     (was: 1.5)
                   nightly

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Blocker
>             Fix For: nightly
>
>         Attachments: TempFileManager.java
>
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


[jira] Issue Comment Edited: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Sujay Chauhan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613955#action_12613955 ] 

sujay.chauhan edited comment on AXIS2-3883 at 7/16/08 6:44 AM:
---------------------------------------------------------------

Hi 

We are seeing the same issue and it is holding us up from moving to production as out production servers would run out of disk space.

This is in regards to a client that we are trying to implement using axis2. We have a folder structure

clientProjectFolder
      --otherFolders
      --....
      --....
      --axis2
          --conf
                --axis2.xml
           --modules
                 --rampart1.3.mar


our axis2.xml file contains the global module <module ref="rampart"/>
In our client code, we make use of the fileSytemConfigurator to configure the client stub before making the call to our service.

Every time we are calling the service, files are added to the TEMP folder (see below)

C:\TEMP\_axis2>dir
 Volume in drive C has no label.
 Volume Serial Number is 0CE7-7F35

 Directory of C:\TEMP\_axis2

07/16/2008  08:36 AM    <DIR>          .
07/16/2008  08:36 AM    <DIR>          ..
07/16/2008  08:36 AM             2,704 axis2473rampart-1.3.mar
               1 File(s)          2,704 bytes
               2 Dir(s)  103,722,340,352 bytes free

The same issue is being duplicated on our prod servers which are not windows based but linux based. the files get put in /tmp/_axis2 folder.

Any advice on if there is a workaround for this?

Thanks,
Sujay

      was (Author: sujay.chauhan):
    Hi 

We are seeing the same issue and it is holding us up from moving to production as out production servers would run out of disk space.

This is in regards to a client that tries to use axis2. We have a folder structure

projectFolder
      --otherFolders
      --axis2
          --conf
                --axis2.xml
           --modules
                 --rampart1.3.mar


our axis2.xml file contains the global module <module ref="rampart"/>
In our client code, we make use of the fileSytemConfigurator to configure the client stub before making the call to our service.

Every time we are calling the service, files are added to the TEMP folder (see below)

C:\TEMP\_axis2>dir
 Volume in drive C has no label.
 Volume Serial Number is 0CE7-7F35

 Directory of C:\TEMP\_axis2

07/16/2008  08:36 AM    <DIR>          .
07/16/2008  08:36 AM    <DIR>          ..
07/16/2008  08:36 AM             2,704 axis2473rampart-1.3.mar
               1 File(s)          2,704 bytes
               2 Dir(s)  103,722,340,352 bytes free

The same issue is being duplicated on our prod servers which are not windows based but linux based. the files get put in /tmp/_axis2 folder.

Any advice on if there is a workaround for this?

Thanks,
Sujay
  
> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Priority: Blocker
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609556#action_12609556 ] 

Davanum Srinivas commented on AXIS2-3883:
-----------------------------------------

Does this happen only when java2 security is on or is this with java2 security off?

thanks,
dims

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Priority: Blocker
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Assigned: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Deepal Jayasinghe reassigned AXIS2-3883:
----------------------------------------

    Assignee: Nandana Mihindukulasooriya

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Blocker
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-3883) file handles not being closed after successful call to webservice

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675771#action_12675771 ] 

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

have you tried in the extracted form?
i.e. you can extract the rampart.mar and put it as a folder under modules directory

i.e modules       
         rampart
               META-INF
                    module.xml
                <other classes>

> file handles not being closed after successful call to webservice
> -----------------------------------------------------------------
>
>                 Key: AXIS2-3883
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3883
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows server 2003 (also Windows XP), axis 2.1.3, Websphere 6.1
>            Reporter: LEE
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Blocker
>             Fix For: 1.5
>
>         Attachments: TempFileManager.java
>
>
> We have been regularly experiencing the following problem when trying to call an axis 2 webservice:
> Stack Dump = java.util.zip.ZipException: Too many open files D:\ibm\profiles\AppSrv02\....\xercesImpl-2.8.1.jar
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:238)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:268)
> 	at com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405)
> 	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379)
> 	at com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474)
> 	at com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916)
> 	at com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913)
> 	at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(AccessController.java:192)
> 	at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown Source)
> 	at javax.xml.parsers.FactoryFinder.find(Unknown Source)
> 	at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151)
> 	at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194)
> 	at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
> 	at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> 	
> On closer inspection of the server we noticed that there are a great number of files in the Windows/Temp directory with names such as C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar,
> C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc.
> The main concern (other than disk space is gradually being taken up) is that all these files still have open file handles. This is a major problem for us as each time a call is made to a webservice more of these files eventually resulting in the application failing due to "too many open files" error.

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