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
Similar Messages
-
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:420Hi 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 -
Connection Pool refresh with weblogic
Hi,
In my application when weblogic starts up it creates connection
pools and uses it later. If the connection is lost it refreshes in regular interval
and it's fine.
The problem I am facing:
If the database connectivity is not there when the weblogic
starts very first time and later the database connectivity
comes back my connection will not refresh.
Any ideas???????Hi,
In my application when weblogic starts up it creates connection
pools and uses it later. If the connection is lost it refreshes in regular interval
and it's fine.
The problem I am facing:
If the database connectivity is not there when the weblogic
starts very first time and later the database connectivity
comes back my connection will not refresh.
Any ideas??????? -
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 -
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. -
Problems with weblogic clustering in 6.1 sp3
We have spent a lot of time trying to get our application deployed to
a cluster using weblogic 6.1 sp3 and we consistently receive a failure
when we attempt to start the managed server. This was not a problem
with weblogic sp1--we got our application to deploy to the cluster
successfully; although there was another weblogic bug there with
clients accessing EJB clusters--we won't go into that here...
We have tried this on both a Windows 2000 machine and an HP machine
running weblogic sp3. The same error occurs on both platforms.
The error in deploying our application to the cluster against weblogic
sp3 looks to have to do with our custom security realm. Inside our
custom realm we make use of a configurable providerUrl which we set to
the cluster address/port. The custom realm makes a call where it
passes in the providerUrl to:
weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
When we have our providerUrl set to the cluster address/port--e.g.,
t3://clustermember1:7001
and attempt to start the managed server we get the error:
Starting WebLogic Server ....
Connecting to http://adminserver:7117...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException:
clustermember1 not found
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
at weblogic.management.Admin.initialize(Admin.java:340)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
When we have our providerUrl set to the admin server address--e.g.,
t3://adminserver:7117
everything starts up fine.
Does anyone know why this would work on sp1 and not sp3 of weblogic
6.1?
We verified that all passwords are correct and everything else we
could determine--any ideas would be helpful.
We don't want the providerUrl to point at our admin server, we want it
to point at the cluster address/port.
When we get the managed server error, we received this error on the
AdminServer:
2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
Caught naming exception null; throwing RuntimeException.
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to
destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:307)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(GabrielRealm.java:416)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRealm.java:347)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.java:51)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:225)
at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(GabrielRealm.java:578)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:221)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
<[WebAppServletContext(8091823,wl_management_internal2,/wl_management_internal2)]
Servlet failed with Exception
java.lang.RuntimeException
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:260)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Thanks for any help.
Rich
Bottom line:
In our custom realm we were not handling user guest correctly. Even if you
have guest user disabled, Weblogic seems to have hard-coded guest to
send messages to the cluster every-so-often. Not sure there--couldn't get
an answer out of bea as to exactly why we see guest still being used...
It seems that with sp3, the user guest interaction started happening earlier
than it did with sp1, consequently making our realm code fail when trying to
retrieve the guest user like someone we knew about in our system.
Hence, our getUser and authUserPassword methods now return null for both
users guest and system, making the secondary realm (file realm) be used to
authenticate and resolve guest & system. BEA helped get our code fixed;
however, we still don't have a lot of depth in understanding Weblogic
server's use of guest...
Apparently, in 7.x the guest & system user behavior and configuration is
different also... We'll see when we start digging into that migration.
Rich
[email protected] (Rich Koch) wrote in message news:<[email protected]>...
> Thanks for the responses--we're working with weblogic support now. We
> think that the custom realm that we have [the developer that wrote it
> left the company] is the problem.
>
> The original developer was told by someone to check:
> weblogic.security.acl.internal.ClusterRealm.THE_ONE != null
>
> In order to determine if the JNDI was available/ready for the whole
> cluster.
>
> It seems that the meaning/setting of THE_ONE changed with this respect
> from
> sp1 to sp3--i.e., this is no longer a valid test to tell us if the
> JNDI is
> ready for the cluster.
>
> We believe this was used because the 'system' user has to be
> authenticated before the custom realm is up. Originally, before this
> check was in place, an exception was received when authenticating
> 'system'. This appears to be a weblogic limitation/issue. Support
> has told us that this is different in weblogic 7.0. Unfortunately, we
> can't upgrade from 6.1 yet.
>
> We'll post the solution when this gets figured out.
>
> Rak
>
> "Sabha" <[email protected]> wrote in message news:<[email protected]>...
> > There was a security restriction enforced from sp2/sp3 onwards in terms of
> > looking up mbeans from admin server.
> >
> > This might cause things to fail if you are attempting to lookup Mbeans with
> > guest priviliges from admin server. Also, can you try doing the following:
> >
> > Run " java weblogic.Admin -url adminServer -username system -password
> > .... -GET -pretty -type Server" and check whether the named clustermember1
> > is available in the list or not.
> >
> > Also you seem to be getting some security exception - can you check that.
> >
> > t3://tomtate.msais.com:7119: Destination
> > unreachable; nested exception is:
> >
> > --- Try running weblogic.Admin PING on this one and see whether you are
> > able to reach this server upon the error message.
> >
> > --Sabha
> >
> > "Rich Koch" <[email protected]> wrote in message
> > news:[email protected]...
> > > We have spent a lot of time trying to get our application deployed to
> > > a cluster using weblogic 6.1 sp3 and we consistently receive a failure
> > > when we attempt to start the managed server. This was not a problem
> > > with weblogic sp1--we got our application to deploy to the cluster
> > > successfully; although there was another weblogic bug there with
> > > clients accessing EJB clusters--we won't go into that here...
> > >
> > > We have tried this on both a Windows 2000 machine and an HP machine
> > > running weblogic sp3. The same error occurs on both platforms.
> > >
> > > The error in deploying our application to the cluster against weblogic
> > > sp3 looks to have to do with our custom security realm. Inside our
> > > custom realm we make use of a configurable providerUrl which we set to
> > > the cluster address/port. The custom realm makes a call where it
> > > passes in the providerUrl to:
> > > weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
> > >
> > > When we have our providerUrl set to the cluster address/port--e.g.,
> > > t3://clustermember1:7001
> > >
> > > and attempt to start the managed server we get the error:
> > >
> > > Starting WebLogic Server ....
> > > Connecting to http://adminserver:7117...
> > >
> ***************************************************************************
> > > The WebLogic Server did not start up properly.
> > > Exception raised:
> > > weblogic.management.configuration.ConfigurationException:
> > > clustermember1 not found
> > > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
> > > at weblogic.management.Admin.initialize(Admin.java:340)
> > > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
> > > at weblogic.Server.main(Server.java:35)
> > > Reason: Fatal initialization exception
> > >
> ***************************************************************************
> > >
> > > When we have our providerUrl set to the admin server address--e.g.,
> > > t3://adminserver:7117
> > >
> > > everything starts up fine.
> > >
> > > Does anyone know why this would work on sp1 and not sp3 of weblogic
> > > 6.1?
> > > We verified that all passwords are correct and everything else we
> > > could determine--any ideas would be helpful.
> > >
> > > We don't want the providerUrl to point at our admin server, we want it
> > > to point at the cluster address/port.
> > >
> > > When we get the managed server error, we received this error on the
> > > AdminServer:
> > >
> > > 2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
> > > 'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
> > > Caught naming exception null; throwing RuntimeException.
> > > javax.naming.CommunicationException. Root exception is
> > > java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
> > > unreachable; nested exception is:
> > > java.net.ConnectException: Connection refused; No available router to
> > > destination
> > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
> > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
> > > at
> > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:307)
> > > at
> > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:211)
> > > at
> > weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
> > ory.java:149)
> > > at
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
> > > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
> > > at javax.naming.InitialContext.init(InitialContext.java:222)
> > > at javax.naming.InitialContext.<init>(InitialContext.java:198)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(Gabriel
> > Realm.java:416)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRea
> > lm.java:347)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.
> > java:51)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:
> > 225)
> > > at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(Gabriel
> > Realm.java:578)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
> > a:221)
> > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
> > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
> > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
> > > at
> > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
> > ava:356)
> > > at
> > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
> > tSecurityManager.java:205)
> > > at
> > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
> > ntext.java:2518)
> > > at
> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
> > :2260)
> > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> > > <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
> > >
> > <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_intern
> > al2)]
> > > Servlet failed with Exception
> > > java.lang.RuntimeException
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
> > a:260)
> > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
> > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
> > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
> > > at
> > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
> > ava:356)
> > > at
> > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
> > tSecurityManager.java:205)
> > > at
> > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
> > ntext.java:2518)
> > > at
> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
> > :2260)
> > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> > >
> > >
> > > Thanks for any help.
> > >
> > > Rich
-
Connection pool issues with Mysql
Hi,
I have defined sufficient read connections (50) in the toplink configuration, I am finding toplink is not releasing the connections in Mysql, this is when run from Jboss App server.
Is anyone aware of toplink connection pool issues with MySql?
thanksTopLink always closes connections, I cannot see how this could occur.
Please include your persistence.xml or sessions.xml. Also ensure you are closing your EntityManager or ClientSession, especially if using exclusive connections.
Also include the exception you are getting.
James : http://www.eclipselink.org -
Problem with Weblogic Builder SP1
I have a problem with Weblogic Builder SP1. I basically re-used my EJB deployment
descriptors from WL5.1 in WL8.1. Before SP1, i have no problem loading my EJB
in WB. But with SP1, WB throws weblogic.marathon.model.LoadFailureException.
I re-attempted by jarring my EJB with WL5.1 descriptors and used my friend's WB
(not SP1) to export new descriptors which I used to re-jar. This new EJB is again
not recognised by WB SP1?
What is wrong?The exception is as follows:
Opening module myproj.jar
java.lang.NullPointerException
at java.util.Arrays.sort(Arrays.java:1181)
at weblogic.marathon.model.EJBJarCMBean.initRelations(EJBJarCMBean.java:1212)
at weblogic.marathon.model.EJBJarCMBean.initBeans(EJBJarCMBean.java:1098)
at weblogic.marathon.model.EJBJarCMBean.setup(EJBJarCMBean.java:1144)
at weblogic.marathon.tasks.OpenModuleTask.getEJBModule(OpenModuleTask.java:156)
at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:191)
at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:230)
at weblogic.marathon.tasks.OpenModuleTask.runBackground(OpenModuleTask.java:89)
at weblogic.tools.jellybeans.core.task.TaskThread.execute(TaskThread.java:127)
at weblogic.tools.jellybeans.core.task.TaskThread.run(TaskThread.java:64)
Module myproj.jar descriptors failed to load
The EJB has no problem deploying.
Rob Woollen <[email protected]> wrote:
You'll have to at least show us the error you get from marathon.
Does your application deploy to the server?
-- Rob
Robin Tan wrote:
I have a problem with Weblogic Builder SP1. I basically re-used myEJB deployment
descriptors from WL5.1 in WL8.1. Before SP1, i have no problem loadingmy EJB
in WB. But with SP1, WB throws weblogic.marathon.model.LoadFailureException.
I re-attempted by jarring my EJB with WL5.1 descriptors and used myfriend's WB
(not SP1) to export new descriptors which I used to re-jar. This newEJB is again
not recognised by WB SP1?
What is wrong? -
Problem with weblogic.Deployer in 8.1
I have a problem with weblogic.Deployer. My application deploys and works fine
if I manually copy the ear or the exploded form into weblogic's applications\
directory (hot deployment). But, if I use the weblogic.Deployer tool, it fails
with the following exception. Does the deployer tool expect something in the ear
(or exploded form) that I'm missing? Thanks in advance.
-Vas
[wldeploy] java.lang.NullPointerException
[wldeploy] at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGener
ator.java:785)
[wldeploy] at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerato
r.java:758)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:803)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] --------------- nested within: ------------------
[wldeploy] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Failed
to generate class for weblogic.common.internal.RMIBootServiceImpl_811_WLStub ]
with nested exception:
[wldeploy] [java.lang.NullPointerException]
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:807)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] java.lang.reflect.InvocationTargetException
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] Caused by: weblogic.utils.AssertionError: ***** ASSERTION FAILED ***
**[ Failed to generate class for weblogic.common.internal.RMIBootServiceImpl_811
_WLStub ] - with nested exception:
[wldeploy] [java.lang.NullPointerException]
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:807)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] ... 15 moreHi Deepak,
I didn't understand the suggested resolution. Can you tell me what it means?
However, I found a similar problem in the archives, so I tried from command line
(outside ant) using "java weblogic.Delployer ...." and it worked! It doesn't work
from ant. So, you think there's some conflict between my ant and weblogic's ant
task "WLDdeploy"?
Thanks,
Vas
"Deepak Vohra" <[email protected]> wrote:
>
Refer to
http://e-docs.bea.com/wls/docs70/notes/resolved.html#1296363
"vas pulipati" <[email protected]> wrote:
I have a problem with weblogic.Deployer. My application deploys andworks
fine
if I manually copy the ear or the exploded form into weblogic's applications\
directory (hot deployment). But, if I use the weblogic.Deployer tool,
it fails
with the following exception. Does the deployer tool expect something
in the ear
(or exploded form) that I'm missing? Thanks in advance.
-Vas
[wldeploy] java.lang.NullPointerException
[wldeploy] at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGener
ator.java:785)
[wldeploy] at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerato
r.java:758)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:803)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] --------------- nested within: ------------------
[wldeploy] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Failed
to generate class for weblogic.common.internal.RMIBootServiceImpl_811_WLStub
with nested exception:
[wldeploy] [java.lang.NullPointerException]
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:807)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] java.lang.reflect.InvocationTargetException
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] Caused by: weblogic.utils.AssertionError: ***** ASSERTION
FAILED ***
**[ Failed to generate class for weblogic.common.internal.RMIBootServiceImpl_811
_WLStub ] - with nested exception:
[wldeploy] [java.lang.NullPointerException]
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:807)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] ... 15 more -
I have 2 ipads 1st ipad 2G and ipad 3G whats the problem with the 3G ipad the wifi is now getting connected to the wifi modem and the ipad 2G is getting connected no problem with the 2G ipad what should i do...????? And I had checked with my iball baton router with the iball sevice provider.
Hi there Paula120,
You may find the troubleshooting steps in the article below helpful.
iOS: Device not recognized in iTunes for Windows
http://support.apple.com/kb/ts1538
-Griff W. -
Connection pooling problem in TopLink with JBoss4.0.3
Hi All
I am using JBoss4.0.3SP1 with TopLink-10g(9.0.4.5) and Sybase as database. I am implementing connection pooling of JBoss with Sybase. I have done all the changes in JBoss mapping files.
Now to enable connection pooling in TopLink I have set the <uses-external-connection-pooling> attribute in sessions.xml file to true and I have added <datasource> attribute corresponding to the datasource defined in JBoss. It is working fine but when I delete the username, password...etc attribute from the sessions.xml then I am not able to get the session from datasource.
Can anyone tell me what to do or where I am making mistake? Any help on this will be appreciatedI tried that code also but the project object that I am getting is null which is in this line
DatabaseLogin login = (DatabaseLogin)mySession.getProject().getLogin();
mySession is an object of oracle.toplink.sessions.Session interface but when I call this method then it returns me a null object of Project class, so I am getting NullPointerException error. I tried to do this stuff by many ways but I am always getting the NullPointereException in setLogin() method of Session. This is the stackTrace of the error.....
java.lang.NullPointerException
at oracle.toplink.publicinterface.Session.setLogin(Session.java:2871)
at com.test.TestCon.executeQurey(TestCon.java:91)
at org.apache.jsp.Test_jsp._jspService(org.apache.jsp.Test_jsp:55)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Unknown Source)
Can you please tell me where I am wrong or any other way to do fix this problem. -
Problem with Weblogic 9.1 JDBC connection pooling
Hi,
We are currently in the middle of a migration from JBoss & WAS to BEA Weblogic. Both in JBoss and Websphere there are no problems with the connection but in Weblogic we (quickly) run out of connections.
Our project uses Hibernate 3.1.3, Spring 1.2.7 and EJB 2.1. Using CMT and Spring to connect to our Oracle database. We tried different using the different drivers Weblogic offers, XA and non-AX, but in all cases we create connections quickly but they are almost never closed... until we run out of connections and get a Exception.
Any ideas what this could be? Are there known errors?Roy van Rijn wrote:
Hi,
We are currently in the middle of a migration from JBoss & WAS to BEA Weblogic. Both in JBoss and Websphere there are no problems with the connection but in Weblogic we (quickly) run out of connections.
Our project uses Hibernate 3.1.3, Spring 1.2.7 and EJB 2.1. Using CMT and Spring to connect to our Oracle database. We tried different using the different drivers Weblogic offers, XA and non-AX, but in all cases we create connections quickly but they are almost never closed... until we run out of connections and get a Exception.
Any ideas what this could be? Are there known errors?Hi. Please try setting the pool's idle-connection-timeout to 10 seconds or something
reasonable, and we'll forcibly retract any leaked connections. So you don't write any
JDBC code yourself, right?
Joe -
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 -
Oracle connection pool problem (dbcp binded with jtom)
Hi,
my webserver is Tomcat5.0.18, I want to offer the connection pool and transaction management
in my currently system
I know in Tomcat5.0 version, we can use the DBCP to offer the database connection pool
service, to apply the transaction management in my system, I adapt the JTOM
now, my problem is
to use DBCP, I setup the datasource factory to be
org.apache.commons.dbcp.BasicDataSourceFactory, the connection pool is ok, but
the transaction management offerred by JTOM will failure
to make the tranaction management of JTOM succeed, I have to setup the datasource factory to be
org.objectweb.jndi.DataSourceFactory, but the connection pool offerred by Tomcat will failure now
it seems that these two datasource factory has conflict
How can I do?, I don't want to use the connection pool offerred in JTOM
Anyone can help me??
Thanks in advanceHi,
I don't know the solution for JOTM, but you could try this JTA and its connection pools:
http://www.atomikos.com ships a JTA that integrates with Tomcat and also provides JDBC connection pooling. There is a GUI control panel so that you don't have to know the XML details for Tomcat's config files.
Best,
Guy -
Oracle 8.1.5 database connection problem with WebLogic 5.1
Hello,
the NSAPI integration works, also the JSP files.
But I have still problems with the Jdriver for my Oracle 8.1.5.
I get the message :
Failed to invoke startup class
weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.JdbcStartup
when the WebLogic Server is started.
Any ideas or hints about that?
Thanks in advance
ArminPost the full stacktrace here
Also you might want to post jdbc related questions to weblogic.developer.
interest.jdbc
Kumar
DreamNEON wrote:
Hello,
the NSAPI integration works, also the JSP files.
But I have still problems with the Jdriver for my Oracle 8.1.5.
I get the message :
Failed to invoke startup class
weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.JdbcStartup
when the WebLogic Server is started.
Any ideas or hints about that?
Thanks in advance
Armin
Maybe you are looking for
-
ORA-01722: INVALID NUMBER ERROR THROWN in suppliers accounting page
Hi, I am facing an issue in the suppliers page. After querying for a supplier, I am click on the update icon to go to the details page. In this page whenver i click on Acounting link in the left side menu, i am getting the following error. ("java.sql
-
Selected file failed to open as a PDF error .. on ARES 7.0
I am trying to enable some reader features using Adobe LiveCycle Reader Ex 7.0 but when I upload the pdf file i got this message "Error 442: Selected file failed to open as a PDF 'com.adobe.document.pdf.PDFOperationFailure: IDL:com/adobe/document/pdf
-
I have installed JRun 4 Web Server and Java 2 SDK, SE v1.4.1_01. When i import servlet import javax.servlet.*;There is an error message. Package javax.servlet does not exist. Please help me, maybe i haven't had package javax.servlet. What do i need t
-
I've installed vista on a few 24" iMacs. The sound produced under vista is just terrible (metallic echo), on all of them. I've used the drivers delivered with OSX 10.5.0. Are ther any better drivers or any settings that produce better audio? btw. The
-
Should Enhanced Turbo still work on H87-G43 for non-k i7-4770?
Having a similar issue to the one described here ( https://forum-en.msi.com/index.php?topic=172887.msg1258722#msg1258722 ) but this is on a H87-G43 with a non-k i7-4770. The feature used to work fine with all 4 cores going to 3.9 GHz on turbo but, wi