PK92025: An UnknownHostException error occurs when a JAX-WS thinclient accesses the WSDL using XML Catalog

Fixes are available

APAR status

Closed as program error.

Error description

The user has the following scenario:
1) A JAX-WS application running on a thinclient.
  2) The application is using XML Catalog to allow the
application to access local versions of the wsdl and xml files.
  3) The remote location of the wsdl file was not accessible.

The following error is reported:

avax.wsdl.WSDLException: WSDLException:
faultCode=WSDL4JWrapper : : java.net.UnknownHostException:
mycomp.org
 at
org.apache.axis2.jaxws.util.WSDL4JWrapper.commonPartsURLConstruc
tor(WSDL4JWrapper.java:234)
 at
org.apache.axis2.jaxws.util.WSDL4JWrapper.<init>(WSDL4JWrapper.j
ava:156)
 at
org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.s
etupWsdlDefinition(ServiceDescriptionImpl.java:1044)
 at
org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<
init>(ServiceDescriptionImpl.java:230)


The error seems to indicate that the XML Catalog feature was
not used to locate the wsdl file.  In this case, the error
occurred because the remote location was not accessible.  If
the remote location was accessible, the user would have
experienced a slight performance degradation when the Web
Service runtime accesses the remote wsdl file.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0       *
*                  administators of JAX-WS applications.       *
****************************************************************
* PROBLEM DESCRIPTION: A JAX-WS XML application running on a   *
*                      thinclient failed with an               *
*                      UnknownHostException error due to an    *
*                      XML Catalog problem.                    *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR      *
****************************************************************
Despite the presence of jax-ws-catalog.xml file in the proper
location in a client application jar, JAX-WS XMLCatalog
lookups are not performed during thinclient application
invocation.  The file is effectively ignored.

Problem conclusion

The root of the problem is the JAX-WS Web Service engine was
not using the XML Catalog feature to locate the wsdl in this
particular scenario.

The JAX-WS Web Service runtime has been fixed to find the
jax-ws-catalog.xml file and perform XML Catalog lookups upon
client service invocation.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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
PK92025
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-22
Closed date
2009-08-05
Last modified date
2009-08-05

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

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK92025: An UnknownHostException error occurs when a JAX-WS thinclient accesses the WSDL using XML Catalog

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

Document Information

Share your feedback

Need support?