Tomcat 5.5 Connection Pooling problem

Hi,
I am trying to setup JDBC connection pooling in Tomcat 5.5 using DB2 database and IBM RAD 7.0 IDE. Although The setup described in JNDI Resources HOW-TO(http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html) for creating JDBC Datasources did work, I would like to work with real connection pooling, which means not declaring datasources into the /META-INF/context.xml file of each web app but having them as <GlobalNamingResources> into /conf/server.xml and accessing them through <ResourceLink> references from /conf/context.xml (or /conf/catalina/localhost/ROOT.xml). However I am stuck with Exception javax.naming.NameNotFoundException: Name jdbc is not bound in this Context. Even if I add an: <resource-env-ref>
          <description>
          </description>
          <resource-env-ref-name>jdbc/DB2T</resource-env-ref-name>
          <resource-env-ref-type>javax.sql.DataSource</resource-env-ref-type>
     </resource-env-ref> record in my /WEB-INF/web.xml I get a javax.naming.NamingException: Cannot create resource instance Exception.
Does anyone have an idea how to resolve this?
Here are my configurations:
-----------------/conf/server.xml-------------------
<Server port="8005" shutdown="SHUTDOWN">
  <!-- Global JNDI resources -->
  <GlobalNamingResources>
   <Resource name="jdbc/DB2T" auth="Container"
   type="javax.sql.DataSource" removeAbandoned="true"
  factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory"
   removeAbandonedTimeout="30" maxActive="100"
   maxIdle="30" maxWait="10000" username="id"
   password="pass"
   driverClassName="com.ibm.db2.jcc.DB2Driver"
   url="jdbc:db2://<ip-addrr>:<port>/dbname"/>
  </GlobalNamingResources>------------------/conf/context.xml----------------------
<!-- The contents of this file will be loaded for each web application -->
<Context>
    <!-- Default set of monitored resources -->
    <WatchedResource>WEB-INF/web.xml</WatchedResource>
    <WatchedResource>META-INF/context.xml</WatchedResource>
<ResourceLink name="jdbc/DB2T" global="jdbc/DB2T"  type="javax.sql.DataSource"/>
</Context>I also try to get the resource with java code like this:
DataSource ds;
InitialContext DSCtx = new InitialContext();
ds = (DataSource) DSCtx.lookup("java:/comp/env/jdbc/DB2T"); PS: When I start the tomcat and hit http://localhost:8080 I can't get the default page although every web app I run loads without problems. Do you think this has a relation with the above problem?

hi,
I think your datasource configuration is incorrect
see this http://tomcat.apache.org/tomcat-5.0-doc/config/globalresources.html
and this
http://forum.java.sun.com/thread.jspa?threadID=610046&messageID=3348979
<GlobalNamingResources ...>
  <ResourceParams name="jdbc/EmployeeDB">
    <parameter>
      <name>driverClassName</name>
      <value>org.hsql.jdbcDriver</value>
    </parameter>
    <parameter>
      <name>driverName</name>
      </value>jdbc:HypersonicSQL:database</value>
    </parameter>
    <parameter>
      <name>user</name>
      <value>dbusername</value>
    </parameter>
    <parameter>
      <name>password</name>
      <value>dbpassword</value>
    </parameter>
  </ResourceParams>
</GlobalNamingResources>be sure that your jdbc driver library (.jar), commons-pool-xx.jar and commons-dbcp-xx.jar are under TOMCAT_DIR/common/lib/
hope that helps

