[
https://issues.apache.org/jira/browse/DBCP-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed DBCP-419.
----------------------------
Resolution: Invalid
This looks like normal behavior to me. This appears to be part of a thread
dump showing one thread holding a lock. Please use the Commons User list to
ask usage questions. If you can demonstrate a deadlock or other actual bug,
feel free to reopen. Also, it would be a good idea to upgrade to a less
ancient version of DBCP.
> Thread got locked while getting connection for MSSQLServer 2008DB
> -----------------------------------------------------------------
>
> Key: DBCP-419
> URL: https://issues.apache.org/jira/browse/DBCP-419
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: AIX, JDK1.7
> Reporter: Santhosh Daida
> Priority: Blocker
>
> Below exception was seen in getting connection for MSSQLServer 2008
> pool-3-thread-17" prio=10 tid=0x00002aaac0158000 nid=0x4cb7 in Object.wait()
> [0x0000000043d77000]
> java.lang.Thread.State: RUNNABLE
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Unknown Source)
> at
> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1130)
> - locked <0x000000078002b498> (a
> org.apache.commons.dbcp.BasicDataSource)
> at
> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
> --------------------
> My application needs only one connection for every 60 seconds and I am using
> default properties of BasicDataSource.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
