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

Solutions on the web

via Oracle Community by 666705, 1 year ago
[Root exception is javax.naming.NameNotFoundExcept ion: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unres olved:'TXDataSource' ; remaining name '']; Link Remaining Name: 'com.bea.wlpi.TX DataSource']
javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.TXDataSource. Resolved: 'com.bea.wlpi' Unresolved:'TXDataSource' ; remaining name '']; Link Remaining Name: 'com.bea.wlpi.TXDataSource'] at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.getConfiguredPlugins(PluginManagerCfgImpl.java:749) at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.initializePlugins(PluginManagerCfgImpl.java:873) at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.init(PluginManagerCfgImpl.java:80) at com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl.init(PluginManagerCfgBean_gebmxi_EOImpl.java:1300) at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:153) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:254) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864) at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)