[JBoss-dev] jboss-head Build Failed

[kimptoc_mail]

View results here -> http://tck2.jboss.com/cc/?log=log20040420080736

BUILD FAILED

Ant Error Message: file:/home/build/cruisecontrol/work/scripts/build-jboss-head.xml:55: exec returned: -122

Date of build: 04/20/2004 08:07:36

Time to build: 22 minutes 17 seconds

Last changed: 04/20/2004 07:42:53

Last log entry: Fix two horrible bugs in the <check-valid-connection-sql> interaction with the pool.1) It was attempting to destroy the connections twice which completely broke the connection countingleading to <min-pool-size> overfilling the pool when configured2) In the same code path, it was releasing the permit twice, allow an extra thread to gain access to the pool

Unit Tests: (0)

No Tests Run

This project doesn't have any tests

Modifications since last build:  (3)
modified	ejort	connector/src/main/org/jboss/resource/connectionmanager/BaseConnectionManager2.java	Fix two horrible bugs in the <check-valid-connection-sql> interaction with the pool.1) It was attempting to destroy the connections twice which completely broke the connection countingleading to <min-pool-size> overfilling the pool when configured2) In the same code path, it was releasing the permit twice, allow an extra thread to gain access to the pool
modified	ejort	connector/src/main/org/jboss/resource/connectionmanager/ConnectionListener.java	Fix two horrible bugs in the <check-valid-connection-sql> interaction with the pool.1) It was attempting to destroy the connections twice which completely broke the connection countingleading to <min-pool-size> overfilling the pool when configured2) In the same code path, it was releasing the permit twice, allow an extra thread to gain access to the pool
modified	ejort	connector/src/main/org/jboss/resource/connectionmanager/InternalManagedConnectionPool.java	Fix two horrible bugs in the <check-valid-connection-sql> interaction with the pool.1) It was attempting to destroy the connections twice which completely broke the connection countingleading to <min-pool-size> overfilling the pool when configured2) In the same code path, it was releasing the permit twice, allow an extra thread to gain access to the pool