PK86161: PERFORMANCE DEGRADATION OVER TIME FOR AN APPLICATION POLLING A QUEUE WITH RECEIVE CALLS WITH A 1SECOND TIMEOUT

Fixes are available

APAR status

Closed as program error.

Error description

Performance degrades over time when a client does a receive
call multiple times without receiving a message. The client is
connecting to a messaging engine that does defined the
destination and so an internal request is sent over.

Local fix

Remove the alarm when the request timeout is set to -1.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for IBM WebSphere Application Server        *
*                  Version 6.1 or Version 7.0                  *
****************************************************************
* PROBLEM DESCRIPTION: When using a long running JMS           *
*                      connection to one messaging engine      *
*                      (ME) to poll a destination hosted on    *
*                      another ME in the bus, performance      *
*                      might degrade over time.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This issue affects an application that establishes a JMS
connection and consumer session, then performs multiple
'receive' method calls with a timeout in a loop - to poll for
messages.
An example application that might be affected by this issue is
an Message Driven POJO (MDP) within the Spring Framework.

The issue only affects applications that connect over a
network to an ME in the bus, which does not host the queue
point (or durable subscription) the application is
consuming from.
Performance degrades over time and the number of Message
Requests on the Known Remote Queue Point will be high.
The problem is seen when the application performs a large
number of receive calls that time-out without receiving a
message.

The problem is caused because the ME the application connects
to creates a new request for messages from the ME that owns
the destination each time the application issues a receive
call, and does not cancel the request when the application's
receive call times out. This results in a build-up of requests
when there are no messages available for consumption.

Problem conclusion

The fix for this APAR changes the code so that an application
creating a long-running JMS connection and message consumer
(over a network to an ME that does not host the destination)
does not cause new a message request to be issued by the ME
each time a receive call is made when no message is available.
This prevents performance from being degraded by the build-up
of unsatisifed message requests.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.27 and 7.0.0.7.  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
PK86161
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-07
Closed date
2009-06-09
Last modified date
2009-06-09

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
620600101

Applicable component levels

R200 PSY
UP

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

Document Information

Modified date:
28 December 2021

Tips

PK86161: PERFORMANCE DEGRADATION OVER TIME FOR AN APPLICATION POLLING A QUEUE WITH RECEIVE CALLS WITH A 1SECOND TIMEOUT

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

R200 PSY

Document Information

Share your feedback

Need support?