PK76004: FIXES TO THE SERVICE INTEGRATION BUS RUNTIME

Fixes are available

APAR status

Closed as program error.

Error description

Fixes to the runtime operation of the default messaging
provider for WebSphere Application Server

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  in WebSphere Application Server 7.0         *
****************************************************************
* PROBLEM DESCRIPTION: Errors thrown from the default          *
*                      messaging provider at runtime.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using a foreign bus connection between two service
integration buses, if the delivery of a message to its target
destination in the foreign bus fails the following FFDC may be
generated and resolving the reason for the failure to deliver
the message may not re-start the flow of messages to the
foreign bus. A re-start of the messaging engines that own the
link will resolve the problem.

FFDC Exception:java.lang.NullPointerException
SourceId:com.ibm.ws.sib.processor.io.MPIO.receiveMessage
ProbeId:1:217:1.30
        at
com.ibm.ws.sib.processor.impl.PtoPInputHandler.checkTargetAbleTo
AcceptOrExceptionMessage(PtoPInputHandler.java:3439)

When using Web Services Notification (  WS-N ) to query
the value of TopicExpression using JAX-WS and a default
namespace, a fault was returned to the client, with
faultstring set to java.lang.StringIndexOutOfBoundsException

When using Web Services Notification ( WS-N ) to query the
value of TerminationTime using JAX-WS on a publisher
registration that does not expire, a fault was returned to the
client, with faultstring set to
java.lang.IllegalArgumentException: WSWS3382E: Error: An
unqualified namespace cannot have a prefix.  Prefix is xsi.

The following two warning messages:
CWSIP0553W: The destination <destination name>, localized at
<messaging engine name> has reached its message depth high
threshold.
and:
CWSIP0554W: The destination <destination name>, localized at
<messaging engine name> has reached its message depth low
threshold.
are logged in error when an application connected to messaging
engine A consumes a message from a destination on messaging
engine B. The warning messages appear in the SystemOut.log of
the application server hosting messaging engine A every time a
message is consumed from a destination on messaging engine B.
These warning messages can be ignored because they should not
have been generated.

When a consuming application is connected to a pre-V7
messaging engine and consumes messages from a queue point (or
subscription) located on a V7 messaging engine the following
FFDC may be seen:
FFDC Exception:java.lang.ArrayIndexOutOfBoundsException
SourceId:com.ibm.ws.sib.processor.io.MPIO.receiveMessage
ProbeId:1:217:1.30
java.lang.ArrayIndexOutOfBoundsException: Array index out of
range: 0
    at
com.ibm.ws.sib.processor.impl.AOStream.processDecisionInternal(A
OStream.java:1967)
    at
com.ibm.ws.sib.processor.impl.AOStream.processReject(AOStream.ja
va:1822)
    at
com.ibm.ws.sib.processor.impl.AnycastOutputHandler.handleControl
Message(AnycastOutputHandler.java:1151)
    at
com.ibm.ws.sib.processor.io.RemoteMessageReceiver.processControl
Message(RemoteMessageReceiver.java:572)
    at
com.ibm.ws.sib.processor.io.RemoteMessageReceiver.receiveMessage
(RemoteMessageReceiver.java:355)
    at
com.ibm.ws.sib.processor.io.MPIO.receiveMessage(MPIO.java:199)
    at
com.ibm.ws.sib.comms.server.mesupport.METransportReceiveListener
.rcvMessage(METransportReceiveListener.java:749)
    at
com.ibm.ws.sib.comms.server.mesupport.METransportReceiveListener
.dataReceived(METransportReceiveListener.java:251)
    at
com.ibm.ws.sib.jfapchannel.impl.rldispatcher.ConversationReceive
ListenerDataReceivedInvocation.invoke(ConversationReceiveListene
rDataReceivedInvocation.java:195)
    at
com.ibm.ws.sib.jfapchannel.impl.rldispatcher.ReceiveListenerDisp
atchQueue.run(ReceiveListenerDispatchQueue.java:526)
    at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527)

and the message will be in "Remote locked" state on the V7
queue point meaning that it cannot be consumed by another
consumer. The message can be unlocked by going to the
corresponding 'known remote queue point' and cancelling the
request that has it locked.

Web Services Notification ( WS-N ) subscriptions are not
visible immediately in the Administration Console if the
subscription uses a dynamic topic space; they are visible if a
permanent topic space is used.

However the SIB subscriptions are visible in the
Administration Console, for both the dynamic and permanent
topic space creation.

The "Message affinity across queue points" option on a default
messaging JMS Queue does not apply when sending messages to a
queue in a foreign service integration bus.

If a default messaging JMS Queue has the "Message affinity
across queue points" option selected and messages are sent to
a service integration bus destination in a foreign service
integration bus, they may not be delivered to a target queue
point. Or if the "Prefer queue points local to this link's
messaging engine" option is unchecked on the service
integration bus link, that setting may be ignored and messages
may only be delivered to queue points local to the link's
messaging engine.

In a messaging system with two service integration buses
linked together with a matching service integration bus link
defined in both buses, if the service integration bus link is
deleted from one bus and then recreated with the same name
without doing the same in the other bus it is possible for the
following error to be seen:

