Issue With MQ Transport In Weblogic 12.2.1.3.0
(Doc ID 2730770.1)
Last updated on MAY 15, 2023
Applies to:
Oracle Service Bus - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.3.0 version, OSB Transports
Issue with MQ Transport in Weblogic 12.2.1.3.0
<WLS_OSB1> <[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <[severity-value: 32] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > < >
The MQ Connection pool size details -
MQ Connection Pool Size
10
MQ Connection Timeout
1800
MQ Connection Max Wait
3000
ERROR
-----------------------
[2020-10-23T02:16:53.599-05:00] [WLS_OSB2] [NOTIFICATION] []
[oracle.osb.debug.mqconnection] [tid: [ACTIVE].ExecuteThread: '30' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: <WLS Kernel>] [ecid:
407e936d-e498-453e-83a7-9b4907bfb6c2-00257fe3,0] [partition-name: DOMAIN]
[tenant-name: GLOBAL] java.util.NoSuchElementException: Timeout waiting for
idle object[[
at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.
java:1134)
at
com.bea.wli.sb.resources.mqconnection.MQConnectionPool.borrowObject(MQConnecti
onPool.java:70)
at
com.bea.wli.sb.resources.mqconnection.MQConnectionContext.getQueueManagerConne
ction(MQConnectionContext.java:133)
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot perform their daily activities
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |