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
Similar Messages
-
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 -
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,
OlivierGoh 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 -
Replace Quotes, Connection Pooling, and Sun Web Server with MySQL, Oracle
This is code I use to insert data into my MySQL and Oracle databases.
I takes care of quotes and shows use of context, i.e. when you use Sun Web Server's
ConnectionPooling. This code works. Feel free to reply if you have questions on how to set up connection pooling using Sun Web Server 6.1SP - it took quite a long time to learn and I couldn't find much information throughout the web, so I hope this helps...
This is not a question and I am not looking for an answer, but please post comments or suggestions.
dailysun
This is in one class where I have a hashtable containing the
column name / value pairs that I want to enter into my table.
This class simply creates the SQL string from the values in the
hashtable. It then passes that hashtable including the database
name to a class which executes that sql statement (second code
portion).
/* Insert data into sf_parts. Create the column strings from
* the provided hash table. Be sure to parse out hash elements which
* are used for the createTemplate process
StringBuffer values = new StringBuffer();
StringBuffer fields = new StringBuffer();
Enumeration keys = fieldHash.keys();
while(keys.hasMoreElements()){
Object currentKey = keys.nextElement();
String fieldValue = (String) fieldHash.get(currentKey);
if(values.length() >0){
values.append(",");
values.append("'"+fieldValue.replaceAll("'","''")+"'"); // Takes care of quotes and various other special characters!
if(fields.length() >0){
fields.append(",");
fields.append(currentKey);
sql = "INSERT INTO myTable (" + fields.toString() + ") VALUES (" + values.toString() + ");";
String insertResult = caq.getInsertDelete(sql,"myDatabaseName"); // your database name is defined in web.xml and sun-web.xml when you use Sun Web Server's Connection Pooling.
returnValue += "<br><br><b>Rows inserted into table(myTable): </b>" + insertResult + "<br>\n";
And, like I describe above, this method executes the sql statement.
* Takes care of insert, update and delete requests.
* Must have set both dbName as well as the sql String.
* Will return number of rows affected as String.
* @return String Number of rows affected
* @exception SQLException
* @exception Exception
public String getInsertDelete() {
checkData(); // this simply checks if the variables dbName and sql are not empty ;-)
InitialContext initContext = null;
int rv = 0;
try{
// Get connection from configured pool
initContext = new InitialContext();
source = (DataSource) initContext.lookup("java:comp/env/jdbc/" + dbName); // I have this set up in web.xml and sun-web.xml (I use Sun Web Server 6.1SP which does connection pooling for me)
conn = source.getConnection();
if(conn != null){
stmt = conn.createStatement();
rv = stmt.executeUpdate(sql);
}catch (SQLException e){
// do something
}catch (Exception e){
// do something
}finally{
try{
stmt.close();
}catch(Exception e){
// do something
try{
conn.close();
}catch(Exception e){
// do something
try{
initContext.close();
}catch(Exception e){
// do something
return rv+"";
}This is code I use to insert data into my MySQL and
Oracle databases.
I takes care of quotes and shows use of context, i.e.
when you use Sun Web Server's
ConnectionPooling. This code works. Feel free to
reply if you have questions on how to set up
connection pooling using Sun Web Server 6.1SP - it
took quite a long time to learn and I couldn't find
much information throughout the web, so I hope this
helps...
This is not a question and I am not looking for an
answer, but please post comments or suggestions.Using prepared statements would mean that you wouldn't have to worry about quotes.
You should be closing the result set.
You are handling all fields as strings. That won't work with time fields and might not work for numeric fields.
Presumably most of your variables are member variables. They should be local variables because that is the scope of the usage.
You must do something with the exceptions.
Hashtables although convienent mean that problems with usage can only be resolved at run time rather than compile time. -
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:01Hi,
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. -
WLST : Error connecting to a remote Weblogic server instance from OEPE 3.7
Attempting a to run a weblogic script connecting to a remote weblogic server instance (10.3.5), which is generating the following exception in OEPE 3.7.2 -
username = 'weblogic'
password = 'weblogic6'
url='t3://xxx.xxx.com:7001'
connect(username,password,url)
Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
This Exception occurred at Fri Feb 01 13:20:54 MST 2013.
Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
Use dumpStack() to view the full stacktrace :
java.lang.AssertionError: Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStubconnect
Problem invoking WLST - Traceback (innermost last):
File "C:\Users\hughese\workspace\12c_wlst\wlst\heapsize.py", line 13, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
Use dumpStack() to view the full stacktrace
Connecting to the local weblogic server instance (t3://localhost:7001) works okay.
From the command prompt (wlst.cmd) I'm able to connect to the remote weblogic server instance -
wls:/offline> connect('weblogic','xxxxx','t3:xxx.xxx.com:7001') ;
Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'IDMDomain'.
I've compared the CLASSPATHs between OEPE and the command prompt.
Any assistance would be greatly appreciated.
Edited by: 950635 on Feb 1, 2013 7:47 PMHi,
1)To get mysql JDBC driver to work on my Linux system, i had to add the classpath for the driver to the .bashrc:
CLASSPATH=./:home/<user>/java/mm.mysql-2.0.6/:home/<user>/java
Note that I execute the java program as the user <user> (and .bashrc is the config. file of this <user>...). Perhaps you must do this as well for the Oracle driver on your client machine. I don't know if your client machine is UNIX/LINUX or WINDOWS. It should only be clear that the CLASSPATH is set in the config. file of the user under which the java program runs and that this user has the permission to access the files.
There are no differences between accessing the database locally than accessing it by a network connection. The only thing that matters are that the connection parameters are right and that the network works properly.
2) are you sure that the table tname (case sensitivity?) exits?
Marc -
Problem downloading WebLogic Server 8
I am having problems downloadingl the eval copy of Weblogic server 8. The'Specify
Download Options' page in the Weblogic installer doesnt request proxy server authentication
information (userid, password). Is there a way to work around this issue and successfully
download the software.
thanks
-vinny"Tanguy" == Tanguy Le Berre <[email protected]> writes:
Tanguy> I have a problem while installing weblogic server 8.11 on a solaris 9 machine.
Tanguy> I use the following instruction: ./filename.bin and I see the following message:
Tanguy> Illegal instruction (memory dumped)
Tanguy> (in french: instruction incorrecte (vidage memoire))
Tanguy> A core file is generated but it doesn't help resolving this problem. It seems
Tanguy> to be talking about unzip, as I found things like this message in this file:
Tanguy> error: cannot allocate unzip buffers
Tanguy> unzipsfx: cannot find myself! [%s]
Tanguy> error [%s]: missing %ld bytes in zipfile
Tanguy> I also tryed to install weblogic server 8.10 and no core file is generated but
Tanguy> I have the following message:
Tanguy> error [export/home/tleberre/net_server810_solaris32.bin]: missing 570 byes in
Tanguy> zipfile
Tanguy> (attempting to process anyway)
Tanguy> ** Error during init, error code = 2.
Tanguy> I first thought the file I downloaded was incomplete, so I downloaded it again
Tanguy> but I still have the same problem. Can anyone help me? What have I forgotten to
Tanguy> do?
Well, perhaps one thing you've forgotten is that it's better to write notes
about particular problems in the newsgroup or mailing list that is most
appropriate to the problem. If people who read this newsgroup only know about
the webserver, then they won't have any idea how to help you with installation
problems with WebLogic server, which this clearly is (the "webserver" is not
"WebLogic Server", but only part of the entire package).
Have you made an attempt to contact BEA support? It seems likely that your zip
file is corrupt.
===================================================================
David M. Karr ; Java/J2EE/XML/Unix/C++
[email protected] ; SCJP; SCWCD; SCBCD -
Problem installing weblogic server 8.11
I have a problem while installing weblogic server 8.11 on a solaris 9 machine.
I use the following instruction: ./filename.bin and I see the following message:
Illegal instruction (memory dumped)
(in french: instruction incorrecte (vidage memoire))
A core file is generated but it doesn't help resolving this problem. It seems
to be talking about unzip, as I found things like this message in this file:
error: cannot allocate unzip buffers
unzipsfx: cannot find myself! [%s]
error [%s]: missing %ld bytes in zipfile
I also tryed to install weblogic server 8.10 and no core file is generated but
I have the following message:
error [export/home/tleberre/net_server810_solaris32.bin]: missing 570 byes in
zipfile
(attempting to process anyway)
** Error during init, error code = 2.
I first thought the file I downloaded was incomplete, so I downloaded it again
but I still have the same problem. Can anyone help me? What have I forgotten to
do?
Thank you
Tanguy Le Berre"Tanguy" == Tanguy Le Berre <[email protected]> writes:
Tanguy> I have a problem while installing weblogic server 8.11 on a solaris 9 machine.
Tanguy> I use the following instruction: ./filename.bin and I see the following message:
Tanguy> Illegal instruction (memory dumped)
Tanguy> (in french: instruction incorrecte (vidage memoire))
Tanguy> A core file is generated but it doesn't help resolving this problem. It seems
Tanguy> to be talking about unzip, as I found things like this message in this file:
Tanguy> error: cannot allocate unzip buffers
Tanguy> unzipsfx: cannot find myself! [%s]
Tanguy> error [%s]: missing %ld bytes in zipfile
Tanguy> I also tryed to install weblogic server 8.10 and no core file is generated but
Tanguy> I have the following message:
Tanguy> error [export/home/tleberre/net_server810_solaris32.bin]: missing 570 byes in
Tanguy> zipfile
Tanguy> (attempting to process anyway)
Tanguy> ** Error during init, error code = 2.
Tanguy> I first thought the file I downloaded was incomplete, so I downloaded it again
Tanguy> but I still have the same problem. Can anyone help me? What have I forgotten to
Tanguy> do?
Well, perhaps one thing you've forgotten is that it's better to write notes
about particular problems in the newsgroup or mailing list that is most
appropriate to the problem. If people who read this newsgroup only know about
the webserver, then they won't have any idea how to help you with installation
problems with WebLogic server, which this clearly is (the "webserver" is not
"WebLogic Server", but only part of the entire package).
Have you made an attempt to contact BEA support? It seems likely that your zip
file is corrupt.
===================================================================
David M. Karr ; Java/J2EE/XML/Unix/C++
[email protected] ; SCJP; SCWCD; SCBCD -
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 VillaniHi. 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 -
JDBC Connection pool recovery after DB server restart
I am finding that Kodo is throwing the following exception after I restart
my database server (mysql). I am doing the database server restart while my
application server is idle, so it is not during a transaction.
Communication link failure: java.net.SocketException [code=0;state=08S01]
NestedThrowables:
com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
This is presumably due to the JDBC connection pooling. Is there a
configuration setting that allows Kodo to detect such failures and reconnect
to the database server without exposing this problem to the application
code? For example, WebLogic Server's JDBC connection pool has a setting that
enables testing a connection and recovering from such failures before
allocating it from the pool.
BenThis is presumably due to the JDBC connection pooling. Is there a
configuration setting that allows Kodo to detect such failures and reconnect
to the database server without exposing this problem to the application
code?Not right now. You can log an enhancement request with our bug database:
http://bugzilla.solarmetric.com/ -
When I first started Weblogic, at that time, the database server wasn’t available, so there was a lot of error about the database connection pool, and definitely the application didn’t work properly, so I realized that because of the database server ka. But after the database server was available, I worked on the application again but it seem like weblogic server didn’t update and still kept the state that it couldn’t find the connection pool although it had already there. Is it possible to make weblogic server automatically update when the database server is available. Any solution to resolve this problem?
In wich version of weblogic ? I 5.1 may be .... from 7.0 to up I don't think so ....
I supose that you don't enable the refresh/testing parameters of jdbc pool.
Please check the e-docs to see more information
Jin -
Problems Starting Weblogic Server for Tutorials (Fresh install)...
Hi guys, need a little help here.
I'm trying to startup Weblogic Server for Java Control Tutorial application and I get all sorts of errors, mostly seeming to deal with JMS/JNDI network stuff. Here's the error dump I get:
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
Starting WLS with line:
C:\bea\JDK142~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket
,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:Com
pileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da
:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls
.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.con
figuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.managem
ent.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ign
oreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.log
ErrorsToConsole=true -Dweblogic.Name=cgServer -Djava.security.policy=C:\bea\WEBL
OG~1\server\lib\weblogic.policy weblogic.Server
<Oct 30, 2005 2:33:31 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting Web
Logic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Micro
systems Inc.>
<Oct 30, 2005 2:33:31 PM PST> <Info> <Configuration Management> <BEA-150016> <Th
is server is being started as the administration server.>
<Oct 30, 2005 2:33:31 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877>
<Oct 30, 2005 2:33:32 PM PST> <Notice> <Management> <BEA-140005> <Loading domain
configuration from configuration repository at C:\bea\WEBLOG~1\samples\domains\
workshop\.\config.xml.>
<Oct 30, 2005 2:33:33 PM PST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\bea\weblogic81\samples\domains\workshop\cgServer\cgServer.log is op
ened. All server side log events will be written to this file.>
<Oct 30, 2005 2:33:34 PM PST> <Notice> <Security> <BEA-090082> <Security initial
izing using security realm myrealm.>
<Oct 30, 2005 2:33:34 PM PST> <Notice> <WebLogicServer> <BEA-000327> <Starting W
ebLogic Admin Server "cgServer" for domain "workshop">
<Oct 30, 2005 2:33:38 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:40 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:42 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:44 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:46 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:47 PM PST> <Error> <JDBC> <BEA-001150> <Connection Pool "cgJM
SPool-nonXA" deployment failed with the following error: 0:Could not create pool
connection. The DBMS driver exception was: SQL-server rejected establishment of
SQL-connection. Pointbase Server may not be running on localhost at port 9093..
>
<Oct 30, 2005 2:33:48 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:50 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:52 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:54 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:56 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001150> <Connection Pool "cgPo
ol" deployment failed with the following error: 0:Could not create pool connecti
on. The DBMS driver exception was: SQL-server rejected establishment of SQL-conn
ection. Pointbase Server may not be running on localhost at port 9093..>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001151> <Data Source "cgDataSo
urce" deployment failed with the following error: DataSource(cgDataSource;cgSamp
leDataSource) can't be created with non-existent Pool (connection or multi) (cgP
ool).>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001151> <Data Source "cgDataSo
urce-nonXA" deployment failed with the following error: DataSource(cgDataSource-
nonXA;weblogic.jdbc.jts.ebusinessPool) can't be created with non-existent Pool (
connection or multi) (cgJMSPool-nonXA).>
<Oct 30, 2005 2:33:57 PM PST> <Alert> <JMS> <BEA-040052> <JMSServer "cgJMSServer
" store failed to open java.io.IOException: JMS JDBC store, connection pool = <c
gJMSPool-nonXA>, prefix = <weblogic>: connection pool does not exist.
java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-nonXA>, prefix
= <weblogic>: connection pool does not exist
at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:48
8)
at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
60)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
28)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Rem
oteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
ServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
xy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
s(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JMS> <BEA-040123> <Failed to start JMS Se
rver "cgJMSServer" due to weblogic.jms.common.JMSException: JMS can not open sto
re cgJMSStore.
weblogic.jms.common.JMSException: JMS can not open store cgJMSStore
at weblogic.jms.backend.BEStore.start(BEStore.java:163)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
60)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
28)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Rem
oteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
ServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
xy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
s(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Caused by: java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-non
XA>, prefix = <weblogic>: connection pool does not exist
at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:48
8)
at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
... 29 more
>
<Oct 30, 2005 2:33:57 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
<Oct 30, 2005 2:33:58 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090170> <Loading the priv
ate key stored under the alias DemoIdentity from the jks keystore file C:\bea\we
blogic81\server\lib\DemoIdentity.jks.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090171> <Loading the iden
tity certificate stored under the alias DemoIdentity from the jks keystore file
C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090169> <Loading trusted
certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.j
ks.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090169> <Loading trusted
certificates from the jks keystore file C:\bea\JDK142~1\jre\lib\security\cacerts
.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000331> <Started We
bLogic Admin Server "cgServer" for domain "workshop" running in Development Mode
>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server sta
rted in RUNNING mode>
<Oct 30, 2005 2:33:58 PM PST> <Warning> <WebLogicServer> <BEA-000372> <HostName:
0.0.0.0, maps to multiple IP addresses:192.168.0.1,70.34.104.139>
<Oct 30, 2005 2:33:58 PM PST> <Warning> <WebLogicServer> <BEA-000372> <HostName:
0.0.0.0, maps to multiple IP addresses:192.168.0.1,70.34.104.139>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "Li
stenThread.Default" listening on port 7001, ip address *.*>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SS
LListenThread.Default" listening on port 7002, ip address *.*>
<Oct 30, 2005 2:34:07 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. Connection failed after 2 attempts. The MDB will attempt to
reconnect every 10 seconds. This log message will repeat every 600 seconds until
the condition clears.>
<Oct 30, 2005 2:34:07 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
<Oct 30, 2005 2:34:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. Connection failed after 2 attempts. The MDB will attempt to reconnect every
10 seconds. This log message will repeat every 600 seconds until the condition
clears.>
<Oct 30, 2005 2:34:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:44:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. Connection failed after 62 attempts. The MDB will attempt to reconnect ever
y 10 seconds. This log message will repeat every 600 seconds until the condition
clears.>
<Oct 30, 2005 2:44:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:44:17 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. Connection failed after 63 attempts. The MDB will attempt to
reconnect every 10 seconds. This log message will repeat every 600 seconds unti
l the condition clears.>
<Oct 30, 2005 2:44:17 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
<Oct 30, 2005 2:54:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. Connection failed after 122 attempts. The MDB will attempt to reconnect eve
ry 10 seconds. This log message will repeat every 600 seconds until the conditio
n clears.>
<Oct 30, 2005 2:54:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:54:17 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. Connection failed after 123 attempts. The MDB will attempt t
o reconnect every 10 seconds. This log message will repeat every 600 seconds unt
il the condition clears.>
<Oct 30, 2005 2:54:17 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
THANK YOU for any help you can provide!These are errors/warning because of incorrect connection pool settings.Either the database parameters were not configured correctly or there were some issues with the configuration itself.
Your server did start up correctly though.
"<Server started in RUNNING mode>" -
Can't modify Outbound Connection Pools properties in WebLogic 10.3.6
I'm trying to configure BAM adapter in WebLogic Administration Console. Navigate to deployments -> OracleBamAdapter -> Configuration -> Outbound Connection Pools -> eis/bam/rmi -> tried to enter property value of Hostname but I couldn't. It is not in edit mode - no check box in front of Hostname column. I tried to enter the value in the hostname property and save but nothing was saved.
I've unlocked domain configuration lock and I see the <lock & edit> button is disabled and <release configuration> button is enabled in the change center. So why can I modify the property value?
WebLogic 10.3.6
SOA 11.1.1.6
BAM
All are installed in the same server and SOA is installed with development mode. I didn't bounce the admin server after unlocking the domain configuration, is this required?Thanks, Arik. I just figured it out and was banging my head against the wall when you posted the message. :-) Thanks for the reply!
-
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
MariaHow 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 -
Cant create connection Pool for MS SQL Server 2000 with Microsoft Driver
i am using bea weblogic server 6.1, i cant create connection pool while using MS
SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft website. when
i give the following class name for JDBC driver and the connection url and click
apply while selecting the available server, a number of exception appears in default
server (that is the connection pool cannot be created..... cannot load the driver
class).
URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
when i use the above setting in a JDBC simple application in Jbuilder
7.0 the application runs successfully and fetches the data deom MS SQL database
but in at Bea connection Pool is not created with these settings. i do give appropriate
username and password in properties field in connection pool. Thankx for any help!khabbab wrote:
That was the original code part from "startweblogic" :
:runWebLogic
echo on
set PATH=.\bin;%PATH%
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;
echo off
and i changed it to :
:runWebLogic
echo on
set PATH=.\bin;%PATH%
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;D:\Program Files\Microsoft
SQL Server 2000 Driver for JDBC\lib\msbase.jar;D:\Program Files\Microsoft SQL
Server 2000 Driver for JDBC\lib\msutil.jar;D:\Program Files\Microsoft SQL Server
2000 Driver for JDBC\lib\mssqlserver.jar;I suggest moving or copying the three ms driver jars to a directory that has no blanks
in it so the classpath doesn't have blanks in it. Ie:
go to the "D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib"
directory and do this:
mkdir D:\microsoft_jdbc_driver
cp *.jar D:\microsoft_jdbc_driver
Then make the classpath include D:\microsoft_jdbc_driver\msbase.jar etc.
Joe
>
>
echo off
when i save and run the bat file, server appears then disappears.
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
The class path which is echoed at server startup does not include thepaths to
driver jar files. when i edited the "startweblogic.bat" file and includedthe
driver class paths to jar files, now the server doesnot even run. tellme what
to do now???Show me what change you made to the startweblogic file.
Joe
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
kindly tell me how can i check that the class paths for driver jarfiles are included
in that string? thanks. also tell me can not i use the jdriver forsql server
2000?.The startup script will echo what it's doing, including printing out
the classpath
it will use. Yes you can use the jDriver for MS SQL2000. It is sufficient
for
basic JDBC, but the MS drivfer is preferable in some ways.
Joe
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
i am using bea weblogic server 6.1, i cant create connection
pool
while
using MS
SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft
website.
when
i give the following class name for JDBC driver and the connectionurl and click
apply while selecting the available server, a number of exception
appears
in default
server (that is the connection pool cannot be created..... cannot
load
the driver
class).The server startup script creates a string that will become the
classpath
for the server.
This string is part of the java call to start the server with a-classpath
argument. You need to
make sure the MS driver jars are part of that classpath string.
Joe
URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
when i use the above setting in a JDBC simple applicationin Jbuilder
7.0 the application runs successfully and fetches the data deom
MS
SQL database
but in at Bea connection Pool is not created with these settings.
i
do give appropriate
username and password in properties field in connection pool.
Thankx
for any help!
khabbab wrote:
The class path which is echoed at server startup does not include thepaths to
driver jar files. when i edited the "startweblogic.bat" file and includedthe
driver class paths to jar files, now the server doesnot even run. tellme what
to do now???
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
kindly tell me how can i check that the class paths for driver jarfiles are included
in that string? thanks. also tell me can not i use the jdriver forsql server
2000?.The startup script will echo what it's doing, including printing out
the classpath
it will use. Yes you can use the jDriver for MS SQL2000. It is sufficient
for
basic JDBC, but the MS drivfer is preferable in some ways.
Joe
Joseph Weinstein <[email protected]_this> wrote:
khabbab wrote:
i am using bea weblogic server 6.1, i cant create connection
pool
while
using MS
SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft
website.
when
i give the following class name for JDBC driver and the connectionurl and click
apply while selecting the available server, a number of exception
appears
in default
server (that is the connection pool cannot be created..... cannot
load
the driver
class).The server startup script creates a string that will become the
classpath
for the server.
This string is part of the java call to start the server with a-classpath
argument. You need to
make sure the MS driver jars are part of that classpath string.
Joe
URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
when i use the above setting in a JDBC simple applicationin Jbuilder
7.0 the application runs successfully and fetches the data deom
MS
SQL database
but in at Bea connection Pool is not created with these settings.
i
do give appropriate
username and password in properties field in connection pool.
Thankx
for any help!
Maybe you are looking for
-
Nokia N8-00 upgrade to Nokia Belle gives confusing...
During the upgrade process I receive a warning message telling me: "Don't use the mobile N8-00, shut ift off, or remove the cable or the unit will stop working". So, therefore I tried to shut it off. Immidiately I receive an errormessage telling me t
-
How can I change the Slideshow in iWeb 08???
I've searched and searched and don't see to find an answer - I used to swap out slide show assets in iWeb 06 for a much better way of navigating through my photos. That's no longer an option in 08 - anyone have any alternative slideshows for 08? In 0
-
Can I make "High Priority" default - or is there a script?
Hi, When sending an email, is there a way to choose to mark the message as "High Priority" without having to go up the the "Message" menu to do so? If there isn't a keyboard shortcut, is there a script out there anywhere that can do that? Patrick
-
Will Not Open To Most Recently Used Folder
I figured out how to save in the same file, but PS still opens some default folder beginning with "THIS PC", instead of the most recently used folder. It should open to the most recently used folder. How do I set that?
-
Westell 327w and Wireless Access Point
I had DSL last year, but have since changed to FIOS, which I love. So I have the Westell 327W modem/router that isn't being used. I have decided to use it in another project for the 4 port ethernet and the wireless capability. As this other project