WLS 10.3: JAX-WS::CONTENTION/PERFORMANCE ISSUE IN LOGICALMESSAGE.GETPAYLOAD()
(Doc ID 1065643.1)
Last updated on OCTOBER 15, 2020
Applies to:Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.
Customer on trying to build JAX-WS services which use a 'LogicalHandler' which in turn calls LogicalContext.getPayload(). When load testing, it is evident from stack traces that there is a bottleneck in LogicalContext.getPayload() while calling 'com/sun/org/apache/xalan/internal/xsltc/trax/SAX2DOM.createDocument()' method.
This is a known JDK bug (6660724) which is resolved in JDK1.6u14 and Jrockit 27.6.5, however weblogic makes use of its own parser factory which circumvents the JDK provided resolution (weblogic uses its own jaxp parser factory wrapper which fails the instanceof check in the SAX2Dom static initialzer)
How to overcome this?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document