com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI was processing a object. Root exception is : Attempted to use a 5.0 DataSource outside of a 2.3 servlet

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via coderanch.com by Unknown author, 1 year ago
Exception occurred while the JNDI was processing a object. Root exception is : Attempted to use a 5.0 DataSource outside of a 2.3 servlet
via coderanch.com by Unknown author, 1 year ago
Exception occurred while the JNDI was processing a object. Root exception is : Attempted to use a 5.0 DataSource outside of a 2.3 servlet
via Google Groups by sonu, 2 years ago
Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is java.lang.Exception: Attempted to use a 5.0 DataSource outside of a 2.3 servlet
com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI was processing a object. Root exception is : Attempted to use a 5.0 DataSource outside of a 2.3 servlet
at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.validServlet(ConnectionFactoryBuilderImpl.java:1109)
at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getCMConfigData(ConnectionFactoryBuilderImpl.java:730)
at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:330)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:874)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:681)
at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1969)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1824)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1737)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1444)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at org.exolab.castor.jdo.engine.DatabaseRegistry.loadDatabase(DatabaseRegistry.java:313)
at org.exolab.castor.jdo.JDO.getDatabase(JDO.java:571)
at com.infra.persist.CastorTransactionFactory.createTransaction(CastorTransactionFactory.java:83)
at com.infra.persist.CastorTransactionFactory.getTransaction(CastorTransactionFactory.java:77)
at com.util.TransactionHandler.openTransaction(TransactionHandler.java:34)
at com.actionmanager.NumberSearchAction.execute(NumberSearchAction.java:58)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.