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-deploy » OpenJPA Persistence Locking Tests #489
Date Sun, 05 Jul 2015 07:37:47 GMT
See <https://builds.apache.org/job/OpenJPA-trunk-deploy/org.apache.openjpa$openjpa-persistence-locking/489/>

------------------------------------------
[...truncated 1692 lines...]
121  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEJoinCon(400)
with PESSIMISTIC_WRITE lock
122  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 ?)" 
123  locking-test  INFO   [main] Tests -  *Found 1 entity
125  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEJoinCon@1f3f11corg.apache.openjpa.persistence.lock.extended.LSEJoinCon@1f3f11c[id=400,
ver=1] first=firstName 400, last=lastName 400
125  locking-test  INFO   [main] Tests -  *Ensure ReadLockLevel remains at level READ
125  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEJoinCon(401)
with no lock to verify query lock set does not affect em lock mode.
125  locking-test  INFO   [main] Tests -  *Find an entity
126  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEJoinCon@f4d603org.apache.openjpa.persistence.lock.extended.LSEJoinCon@f4d603[id=401,
ver=2] first=firstName 401, last=lastName 401
126  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.4.1-SNAPSHOT
14  locking-test  INFO   [main] openjpa.jdbc.JDBC - Connected to Apache Derby version 10.10
using JDBC driver Apache Derby Embedded JDBC Driver version 10.8.2.2 - (1181258). 
56  locking-test  INFO   [main] Tests - ** testExtendedJoinedLock()
66  locking-test  INFO   [main] Tests - ** testExtendedJoinedLock()
66  locking-test  INFO   [main] Tests - -- Test find with no lock in Extended scope
67  locking-test  INFO   [main] Tests -  *Begin a transaction.
67  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEJoinCon(410)
with no lock
67  locking-test  INFO   [main] Tests -  *Find entity
67  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEJoinCon@1b7ed27org.apache.openjpa.persistence.lock.extended.LSEJoinCon@1b7ed27[id=410,
ver=1] first=firstName 410, last=lastName 410
68  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEJoinCon(411)
with pessimistic force increment lock
68  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.version, t1.firstName, t0.lastName FROM LSEJoinCon t0 INNER JOIN LSEJoinAbs
t1 ON t0.id = t1.id WHERE t0.id = ?" 
69  locking-test  INFO   [main] Tests -  *Find entity
70  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEJoinCon@c1b434org.apache.openjpa.persistence.lock.extended.LSEJoinCon@c1b434[id=411,
ver=1] first=firstName 411, last=lastName 411
70  locking-test  INFO   [main] Tests - Committing transaction.
80  locking-test  INFO   [main] Tests - -- Test query with pessimistic read lock in Extended
scope
80  locking-test  INFO   [main] Tests -  *Begin a transaction.
80  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
80  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEJoinCon(410)
with PESSIMISTIC_READ lock
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"?
82  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 ?)" 
83  locking-test  INFO   [main] Tests -  *Found 1 entity
86  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEJoinCon@11b8762org.apache.openjpa.persistence.lock.extended.LSEJoinCon@11b8762[id=410,
ver=1] first=firstName 410, last=lastName 410
86  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.
86  locking-test  INFO   [main] Tests -  *Find entity
86  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEJoinCon@2fa870org.apache.openjpa.persistence.lock.extended.LSEJoinCon@2fa870[id=411,
ver=2] first=firstName 411, last=lastName 411
86  locking-test  INFO   [main] Tests - Committing transaction.
87  locking-test  INFO   [main] Tests - -- Test name query with pessimistic write lock in
Extended scope
87  locking-test  INFO   [main] Tests -  *Begin a transaction.
87  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
87  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"?
88  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 ?)" 
89  locking-test  INFO   [main] Tests -  *Found 1 entity
92  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEJoinCon@379d88org.apache.openjpa.persistence.lock.extended.LSEJoinCon@379d88[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@15fb626org.apache.openjpa.persistence.lock.extended.LSEJoinCon@15fb626[id=411,
ver=2] first=firstName 411, last=lastName 411
92  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.4.1-SNAPSHOT
14  locking-test  INFO   [main] openjpa.jdbc.JDBC - Connected to Apache Derby version 10.10
using JDBC driver Apache Derby Embedded JDBC Driver version 10.8.2.2 - (1181258). 
55  locking-test  INFO   [main] Tests - ** testNormalElementCollectionLock()
70  locking-test  INFO   [main] Tests - ** testNormalElementCollectionLock()
70  locking-test  INFO   [main] Tests - -- Test find with no lock in Normal scope
70  locking-test  INFO   [main] Tests -  *Begin a transaction.
70  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(500)
with no lock
74  locking-test  INFO   [main] Tests -  *Find entity
77  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@aa58ff[id=500,
ver=1, firstName=firstName lazy 500] one=[500String1, 500String2]
77  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(501)
with pessimistic force increment lock
84  locking-test  INFO   [main] Tests -  *Find entity
84  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@8a9271[id=501,
ver=1, firstName=lazy 501] one=[501String1, 501String2]
84  locking-test  INFO   [main] Tests - Committing transaction.
97  locking-test  INFO   [main] Tests - -- Test query with pessimistic read lock in Normal
scope
97  locking-test  INFO   [main] Tests -  *Begin a transaction.
97  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
97  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleCol(500)
with PESSIMISTIC_READ lock
103  locking-test  INFO   [main] Tests -  *Found 1 entity
103  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@2e5d05[id=500,
ver=1, firstName=firstName lazy 500] one=[500String1, 500String2]
103  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.
104  locking-test  INFO   [main] Tests -  *Find entity
104  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@162b352[id=501,
ver=2, firstName=lazy 501] one=[501String1, 501String2]
104  locking-test  INFO   [main] Tests - Committing transaction.
105  locking-test  INFO   [main] Tests - -- Test name query with pessimistic write lock in
Normal scope
105  locking-test  INFO   [main] Tests -  *Begin a transaction.
105  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
105  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleCol(500)
with PESSIMISTIC_WRITE lock
106  locking-test  INFO   [main] Tests -  *Found 1 entity
107  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@5a8a3[id=500,
ver=1, firstName=firstName lazy 500] one=[500String1, 500String2]
107  locking-test  INFO   [main] Tests -  *Ensure ReadLockLevel remains at level READ
107  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.
107  locking-test  INFO   [main] Tests -  *Find an entity
107  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@1b6ae53[id=501,
ver=2, firstName=lazy 501] one=[501String1, 501String2]
108  locking-test  INFO   [main] Tests - Committing transaction.
0  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".
13  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.4.1-SNAPSHOT
15  locking-test  INFO   [main] openjpa.jdbc.JDBC - Connected to Apache Derby version 10.10
using JDBC driver Apache Derby Embedded JDBC Driver version 10.8.2.2 - (1181258). 
56  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
66  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@1d54e26[id=510,
ver=1, firstName=firstName lazy 510] one=[510String1, 510String2]
66  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleCol(511)
with pessimistic force increment lock
70  locking-test  INFO   [main] Tests -  *Find entity
71  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@e10809[id=511,
ver=1, firstName=lazy 511] one=[511String1, 511String2]
71  locking-test  INFO   [main] Tests - Committing transaction.
81  locking-test  INFO   [main] Tests - -- Test query with pessimistic read 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_READ lock
83  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  INFO   [main] Tests -  *Found 1 entity
84  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@199bef1[id=510,
ver=1, firstName=firstName lazy 510] one=[510String1, 510String2]
84  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.
85  locking-test  INFO   [main] Tests -  *Find entity
85  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@f1332c[id=511,
ver=2, firstName=lazy 511] one=[511String1, 511String2]
85  locking-test  INFO   [main] Tests - Committing transaction.
85  locking-test  INFO   [main] Tests - -- Test name query with pessimistic write lock in
Extended scope
86  locking-test  INFO   [main] Tests -  *Begin a transaction.
86  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
86  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleCol(510)
with PESSIMISTIC_WRITE lock
86  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] Tests -  *Found 1 entity
88  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@db03e4[id=510,
ver=1, firstName=firstName lazy 510] one=[510String1, 510String2]
88  locking-test  INFO   [main] Tests -  *Ensure ReadLockLevel remains at level READ
88  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.
89  locking-test  INFO   [main] Tests -  *Find an entity
89  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleCol@1a6f0be[id=511,
ver=2, firstName=lazy 511] one=[511String1, 511String2]
89  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".
13  locking-test  INFO   [main] openjpa.Runtime - Starting OpenJPA 2.4.1-SNAPSHOT
15  locking-test  INFO   [main] openjpa.jdbc.JDBC - Connected to Apache Derby version 10.10
using JDBC driver Apache Derby Embedded JDBC Driver version 10.8.2.2 - (1181258). 
55  locking-test  INFO   [main] Tests - ** testNormalElementCollectionEagerLock()
67  locking-test  INFO   [main] Tests - ** testNormalElementCollectionEagerLock()
67  locking-test  INFO   [main] Tests - -- Test find with no lock in Normal scope
67  locking-test  INFO   [main] Tests -  *Begin a transaction.
67  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(600)
with no lock
74  locking-test  INFO   [main] Tests -  *Find entity
74  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@f9ad94[id=600,
ver=1, firstName=firstName eager 600] one=[600String2, 600String1]
74  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(601)
with pessimistic force increment lock
74  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 = ? ORDER
BY t1.LSEELECOLEGR_ID ASC" 
81  locking-test  INFO   [main] Tests -  *Find entity
81  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@1b3795b[id=601,
ver=1, firstName=firstName eager 601] one=[601String2, 601String1]
81  locking-test  INFO   [main] Tests - Committing transaction.
92  locking-test  INFO   [main] Tests - -- Test query with pessimistic read lock in Normal
scope
92  locking-test  INFO   [main] Tests -  *Begin a transaction.
92  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
92  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 ?) 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@17e251f[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@1997242[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 ?) 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@1cf2357[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.
110  locking-test  INFO   [main] Tests -  *Find an entity
110  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@688013[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".
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.4.1-SNAPSHOT
14  locking-test  INFO   [main] openjpa.jdbc.JDBC - Connected to Apache Derby version 10.10
using JDBC driver Apache Derby Embedded JDBC Driver version 10.8.2.2 - (1181258). 
55  locking-test  INFO   [main] Tests - ** testExtendedElementCollectionEagerLock()
67  locking-test  INFO   [main] Tests - ** testExtendedElementCollectionEagerLock()
68  locking-test  INFO   [main] Tests - -- Test find with no lock in Extended scope
68  locking-test  INFO   [main] Tests -  *Begin a transaction.
68  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(610)
with no lock
69  locking-test  INFO   [main] Tests -  *Find entity
69  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@13a68f0[id=610,
ver=1, firstName=firstName eager 610] one=[610String1, 610String2]
69  locking-test  INFO   [main] Tests -  *Find org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(611)
with pessimistic force increment lock
69  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 = ? ORDER
BY t1.LSEELECOLEGR_ID ASC" 
74  locking-test  INFO   [main] Tests -  *Find entity
75  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@d5ecda[id=611,
ver=1, firstName=firstName eager 611] one=[611String1, 611String2]
75  locking-test  INFO   [main] Tests - Committing transaction.
84  locking-test  INFO   [main] Tests - -- Test query with pessimistic read lock in Extended
scope
84  locking-test  INFO   [main] Tests -  *Begin a transaction.
84  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
84  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(610)
with PESSIMISTIC_READ lock
86  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  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 ?) ORDER BY t0.id ASC" 
88  locking-test  INFO   [main] Tests -  *Found 1 entity
88  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@1b8ed44[id=610,
ver=1, firstName=firstName eager 610] one=[610String1, 610String2]
88  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.
89  locking-test  INFO   [main] Tests -  *Find entity
89  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@f938c7[id=611,
ver=2, firstName=firstName eager 611] one=[611String1, 611String2]
89  locking-test  INFO   [main] Tests - Committing transaction.
90  locking-test  INFO   [main] Tests - -- Test name query with pessimistic write lock in
Extended scope
90  locking-test  INFO   [main] Tests -  *Begin a transaction.
90  locking-test  INFO   [main] Tests -  *Save ReadLockLevel before Query:READ
90  locking-test  INFO   [main] Tests -  *Query org.apache.openjpa.persistence.lock.extended.LSEEleColEgr(610)
with PESSIMISTIC_WRITE lock
90  locking-test  WARN   [main] openjpa.Runtime - "javax.persistence.lock.scope" is not a
supported query hint. May be you meant "javax.persistence.lock.timeout"?
91  locking-test  WARN   [main] openjpa.Runtime - "javax.persistence.lock.scope" is not a
supported query hint. May be you meant "javax.persistence.lock.timeout"?
91  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 ?) ORDER BY t0.id ASC" 
93  locking-test  INFO   [main] Tests -  *Found 1 entity
93  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@1f669c0[id=610,
ver=1, firstName=firstName eager 610] one=[610String1, 610String2]
93  locking-test  INFO   [main] Tests -  *Ensure ReadLockLevel remains at level READ
93  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.
94  locking-test  INFO   [main] Tests -  *Find an entity
94  locking-test  INFO   [main] Tests -  *Found entity:org.apache.openjpa.persistence.lock.extended.LSEEleColEgr@ee03ec[id=611,
ver=2, firstName=firstName eager 611] one=[611String1, 611String2]
94  locking-test  INFO   [main] Tests - Committing transaction.
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.745 sec - in org.apache.openjpa.persistence.lock.extended.TestBasicLockScope

Results :

Tests run: 197, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ openjpa-persistence-locking ---
[INFO] Building jar: <https://builds.apache.org/job/OpenJPA-trunk-deploy/org.apache.openjpa$openjpa-persistence-locking/ws/target/openjpa-persistence-locking-2.4.1-SNAPSHOT.jar>
[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ openjpa-persistence-locking
---
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:test-jar (attach-tests) @ openjpa-persistence-locking ---
[INFO] Building jar: <https://builds.apache.org/job/OpenJPA-trunk-deploy/org.apache.openjpa$openjpa-persistence-locking/ws/target/openjpa-persistence-locking-2.4.1-SNAPSHOT-tests.jar>
[INFO] 
[INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ openjpa-persistence-locking
---
[INFO] Checking legal files in: openjpa-persistence-locking-2.4.1-SNAPSHOT.jar
[INFO] Checking legal files in: openjpa-persistence-locking-2.4.1-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- apache-rat-plugin:0.7:check (default) @ openjpa-persistence-locking ---
[INFO] Exclude: **/.*/**
[INFO] Exclude: **/target/**/*
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ openjpa-persistence-locking
---
[INFO] Installing <https://builds.apache.org/job/OpenJPA-trunk-deploy/org.apache.openjpa$openjpa-persistence-locking/ws/target/openjpa-persistence-locking-2.4.1-SNAPSHOT.jar>
to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/openjpa/openjpa-persistence-locking/2.4.1-SNAPSHOT/openjpa-persistence-locking-2.4.1-SNAPSHOT.jar
[INFO] Installing <https://builds.apache.org/job/OpenJPA-trunk-deploy/org.apache.openjpa$openjpa-persistence-locking/ws/pom.xml>
to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/openjpa/openjpa-persistence-locking/2.4.1-SNAPSHOT/openjpa-persistence-locking-2.4.1-SNAPSHOT.pom
[INFO] Installing <https://builds.apache.org/job/OpenJPA-trunk-deploy/org.apache.openjpa$openjpa-persistence-locking/ws/target/openjpa-persistence-locking-2.4.1-SNAPSHOT-tests.jar>
to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/openjpa/openjpa-persistence-locking/2.4.1-SNAPSHOT/openjpa-persistence-locking-2.4.1-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ openjpa-persistence-locking
---
[INFO] Downloading: https://repository.apache.org/content/repositories/snapshots/org/apache/openjpa/openjpa-persistence-locking/2.4.1-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata org.apache.openjpa:openjpa-persistence-locking:2.4.1-SNAPSHOT/maven-metadata.xml
from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots):
Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/openjpa/openjpa-persistence-locking/2.4.1-SNAPSHOT/maven-metadata.xml.
Return code is: 502 , ReasonPhrase:Proxy Error.

Mime
View raw message