PK85979: WS-N APPLICATION WITH WS-RM ENABLED CANNOT SEND MESSAGES AFTER SERVER RESTART

Fixes are available

APAR status

Closed as program error.

Error description

My WS-N application is unable to send messages after I shutdown
and then restart the WebSphere Application Server. This only
happens if I've enabled WS-RM.

After restarting the server, I see the following errors in the
log file:

(snippet of log file errors)
[4/3/09 12:46:23:363 BST] 00000038 ActivateUtils 3
org.apache.axis2.context.externalize.ActivateUtils findService
ObjectStateUtils:findService():
[org.apache.axis2.description.AxisService]
[OutboundService.OutboundPort1238759027444]  returning  [null]
...
[4/3/09 12:46:23:364 BST] 00000038 ActivateUtils 3
org.apache.axis2.context.externalize.ActivateUtils
findServiceGroup ObjectStateUtils:findServiceGroup():
[org.apache.axis2.description.AxisServiceGroup]
[OutboundService.OutboundPort1238759027444]  returning  [null]
...
[4/3/09 12:46:23:366 BST] 00000038 PersistentSto 3
Rebuilding MessageContext as no AxisService
[4/3/09 12:46:23:366 BST] 00000038 PersistentSto 3   Recovered
wsdl null :
{http://p5weft05.hursley.ibm.com:9081/WSNPushConsumer_WAS70_Web/
PushNotificationConsumer?10}OutboundService :
javax.xml.ws.Service :
{http://p5weft05.hursley.ibm.com:9081/WSNPushConsumer_WAS70_Web/
PushNotificationConsumer?10}OutboundPort
...
[4/3/09 12:46:25:708 BST] 00000038 MessageContex 3
org.apache.axis2.context.MessageContext readExternal
[MessageContext:
logID=urn:uuid:AF96B82B16CBEB20FE1238759060684]:readExternal():
 message context object created for  [MessageContext:
logID=urn:uuid:AF96B82B16CBEB20FE1238759060684]
...
[4/3/09 12:46:25:708 BST] 00000038 MessageContex 3
org.apache.axis2.context.MessageContext readExternal
[MessageContext:
logID=urn:uuid:AF96B82B16CBEB20FE1238759060684]:readExternal():
 message context object created for  [MessageContext:
logID=urn:uuid:AF96B82B16CBEB20FE1238759060684]
[4/3/09 12:46:25:709 BST] 00000038 ActivateUtils 3
org.apache.axis2.context.externalize.ActivateUtils findService
ObjectStateUtils:findService():
[org.apache.axis2.description.AxisService]
[OutboundService.OutboundPort1238759027444]  returning  [null]
[4/3/09 12:46:25:709 BST] 00000038 ActivateUtils 3
org.apache.axis2.context.externalize.ActivateUtils
findServiceGroup ObjectStateUtils:findServiceGroup():
[org.apache.axis2.description.AxisServiceGroup]
[OutboundService.OutboundPort1238759027444]  returning  [null]

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server web service support using both       *
*                  WS-Notification (WS-N) and                  *
*                  WS-ReliableMessaging (WS-RM)                *
****************************************************************
* PROBLEM DESCRIPTION: WS-N applications using WS-RM fail      *
*                      after server restart.                   *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR      *
****************************************************************
When a web service application is using both WS-Notification
and WS-ReliableMessaging, errors occur after the server is
restarted and the WS-N messages in the WS-RM store can not be
sent.

Problem conclusion

The problem is that the WS-N messages were persisted with
dynamically created names on the metadata, and when the
messages are read back in after a server restart, the
dynamically created names on the new metadata do not match
what was previously persisted.

The web services runtime is corrected so that additional
information is persisted to allow the messages to be sent
using the correct metadata object created after a server
restart.

The fix for this APAR is currently targeted for inclusion in
fix pack 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
PK85979
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-05-05
Closed date
2009-05-13
Last modified date
2009-05-13

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

PK85979: WS-N APPLICATION WITH WS-RM ENABLED CANNOT SEND MESSAGES AFTER SERVER RESTART

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?