PK83856: MEDIATIONS STOP PROCESSING MESSAGES AFTER AN FFDC WITH PROBEID 145 FROM MEDIATIONTHREADPOOL.EXECUTE

Fixes are available

APAR status

Closed as program error.

Error description

The FFDCs shows that a ThreadPoolQueueIsFullException
exception was thrown to method
com.ibm.ws.sib.mediation.runtime.MediationThreadPool.execute.

The probe id is 145, and the FFDC contained the following
variables that showed the ThreadPoolQueueIsFullException was
thrown to the mediation code while there were no threads
active in the thread pool.
_maxPoolsize = 35
_activeThreads = 0
_threadCount = 35

There were no hung threads shown in javacores, or other errors
logged, but the mediation stopped processing messages.

Local fix

To minimise the chance of this problem re-occurring, I suggest
tuning
the mediation thread pool to disable grow-as-needed.
The mediation threadpool is configured using scripting, as
described
in the following information center section:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/

com.ibm.websphere.pmc.nd.multiplatform.doc/tasks/tjp0070_.html
Here are is sample JACL that would configure a threadpool with a
maximum size of 35, and grow-as-needed disabled.
set messagingEngine [$AdminTask listSIBEngines { -bus

EDI.GATEWAY.PROD.EdiProdCell0.Bus }]
set threadPool [$AdminConfig create ThreadPool $messagingEngine
     {{name EDI.GATEWAY.PROD.mediationThreadPool}}
mediationThreadPool]
$AdminConfig modify $threadPool {{maximumSize 35} {isGrowable
false}}
$AdminConfig showall $threadPool

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for IBM WebSphere Application Server        *
*                  Version 6.1 or Version 7.0 using Service    *
*                  Integration Bus medations                   *
****************************************************************
* PROBLEM DESCRIPTION: Mediation hosted by a messaging         *
*                      engine stop processing messages,        *
*                      after an FFDC with probe id 145 from    *
*                      MediationThreadPool.execute is logged   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The issue occurred due to incorrect handling within throttling
code in the mediation thread pool, of an exception thrown by
the underlying application server thread pool indicating that
the queue of items being submitted to the pool was full.
This resulted in the mediation thread pool stopping processing
of messages, assuming that one of the threads in the pool
would resume processing when it completed. However, in this
case there were no threads active in the thread pool so
processing never resumed.

Problem conclusion

The exception handling within the throttling code of
the mediation thread pool has been updated to prevent it
pausing processing unless there is an active thread to resume
processing at a later point.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.27 and 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
PK83856
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-04-01
Closed date
2009-04-30
Last modified date
2009-04-30

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:
29 December 2021

Tips

PK83856: MEDIATIONS STOP PROCESSING MESSAGES AFTER AN FFDC WITH PROBEID 145 FROM MEDIATIONTHREADPOOL.EXECUTE

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?