PM56170: Improve performance of JAXBContext creation when a package list cannot be used.

Fixes are available

APAR status

Closed as program error.

Error description

The optimum path for creating a JAXBContext is for all
the packages in the context to have either an ObjectFactory
class or jaxb.index file.  If that were the case, we would not
search for classes.

Here is an example trace line logged when we encounter a
package without one of these classes:

[11/10/11 13:46:34:401 PST] 0000003c JAXBUtils     1
org.apache.axis2.jaxws.message.databinding.JAXBUtils
createJAXBContextValue Package com.acompany.apackage does not
contain an  ObjectFactory or package-info class.  Searching
for JAXB classes

So, the most performant JAXBContext creation is to ensure
your packages in the context have an ObjectFactory class or
jaxb.index file (jaxb.index file support requries PM59472).

Once we find a package without either of the mentioned
classes, we enter the path of searching for potential JAXB
classes within the classpath which is more time consuming.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All developers of IBM WebSphere Application *
*                  Server JAX-WS applications.                 *
****************************************************************
* PROBLEM DESCRIPTION: Improve performance of JAXBContext      *
*                      creation when                           *
*                      getAllClassesFromPackage() is invoked.  *
****************************************************************
* RECOMMENDATION:  Apply PM59472 and use jaxb.index files      *
*                  when packages are included that do not      *
*                  have ObjectFactory classes and avoid the    *
*                  searching for classes.                      *
****************************************************************
When a package is identified as not having an ObjectFactory
class we are forced to search the classpath for potential JAXB
classes.  This is not as efficient as using the packages to
create the JAXBContext.

Problem conclusion

As stated, it is recommended to install PM59472 and use the
jaxb.index file.  This APAR was an earlier and a less
efficient improvement.

With this APAR, the results of a package search can now be
cached as a softreference and later requests to search that
package will be avoided.

This is controlled with the following property:
com.ibm.ws.websvcs.getJAXBContext.cacheClassList

The default value of the JVM proeprty is false.
To enable caching of the class search results, set the
property value to true.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.25 and 8.0.0.4.  Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM56170
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-17
Closed date
2012-04-13
Last modified date
2012-04-13

APAR is sysrouted FROM one or more of the following:

PM54432
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM56170: Improve performance of JAXBContext creation when a package list cannot be used.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?