Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F0837E493 for ; Tue, 22 Jan 2013 07:54:15 +0000 (UTC) Received: (qmail 2849 invoked by uid 500); 22 Jan 2013 07:54:14 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 2686 invoked by uid 500); 22 Jan 2013 07:54:14 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 2631 invoked by uid 99); 22 Jan 2013 07:54:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jan 2013 07:54:13 +0000 Date: Tue, 22 Jan 2013 07:54:13 +0000 (UTC) From: "steve lee (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DBCP-395) Please help.. Is it over connected or stucked? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DBCP-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steve lee updated DBCP-395: --------------------------- Summary: Please help.. Is it over connected or stucked? (was: Please help.. Is it over connect or stucked?) > Please help.. Is it over connected or stucked? > ---------------------------------------------- > > Key: DBCP-395 > URL: https://issues.apache.org/jira/browse/DBCP-395 > Project: Commons Dbcp > Issue Type: Bug > Affects Versions: 1.2.1 > Environment: OS : Ubuntu 11.10 > JDK : 1.6 > Database : Oracle 10g > JDBC Driver : oracle jdbc driver type 4 > DB Commits per secs : 600 > Reporter: steve lee > Attachments: epmailer.out_ > > > We had ran email sendding system over 10 years. Recently we had oracle connection problem. We have 8 servers and all servers had same problem. > My system's thread dump is following. I appreciate any helps. Thanks. > ... > "Thread-6293" daemon prio=10 tid=0x00007f65cc35e800 nid=0x637c waiting for monitor entry [0x00007f65c6e3b000] > java.lang.Thread.State: BLOCKED (on object monitor) > at ep.server.epmailer.util.EPPoolingDataSource.getConnection(EPPoolingDataSource.java:72) > - waiting to lock <0x00000000fb430c20> (a java.lang.Class for ep.server.epmailer.util.EPPoolingDataSource) > at ep.server.epmailer.EPMailSenderThread.checkOtherMailerStatus(EPMailSenderThread.java:2799) > at ep.server.epmailer.EPMailSenderThread.run(EPMailSenderThread.java:438) > at java.lang.Thread.run(Thread.java:662) > "Thread-6292" daemon prio=10 tid=0x00007f65cc35d800 nid=0x637b waiting for monitor entry [0x00007f65beab4000] > java.lang.Thread.State: BLOCKED (on object monitor) > at ep.server.epmailer.util.EPPoolingDataSource.getConnection(EPPoolingDataSource.java:72) > - waiting to lock <0x00000000fb430c20> (a java.lang.Class for ep.server.epmailer.util.EPPoolingDataSource) > at ep.server.epmailer.EPMailSenderThread.updateSuccessMail(EPMailSenderThread.java:2597) > at ep.server.epmailer.EPMailSenderThread.run(EPMailSenderThread.java:330) > at java.lang.Thread.run(Thread.java:662) > "Thread-6291" daemon prio=10 tid=0x00007f65cc80c000 nid=0x6377 runnable [0x00007f65beaf4000] > java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at oracle.net.ns.Packet.receive(Unknown Source) > at oracle.net.ns.NSProtocol.connect(Unknown Source) > at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:844) > at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:268) > at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:414) > at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:165) > at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35) > at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801) > at java.sql.DriverManager.getConnection(DriverManager.java:582) > at java.sql.DriverManager.getConnection(DriverManager.java:185) > at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:48) > at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) > - locked <0x00000000c231e9a8> (a org.apache.commons.dbcp.PoolableConnectionFactory) > at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771) > at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) > at ep.server.epmailer.util.EPPoolingDataSource.getConnection(EPPoolingDataSource.java:75) > - locked <0x00000000fb430c20> (a java.lang.Class for ep.server.epmailer.util.EPPoolingDataSource) > at ep.server.epmailer.EPMailSenderThread.checkOtherMailerStatus(EPMailSenderThread.java:2799) > at ep.server.epmailer.EPMailSenderThread.run(EPMailSenderThread.java:438) > at java.lang.Thread.run(Thread.java:662) > "Thread-6290" daemon prio=10 tid=0x00007f65cc1b8800 nid=0x6376 waiting for monitor entry [0x00007f65c68e6000] > java.lang.Thread.State: BLOCKED (on object monitor) > at ep.server.epmailer.util.EPPoolingDataSource.getConnection(EPPoolingDataSource.java:72) > - waiting to lock <0x00000000fb430c20> (a java.lang.Class for ep.server.epmailer.util.EPPoolingDataSource) > at ep.server.epmailer.EPMailSenderThread.checkOtherMailerStatus(EPMailSenderThread.java:2799) > at ep.server.epmailer.EPMailSenderThread.run(EPMailSenderThread.java:438) > at java.lang.Thread.run(Thread.java:662) > "Thread-6289" daemon prio=10 tid=0x00007f65cc318800 nid=0x6375 waiting for monitor entry [0x00007f65bebb8000] > java.lang.Thread.State: BLOCKED (on object monitor) > at ep.server.epmailer.util.EPPoolingDataSource.getConnection(EPPoolingDataSource.java:72) > - waiting to lock <0x00000000fb430c20> (a java.lang.Class for ep.server.epmailer.util.EPPoolingDataSource) > at ep.server.epmailer.EPMailSenderThread.updateRecvTable(EPMailSenderThread.java:2943) > at ep.server.epmailer.EPMailSenderThread.run(EPMailSenderThread.java:463) > at java.lang.Thread.run(Thread.java:662) > ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira