-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: EAP_EWP 5.1.2
-
Fix Version/s: EAP_EWP 5.2.0
-
Component/s: Web Services
-
Labels:None
-
Affects:Release Notes
-
Workaround Description:
-
Release Notes Text:
-
Release Notes Docs Status:Documented as Resolved Issue
-
Docs QE Status:NEW
Currently JBossWS creates temporary files using File.createTempFile(). This has several issues:
- In a load balanced environment, imported WSDL names aren't consistent between nodes.
- There is a situation where a web service client can fill up the classloader's black list with temporary file names if the Service object is regenerated millions of times, causing OutOfMemoryErrors.
- blocks
-
JBPAPP-9494 [JBossWS] Release and upgrade JBossWS Native for EAP 5.2.0
-
- Closed
-
- incorporates
-
JBPAPP-8018 WSDL files under the data/wsdl directory increases for every time JBoss is re-started
-
- Closed
-
- is related to
-
JBPAPP-10625 Cannot deploy two WS with same serviceName but different endpointInterface, targetNamespace and portName
-
- Resolved
-
- relates to
-
JBPAPP-9860 JBossWS Native stack performance issues in load test
-
- Closed
-