PI61894: AN MDB APP FAILS TO START AN ACTIVATION ERROR, BUT THE ACTIVATIO N SPEC STARTS AND TRIES TO CONSUME MESSAGES

Fixes are available

APAR status

Closed as program error.

Error description

Recreate was performed using an App containing an MDB which
injects a startup EJB that is coded to fail in the
@PostConstruct.  The application is reported as having failed in

Application fails to start:
Trace: 2016/04/14 15:50:54.583 02 t=9ACCF0 c=UNK key=P8 tag=
(13007004)
SourceId: com.ibm.ws.runtime.component.DeployedApplicationImpl
ExtendedMessage: BBOO0221W: WSVR0206E: Module,
SimpleMDBTesterEJB.jar, of application,
XXX_simplemdbtester.ear/deployments/XXX_simplemdbtester,
failed to start

The Adjunct Region logs indicate that the activation spec is act

Trace: 2016/04/14 15:50:53.966 02 t=9B55B0 c=UNK key=P8 tag=
(13007004)
SourceId: com.ibm.ejs.j2c.ActivationSpecWrapperImpl
ExtendedMessage: J2CA0523I: The Message Endpoint for
ActivationSpec test/jms/actspec/TESTQUEUE_MDB
(com.ibm.mq.connector.inbound.ActivationSpecImpl) and MDB
Application
XXX_simplemdbtester#SimpleMDBTesterEJB.jar#TestMessageConsumer
is activated.

In this state, the activation specification continues mark messa
processed.

Local fix

To stop the loop try to:
A) Pause the activation spec (when CPU wasn't pegged and
preventing the ability to do so)
B) Stop the application, even though the app status shows it is
stopped already (and again assuming the CPU usage doesn't
prevent you from doing it).  This resulted in errors about the
app already being stopped, but proceeds to deactivate the
activation spec afterward.
C) Change the app to a no-start status and restart the server

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users of       *
*                  WebSphere MQ Activation Specifications on   *
*                  z/OS                                        *
****************************************************************
* PROBLEM DESCRIPTION: Activation Specification loops trying   *
*                      to                                      *
*                      consume messages for which it has no    *
*                      active consumer in the servant region.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If a Message Driven Bean driven by an activation specification
fails to activate in one of the servant regions the
MessageReferenceHandler in the control region adjunct process is
not informed of the failure and the throttle size is not
adjusted accordingly.  If there is a single servant regions, or
the MDB fails to activate in all servant regions, then the
control region adjunct process will continue to loop, marking
messages and attempting to deliver them to consumers in the
servant regions which do not exist.  This consumes processing
resources unnecessarily and will delay other application servers
configured to consume the messages from doing so.

Problem conclusion

A new mechanism for setting the throttle size of the
MessageReferenceHandler in the control region adjunct has been
provided that directly bases the multiplier used to calculate
the throttle size on the number of active consumers in the
servant regions.  This mechanism is optional and non-default.

A new WebSphere variable
com.ibm.ws.wmqra.ThrottleOnActiveConsumerCount must be set to a
value of true at the desired scope to select the new mechanism.
Alternatively a JVM system property of the same name and value
may be used though this must be specified for both the servant
regions and the control region adjunct.  Changes to these
values
are not dynamic and require a server restart to take effect.

APAR PI61894 is currently targeted for inclusion in Fix Packs
8.5.5.11 and 9.0.0.1 of WebSphere Application Server.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

In addition, please refer to URL:
http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack PTF information.

Temporary fix

Comments

APAR Information

APAR number
PI61894
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-05-04
Closed date
2016-09-13
Last modified date
2016-09-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 FOR Z
Fixed component ID
5655I3500

Applicable component levels

R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI61894: AN MDB APP FAILS TO START AN ACTIVATION ERROR, BUT THE ACTIVATIO N SPEC STARTS AND TRIES TO CONSUME MESSAGES

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

R850 PSY

Document Information

Share your feedback

Need support?