1 Reply Latest reply on Aug 12, 2012 6:52 PM by anjhawar - oracle

    WebLogic, TimesTen Issue


      We have issues with TimesTen and Integrated Weblogic used in JDeveloper.

      Root cause of ServletException.
      oracle.jbo.DMLException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-27200
      at oracle.jbo.server.DBTransactionImpl.lookupDataSource(DBTransactionImpl.java:1476)
      at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:332)
      at oracle.jbo.common.ampool.DefaultConnectionStrategy.connect(DefaultConnectionStrategy.java:203)
      at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolConnect(ApplicationPoolMessageHandler.java:592)
      at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolMessage(ApplicationPoolMessageHandler.java:422)
      Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.TimesTenDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/TimesTenDS'
      at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
      at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
      at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
      at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
      at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
      at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
      <Aug 3, 2012 11:13:08 AM PDT> <Alert> <Diagnostics> <BEA-320016> <Creating diagnostic image in /root/.jdeveloper/system11. with a lockout minute period of 1.>
      <Logger> <error> ServletContainerAdapter manager not initialized correctly.
      <Aug 3, 2012 11:42:34 AM PDT> <Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
      <Aug 3, 2012 11:43:04 AM PDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=JdbcDatasourcesJDBCDataSourceConfigTabPage&JdbcDatasourcesJDBCDataSourceConfigPortlethandle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTimesTenDS%2CType%3Dweblogic.j2ee.descriptor.wl.JDBCDataSourceBean%2CParent%3D%5BDefaultDomain%5D%2FJDBCSystemResources%5BTimesTenDS%5D%2CPath%3DJDBCResource%5BTimesTenDS%5D%22%29.>
      <Aug 3, 2012 11:43:40 AM PDT> <Warning> <JDBC> <BEA-001110> <No test table set up for pool "TimesTenDS". Connections will not be tested.>
      <Aug 3, 2012 11:43:53 AM PDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=JdbcDatasourcesJDBCDataSourceMonitorTestingPage.>

      We've configured in Weblogic to use JNDI: jdbc/TimesTen; we also configured the same in ADF BC layer to use JNDI: jbdc/TimesTen

      What are we doing wrong ?
      Any help is appreciated
        • 1. Re: WebLogic, TimesTen Issue
          anjhawar - oracle
          I think what you have tried is:

          a. Created a data source named "TimesTenDS" with the JNDI named "jdbc/TimesTenDS".
          b. In the application while looking up for the connection, you might be doing a initial context look on the DS named "jdbc/TimesTenDS".

          Is that correct?

          If thats the case can you try the following:

          a. Check whether the DS is properly targeted to an active WLS instance and whether you are able to monitor the connection pool of the same. Also try to enable the test table and test connection of reserve properties of the same to see in case you are facing any issue will requesting for a connection for recreating a connection pool.

          b. Check whether you are getting the JNDI name "jdbc/TimesTenDS" in the JNDI tree of the target managed node, if not then there is any issue with the configuration, else things are fine till now.

          c. While doing the look-up you might be giving the connection_url or by default the application might be doing a look-up on the local JVM (to which the application is targeted to) and the DS might not be there thus you can cross check the connection_url too.