Loading...

XML

Word

Printable

Affects:

Release Notes
Workaround Description:

Hide

Only create your Service object once, and create it using a locally stored WSDL (including any external resources).

Show
Only create your Service object once, and create it using a locally stored WSDL (including any external resources).
Release Note Text:

Hide
An issue was identified with the creation of temporary files which could result in inconsistencies in a load-balanced environment, also OutOfMemory errors in cases where millions of temporary files were created. The previous method added a random number to each temporary file's name but this meant naming was not consistent across restarting or rebooting an instance, also instances in a load-balanced environment. The new method uses an MD5 hash to uniquely identify each file, avoiding the issues resulting from the previous method.

Show
An issue was identified with the creation of temporary files which could result in inconsistencies in a load-balanced environment, also OutOfMemory errors in cases where millions of temporary files were created. The previous method added a random number to each temporary file's name but this meant naming was not consistent across restarting or rebooting an instance, also instances in a load-balanced environment. The new method uses an MD5 hash to uniquely identify each file, avoiding the issues resulting from the previous method.
Release Note 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

incorporates

JBPAPP-8018 WSDL files under the data/wsdl directory increases for every time JBoss is re-started

is related to

JBPAPP-10625 Cannot deploy two WS with same serviceName but different endpointInterface, targetNamespace and portName

relates to

JBPAPP-9860 JBossWS Native stack performance issues in load test