PK70746: TIBCO PROPERTIES ARE NOT PASSED THROUGH WHEN SET ON THE GENERIC JMS PROVIDER

Fixes are available

APAR status

Closed as program error.

Error description

When using message-driven beans (MDBs) with WebSphere
Application Server Version 6.1.0.x  and TIBCO ems with SSL as
the JMS provider, the Custom property does not allow Tibco
properties to be passed through when set on the generic JMS
provider. The properties seem to be in use but when url comes
back and it tries to connect it appears that properties are
not set.

the following errors occur


[8/7/08 10:42:32:112 EDT] 00000020 MDBListenerIm W   WMSG0019E:
Unable
to start MDB Listener FileTest, JMSDestination jms/JGTestSSL :
javax.jms.JMSException: Failed to create queue connection
 at
com.ibm.ejs.jms.JMSCMUtils.mapToJMSException(JMSCMUtils.java:141
)
 at
com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle.createQueueConne
ction(JM
SQueueConnectionFactoryHandle.java:90)
 at
com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBList
enerImpl
.java:412)
 at
com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListen
erImpl.j
ava:727)
 at
com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.j
ava:650)
 at
com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListene
rManager
Impl.java:634)
 at
com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.jav
a:227)
 at
com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplication
MDBs(MDB
ListenerManagerImpl.java:872)
 at
com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDB
Listener
ManagerImpl.java:830)
 at
com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(Me
ssageLis
tenerImpl.java:188)
 at
com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(App
lication
MgrImpl.java:1253)
 at
..
..
.
com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.r
un(Appli
cationMgrImpl.java:2120)
 at
com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializ
er.run(W
sComponentImpl.java:342)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
---- Begin backtrace for Nested Throwables
javax.resource.spi.ResourceAllocationException:
ConnectionFactory not
found in JNDI
 at
com.ibm.ejs.j2c.FreePool.createManagedConnectionWithMCWrapper(Fr
eePool.j
ava:2102)
 at
com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java
:1543)
 at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2215)
 at
com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionMa
nager.ja
va:896)
 at
...
..
.

 at
com.ibm.ejs.jms.GenericJMSManagedQueueConnectionFactory.createMa
nagedCon
nection(GenericJMSManagedQueueConnectionFactory.java:91)
 at
com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnect
ion(JMSM
anagedConnectionFactory.java:584)
 at
com.ibm.ejs.j2c.FreePool.createManagedConnectionWithMCWrapper(Fr
eePool.j
ava:1811)
 ... 22 more
Caused by: javax.jms.JMSException: Failed to connect to the
server at
tcp://xxxxx.xxx.nxxx.net:40643
 at
com.tibco.tibjms.TibjmsxLinkTcp._doHandshake(TibjmsxLinkTcp.java
:898)
 at
com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:916)
 at
com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:
1274)
 at
com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:4
100)
 at
com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnect
ion.java
:36)
 at
com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:20
0)
 at
com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.j
ava:253)
 at
com.tibco.tibjms.TibjmsQueueConnectionFactory.createQueueConnect
ion(Tibj
msQueueConnectionFactory.java:87)
 at
com.tibco.tibjms.naming.TibjmsContext$Messenger.request(TibjmsCo
ntext.ja
va:325)
 at
com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:
655)
 ... 31 more
---- Begin backtrace for Nested Throwables

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  v6.1 using a Generic Java Message Service   *
*                  (JMS) Provider                              *
****************************************************************
* PROBLEM DESCRIPTION: Only certain custom properties set on   *
*                      the Generic JMS Provider were allowed   *
*                      to be passed through to the external    *
*                      JMS provider. This would cause          *
*                      problems as certain providers           *
*                      required custom properties to be set    *
*                      on a per Generic JMS Provider scope.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
By only allowing certain custom properties that have a
specific package name to be passed to the external provider
meant that some configurations could not be achieved without
setting these properties globally rather than per generic JMS
provider.

Problem conclusion

This APAR solves to problem by allowing any custom properties
that are set on the Generic JMS Provider to be passed to the
external JMS provider. No validation of these properties is
done on the Application Server side.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.21.  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
PK70746
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-08-19
Closed date
2008-08-29
Last modified date
2008-08-29

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 APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z 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

PK70746: TIBCO PROPERTIES ARE NOT PASSED THROUGH WHEN SET ON THE GENERIC JMS PROVIDER

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?