PM62434: jax-ws-catalog.xml is not used and a parseCatalog exception is seen in the trace.

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• The following error might be seen due to an IOException not
  being caught: ServiceDescri 1
  org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl
  createCatalogManager ServiceDescriptionImpl caught exception
  from parseCatalog
  
  This will cause catalogManger to return as null as seen below:
  CatalogURIRes 1 org.apache.axis2.jaxws.util.CatalogURIResolver
  <init> init: catalogManager :null
  
  This in-turn will cause jax-ws-catalog.xml to not be used.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using JAX-WS web services            *
  ****************************************************************
  * PROBLEM DESCRIPTION: jax-ws-catalog.xml is not used and a    *
  *                      parseCatalog exception is seen in the   *
  *                      trace.                                  *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack containing this APAR     *
  ****************************************************************
  The following error might be seen due to an IOException not
  being caught in parseCatalogFile() method in the Catalog class
  in the xml-resolver-1.2 jar:
  ServiceDescri 1
  org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl
  createCatalogManager ServiceDescriptionImpl caught exception
  from parseCatalog
  This in-turn caused jax-ws-catalog.xml to not be used.
  

Problem conclusion

• The previous code was only catching a FileNotFoundException,
  instead of all types of IOException. This caused catalogManger
  to return as null as seen below:
  CatalogURIRes 1 org.apache.axis2.jaxws.util.CatalogURIResolver
  <init> init: catalogManager :null
  All IOExceptions are now caught.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 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 is sysrouted FROM one or more of the following:

• 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

• R800 PSY

     UP