• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Datasource lookup fails after 2 successive send to queue - WAS 5.x, DB2 7.x

 
Sam Gehouse
Ranch Hand
Posts: 281
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is a messaging application using Messaging Driven Bean, DB2 7.x deployed in WebSphere 5.1.1.3. When the messages are received by Message Driven bean, certain messages are sent to a queue and some other messages are persisted to database, based on business logic.

If 2 SUCCESSIVE messages are sent to queue, datasource lookup throws exception. However, a combination of sendToQueue-datasourceLookUp-sendToQueue-datasourceLookUp-sendToQueue-datasourceLookUp does NOT throw this exception. Only 2 successive sendToQueue before a datasource lookUp throws this exception. In other words, this exception is thrown only in scenario like:

sendToQueue-sendToQueue-datasourceLookUp

This is apparently a bug in WebSphere. I am using WebSphere 5.1.1.3 and DB2 7.x and datasource to lookup database.

Exception StackTrace:

J2CA0036E: An exception occurred while invoking method setDataSourceProperties on com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource
resource myDataSource : java.lang.reflect.InvocationTargetException null at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)null at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)null at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)null at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)null at java.lang.reflect.Method.invoke(Method.java:391)null at com.ibm.ejs.j2c.J2CXAResourceFactory.createMCFEntry(J2CXAResourceFactory.java:375)null at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1420)null at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1208)null at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:314)null at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:873)null at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:680)null at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1712)null at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1567)null at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1480)null at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1187)null at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1067)null at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)null at javax.naming.InitialContext.lookup(InitialContext.java:361)null at ....
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35279
384
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sam,
I'm moving this to our IBM forum as it sounds like it has more to do with WebSphere than JDBC.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic