openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Jenkins Server <jenk...@builds.apache.org>
Subject Build failed in Jenkins: OpenJPA-trunk #701
Date Thu, 26 Apr 2012 18:16:02 GMT
See <https://builds.apache.org/job/OpenJPA-trunk/701/changes>

Changes:

[struberg] OPENJPA-2178 switch Date PostgreSQL preci from CENTI to MICRO

We looked at the PostgreSQL documentation back to pgsql-6.3 (1998)
and all versions since then can deal with microseconds for TIMESTAMP 
fields.

------------------------------------------
[...truncated 20770 lines...]
86  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
86  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEJoinCon(410)
with PESSIMISTIC_WRITE lock
87  locking-test  WARN   [main] openjpa.Runtime - "javax.persistence.lock.scope" is not a
supported query hint. May be you meant "javax.persistence.lock.timeout"?
87  locking-test  WARN   [main] openjpa.Runtime - "javax.persistence.lock.scope" is not a
supported query hint. May be you meant "javax.persistence.lock.timeout"?
88  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t0.id, t1.version, t1.firstName, t0.lastName FROM LSEJoinCon t0 INNER JOIN
LSEJoinAbs t1 ON t0.id = t1.id WHERE (t1.firstName LIKE ? ESCAPE '\')" 
89  locking-test  INFO   [main] Tests -  *Found 1 entity
92  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEJoinCon@1c7d395org.apache.openjpa.persistence.lock.extended.LSEJoinCon@1c7d395[id=410,
ver=1] first=firstName 410, last=lastName 410
92  locking-test  INFO   [main] Tests -  *Ensure ReadLockLevel remains at level READ
92  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEJoinCon(411)
with no lock to verify query lock set does not affect em lock mode.
92  locking-test  INFO   [main] Tests -  *Find an entity
92  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEJoinCon@3a3b6borg.apache.openjpa.persistence.lock.extended.LSEJoinCon@3a3b6b[id=411,
ver=2] first=firstName 411, last=lastName 411
92  locking-test  INFO   [main] Tests - Committing transaction.
1  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
0  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
12  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.3.0-SNAPSHOT
225  locking-test  INFO   [main] Tests - ** testNormalElementCollectionLock()
239  locking-test  INFO   [main] Tests - ** testNormalElementCollectionLock()
239  locking-test  INFO   [main] Tests - -- Test find with no lock in Normal scope
239  locking-test  INFO   [main] Tests -  *Begin a transaction.
239  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(500)
with no lock
243  locking-test  INFO   [main] Tests -  *Find entity
247  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@12515db[id=500,
ver=1, firstName=firstName lazy 500] one=[500String1, 500String2]
247  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(501)
with pessimistic force increment lock
253  locking-test  INFO   [main] Tests -  *Find entity
253  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@c5d3b8[id=501,
ver=1, firstName=lazy 501] one=[501String1, 501String2]
253  locking-test  INFO   [main] Tests - Committing transaction.
265  locking-test  INFO   [main] Tests - -- Test query with pessimistic read lock in Normal
scope
265  locking-test  INFO   [main] Tests -  *Begin a transaction.
265  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
266  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleCol(500)
with PESSIMISTIC_READ lock
272  locking-test  INFO   [main] Tests -  *Found 1 entity
273  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@b88d29[id=500,
ver=1, firstName=firstName lazy 500] one=[500String1, 500String2]
273  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(501)
with no lock to verify query lock set does not affect em lock mode.
273  locking-test  INFO   [main] Tests -  *Find entity
273  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@143b598[id=501,
ver=2, firstName=lazy 501] one=[501String1, 501String2]
274  locking-test  INFO   [main] Tests - Committing transaction.
274  locking-test  INFO   [main] Tests - -- Test name query with pessimistic write lock in
Normal scope
274  locking-test  INFO   [main] Tests -  *Begin a transaction.
274  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
274  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleCol(500)
with PESSIMISTIC_WRITE lock
275  locking-test  INFO   [main] Tests -  *Found 1 entity
276  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@1d0740e[id=500,
ver=1, firstName=firstName lazy 500] one=[500String1, 500String2]
276  locking-test  INFO   [main] Tests -  *Ensure ReadLockLevel remains at level READ
276  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(501)
with no lock to verify query lock set does not affect em lock mode.
276  locking-test  INFO   [main] Tests -  *Find an entity
276  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@1e77a3e[id=501,
ver=2, firstName=lazy 501] one=[501String1, 501String2]
277  locking-test  INFO   [main] Tests - Committing transaction.
0  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
0  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
12  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.3.0-SNAPSHOT
58  locking-test  INFO   [main] Tests - ** testExtendedElementCollectionLock()
64  locking-test  INFO   [main] Tests - ** testExtendedElementCollectionLock()
64  locking-test  INFO   [main] Tests - -- Test find with no lock in Extended scope
64  locking-test  INFO   [main] Tests -  *Begin a transaction.
64  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(510)
with no lock
65  locking-test  INFO   [main] Tests -  *Find entity
65  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@f9e8eb[id=510,
ver=1, firstName=firstName lazy 510] one=[510String1, 510String2]
65  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(511)
with pessimistic force increment lock
66  locking-test  INFO   [main] Tests -  *Find entity
67  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@15a3dac[id=511,
ver=1, firstName=lazy 511] one=[511String1, 511String2]
67  locking-test  INFO   [main] Tests - Committing transaction.
76  locking-test  INFO   [main] Tests - -- Test query with pessimistic read lock in Extended
scope
76  locking-test  INFO   [main] Tests -  *Begin a transaction.
76  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
76  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleCol(510)
with PESSIMISTIC_READ lock
78  locking-test  WARN   [main] openjpa.Runtime - "javax.persistence.lock.scope" is not a
supported query hint. May be you meant "javax.persistence.lock.timeout"?
79  locking-test  INFO   [main] Tests -  *Found 1 entity
79  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@c5b47d[id=510,
ver=1, firstName=firstName lazy 510] one=[510String1, 510String2]
79  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(511)
with no lock to verify query lock set does not affect em lock mode.
80  locking-test  INFO   [main] Tests -  *Find entity
80  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@971770[id=511,
ver=2, firstName=lazy 511] one=[511String1, 511String2]
80  locking-test  INFO   [main] Tests - Committing transaction.
80  locking-test  INFO   [main] Tests - -- Test name query with pessimistic write lock in
Extended scope
81  locking-test  INFO   [main] Tests -  *Begin a transaction.
81  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
81  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleCol(510)
with PESSIMISTIC_WRITE lock
81  locking-test  WARN   [main] openjpa.Runtime - "javax.persistence.lock.scope" is not a
supported query hint. May be you meant "javax.persistence.lock.timeout"?
82  locking-test  WARN   [main] openjpa.Runtime - "javax.persistence.lock.scope" is not a
supported query hint. May be you meant "javax.persistence.lock.timeout"?
83  locking-test  INFO   [main] Tests -  *Found 1 entity
83  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@1c76b4c[id=510,
ver=1, firstName=firstName lazy 510] one=[510String1, 510String2]
83  locking-test  INFO   [main] Tests -  *Ensure ReadLockLevel remains at level READ
83  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(511)
with no lock to verify query lock set does not affect em lock mode.
83  locking-test  INFO   [main] Tests -  *Find an entity
84  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@1e3728[id=511,
ver=2, firstName=lazy 511] one=[511String1, 511String2]
84  locking-test  INFO   [main] Tests - Committing transaction.
1  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
1  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
12  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.3.0-SNAPSHOT
58  locking-test  INFO   [main] Tests - ** testNormalElementCollectionEagerLock()
69  locking-test  INFO   [main] Tests - ** testNormalElementCollectionEagerLock()
69  locking-test  INFO   [main] Tests - -- Test find with no lock in Normal scope
69  locking-test  INFO   [main] Tests -  *Begin a transaction.
69  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(600)
with no lock
75  locking-test  INFO   [main] Tests -  *Find entity
75  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@1f35106[id=600,
ver=1, firstName=firstName eager 600] one=[600String2, 600String1]
75  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(601)
with pessimistic force increment lock
75  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t0.version, t0.firstName, t1.LSEELECOLEGR_ID, t1.element FROM LSEEleColEgr t0 LEFT
OUTER JOIN LSEEleColEgr_collection t1 ON t0.id = t1.LSEELECOLEGR_ID WHERE t0.id = ?" 
82  locking-test  INFO   [main] Tests -  *Find entity
82  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@1435263[id=601,
ver=1, firstName=firstName eager 601] one=[601String2, 601String1]
82  locking-test  INFO   [main] Tests - Committing transaction.
91  locking-test  INFO   [main] Tests - -- Test query with pessimistic read lock in Normal
scope
91  locking-test  INFO   [main] Tests -  *Begin a transaction.
91  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
91  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(600)
with PESSIMISTIC_READ lock
98  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t0.id, t1.element FROM LSEEleColEgr t0 INNER JOIN LSEEleColEgr_collection t1 ON t0.id
= t1.LSEELECOLEGR_ID WHERE (t0.firstName LIKE ? ESCAPE '\') ORDER BY t0.id ASC" 
105  locking-test  INFO   [main] Tests -  *Found 1 entity
106  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@189df8c[id=600,
ver=1, firstName=firstName eager 600] one=[600String2, 600String1]
106  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(601)
with no lock to verify query lock set does not affect em lock mode.
106  locking-test  INFO   [main] Tests -  *Find entity
106  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@a0c570[id=601,
ver=2, firstName=firstName eager 601] one=[601String2, 601String1]
106  locking-test  INFO   [main] Tests - Committing transaction.
107  locking-test  INFO   [main] Tests - -- Test name query with pessimistic write lock in
Normal scope
107  locking-test  INFO   [main] Tests -  *Begin a transaction.
107  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
107  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(600)
with PESSIMISTIC_WRITE lock
108  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t0.id, t1.element FROM LSEEleColEgr t0 INNER JOIN LSEEleColEgr_collection t1 ON t0.id
= t1.LSEELECOLEGR_ID WHERE (t0.firstName LIKE ? ESCAPE '\') ORDER BY t0.id ASC" 
109  locking-test  INFO   [main] Tests -  *Found 1 entity
109  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@187d48[id=600,
ver=1, firstName=firstName eager 600] one=[600String2, 600String1]
109  locking-test  INFO   [main] Tests -  *Ensure ReadLockLevel remains at level READ
109  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(601)
with no lock to verify query lock set does not affect em lock mode.
109  locking-test  INFO   [main] Tests -  *Find an entity
109  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@c1beab[id=601,
ver=2, firstName=firstName eager 601] one=[601String2, 601String1]
110  locking-test  INFO   [main] Tests - Committing transaction.
1  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
1  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
12  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.3.0-SNAPSHOT
54  locking-test  INFO   [main] Tests - ** testExtendedElementCollectionEagerLock()
62  locking-test  INFO   [main] Tests - ** testExtendedElementCollectionEagerLock()
62  locking-test  INFO   [main] Tests - -- Test find with no lock in Extended scope
62  locking-test  INFO   [main] Tests -  *Begin a transaction.
62  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(610)
with no lock
63  locking-test  INFO   [main] Tests -  *Find entity
63  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@15db23e[id=610,
ver=1, firstName=firstName eager 610] one=[610String1, 610String2]
63  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(611)
with pessimistic force increment lock
64  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t0.version, t0.firstName, t1.LSEELECOLEGR_ID, t1.element FROM LSEEleColEgr t0 LEFT
OUTER JOIN LSEEleColEgr_collection t1 ON t0.id = t1.LSEELECOLEGR_ID WHERE t0.id = ?" 
68  locking-test  INFO   [main] Tests -  *Find entity
69  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@c1a427[id=611,
ver=1, firstName=firstName eager 611] one=[611String1, 611String2]
69  locking-test  INFO   [main] Tests - Committing transaction.
78  locking-test  INFO   [main] Tests - -- Test query with pessimistic read lock in Extended
scope
78  locking-test  INFO   [main] Tests -  *Begin a transaction.
78  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
78  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(610)
with PESSIMISTIC_READ lock
80  locking-test  WARN   [main] openjpa.Runtime - "javax.persistence.lock.scope" is not a
supported query hint. May be you meant "javax.persistence.lock.timeout"?
81  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t0.id, t1.element FROM LSEEleColEgr t0 INNER JOIN LSEEleColEgr_collection t1 ON t0.id
= t1.LSEELECOLEGR_ID WHERE (t0.firstName LIKE ? ESCAPE '\') ORDER BY t0.id ASC" 
82  locking-test  INFO   [main] Tests -  *Found 1 entity
82  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@146817d[id=610,
ver=1, firstName=firstName eager 610] one=[610String1, 610String2]
82  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(611)
with no lock to verify query lock set does not affect em lock mode.
83  locking-test  INFO   [main] Tests -  *Find entity
83  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@939dc[id=611,
ver=2, firstName=firstName eager 611] one=[611String1, 611String2]
83  locking-test  INFO   [main] Tests - Committing transaction.
83  locking-test  INFO   [main] Tests - -- Test name query with pessimistic write lock in
Extended scope
83  locking-test  INFO   [main] Tests -  *Begin a transaction.
83  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
83  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(610)
with PESSIMISTIC_WRITE lock
84  locking-test  WARN   [main] openjpa.Runtime - "javax.persistence.lock.scope" is not a
supported query hint. May be you meant "javax.persistence.lock.timeout"?
84  locking-test  WARN   [main] openjpa.Runtime - "javax.persistence.lock.scope" is not a
supported query hint. May be you meant "javax.persistence.lock.timeout"?
85  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t0.id, t1.element FROM LSEEleColEgr t0 INNER JOIN LSEEleColEgr_collection t1 ON t0.id
= t1.LSEELECOLEGR_ID WHERE (t0.firstName LIKE ? ESCAPE '\') ORDER BY t0.id ASC" 
86  locking-test  INFO   [main] Tests -  *Found 1 entity
86  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@8690e3[id=610,
ver=1, firstName=firstName eager 610] one=[610String1, 610String2]
86  locking-test  INFO   [main] Tests -  *Ensure ReadLockLevel remains at level READ
86  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(611)
with no lock to verify query lock set does not affect em lock mode.
87  locking-test  INFO   [main] Tests -  *Find an entity
87  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@1bfbe41[id=611,
ver=2, firstName=firstName eager 611] one=[611String1, 611String2]
87  locking-test  INFO   [main] Tests - Committing transaction.
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.614 sec
Running org.apache.openjpa.persistence.lockmgr.TestPessimisticLocks
0  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
0  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.3.0-SNAPSHOT
0  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
560  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t0.id, t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN
Department t1 ON t0.FK_DEPT = t1.id WHERE (t0.id < CAST(? AS BIGINT))" 
570  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN Department
t1 ON t0.FK_DEPT = t1.id WHERE t0.id = ?" 
60591  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN Department
t1 ON t0.FK_DEPT = t1.id WHERE t0.id = ?" 
0  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
1  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.3.0-SNAPSHOT
1  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
40  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t0.id, t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN
Department t1 ON t0.FK_DEPT = t1.id WHERE (t0.id < CAST(? AS BIGINT)) ORDER BY t0.id ASC"

48  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN Department
t1 ON t0.FK_DEPT = t1.id WHERE t0.id = ?" 
60054  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name, t0.FK_DEPT FROM Employee t0 LEFT OUTER JOIN Department t1 ON t0.FK_DEPT
= t1.id WHERE (t0.id < CAST(? AS BIGINT)) ORDER BY t0.FK_DEPT ASC" 
60064  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN Department
t1 ON t0.FK_DEPT = t1.id WHERE t0.id = ?" 
1  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
0  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.3.0-SNAPSHOT
0  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
30  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN Department
t1 ON t0.FK_DEPT = t1.id WHERE t0.id = ?" 
33  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name FROM Employee t0 LEFT OUTER JOIN Department t1 ON t0.FK_DEPT = t1.id
WHERE (t0.id < CAST(? AS BIGINT))" 
35  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN Department
t1 ON t0.FK_DEPT = t1.id WHERE t0.id = ?" 
37  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t0.id, t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN
Department t1 ON t0.FK_DEPT = t1.id WHERE (t0.id < CAST(? AS BIGINT))" 
0  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
0  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.3.0-SNAPSHOT
0  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
29  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN Department
t1 ON t0.FK_DEPT = t1.id WHERE t0.id = ?" 
33  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name, t0.FK_DEPT FROM Employee t0 LEFT OUTER JOIN Department t1 ON t0.FK_DEPT
= t1.id WHERE (t0.id < CAST(? AS BIGINT)) ORDER BY t0.FK_DEPT ASC" 
35  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t1.id, t1.name, t0.firstName, t0.lastName FROM Employee t0 LEFT OUTER JOIN Department
t1 ON t0.FK_DEPT = t1.id WHERE t0.id = ?" 
38  locking-test  INFO   [main] openjpa.Runtime - The database is unable to lock this query.
 Each object matching the query will be locked individually after it is loaded; however, it
is technically possible that another transaction could modify the data before the lock is
obtained.  See the documentation on Object Locking for details.
"SELECT t0.id, t1.id, t1.name, t0.firstName, t0.lastName, t0.FK_DEPT FROM Employee t0 LEFT
OUTER JOIN Department t1 ON t0.FK_DEPT = t1.id WHERE (t0.id < CAST(? AS BIGINT)) ORDER
BY t0.FK_DEPT ASC" 
1  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
0  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.3.0-SNAPSHOT
1  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
0  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
0  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.3.0-SNAPSHOT
1  locking-test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
Build timed out (after 162 minutes). Marking the build as failed.
killed.
[JENKINS] Recording test results
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to call isArchivingDisabled. Invalid object ID 22
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.IllegalStateException: Unable to call isArchivingDisabled. Invalid object ID 22
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:268)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:255)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:287)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:722)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 136 minutes 51 seconds
[INFO] Finished at: Thu Apr 26 18:16:00 UTC 2012
[INFO] Final Memory: 100M/582M
[INFO] ------------------------------------------------------------------------
channel stopped

Mime
View raw message