Similar Messages

  • Oracle.DataAccess 2.112.1.0 - Connection Pool Problem

    Hi,
    Oracle.DataAccess 2.112.1.0 is having connection pool problem. The no. of TCP connections to Oracle database keep increasing untill the server's session run out of limit. My application created connections, use them, close them, and dispose them properly. When using previous Oracle.DataAccess 2.111.6.20, the no. of TCP connections do not increase.
    My database connection string has "Min Pool Size = 3 and Max Pool Size = 150".
    With 2.111.6.20 version, TCP connection stays at 3.
    With 2.112.1.0, TCP connection keep increasing for every 5 minutes. I've tried to disable Self Tuning, but still can't prevent the connections from increasing.
    Later today, I downloaded Oracle.DataAccess 2.112.1.2 (it comes with ODAC 11.2.0.1.2) and test again, the problem is resolved... no more connection increases... but.... it is only for 32 bit Windows.
    Unfortunately, there is no Oracle.DataAccess 2.112.1.2 for 64 bit Windows Server 2008.
    May I know how can i resolve this problem on 64bit Window installed with Oracle 11g R2 client, which comes with Oracle.DataAccess 2.112.1.0, which has serious problems...(according to this 11.2 ODP.NET causing test runner failures )
    Many thanks for your time and answers!
    Edited by: user1502907 on 04-Sep-2010 23:01

    Hi,
    The only thing that jumps out within your problem description is that connections are being increased every 5 minutes. Are you sure its every 5 minutes and not 3 minutes which is the timing interval used by the Connection Pool facility to perform connection pool maintenance. If this occurs even when the application is idle then you could be running into the following known issue filed against 11.2.0.1.0 and fixed in 11.2.0.1.2.
    Bug 9711600 - CONNECTIONS INCREASE BEYOND MAX POOL SIZE EVERY 3 MINUTE
    This is specific to using the option CommandBehavior.CloseConnection when calling execute reader. Are you using this option and then also closing the connection in code before the datareader object is closed, if so you may be hitting this bug. You can also generate an ODP trace at level 15 of the behavior and if you see negative pool counts, that is also a diagnostic that points to this bug.
    This is fixed in 11.2.0.1.0 Patch 3 or later for x64. If you have support, I recommend you open a service request to verify if this is your issue and if a patch set may help you.
    Regards
    Jenny B.

  • Serious connection pool problem on Tomcat

    Hi,
    We are deploying our JSF creator-made app onto Tomcat 1.5. We set up our JNDI datasource on Tomcat (using the i-net driver ).
    Initially the pages load ok but after a short period of time we are getting these errors:
    Initialization Failure: javax.faces.FacesException: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool exhaustedWe believe that somehow the Creator-generated code is NOT freeing up connections in the connection pool.
    We think that when the afterRenderResponse() methods in the beans call rowset.close() this is NOT returning the connections to the pool. Can someone, hopefully a Sun Engineer confirm that the rowset.close() code in afterRenderResponse() returns the connection behind the rowset to the connection pool.
    Could this be a driver issue? We are using the i-net driver not the DataDirect one, but this should implement the full API.
    This is a very serious problem for us.
    regards,
    john

    do you have any example code you could post? I have a Spring/JSC tutorial on this forum. Just search for Spring and you should find it. It you need something more, I'll try to give you some help...time provided.
    am i
    right in thinking that you use the forms designer to
    lay out your pages and just put your own stuff in the
    bean constructor?Close...but not everything goes in the constructor.
    >
    One thing that may have caused a problem is we have
    just noticed that in one of our most commonly hit
    pages this line:
    dataTable1Model.setDataCacheKey("com.sun.datacache.my_
    page.my_rowset");
    featured the WRONG "my_page" jsp page but the correct
    rowset name "my_rowset". The page DID load correctly
    and run correctly, though. Could this cause problems
    with connection pooling? Anyone?I wouldn't think so, but it depends on how Creator builds the code.

  • Tomcat Connection pooling problem

    I am using Tomcat connection pooling (DBCP) to get the connection from the Database
    It really works great with Oracle, MySQL, Sybase and as well as DB2.
    Recently I tried to integrate apache with tomcat to improve the performance.
    But now the problem is I am unable to load the JDBC Driver its giving me an error message as Cannot load JDBC driver class ?null?
    @ org.apache.commons.dbcp.BasicDataSource.createDataSource ..
    Interseting thing is I am able to get connection through datasource(DBCP) if I use the following URL
    http://localhost:8080/application _name/Hello.jsp
    But I get the error message when I try to get connection through datasource(DBCP)
    as Cannot load JDBC driver class ?null? for this URL
    http://localhost/application_name/Hello.jsp
    Both the URL use same server.xml, httpd.conf,servlet class and jsp pages
    Gurus can you please help me to understand why my application is unable to get the connection when I use this URL http://localhost/application_name/Hello.jsp
    But not with other one
    Please........... Some one help me
    Thanks in Advance
    Maria

    How did you make Tomcat connection pooling(DBCP) working with Oracle?
    I refereced to the "JNDI Datasource HOW-TO" in Jakarta Tomcat. I am using Tomcat 4.18. I can get DataSource object, but when to get connection from dataSource, not any response, It seems freezing.
    I appreciate any reply.
    Johnson Ouyang

  • Oracle connection pool problem (dbcp binded with  jtom)

    Hi,
    my webserver is Tomcat5.0.18, I want to offer the connection pool and transaction management
    in my currently system
    I know in Tomcat5.0 version, we can use the DBCP to offer the database connection pool
    service, to apply the transaction management in my system, I adapt the JTOM
    now, my problem is
    to use DBCP, I setup the datasource factory to be
    org.apache.commons.dbcp.BasicDataSourceFactory, the connection pool is ok, but
    the transaction management offerred by JTOM will failure
    to make the tranaction management of JTOM succeed, I have to setup the datasource factory to be
    org.objectweb.jndi.DataSourceFactory, but the connection pool offerred by Tomcat will failure now
    it seems that these two datasource factory has conflict
    How can I do?, I don't want to use the connection pool offerred in JTOM
    Anyone can help me??
    Thanks in advance

    Hi,
    I don't know the solution for JOTM, but you could try this JTA and its connection pools:
    http://www.atomikos.com ships a JTA that integrates with Tomcat and also provides JDBC connection pooling. There is a GUI control panel so that you don't have to know the XML details for Tomcat's config files.
    Best,
    Guy

  • Connection pooling problem in TopLink with JBoss4.0.3

    Hi All
    I am using JBoss4.0.3SP1 with TopLink-10g(9.0.4.5) and Sybase as database. I am implementing connection pooling of JBoss with Sybase. I have done all the changes in JBoss mapping files.
    Now to enable connection pooling in TopLink I have set the <uses-external-connection-pooling> attribute in sessions.xml file to true and I have added <datasource> attribute corresponding to the datasource defined in JBoss. It is working fine but when I delete the username, password...etc attribute from the sessions.xml then I am not able to get the session from datasource.
    Can anyone tell me what to do or where I am making mistake? Any help on this will be appreciated

    I tried that code also but the project object that I am getting is null which is in this line
    DatabaseLogin login = (DatabaseLogin)mySession.getProject().getLogin();
    mySession is an object of oracle.toplink.sessions.Session interface but when I call this method then it returns me a null object of Project class, so I am getting NullPointerException error. I tried to do this stuff by many ways but I am always getting the NullPointereException in setLogin() method of Session. This is the stackTrace of the error.....
    java.lang.NullPointerException
    at oracle.toplink.publicinterface.Session.setLogin(Session.java:2871)
    at com.test.TestCon.executeQurey(TestCon.java:91)
    at org.apache.jsp.Test_jsp._jspService(org.apache.jsp.Test_jsp:55)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
    at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
    at java.lang.Thread.run(Unknown Source)
    Can you please tell me where I am wrong or any other way to do fix this problem.

  • Connection pool problems

    I�ve launched a site which runs on Tomcat using jsp. The site�s database driven using mysql and java. This includes the use of connection pooling to control database access.
    Problem is the site keeps hanging. The front page is accessible but when any kind of access to the database is required it cant connect and no data is returned.
    Restarting the tomcat context on the hosting server cures the problem for a few hours.
    I�ll elaborate if possible, this is now a live site but obviously is pretty crap because of this.
    I�m led to believe it�s to do with connection pooling but my developer appears to be getting nowhere.
    Any help appreciated.

    Problem is the site keeps hanging. The front page is
    accessible but when any kind of access to the database
    is required it cant connect and no data is returned.
    Restarting the tomcat context on the hosting server
    cures the problem for a few hours.If it works for a while and then starts hanging it could be because the SQL statement objects aren't being closed, connections aren't being returned to the pool etc.

  • Connection Pooling problem in Weblogic Server 6.1

    Hi
    We are using weblogic server 6.1 sp3. The server creates three database connection
    pools (details available in the attached config.xml).
    The database has a regular downtime every day for a few hours. We are running
    the server as a windows service. As per the "RefreshMinutes" property, the server
    should be able to get new fresh connections once the database comes up. But in
    our case it is not doing so. Once the database comes up after its regular downtime:
    -- Sometimes the server does not respond as in we are not able to open the console
    page.
    -- Any client that tries connecting to the database thru the server gets blocked
    and does not respond.
    -- The log file(weblogic.log) does not get updated after some time.
    Can someone suggest why the server is showing such a behaviour??
    Could it be anything related to the DBMS setting or to the local machine's settings
    ? Following is the thread dump after the server stops responding:
    Full thread dump:
    "ListenThread" prio=5 tid=0x14ffb570 nid=0x148c runnable [0x1685f000..0x1685fdbc]
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:468)
         at java.net.ServerSocket.implAccept(ServerSocket.java:243)
         at java.net.ServerSocket.accept(ServerSocket.java:222)
         at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:260)
    "Thread-3" daemon prio=5 tid=0x14fb18b8 nid=0x12d4 waiting on monitor [0x167df000..0x167dfdbc]
         at java.lang.Thread.sleep(Native Method)
         at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "Thread-2" daemon prio=5 tid=0x14f21c68 nid=0xf08 waiting on monitor [0x1679f000..0x1679fdbc]
         at java.lang.Thread.sleep(Native Method)
         at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "Thread-1" daemon prio=5 tid=0x14fb97d8 nid=0xcac waiting on monitor [0x1675f000..0x1675fdbc]
         at java.lang.Thread.sleep(Native Method)
         at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e75a10
    nid=0x13ec waiting on monitor [0x1671f000..0x1671fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e74e58
    nid=0x1434 waiting on monitor [0x166df000..0x166dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e742a0
    nid=0x1154 waiting on monitor [0x1669f000..0x1669fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e72ed0
    nid=0xfe4 waiting on monitor [0x1665f000..0x1665fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e72318
    nid=0x9a4 waiting on monitor [0x1661f000..0x1661fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e717d8 nid=0xf38
    waiting on monitor [0x165df000..0x165dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e70c98 nid=0xf68
    waiting on monitor [0x1659f000..0x1659fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e70158 nid=0x1008
    waiting on monitor [0x1655f000..0x1655fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6f610 nid=0x1204
    waiting on monitor [0x1651f000..0x1651fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6ead0 nid=0xef4
    waiting on monitor [0x164df000..0x164dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6dfa8 nid=0x12bc
    waiting on monitor [0x1649f000..0x1649fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6d5e8 nid=0xf70
    waiting on monitor [0x1645f000..0x1645fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6ccb0 nid=0xf84
    waiting on monitor [0x1641f000..0x1641fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e67510 nid=0x1418
    waiting on monitor [0x163df000..0x163dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e64f60 nid=0x1228
    waiting on monitor [0x1639f000..0x1639fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x14e5c3f0 nid=0xf60 waiting on monitor [0x1635f000..0x1635fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x14e5b908 nid=0xf78 waiting on monitor [0x1631f000..0x1631fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x14e3ebe0 nid=0xfb4 waiting on monitor [0x162df000..0x162dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e35958
    nid=0x9e8 waiting on monitor [0x1629f000..0x1629fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e3ba30
    nid=0x5ac waiting on monitor [0x1625f000..0x1625fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e3af20
    nid=0xdc4 waiting on monitor [0x1621f000..0x1621fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e3a410
    nid=0x11ec waiting on monitor [0x161df000..0x161dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14bfdff0
    nid=0x1078 waiting on monitor [0x1619f000..0x1619fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14bfd4e0
    nid=0x43c waiting on monitor [0x1615f000..0x1615fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e32410
    nid=0xb64 waiting on monitor [0x1611f000..0x1611fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14c4ee68
    nid=0xe30 waiting on monitor [0x160df000..0x160dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14c4ec10
    nid=0x1140 waiting on monitor [0x1609f000..0x1609fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e33b18
    nid=0xfc0 waiting on monitor [0x1605f000..0x1605fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon prio=5 tid=0x14e33968
    nid=0x718 waiting on monitor [0x1601f000..0x1601fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon prio=5 tid=0x14e3c0a0
    nid=0x119c waiting on monitor [0x15fdf000..0x15fdfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x14bfbce0 nid=0xb90 waiting on monitor
    [0x15f9f000..0x15f9fdbc]
         at java.lang.Object.wait(Native Method)
         at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
         at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=5 tid=0x14e39758
    nid=0x11ac waiting on monitor [0x15f5f000..0x15f5fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=5 tid=0x14e38898
    nid=0x1194 waiting on monitor [0x15f1f000..0x15f1fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x14bfc040 nid=0x10a8 waiting on monitor
    [0x15edf000..0x15edfdbc]
         at java.lang.Object.wait(Native Method)
         at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
         at java.lang.Thread.run(Thread.java:484)
    "SpinnerRandomSource" daemon prio=5 tid=0x14e30c40 nid=0x794 waiting on monitor
    [0x15e9f000..0x15e9fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:57)
         at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '29' for queue: 'default'" daemon prio=5 tid=0x14e2fe20 nid=0xee8
    runnable [0x15e5f000..0x15e5fdbc]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:90)
         at oracle.net.ns.Packet.receive(Unknown Source)
         at oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
         at oracle.net.ns.NetInputStream.read(Unknown Source)
         at oracle.net.ns.NetInputStream.read(Unknown Source)
         at oracle.net.ns.NetInputStream.read(Unknown Source)
         at oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java:931)
         at oracle.jdbc.ttc7.MAREngine.unmarshalSB1(MAREngine.java:893)
         at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:369)
         at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
         at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:830)
         at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672)
         at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:572)
         at weblogic.jdbc.pool.Statement.executeQuery(Statement.java:850)
         at tavant.platform.jdbc.JDBCTransaction.executeReadQuery(Unknown Source)
         at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean.invokeSQL(Unknown
    Source)
         at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean_t63yf9_EOImpl.invokeSQL(WebServiceBean_t63yf9_EOImpl.java:456)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.soap.server.servlet.StatelessBeanAdapter.invokeMethod(StatelessBeanAdapter.java:184)
         at weblogic.soap.server.servlet.StatelessBeanAdapter.doPost(StatelessBeanAdapter.java:115)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '28' for queue: 'default'" daemon prio=5 tid=0x14e2f268 nid=0x12f0
    runnable [0x15e1f000..0x15e1fdbc]
         at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
         at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:589)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '27' for queue: 'default'" daemon prio=5 tid=0x14be7af0 nid=0x11c4
    runnable [0x15ddf000..0x15ddfdbc]
         at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
         at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:589)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '26' for queue: 'default'" daemon prio=5 tid=0x14be7748 nid=0x6dc
    waiting for monitor entry [0x15d9f000..0x15d9fdbc]
         at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:681)
         at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:520)
         at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
         at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
         at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
         at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
         at java.sql.DriverManager.getConnection(DriverManager.java:517)
         at java.sql.DriverManager.getConnection(DriverManager.java:199)
         at tavant.platform.jdbc.JDBCTransaction.getConnection(Unknown Source)
         at tavant.platform.jdbc.JDBCTransaction.start(Unknown Source)
         at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean.invokeSQL(Unknown
    Source)
         at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean_t63yf9_EOImpl.invokeSQL(WebServiceBean_t63yf9_EOImpl.java:456)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.soap.server.servlet.StatelessBeanAdapter.invokeMethod(StatelessBeanAdapter.java:184)
         at weblogic.soap.server.servlet.StatelessBeanAdapter.doPost(StatelessBeanAdapter.java:115)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '25' for queue: 'default'" daemon prio=5 tid=0x14be6b90 nid=0x10f4
    waiting for monitor entry [0x15d5f000..0x15d5fdbc]
         at java.sql.DriverManager.println(DriverManager.java:424)
         at java.sql.SQLException.<init>(SQLException.java:44)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333)
         at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:404)
         at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:197)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:270)
         at weblogic.jdbc.common.internal.ConnectionEnv.refresh(ConnectionEnv.java:919)
         at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:885)
         at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
         at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:381)
         at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1125)
         at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
         at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
         at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:69)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '24' for queue: 'default'" daemon prio=5 tid=0x14be5fd8 nid=0x10a4
    waiting on monitor [0x15d1f000..0x15d1fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '23' for queue: 'default'" daemon prio=5 tid=0x14be5420 nid=0x11b0
    waiting on monitor [0x15cdf000..0x15cdfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '22' for queue: 'default'" daemon prio=5 tid=0x14be4868 nid=0x11bc
    waiting for monitor entry [0x15c9f000..0x15c9fdbc]
         at java.sql.DriverManager.println(DriverManager.java:424)
         at java.sql.SQLException.<init>(SQLException.java:44)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
         at oracle.jdbc.driver.OracleConnection.privateCreateStatement(OracleConnection.java:758)
         at oracle.jdbc.driver.OracleConnection.createStatement(OracleConnection.java:712)
         at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:977)
         at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:470)
         at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:381)
         at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1125)
         at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
         at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
         at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:69)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '21' for queue: 'default'" daemon prio=5 tid=0x14be3cb0 nid=0x10e0
    waiting on monitor [0x15c5f000..0x15c5fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '20' for queue: 'default'" daemon prio=5 tid=0x14be30f8 nid=0x620
    waiting on monitor [0x15c1f000..0x15c1fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '19' for queue: 'default'" daemon prio=5 tid=0x14be2540 nid=0x350
    waiting on monitor [0x15bdf000..0x15bdfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '18' for queue: 'default'" daemon prio=5 tid=0x14be1988 nid=0x104c
    waiting on monitor [0x15b9f000..0x15b9fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '17' for queue: 'default'" daemon prio=5 tid=0x14c4db30 nid=0xff0
    waiting on monitor [0x15b5f000..0x15b5fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '16' for queue: 'default'" daemon prio=5 tid=0x14c4cf78 nid=0x1148
    waiting on monitor [0x15b1f000..0x15b1fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '15' for queue: 'default'" daemon prio=5 tid=0x14c4c3c0 nid=0x1118
    waiting on monitor [0x15adf000..0x15adfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x14c4b808 nid=0x684
    waiting on monitor [0x15a9f000..0x15a9fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'default'" daemon prio=5 tid=0x14c4ac50 nid=0xd7c
    waiting on monitor [0x15a5f000..0x15a5fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x14c4a098 nid=0xdb4
    waiting on monitor [0x15a1f000..0x15a1fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=5 tid=0x14c49588 nid=0x114c
    waiting on monitor [0x159df000..0x159dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x14bdf540 nid=0x90c
    waiting on monitor [0x1599f000..0x1599fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=5 tid=0x14bdea00 nid=0x11cc
    waiting on monitor [0x1595f000..0x1595fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=5 tid=0x14bdded8 nid=0x12f8
    waiting on monitor [0x1591f000..0x1591fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=5 tid=0x14ba0420 nid=0x1350
    waiting on monitor [0x158df000..0x158dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x14bfae20 nid=0x11d8
    waiting on monitor [0x1589f000..0x1589fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'default'" daemon prio=5 tid=0x14b9e6a8 nid=0x134c
    waiting on monitor [0x1585f000..0x1585fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'default'" daemon prio=5 tid=0x14b9e430 nid=0x10bc
    waiting on monitor [0x1581f000..0x1581fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=5 tid=0x14bdbc00 nid=0x1090
    waiting on monitor [0x157df000..0x157dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420

    Hi Joseph,
    Thanks for your useful suggestion.
    BTW, I am attaching the config.xml for your
    convenience.
    Please go through and let us know if anything
    to be tuned.
    Regards.
    Kunal
    Joseph Weinstein <[email protected]> wrote:
    >
    >
    Kunal Jain wrote:
    Hi
    We are using weblogic server 6.1 sp3. The server creates three databaseconnection
    pools (details available in the attached config.xml).
    The database has a regular downtime every day for a few hours. We arerunning
    the server as a windows service. As per the "RefreshMinutes" property,the server
    should be able to get new fresh connections once the database comesup. But in
    our case it is not doing so. Once the database comes up after its regulardowntime:
    -- Sometimes the server does not respond as in we are not able toopen the console
    page.
    -- Any client that tries connecting to the database thru the servergets blocked
    and does not respond.
    -- The log file(weblogic.log) does not get updated after some time.
    Can someone suggest why the server is showing such a behaviour??
    Could it be anything related to the DBMS setting or to the local machine'ssettings
    ? Following is the thread dump after the server stops responding:Hi. I do see a problem in the thread dump. The application code is calling
    java.sql.DriverManager
    calls, which are a serious problem in multithreaded applications like
    weblogic, because
    DriverManager calls are all class-synchronized! All JDBC drivers and
    the SQLException constructor
    call DriverManager calls all the time, so a single long-running call
    to DriverManager.getConnection()
    can stop all other JDBC in the whole JVM. One problem you can fix is
    at:
    at tavant.platform.jdbc.JDBCTransaction.getConnection(Unknown Source)
    at tavant.platform.jdbc.JDBCTransaction.start(Unknown Source)
    The getConnection() method should be altered to instantiate a Driver
    object and
    call Driver.connect() directly to make a pool connection, avoiding the
    DriverManager
    call:
    Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    Connection c = d.connect("jdbc:weblogic:pool:" + myPoolName, null );
    Let me know if you can make this application change and whether it fixes
    the
    problem or not.
    I could also help if I could see the config.xml, but you seem to have
    attached the
    startup script.
    Joe Weinstein
    Full thread dump:
    "ListenThread" prio=5 tid=0x14ffb570 nid=0x148c runnable [0x1685f000..0x1685fdbc]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:468)
    at java.net.ServerSocket.implAccept(ServerSocket.java:243)
    at java.net.ServerSocket.accept(ServerSocket.java:222)
    at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:260)
    "Thread-3" daemon prio=5 tid=0x14fb18b8 nid=0x12d4 waiting on monitor[0x167df000..0x167dfdbc]
    at java.lang.Thread.sleep(Native Method)
    at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "Thread-2" daemon prio=5 tid=0x14f21c68 nid=0xf08 waiting on monitor[0x1679f000..0x1679fdbc]
    at java.lang.Thread.sleep(Native Method)
    at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "Thread-1" daemon prio=5 tid=0x14fb97d8 nid=0xcac waiting on monitor[0x1675f000..0x1675fdbc]
    at java.lang.Thread.sleep(Native Method)
    at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e75a10
    nid=0x13ec waiting on monitor [0x1671f000..0x1671fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e74e58
    nid=0x1434 waiting on monitor [0x166df000..0x166dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e742a0
    nid=0x1154 waiting on monitor [0x1669f000..0x1669fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e72ed0
    nid=0xfe4 waiting on monitor [0x1665f000..0x1665fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e72318
    nid=0x9a4 waiting on monitor [0x1661f000..0x1661fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e717d8nid=0xf38
    waiting on monitor [0x165df000..0x165dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e70c98nid=0xf68
    waiting on monitor [0x1659f000..0x1659fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e70158nid=0x1008
    waiting on monitor [0x1655f000..0x1655fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6f610nid=0x1204
    waiting on monitor [0x1651f000..0x1651fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6ead0nid=0xef4
    waiting on monitor [0x164df000..0x164dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6dfa8nid=0x12bc
    waiting on monitor [0x1649f000..0x1649fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6d5e8nid=0xf70
    waiting on monitor [0x1645f000..0x1645fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6ccb0nid=0xf84
    waiting on monitor [0x1641f000..0x1641fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e67510nid=0x1418
    waiting on monitor [0x163df000..0x163dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e64f60nid=0x1228
    waiting on monitor [0x1639f000..0x1639fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemonprio=5
    tid=0x14e5c3f0 nid=0xf60 waiting on monitor [0x1635f000..0x1635fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemonprio=5
    tid=0x14e5b908 nid=0xf78 waiting on monitor [0x1631f000..0x1631fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemonprio=5
    tid=0x14e3ebe0 nid=0xfb4 waiting on monitor [0x162df000..0x162dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e35958
    nid=0x9e8 waiting on monitor [0x1629f000..0x1629fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e3ba30
    nid=0x5ac waiting on monitor [0x1625f000..0x1625fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e3af20
    nid=0xdc4 waiting on monitor [0x1621f000..0x1621fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e3a410
    nid=0x11ec waiting on monitor [0x161df000..0x161dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14bfdff0
    nid=0x1078 waiting on monitor [0x1619f000..0x1619fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14bfd4e0
    nid=0x43c waiting on monitor [0x1615f000..0x1615fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e32410
    nid=0xb64 waiting on monitor [0x1611f000..0x1611fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14c4ee68
    nid=0xe30 waiting on monitor [0x160df000..0x160dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14c4ec10
    nid=0x1140 waiting on monitor [0x1609f000..0x1609fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e33b18
    nid=0xfc0 waiting on monitor [0x1605f000..0x1605fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemonprio=5 tid=0x14e33968
    nid=0x718 waiting on monitor [0x1601f000..0x1601fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemonprio=5 tid=0x14e3c0a0
    nid=0x119c waiting on monitor [0x15fdf000..0x15fdfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x14bfbce0 nid=0xb90 waitingon monitor
    [0x15f9f000..0x15f9fdbc]
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
    at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=5tid=0x14e39758
    nid=0x11ac waiting on monitor [0x15f5f000..0x15f5fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=5tid=0x14e38898
    nid=0x1194 waiting on monitor [0x15f1f000..0x15f1fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x14bfc040 nid=0x10a8 waitingon monitor
    [0x15edf000..0x15edfdbc]
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
    at java.lang.Thread.run(Thread.java:484)
    "SpinnerRandomSource" daemon prio=5 tid=0x14e30c40 nid=0x794 waitingon monitor
    [0x15e9f000..0x15e9fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:57)
    at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '29' for queue: 'default'" daemon prio=5 tid=0x14e2fe20nid=0xee8
    runnable [0x15e5f000..0x15e5fdbc]
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at oracle.net.ns.Packet.receive(Unknown Source)
    at oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
    at oracle.net.ns.NetInputStream.read(Unknown Source)
    at oracle.net.ns.NetInputStream.read(Unknown Source)
    at oracle.net.ns.NetInputStream.read(Unknown Source)
    at oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java:931)
    at oracle.jdbc.ttc7.MAREngine.unmarshalSB1(MAREngine.java:893)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:369)
    at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:830)
    at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672)
    at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:572)
    at weblogic.jdbc.pool.Statement.executeQuery(Statement.java:850)
    at tavant.platform.jdbc.JDBCTransaction.executeReadQuery(UnknownSource)
    at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean.invokeSQL(Unknown
    Source)
    at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean_t63yf9_EOImpl.invokeSQL(WebServiceBean_t63yf9_EOImpl.java:456)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.soap.server.servlet.StatelessBeanAdapter.invokeMethod(StatelessBeanAdapter.java:184)
    at weblogic.soap.server.servlet.StatelessBeanAdapter.doPost(StatelessBeanAdapter.java:115)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '28' for queue: 'default'" daemon prio=5 tid=0x14e2f268nid=0x12f0
    runnable [0x15e1f000..0x15e1fdbc]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:589)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '27' for queue: 'default'" daemon prio=5 tid=0x14be7af0nid=0x11c4
    runnable [0x15ddf000..0x15ddfdbc]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:589)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '26' for queue: 'default'" daemon prio=5 tid=0x14be7748nid=0x6dc
    waiting for monitor entry [0x15d9f000..0x15d9fdbc]
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:681)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:520)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
    at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
    at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
    at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
    at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
    at java.sql.DriverManager.getConnection(DriverManager.java:517)
    at java.sql.DriverManager.getConnection(DriverManager.java:199)
    at tavant.platform.jdbc.JDBCTransaction.getConnection(UnknownSource)
    at tavant.platform.jdbc.JDBCTransaction.start(Unknown Source)
    at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean.invokeSQL(Unknown
    Source)
    at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean_t63yf9_EOImpl.invokeSQL(WebServiceBean_t63yf9_EOImpl.java:456)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.soap.server.servlet.StatelessBeanAdapter.invokeMethod(StatelessBeanAdapter.java:184)
    at weblogic.soap.server.servlet.StatelessBeanAdapter.doPost(StatelessBeanAdapter.java:115)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '25' for queue: 'default'" daemon prio=5 tid=0x14be6b90nid=0x10f4
    waiting for monitor entry [0x15d5f000..0x15d5fdbc]
    at java.sql.DriverManager.println(DriverManager.java:424)
    at java.sql.SQLException.<init>(SQLException.java:44)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333)
    at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:404)
    at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:197)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:270)
    at weblogic.jdbc.common.internal.ConnectionEnv.refresh(ConnectionEnv.java:919)
    at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:885)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
    at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:381)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1125)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:69)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '24' for queue: 'default'" daemon prio=5 tid=0x14be5fd8nid=0x10a4
    waiting on monitor [0x15d1f000..0x15d1fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '23' for queue: 'default'" daemon prio=5 tid=0x14be5420nid=0x11b0
    waiting on monitor [0x15cdf000..0x15cdfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '22' for queue: 'default'" daemon prio=5 tid=0x14be4868nid=0x11bc
    waiting for monitor entry [0x15c9f000..0x15c9fdbc]
    at java.sql.DriverManager.println(DriverManager.java:424)
    at java.sql.SQLException.<init>(SQLException.java:44)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
    at oracle.jdbc.driver.OracleConnection.privateCreateStatement(OracleConnection.java:758)
    at oracle.jdbc.driver.OracleConnection.createStatement(OracleConnection.java:712)
    at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:977)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:470)
    at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:381)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1125)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:69)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '21' for queue: 'default'" daemon prio=5 tid=0x14be3cb0nid=0x10e0
    waiting on monitor [0x15c5f000..0x15c5fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '20' for queue: 'default'" daemon prio=5 tid=0x14be30f8nid=0x620
    waiting on monitor [0x15c1f000..0x15c1fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '19' for queue: 'default'" daemon prio=5 tid=0x14be2540nid=0x350
    waiting on monitor [0x15bdf000..0x15bdfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '18' for queue: 'default'" daemon prio=5 tid=0x14be1988nid=0x104c
    waiting on monitor [0x15b9f000..0x15b9fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '17' for queue: 'default'" daemon prio=5 tid=0x14c4db30nid=0xff0
    waiting on monitor [0x15b5f000..0x15b5fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at webl

  • Multiple connection pools problem

    Hi,
    Here is the problem. We use several connection pools to access differents
    schema of our database. We also have a connection pool
    opened for Weblogic Commerce which connects to the Commerce schema in our
    database. Here is a sample of our weblogic.properties file:
    #========================================================
    # WeblogicCommerce pool and data source
    #========================================================
    weblogic.jdbc.connectionPool.commercePool=\
    url=jdbc:oracle:thin:@careon_dev:1521:careon,\
    driver=oracle.jdbc.driver.OracleDriver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=1,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    testConnsOnReserve=true,\
    props=user=WLCS_TEST;password=WLCS_TEST,\
    testTable=WLCS_IS_ALIVE,\
    refreshMinutes=5
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.commercePool=everyone,
    CareonDev
    weblogic.jdbc.DataSource.weblogic.jdbc.jts.commercePool=commercePool
    #========================================================
    # WeblogicCommerce Document Management pool
    #========================================================
    # This is the pool the beans reference
    weblogic.jdbc.connectionPool.docPool=\
    url=jdbc:beasys:docmgmt:com.beasys.commerce.axiom.document.ref.RefDocumentPr
    ovider,\
    driver=com.beasys.commerce.axiom.document.jdbc.Driver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=1,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    props=jdbc.url=jdbc:weblogic:pool:commercePool;\
    jdbc.isPooled=true;\
    weblogic.t3.waitForConnection=true;\
    weblogic.t3.waitSecondsForConnection=999999999999;\
    docBase=C:/WebLogicCommerce/dmsBase/;\
    schemaXML=C:/WebLogicCommerce/dmsBase/doc-schema.xml
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.docPool=everyone,
    CareonDev
    # Add the show doc servlet
    weblogic.httpd.register.ShowDocServlet=com.beasys.commerce.content.ShowDocSe
    rvlet
    #========================================================
    # Careon's CDRpool and data source
    #========================================================
    weblogic.jdbc.connectionPool.cdrPool=\
    url=jdbc:oracle:thin:@careon_dev:1521:careon,\
    driver=oracle.jdbc.driver.OracleDriver,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=2,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    testTable=dual,\
    props=user=test;password=test
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.cdrPool=everyone,
    CareonDev
    Inpredictably, we obtain the following error:
    java.sql.SQLException: Connection has already been created in this tx
    context for pool named commercePool. Illegal attempt to create connection
    from another pool: cdrPool
    Does anybody have a solution or at least pointers ?
    Many thanks,
    Olivier

    Goh Yew Yap wrote:
    >
    Is there any workaround for this?Yes. In 6.0, presuming you use XA-compliant JDBC drivers
    for the DBMS or DBMSes involved, transactions will be able
    to involve any number of pools/DBMSes in a transaction.
    For 5.1 and/or for DBMSes that do not have an XA-compliant
    JDBC driver, you can write BMP beans that will do their own
    JDBC access to all but one DBMS, using the non-transactional
    pool driver, and you will be fully responsible for any
    transactional state involving this under-the-covers JDBC.
    This is easy to do in cases where a second DBMS is used
    primarily for queries, not updates, so the non-JTS-managed
    JDBC access can't corrupt that DBMS.
    Joe
    >
    "Joseph Weinstein" <[email protected]> wrote in message
    news:[email protected]...
    Olivier Baujard wrote:
    Hi,
    Here is the problem.
    Inpredictably, we obtain the following error:
    java.sql.SQLException: Connection has already been created in this tx
    context for pool named commercePool. Illegal attempt to create connection
    from another pool: cdrPoolHi. This means that within a single JTS/EJB transaction, there weremultiple
    beans and/or JSPs etc that got JDBC connections to do work, but not all ofthese
    routines asked for a connection from the same pool. That's a requirementfor
    5.1 or 4.5. The transaction coordinator and JTS driver cooperate to ensurethat
    only one JDBC connection is really ever used in a given transaction. Ifmultiple
    beans ask for a pool connection within a given tx, we ensure that theyreally get
    the same connection. This is because JDBC drivers typically don'timplement
    2-phase commit, so we must enforse that only one DBMS connection isinvolved so we
    can just commit or roll back on it, and ensure transactional correctness.If a
    bean asks for a connection from a different pool than a previous bean inthe same
    tx, we know we can't give them the already-established connection, so wethrow
    this exception.
    For 6.0, for pools made with XA-compliant JDBC drivers, this will be OK.
    Joe
    We use several connection pools to access differents
    schema of our database. We also have a connection pool
    opened for Weblogic Commerce which connects to the Commerce schema in
    our
    database. Here is a sample of our weblogic.properties file:
    #========================================================
    # WeblogicCommerce pool and data source
    #========================================================
    weblogic.jdbc.connectionPool.commercePool=\
    url=jdbc:oracle:thin:@careon_dev:1521:careon,\
    driver=oracle.jdbc.driver.OracleDriver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=1,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    testConnsOnReserve=true,\
    props=user=WLCS_TEST;password=WLCS_TEST,\
    testTable=WLCS_IS_ALIVE,\
    refreshMinutes=5
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.commercePool=everyone,
    CareonDev
    weblogic.jdbc.DataSource.weblogic.jdbc.jts.commercePool=commercePool
    #========================================================
    # WeblogicCommerce Document Management pool
    #========================================================
    # This is the pool the beans reference
    weblogic.jdbc.connectionPool.docPool=\
    url=jdbc:beasys:docmgmt:com.beasys.commerce.axiom.document.ref.RefDocumentPr
    ovider,\
    driver=com.beasys.commerce.axiom.document.jdbc.Driver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=1,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    props=jdbc.url=jdbc:weblogic:pool:commercePool;\
    jdbc.isPooled=true;\
    weblogic.t3.waitForConnection=true;\
    weblogic.t3.waitSecondsForConnection=999999999999;\
    docBase=C:/WebLogicCommerce/dmsBase/;\
    schemaXML=C:/WebLogicCommerce/dmsBase/doc-schema.xml
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.docPool=everyone,
    CareonDev
    # Add the show doc servlet
    weblogic.httpd.register.ShowDocServlet=com.beasys.commerce.content.ShowDocSe
    rvlet
    #========================================================
    # Careon's CDRpool and data source
    #========================================================
    weblogic.jdbc.connectionPool.cdrPool=\
    url=jdbc:oracle:thin:@careon_dev:1521:careon,\
    driver=oracle.jdbc.driver.OracleDriver,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=2,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    testTable=dual,\
    props=user=test;password=test
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.cdrPool=everyone,
    CareonDev
    Inpredictably, we obtain the following error:
    java.sql.SQLException: Connection has already been created in this tx
    context for pool named commercePool. Illegal attempt to createconnection
    from another pool: cdrPool
    Does anybody have a solution or at least pointers ?
    Many thanks,
    Olivier--
    PS: Folks: BEA WebLogic is in S.F. with both entry and advanced positionsfor
    people who want to work with Java and E-Commerce infrastructure products.Send
    resumes to [email protected]
    The Weblogic Application Server from BEA
    JavaWorld Editor's Choice Award: Best Web Application Server
    Java Developer's Journal Editor's Choice Award: Best Web ApplicationServer
    Crossroads A-List Award: Rapid Application Development Tools for Java
    Intelligent Enterprise RealWare: Best Application Using a ComponentArchitecture
    http://www.bea.com/press/awards_weblogic.html
    PS: Folks: BEA WebLogic is in S.F. with both entry and advanced positions for
    people who want to work with Java and E-Commerce infrastructure products. Send
    resumes to [email protected]
    The Weblogic Application Server from BEA
    JavaWorld Editor's Choice Award: Best Web Application Server
    Java Developer's Journal Editor's Choice Award: Best Web Application Server
    Crossroads A-List Award: Rapid Application Development Tools for Java
    Intelligent Enterprise RealWare: Best Application Using a Component Architecture
    http://www.bea.com/press/awards_weblogic.html

  • JDBC connection pools problems: weblogic doesn't release connections

    Hi all,
    we use Weblogic 5.1 in conjunction with Content Server 3.6 and Oracle
    8.1.6;
    We have this strange problem:
    Calling a page the connections, in the content server connection pool,
    grows up till the maximum. We think the problem is that Weblogic
    doesn't release used connections.
    Does anybody can help us? Did anybody had the same problem?
    Best Regards,
    Marcello Villani

    Hi. I'd have to see the code. When a pool connection is closed, it gets
    back into the pool. Until it's closed, it doesn't.
    Marcello Villani wrote:
    Hi all,
    we use Weblogic 5.1 in conjunction with Content Server 3.6 and Oracle
    8.1.6;
    We have this strange problem:
    Calling a page the connections, in the content server connection pool,
    grows up till the maximum. We think the problem is that Weblogic
    doesn't release used connections.
    Does anybody can help us? Did anybody had the same problem?
    Best Regards,
    Marcello Villani

  • Connection pooling problem in web service call

    Hi,
    I want to create some REST web services which will be called frequently by other applications (making calls at each 4-5 seconds).
    During the day there can be several instances active (20-30) which will use those web services. In conclusion there will be many database calls.
    What's the best solution to avoid seeing JDBC connection failure in weblogic console and to use connection pooling properly?
    1. Use createRootApplicationModule and after that call release
    2. Get the datasource instance and after that do whatever business (get VOs, methods etc.)
    ...or there is another solution?
    Thanks.
    Edited by: DorinS on 03.11.2011 12:02

    Hi,
    If the POJO you use to expose the service stays in memory then you don't need to close the AM reference. However, what you really want to do is to use JDBC Datasources with your AM configuration so the server manages a pool of database connections the AM then reaches out to
    Frank

  • Connection Pooling Problem in the HttpServlet, Need Help..... ASAP

    hi all,
    sample httpsevlet program is deployed and successfully executed.
    but when i am using connection pooling that servlet is deployed but it is not displayed any output on the browser
    who knows this connection pooling plz send the sample code for connection pool to create a table in the database........
    thanks in advance..
    Sree

    hi
    Using java Forums to maximum..
    you just need to create a datasource object first
    then call datasource.getConnection();
    that will create u the connection
    sample::::::::::::::::::::::::
    try {
                        ctx= new InitialContext();
                        System.out.println("After Context");
                        ds=(DataSource)ctx.lookup(testProperties.getProperty("JNDINAME"));
                             try {
                             conn=(Connection)ds.getConnection();
                             System.out.println("The Connection"+conn);
                             return conn;
                             } catch (SQLException e) {
                             // TODO Auto-generated catch block
                             e.printStackTrace();
                        } catch (NamingException e) {
                        // TODO Auto-generated catch block
                        e.printStackTrace();
                   System.out.println(testProperties.getProperty("propOne"));
                   catch (IOException e) {
              }

  • Connection Pool problems with Weblogic SP4 & Toplink 9.0.4.5

    Hi,
    i have updated my Weblogic 8.1 from SP2 to SP4. Since that I always get the following exception:
    Hi,
    i have updated my Weblogic 8.1 from SP2 to Sp4. Since that I always get the following exception:
    Exception [TOPLINK-4002] (TopLink (WLS CMP) - 10g (9.0.4.5) (Build 040930)): oracle.toplink.exceptions.DatabaseException
    Exception-Beschreibung: java.sql.SQLException: Pool connect failed : javax.security.auth.login.FailedLoginException: [Securit
    y:090304]Authentication Failed: User javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied
    This exception is thrown when the StartUp-Servlet tries the first time to establish an connection to my Connection Pool. The connection pool itself has been tested in the Weblogic-console and works fine.
    Thanks for help.

    Sebastian,
    9.0.4.5 is the version with fixes to address changes made by BEA in SP4 so this should work. I do recall some issue with our login configuration and the data source.
    Is the user-name specified in either your sessions configuration of project XML without a password. This may be an issue where if part of the credentials are supplied it is asking for the rest.
    Doug

  • Tomcat 5.5 + JDBC connection pooling -- help

    I recently upgraded from java 1.4/tomcat 5.0 to java 1.5/tomcat 5.5. I am having difficulty getting connection pooling to work, however.
    Here are the details:
    1. Using mysql 4.1.3 beta -- it has been working fine for my purposes for a while
    2. put mysql-connector-java-3.1.7-bin.jar in tomcat/common/lib.
    3. Here is server.xml:
    <Server port="8005" shutdown="SHUTDOWN">
        <GlobalNamingResources>
            <Resource auth="Container" name="jdbc/TestDB"
            type="javax.sql.DataSource"/>
            <ResourceParams name="jdbc/TestDB">
                <parameter>
                    <name>url</name>
                    <value>jdbc:mysql://localhost:3306/TestDB?autoReconnect=true</value>
                </parameter>
                <parameter>
                    <name>maxIdle</name>
                    <value>40</value>
                </parameter>
                <parameter>
                    <name>maxActive</name>
                    <value>150</value>
                </parameter>
                <parameter>
                    <name>driverClassName</name>
                    <value>com.mysql.jdbc.Driver</value>
                </parameter>
                <parameter>
                    <name>maxWait</name>
                    <value>3000</value>
                </parameter>
                <parameter>
                    <name>removeAbandoned</name>
                    <value>true</value>
                </parameter>
                <parameter>
                    <name>username</name>
                    <value>webapp</value>
                </parameter>
                <parameter>
                    <name>factory</name>
                    <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
                </parameter>
                <parameter>
                    <name>logAbandoned</name>
                    <value>true</value>
                </parameter>
                <parameter>
                    <name>removeAbandonedTimeout</name>
                    <value>90</value>
                </parameter>
                <parameter>
                    <name>password</name>
                    <value>secret</value>
                </parameter>
            </ResourceParams>
        </GlobalNamingResources>
        <Service name="Catalina">
            <Connector port="8080" />
            <Engine name="Catalina" defaultHost="localhost">
                <Host appBase="webapps"
                      autoDeploy="true"
                      debug="5"
                      liveDeploy="true"
                      name="localhost"
                      unpackWARs="true"
                      xmlValidation="true"/>
            </Engine>
        </Service>
    </Server>4. My application is called "bertle". Here is tomcat/conf/Catalina/localhost/bertle.xml:
    <Context path="/bertle" reloadable="true"
             docBase="C:\eclipse\workspace\bertle\bertle"
             workDir="C:\eclipse\workspace\bertle\work">
        <ResourceLink global="jdbc/TestDB"
                      name="jdbc/TestDB"
                      type="javax.sql.DataSource" />
    </Context>5. Tomcat starts up find without showing any errors. However, when I try and run the application I get an error. The error occurs when the user tries to log in, which involves querying the mysql database. Here is some of what it spits up:
    SEVERE: Error in validating user.
    Feb 28, 2005 5:05:16 PM edu.harvard.dsg.chv.model.LoginBean validateUser
    SEVERE: SQL statement =
    org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null'
         at  org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:780)
         at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
         at mypackage.model.LoginBean.validateUser(LoginBean.java:49)
         at mypackage.action.LoginAction.execute(LoginAction.java:58)6. Here is the line at LoginBean.java:49:
    49    con = dataSource.getConnection();Here are the lines at LoginAction.java:58
    46        // Obtain our environment naming context
    47        Context initCtx = new InitialContext();
    48        Context envCtx = (Context) initCtx.lookup("java:comp/env");
    49       
    50        // Look up our data source
    51        DataSource ds = (DataSource) envCtx.lookup("jdbc/TestDB");
    52       
    53        // create a new LoginBean passing the datasource
    54        LoginBean lb = new LoginBean(ds);
    55       
    56        // check to see if this user/password combination are valid
    57        // will return a non-null UserDTO if valid
    58        UserDTO user = lb.validateUser((String)((DynaValidatorForm)form).get("handle"),
    59                (String)((DynaValidatorForm)form).get("password"));Is there something I am also supposed to add to WEB-INF/web.xml ?
    I am offering many kudos to anyone who can tell me what I am overlooking.
    Thanks,
    Jon

    the stuff you added in server.xml is old and wiilnot
    work with 5.5.*
    might pass dtd but it will not work
    did you try changing it to new layoutI gave you one Duke dollar for helping me with this.
    I will give another one to anyone who can tell me
    e how to set up global connection pooling in tomcat.Hi,
    Please bear with me for replying to a thread that's a week old.
    I was trying to set up connection pooling in tomcat and this thread helped me clear up some issues for the same.
    Incidentally google returns this thread among the top 10 when i search for tomcat 5.5 connection pooling.
    There are some unexplained questions here (regarding global connection pooling) and since I was able to set that up too, this may, in the future, benefit anybody who faces similar issues.
    Setting Up Global Connection Pooling
    Add this piece of code to server.xml under the server element
    <Server port="8005" shutdown="SHUTDOWN">
      <!-- other elements -->
      <GlobalNamingResources>
         <!-- other global resources-->
          <Resource name="jdbc/learning" auth="Container"                      type="javax.sql.DataSource" driverClassName="oracle.jdbc.driver.OracleDriver"
                         url="jdbc:oracle:thin:@localhost:1521:learning"
                         username="Learning" password="Learning" maxActive="20" maxIdle="10"  maxWait="-1"/>         
      </GlobalNamingResources>And then in your context file (which may be the <webapps>/<your appn>/META-INF/<your_web_app.xml> directory or conf/catalina/localhost/<your_web_app.xml>)
    add this code
    <Context docBase="${catalina.home}/webapps/webtest"
             privileged="true" antiResourceLocking="false" antiJARLocking="false">
    <!-- Use this if you dont require global resources
      <Resource name="jdbc/learning" auth="Container"
                         type="javax.sql.DataSource" driverClassName="oracle.jdbc.driver.OracleDriver"
                         url="jdbc:oracle:thin:@localhost:1521:learning"
                         username="Learning" password="Learning" maxActive="20" maxIdle="10"
                  maxWait="-1"/>
    -->
    <!-- this is a resource link if you have defined resource globally-->
    <ResourceLink
                name="jdbc/learning"
                global="jdbc/learning"
                type="javax.sql.DataSource"
              />
    </Context>also tomcat recommends defining the docBase outside the webapps directory (ie any other location outside the tomcat installation dir) if you choose to define contexts in xml files.
    thanks,
    ram.

  • Problem in DBCP Connection Pooling with BLOB in Tomcat

    Hi All,
    I am using the DBCP connection pooling in tomcat server version 6.0.18.
    I have session table which maintains the session details of the user in BLOB column. Recently I am facing a problem. When a user logs in, I am storing the session details in the DB. It throws an exception like this. When I restart the tomcat, it just works fine. But after some days it is again throwing the same exception.
    Code:
    2009-01-27 06:03:13,789 DEBUG [org.springframework.jdbc.core.JdbcTemplate] - Executing prepared SQL statement [INSERT INTO SESSION (SESSION_CODE,LAST_ACCESS,VALID_SESSION,SESSION_DATA) VALUES(?,?,?,?)]
    2009-01-27 06:03:13,789 DEBUG [org.springframework.transaction.support.TransactionSynchronizationManager] - Retrieved value [org.springframework.jdbc.datasource.ConnectionHolder@154136a] for key [org.apache.commons.dbcp.BasicDataSource@bdec44] bound to thread [http-8443-6]
    2009-01-27 06:03:13,789 DEBUG [org.springframework.jdbc.core.StatementCreatorUtils] - Setting SQL statement parameter value: column index 1, parameter value [c2896a488efb7fe15430fab10d502577], value class [java.lang.String], SQL type unknown
    2009-01-27 06:03:13,789 DEBUG [org.springframework.jdbc.core.StatementCreatorUtils] - Setting SQL statement parameter value: column index 2, parameter value [1233064993], value class [java.lang.Long], SQL type unknown
    2009-01-27 06:03:13,789 DEBUG [org.springframework.jdbc.core.StatementCreatorUtils] - Setting SQL statement parameter value: column index 3, parameter value [1], value class [java.lang.Integer], SQL type unknown
    2009-01-27 06:03:13,789 DEBUG [org.springframework.jdbc.core.StatementCreatorUtils] - Setting SQL statement parameter value: column index 4, parameter value [org.springframework.jdbc.core.support.SqlLobValue@18af32e], value class [org.springframework.jdbc.core.support.SqlLobValue], SQL type 2004
    2009-01-27 06:03:13,789 DEBUG [org.springframework.jdbc.support.lob.DefaultLobHandler] - Set bytes for BLOB with length 390
    2009-01-27 06:03:13,789 DEBUG [org.springframework.transaction.support.TransactionSynchronizationManager] - Retrieved value [org.springframework.jdbc.datasource.ConnectionHolder@154136a] for key [org.apache.commons.dbcp.BasicDataSource@bdec44] bound to thread [http-8443-6]
    2009-01-27 06:03:13,790 DEBUG [org.springframework.transaction.support.TransactionSynchronizationManager] - Retrieved value [org.springframework.jdbc.datasource.ConnectionHolder@154136a] for key [org.apache.commons.dbcp.BasicDataSource@bdec44] bound to thread [http-8443-6]
    2009-01-27 06:03:13,790 DEBUG [org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator] - Unable to translate SQLException with Error code '17410', will now try the fallback translator
    2009-01-27 06:03:13,790 INFO [web.controller.LoginController] - Caught Exception while creating sesion in DB
    2009-01-27 06:03:13,790 DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Triggering beforeCompletion synchronization
    2009-01-27 06:03:13,790 DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Initiating transaction rollback
    2009-01-27 06:03:13,790 DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Rolling back JDBC transaction on Connection [jdbc:oracle:thin:@stagedb1c:2115:WEB1C, UserName=WEBAPP, Oracle JDBC driver]
    2009-01-27 06:03:13,791 DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Triggering afterCompletion synchronization
    2009-01-27 06:03:13,791 DEBUG [org.springframework.transaction.support.TransactionSynchronizationManager] - Clearing transaction synchronization
    2009-01-27 06:03:13,791 DEBUG [org.springframework.transaction.support.TransactionSynchronizationManager] - Removed value [org.springframework.jdbc.datasource.ConnectionHolder@154136a] for key [org.apache.commons.dbcp.BasicDataSource@bdec44] from thread [http-8443-6]
    2009-01-27 06:03:13,791 DEBUG [org.springframework.jdbc.datasource.DataSourceTransactionManager] - Releasing JDBC Connection [connection is closed] after transaction
    2009-01-27 06:03:13,791 DEBUG [org.springframework.jdbc.datasource.DataSourceUtils] - Returning JDBC Connection to DataSource
    2009-01-27 06:03:13,791 DEBUG [org.springframework.jdbc.datasource.DataSourceUtils] - Could not close JDBC Connection
    java.sql.SQLException: Already closed.
    at org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:84)
    at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(PoolingDataSource.java:181)
    at org.springframework.jdbc.datasource.DataSourceUtils.doReleaseConnection(DataSourceUtils.java:313)
    at org.springframework.jdbc.datasource.DataSourceUtils.releaseConnection(DataSourceUtils.java:274)
    at org.springframework.jdbc.datasource.DataSourceTransactionManager.doCleanupAfterCompletion(DataSourceTransactionManager.java:316)
    at org.springframework.transaction.support.AbstractPlatformTransactionManager.cleanupAfterCompletion(AbstractPlatformTransactionManager.java:966)
    at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:832)
    at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:777)
    at web.controller.LoginController.onSubmit(LoginController.java:109)
    at org.springframework.web.servlet.mvc.SimpleFormController.processFormSubmission(SimpleFormController.java:267)
    at org.springframework.web.servlet.mvc.AbstractFormController.handleRequestInternal(AbstractFormController.java:265)
    at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
    at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Thread.java:595)
    My Session table has the following structure:
    Code:
    Name Null? Type
    SESSION_CODE NOT NULL VARCHAR2(100)
    LAST_ACCESS NOT NULL NUMBER
    VALID_SESSION NOT NULL NUMBER
    SESSION_DATA NOT NULL BLOB
    I have the following in the Spring context file :
    Code:
    <bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
    <property name="driverClassName" value="${jdbc.driverClassName}"/>
    <property name="url" value="${jdbc.url}"/>
    <property name="username" value="${jdbc.username}"/>
    <property name="password" value="${jdbc.password}"/>
    <property name="initialSize" value="5"/>
    <property name="maxActive" value="5"/>
    <property name="minIdle" value="2"/>
    <property name="poolPreparedStatements" value="true"/>
    <property name="defaultAutoCommit" value="false"/>
    </bean>
    I am using the oracle.jdbc.driver.OracleDriver as jdbc driver. And also using the commons-dbcp-1.2.2.jar and ojdbc14.jar.
    Can some one help me out to solve this issue?
    Thanks in Advance.

    I am also facing the same problem, please let me know if there any suggestions,
    DEBUG|2010-05-07 16:41:25,866|main|(SQLErrorCodeSQLExceptionTranslator.java:266)|org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator|Unable to translate SQLException with Error code '17410', will now try the fallback translator
    DEBUG|2010-05-07 16:41:25,866|main|(SQLStateSQLExceptionTranslator.java:94)|org.springframework.jdbc.support.SQLStateSQLExceptionTranslator|Extracted SQL state class '08' from value '08000'
    thanks
    sundaravel n

Maybe you are looking for

  • Problem with FLVPlayer in Flash CS3 (need to save out as Actionscript 3.0 SWf file)

    I am using Flash CS3 and am trying to publish a SWf file that makes use of the "FLVPlayback" component. I need for this SWF file to be published as an Actionscript 3.0 file, so I have set my publish settings to Flash Player 9.0 and Actionscript 3.0,

  • Losing internet on WRT54GS, and only unplug/replug works.

    My router keeps going out, and the only thing that gets me back on is to unplug, replug, then I'm good but only for about 20 minutes.  Ideas?

  • Getting error while using jaxb/xjc

    hello every one, i have a xsd and i want automated classes from it for which i am using jaxb and xjc compiler but when i am running it then i am getting error parsing a schema... compiling a schema... Exception in thread "main" java.lang.IllegalArgum

  • Stopping loop when output = 0

    Hi, I was wondering if anyone knew how to stop a loop when the final output is 0.  I'm doing battery life testing with a agilent multimeter and want to loop the reading of the voltage until the output = 0 so that the timer can stop at that point.  Ho

  • Cannot Connect to iTunes Store and iMessages Slow

    My friends cannot connect to the iTunes store via the iTunes app on iOS 7. They're using an iPhone 5, and their App Store is loading fine. Their iPhone's also experience random crashes (respring crashes not application crashes) and this occurs durrin