PK78256: JAX-RPC WEB SERVICES APPLICATIONS DO NOT FUNCTION CORRECTLY WHEN INSTALLED USING A NON-DEFAULT APPLICATION NAME

Fixes are available

APAR status

Closed as program error.

Error description

JAX-RPC applications that are installed using a non-default
application name are installed correctly, but fail to start
properly.  The same application will install and start
correctly when installed using the default application name.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server V7.0           *
*                  administrators who install JAX-RPC web      *
*                  services applications                       *
****************************************************************
* PROBLEM DESCRIPTION: JAX-RPC web service applications        *
*                      installed with a non-default name do    *
*                      not start correctly.                    *
****************************************************************
* RECOMMENDATION:  Apply a fix pack that contains this APAR.   *
****************************************************************
JAX-RPC applications that are installed using a non-default
application name are installed correctly, but fail to start
properly.  An error similar to the following will occur:

[1/7/09 12:45:29:801 EST] 00000012 WSServerImpl  E
WSWS1002E: An error occurred while processing the
Web services deployment descriptor for module:
SOABenchWeb.war with error: java.lang.
NullPointerException
at com.ibm.ws.classloader.CompoundClassLoader.
loadClass(CompoundClassLoader.java:449)
at java.lang.ClassLoader.loadClass(ClassLoader.
java:609)
at com.ibm.ws.webservices.component.WSServerImpl.
setupWsddPort(WSServerImpl.java:1150)
at com.ibm.ws.webservices.component.WSServerImpl.
warMetaDataCreated(WSServerImpl.java:2089)
at com.ibm.ws.webservices.component.WSServerImpl.
metaDataCreated(WSServerImpl.java:633)
at com.ibm.ws.runtime.component.MetaDataMgrImpl.
fireMetaDataCreated(MetaDataMgrImpl.java:189)
at com.ibm.ws.webcontainer.metadata.WebMetaDataFactory.
createMetaData(WebMetaDataFactory.java:205)

The same application will install and start correctly when
installed using the default application name.

Problem conclusion

JAX-RPC web services applications installed with a non-default
(user-supplied) name were not fully processed by the web
services runtime. This caused a failure during the start-up of
the application.

JAX-RPC web services applications with non-default names are
now correctly processed by the web services runtime and start
correctly.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.3.  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
PK78256
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-01-07
Closed date
2009-02-02
Last modified date
2009-02-02

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:
25 October 2021

Tips

PK78256: JAX-RPC WEB SERVICES APPLICATIONS DO NOT FUNCTION CORRECTLY WHEN INSTALLED USING A NON-DEFAULT APPLICATION NAME

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?