PM08283: Asynchronous JAX-WS applications may fail after migrating from V6.1 to a later release

Fixes are available

APAR status

Closed as program error.

Error description

When migrating a Deployment Manager profile from WebSphere
Application Server V6.1 (with the Feature Pack for Web
Services) to V7, a JAX-WS asynchronous application may
experience a timeout.

Here is an example error that may occur:
[1/22/10 15:17:09:570 CST] 00000038 WebContainer  E
SRVE0255E: A WebGroup/Virtual
Host to handle /IBM_WS_SYS_RESPONSESERVLET/
WSSampleClientSei:SampleClientSei.war/serv
ices/EchoService.EchoServicePort has not been defined.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0       *
*                  administrators migrating JAX-WS             *
*                  applications from V6.1.                     *
****************************************************************
* PROBLEM DESCRIPTION: Asynchronous JAX-WS applications        *
*                      may fail after migrating only a         *
*                      deployment manager profile from V6.1    *
*                      to V7.                                  *
****************************************************************
* RECOMMENDATION:  Install a fixpack that includes this APAR   *
****************************************************************
When migrating a Deployment Manager profile from WebSphere
Application Server V6.1 (with the Feature Pack for Web
Services) to V7, a JAX-WS asynchronous application may
experience a timeout.

Here is an example error that may occur:
[1/22/10 15:17:09:570 CST] 00000038 WebContainer  E
SRVE0255E: A WebGroup/Virtual
Host to handle /IBM_WS_SYS_RESPONSESERVLET/
WSSampleClientSei:SampleClientSei.war/serv
ices/EchoService.EchoServicePort has not been defined.


The WebSpere Application Server's profile migration feature
fails to properly migrate the IBMASYNCRSP application to the
new v7 profile.

The IBMASYNCRSP is an internal application that is required for
proper functioning of web service applications that make use
asynchronous behavior.

Problem conclusion

The IBMASYNCRSP application was never being installed to the
new v7 Deployment Manager profile when only the Deployment
Manager profile was under migration.

The Deployment Manager migration code has been corrected to
properly migrate the application by invoking the install
action in the case when only the Deployment Manager profile is
being migrated

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.11.  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
PM08283
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
2010-02-22
Closed date
2010-03-23
Last modified date
2010-03-23

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
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

PM08283: Asynchronous JAX-WS applications may fail after migrating from V6.1 to a later release

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R700 PSY

Document Information

Share your feedback

Need support?