Fixes are available
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as new function.
Error description
With Message Listener Ports it was possible to configure the Listener Port to stop if a number of failures where hit with the MDB. This was missing from the SIBus Resource Adapter for SIBus MDBs and caused problems for migrating customers. The SIBus Resource Adapter will now indicate when it believes the MDB should be stopped.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of Message Driven Beans with * * WebSphere Application Server V6. * * In particular, users of JMS Message * * Driven Beans using the default * * messaging provider. * **************************************************************** * PROBLEM DESCRIPTION: There is no way to stop and start a * * specific Message Endpoint other than * * to stop and start the application that * * contains the Message Driven Bean. * * * * There is also currently no way to * * distinguish between a general problem * * with a default messaging provider JMS * * Message Driven Bean that will occur * * for every invocation and a problem * * with just certain messages sent to * * that Message Driven Bean. * **************************************************************** * RECOMMENDATION: * **************************************************************** A user should have a finer grain ability to stop and start a Message Endpoint for a deployed Message Driven Bean. Also, a user should be notified if any general problem with a default messaging provider JMS Message Driven Bean causes good messages to be sent to the exception destination.
Problem conclusion
This APAR introduces the J2CMessageEndpoint MBean which can be used to pause (stop) and resume (start) a specific J2C Message Endpoint. The methods on this MBean are as follows: /** * Deactivate this MessageEndpoint. * @exception IllegalStateException whenever the MessageEndpoint is * already deactivated or stopped. * @exception ResourceException whenever the MessageEndpoint fails to * deactivate. */ public void pause() throws IllegalStateException, ResourceException; /** * Activate this MessageEndpoint. * @exception IllegalStateException whenever the MessageEndpoint is * already activated or stopped. * @exception ResourceException whenever the MessageEndpoint fails to * activate. */ public void resume() throws IllegalStateException, ResourceException; /** * Determine whether this MessageEndpoint is stopped, activated, or * deactivated. * @return an integer representing the MessageEndpoint status: * 1 (activated), 2 (deactivated), or 3 (stopped). */ public int getStatus(); /** * Determine the run-time activation properties of this MessageEndpoint. * @return a comma-delimited list of JMS properties for this MessageEndpoint * @exception IllegalStateException whenever the MessageEndpoint is stopped. */ public String getActivationProperties() throws IllegalStateException; This APAR also introduces the following message to inform a user that a general problem with a default messaging provided Message Driven Driven bean appears to be causing good messages to be delivered to an exception destination: CWSIV0605W: The Message Endpoint {0} that was listening to the destination {1} should be deactivated as the the maximum number of sequential failures was reached. The user can then use the above message as an indicator to pasue (stop) the J2CMessageEndpoint (as outputted by insert {0} ) as there is a general problem with the MDB. A new property is available on the activation specification for the default messaging provider - 'maxSequentialMessageFailure'. This can be provided by the user to indicate how many messages must sequentially hit the max failed deliveries value (and hence are delivered to the exception destination) before the new CWSIV0605W message is generated. This property will only be available for new activation specifications in profiles created after this APAR has been applied. By default the value of this property is -1, and the CWSIV0605W will never be generated. To configure this property in the Administration Console select: Resources -> Resource Adapters -> J2C activation specifications in the left navigation. Click on the default messaging provider activation specification in the list. The "Provider" column will contain "SIB JMS Resource Adapter". Click "J2C activation specification custom properties".
Temporary fix
Comments
APAR Information
APAR number
PK49507
Reported component name
PLAT MSG COM
Reported component ID
620400101
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-07-23
Closed date
2007-10-09
Last modified date
2008-06-20
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
620400101
Applicable component levels
R100 PSY
UP
Document Information
Modified date:
29 December 2021