FFDC
Exception:com.ibm.websphere.sib.exception.SIErrorException
SourceId:com.ibm.ws.cluster.selection.CallbackWhenAvailableThrea
d ProbeId:208
Reporter:com.ibm.ws.cluster.selection.CallbackWhenAvailableThrea
d$1@<hash code>
com.ibm.websphere.sib.exception.SIErrorException: CWSIP0005E:
An internal messaging error occurred <UUID> in
com.ibm.ws.sib.processor.proxyhandler.Neighbours, 1:939:1.112
       at
com.ibm.ws.sib.processor.proxyhandler.Neighbours.removeNeighbour
(Neighbours.java:934)
       at
com.ibm.ws.sib.processor.proxyhandler.MultiMEProxyHandler.delete
NeighbourForced(MultiMEProxyHandler.java:1032)
       at
com.ibm.ws.sib.processor.impl.destination.LinkState.updateLocali
sationSet(LinkState.java:454)
       at
com.ibm.ws.sib.processor.impl.LinkHandler.updateLocalisationSet(
LinkHandler.java:420)
       at
com.ibm.ws.sib.processor.impl.LinkChangeListener.linkChange(Link
ChangeListener.java:174)
       at
com.ibm.ws.sib.trm.wlm.server.Manager$LCL_WLMCallback.callback(M
anager.java:1382)
       at
com.ibm.ws.cluster.selection.CallbackWhenAvailableThread$1.run(C
allbackWhenAvailableThread.java:190)
       at
com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager
Impl.java:4238)
       at
com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextM
anagerImpl.java:4416)
       at
com.ibm.ws.cluster.selection.CallbackWhenAvailableThread.run(Cal
lbackWhenAvailableThread.java:224)
       at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527)


When attempting to view messages on a queue point a "Website
cannot display this page" message may be seen and the
following ffdc may be generated:
FFDC Exception:com.ibm.ws.sib.msgstore.NotInMessageStore
SourceId:com.ibm.ws.sib.processor.runtime.QueuedMessage.QueuedMe
ssage ProbeId:1:128:1.65
Reporter:com.ibm.ws.sib.processor.runtime.QueuedMessage@109e109e
com.ibm.ws.sib.msgstore.NotInMessageStore
    at
com.ibm.ws.sib.msgstore.AbstractItem.getID(AbstractItem.java:428
)
    at
com.ibm.ws.sib.processor.runtime.QueuedMessage.<init>(QueuedMess
age.java:116)
    at
com.ibm.ws.sib.processor.impl.store.items.MessageItem.createCont
rolAdapter(MessageItem.java:2431)
    at
com.ibm.ws.sib.processor.impl.store.items.MessageItem.getControl
Adapter(MessageItem.java:2397)
    at
com.ibm.ws.sib.processor.runtime.LocalQueuePoint.getQueuedMessag
eIterator(LocalQueuePoint.java:248)
    at
com.ibm.ws.sib.admin.impl.JsQueuePoint.getQueuedMessages(JsQueue
Point.java:270)
    ...
    Caused by: java.lang.NullPointerException
    at
com.ibm.ws.sib.admin.impl.SIBMBeanResultFactory.createSIBQueuedM
essage(SIBMBeanResultFactory.java:464)
    at
com.ibm.ws.sib.admin.impl.JsQueuePoint.getQueuedMessages(JsQueue
Point.java:282)
    ...


A consumer that is connected to messaging engine A but is
consuming messages from a destination on messaging engine B
where the JMS Queue that points at the destination has
"Messages on all queue points are visible" set may stop
consuming messages due to an internal deadlock.


WebSphere MQ V7 Publish/Subscribe does not emulate the
SYSTEM.BROKER.ADMIN.QUEUE. This causes problems as this queue
is used at application server start-up by WebSphere MQ link
publish/subscribe broker profiles in order to check that
subscriptions have been correctly cleaned up.

The fact that the queue no longer exists results in the queue
manager returning an error when it can't send to the queue.
This error can result in the channel between WebSphere
Application Server and WebSphere MQ going down repeatedly
particularly if there is no default dead letter queue defined.


It is not possible to view web service or port destinations
from the admin console.
Web service and port destinations are created whenever Service
integration bus inbound/outbound services,
inbound/outbound ports and v6.1 WS-notification
services/service points are created. The symptom
of this problem is an "Error 500" message displayed when
attempting view a web service or port destination.


If the activation specification used by an MDB has the
'Automatically stop endpoints on repeated message failure'
option set, administrative security is enabled and the
'Sequential failed message threshold' is reached, an attempt
will be made to pause the endpoint so that the MDB does not
try and consume any more messages. No more messages will be
consumed and a CWSIV0902W message stating that the enpoint has
been paused will appear in the SystemOut log, but the MDB will
not show as being paused in the administrative console and a
CWSIV0903W warning message will be seen in the SystemOut log
saying that the attempt to pause the endpoint failed.

Problem conclusion

This APAR fixes these problems in the runtime of the default
messaging provider.

Temporary fix

Comments

APAR Information

APAR number
PK76004
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2008-11-19
Closed date
2009-02-27
Last modified date
2009-02-27

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
PLAT MSG COM
Fixed component ID
620800101

Applicable component levels

R300 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:
23 October 2021

Tips

PK76004: FIXES TO THE SERVICE INTEGRATION BUS RUNTIME

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

R300 PSY

Document Information

Share your feedback

Need support?