PK89421: INTERMITENT EXCEPTION FROM WS-RELIABLEMESSAGING SAYING A SERVICE DOES NOT BELONG TO A SERVICE GROUP

Fixes are available

APAR status

Closed as program error.

Error description

With WS-Reliable (WS-RM) Messaging enabled, intermittently a
WS-RM exception occurs when sending a MakeConnection indicating
a service is not valid and does not belong to a particular
service group.
For example:

[17/06/09 17:24:51:951 BST] 00000034 PollingManage 1
org.apache.sandesha2.polling.PollingManager internalRun
Exception

org.apache.sandesha2.SandeshaException: The PingService.WSRM
service, which is not valid, does not belong to the
PingService.WSRM1245255880701 service group.
at
org.apache.sandesha2.util.SandeshaUtil.createNewRelatedMessageCo
ntext(SandeshaUtil.java:465)
at
org.apache.sandesha2.util.RMMsgCreator.createMakeConnectionMessa
ge(RMMsgCreator.java:601)
at
org.apache.sandesha2.polling.PollingManager.pollForSequence(Poll
ingManager.java:255)
at
org.apache.sandesha2.polling.PollingManager.pollRMSSide(PollingM
anager.java:183)
at
org.apache.sandesha2.polling.PollingManager.internalRun(PollingM
anager.java:117)
at
org.apache.sandesha2.workers.SandeshaThread.run(SandeshaThread.j
ava:317)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 Java API for XML-Based Web      *
*                  Services (JAX-WS)and Web Services Reliable  *
*                  Messaging (WS-RM).                          *
****************************************************************
* PROBLEM DESCRIPTION: Getting an intermittent exception       *
*                      using WS-RM saying a service is not     *
*                      valid under a service group.            *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR      *
****************************************************************
With WS-Reliable Messaging enabled, intermittently there is an
exception from WS-RM when sending a MakeConnection.  The
exception indicates a particular service is not valid and does
not belong to a particular service group.  For example:

[17/06/09 17:24:51:951 BST] 00000034 PollingManage 1
org.apache.sandesha2.polling.PollingManager internalRun
Exception

org.apache.sandesha2.SandeshaException: The PingService.WSRM
service, which is not valid, does not belong to the
PingService.WSRM1245255880701 service group.
 at
org.apache.sandesha2.util.SandeshaUtil.createNewRelatedMessageCo
ntext(SandeshaUtil.java:465)
 at
org.apache.sandesha2.util.RMMsgCreator.createMakeConnectionMessa
ge(RMMsgCreator.java:601)
 at
org.apache.sandesha2.polling.PollingManager.pollForSequence(Poll
ingManager.java:255)
 at
org.apache.sandesha2.polling.PollingManager.pollRMSSide(PollingM
anager.java:183)
 at
org.apache.sandesha2.polling.PollingManager.internalRun(PollingM
anager.java:117)
 at
org.apache.sandesha2.workers.SandeshaThread.run(SandeshaThread.j
ava:317)

Problem conclusion

The issue is that during deserialization of the MessageContext
for use by WS-RM, it is being connected to the wrong
AxisService (PingService.WSRM in the above example) based on
the ServiceQName and Port name instead of searching all the
current AxisServices for a matching service name as well
(PingService.WSRM1245255880701 in the above example).  When
WS-RM attempts to use the MessageContext with the incorrect
AxisService attached, the exception is thrown.

The Web Services engine is corrected to deserialize the
MessageContext and correctly associate it with the correct
AxisService.

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
PK89421
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-06-19
Closed date
2009-07-15
Last modified date
2009-07-15

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

PK89421: INTERMITENT EXCEPTION FROM WS-RELIABLEMESSAGING SAYING A SERVICE DOES NOT BELONG TO A SERVICE GROUP

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?