PK80182: JAX-WS RUNTIME IS NOT ABLE TO DETECT HANDLER CONFIGURATION FILE

Fixes are available

APAR status

Closed as program error.

Error description

JAX-WS runtime might not be able to detect its handler
configuration file on Web Services consumer.
.
For example, if you specify the location of the handler
configuration as a relative path from the annotated file, such
as:
.
@HandlerChain(file="myhandler.xml")
.
this exception might be thrown:
.
org.apache.axis2.jaxws.ExceptionFactory
createWebServiceException
Create Exception: javax.xml.ws.WebServiceException: The
@HandlerChain configuration file myhandler.xml in the class
yourClass/YourService could not be loaded.
  at
org.apache.axis2.jaxws.ExceptionFactory.createWebServiceExceptio
n(ExceptionFactory.java:178)
  at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:79)
  at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:125)
  at
org.apache.axis2.jaxws.description.impl.DescriptionUtils.openHan
dlerConfigStream(DescriptionUtils.java:340)
  at
org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.g
etHandlerChain(ServiceDescriptionImpl.java:1482)
  at
org.apache.axis2.jaxws.handler.HandlerResolverImpl.resolveHandle
rs(HandlerResolverImpl.java:138)
  at
org.apache.axis2.jaxws.handler.HandlerResolverImpl.getHandlerCha
in(HandlerResolverImpl.java:77)
  at
org.apache.axis2.jaxws.handler.HandlerResolverImpl.getHandlerCha
in(HandlerResolverImpl.java:44)
  at
org.apache.axis2.jaxws.BindingProvider.initialize(BindingProvide
r.java:95)
  at
org.apache.axis2.jaxws.BindingProvider.<init>(BindingProvider.ja
va:53)
  at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.<init>(JAX
WSProxyHandler.java:95)
  at
org.apache.axis2.jaxws.spi.ServiceDelegate.getPort(ServiceDelega
te.java:254)
  at javax.xml.ws.Service.getPort(Service.java:94)
  ...

Local fix

```
N/A.
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  Feature Pack for Web Services that use      *
*                  JAX-WS handlers.                            *
****************************************************************
* PROBLEM DESCRIPTION: The file specified in the               *
*                      @HandlerChain annotation might not be   *
*                      found.                                  *
****************************************************************
* RECOMMENDATION:  Install a Fix Pack which contains this APAR.*
****************************************************************
The @HandlerChain annotation contains a reference to a
configuration file describing the handlers.  In some
situations, this web service engine is not able to find this
file.  The following exception may be reported:

org.apache.axis2.jaxws.ExceptionFactory
createWebServiceException
Create Exception: javax.xml.ws.WebServiceException: The
@HandlerChain configuration file myHandler.xml in the class
yourClass/YourService could not be loaded.
at
org.apache.axis2.jaxws.ExceptionFactory.createWebServiceExceptio
n(ExceptionFactory.java:178)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:79)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:125)
at
org.apache.axis2.jaxws.description.impl.DescriptionUtils.openHan
dlerConfigStream(DescriptionUtils.java:340)
at
org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.g
etHandlerChain(ServiceDescriptionImpl.java:1482)
at
org.apache.axis2.jaxws.handler.HandlerResolverImpl.resolveHandle
rs(HandlerResolverImpl.java:138)
at
org.apache.axis2.jaxws.handler.HandlerResolverImpl.getHandlerCha
in(HandlerResolverImpl.java:77)
at
org.apache.axis2.jaxws.handler.HandlerResolverImpl.getHandlerCha
in(HandlerResolverImpl.java:44)

Problem conclusion

The webservice engine code is updated to use an alternative
search technique to find the file if the first attempt to find
the file fails.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.25 and 7.0.0.5.  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
PK80182
Reported component name
WEBSERVIC FEATU
Reported component ID
5724J0850
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-02-06
Closed date
2009-03-12
Last modified date
2009-04-07

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
WEBSERVIC FEATU
Fixed component ID
5724J0850

Applicable component levels

R610 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 December 2021

Tips

PK80182: JAX-WS RUNTIME IS NOT ABLE TO DETECT HANDLER CONFIGURATION FILE

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

R610 PSY

Document Information

Share your feedback

Need support?