openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dick <michael.d.d...@gmail.com>
Subject Re: Build failed in Hudson: OpenJPA-trunk #400
Date Mon, 14 Feb 2011 15:35:35 GMT
Build failures like this one have been cropping up lately.

The slice module appears to hang sporadically when we run in Hudson, but
I've never been able to reproduce it. Has anyone else seen this if they
build locally?

-mike

On Fri, Feb 11, 2011 at 9:42 PM, Apache Hudson Server

<snip>


> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.apache.openjpa.slice.TestQuery
> 5  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 6  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 39  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 162  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 482  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary
> class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5106  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary
> class "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 13071  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p)
> FROM PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 13299  ordering  WARN   [main] openjpa.Runtime - Query "SELECT p.value,p
> FROM PObject p ORDER BY p.value ASC" is removed from cache  excluded
> permanently. Query "SELECT p.value,p FROM PObject p ORDER BY p.value ASC" is
> not cached because its result is not obtained by executing a select
> statement. This can happen if the query was evaluated in-memory. The result
> was provided by
> org.apache.openjpa.kernel.OrderingMergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 3  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 12  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 10  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 8  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 371  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 471  ordering  WARN   [main] openjpa.Runtime - Query "SELECT p FROM PObject
> p ORDER BY p.value ASC" is removed from cache  excluded permanently. Query
> "SELECT p FROM PObject p ORDER BY p.value ASC" is not cached because its
> result is not obtained by executing a select statement. This can happen if
> the query was evaluated in-memory. The result was provided by
> org.apache.openjpa.kernel.OrderingMergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 3  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 11  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 9  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 8  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 205  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 337  ordering  WARN   [main] openjpa.Runtime - Query "SELECT p FROM Person
> p JOIN p.address a ORDER BY a.zip ASC, a.city DESC" is removed from cache
>  excluded permanently. Query "SELECT p FROM Person p JOIN p.address a ORDER
> BY a.zip ASC, a.city DESC" is not cached because its result is not obtained
> by executing a select statement. This can happen if the query was evaluated
> in-memory. The result was provided by
> org.apache.openjpa.kernel.OrderingMergedResultObjectProvider.  .
> 1  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 1  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 3  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 10  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 8  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 7  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 202  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 341  ordering  WARN   [main] openjpa.Runtime - Query "SELECT MAX(p.value)
> FROM PObject p" is removed from cache  excluded permanently. Query "SELECT
> MAX(p.value) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 350  ordering  WARN   [main] openjpa.Runtime - Query "SELECT MIN(p.value)
> FROM PObject p" is removed from cache  excluded permanently. Query "SELECT
> MIN(p.value) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 360  ordering  WARN   [main] openjpa.Runtime - Query "SELECT SUM(p.value)
> FROM PObject p" is removed from cache  excluded permanently. Query "SELECT
> SUM(p.value) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 372  ordering  WARN   [main] openjpa.Runtime - Query "SELECT
> MIN(p.value),MAX(p.value) FROM PObject p" is removed from cache  excluded
> permanently. Query "SELECT MIN(p.value),MAX(p.value) FROM PObject p" is not
> cached because it returns a single value rather than a list. A query that
> returns single value can not be cached. .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 9  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 7  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 6  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 177  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 268  ordering  WARN   [main] openjpa.Runtime - Query "SELECT MAX(p.value)
> FROM PObject p WHERE MOD(p.value,2)=0" is removed from cache  excluded
> permanently. Query "SELECT MAX(p.value) FROM PObject p WHERE
> MOD(p.value,2)=0" is not cached because it returns a single value rather
> than a list. A query that returns single value can not be cached. .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 1  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 3  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 10  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 8  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 6  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 176  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 345  ordering  WARN   [main] openjpa.Runtime - Query "SELECT p FROM PObject
> p ORDER BY p.value ASC" is removed from cache  excluded permanently. Query
> "SELECT p FROM PObject p ORDER BY p.value ASC" is not cached because its
> result is not obtained by executing a select statement. This can happen if
> the query was evaluated in-memory. The result was provided by
> org.apache.openjpa.kernel.OrderingMergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 8  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 7  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 6  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 236  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 320  ordering  WARN   [main] openjpa.Runtime - Query "SELECT p FROM PObject
> p" is removed from cache  excluded permanently. Query "SELECT p FROM PObject
> p" is not cached because its result is not obtained by executing a select
> statement. This can happen if the query was evaluated in-memory. The result
> was provided by org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 7  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 6  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 7  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 159  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 240  ordering  WARN   [main] openjpa.Runtime - Query "SELECT p FROM PObject
> p" is removed from cache  excluded permanently. Query "SELECT p FROM PObject
> p" is not cached because its result is not obtained by executing a select
> statement. This can happen if the query was evaluated in-memory. The result
> was provided by org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 7  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 5  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 154  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 239  ordering  WARN   [main] openjpa.Runtime - Query "SELECT p FROM PObject
> p ORDER BY p.value" is removed from cache  excluded permanently. Query
> "SELECT p FROM PObject p ORDER BY p.value" is not cached because its result
> is not obtained by executing a select statement. This can happen if the
> query was evaluated in-memory. The result was provided by
> org.apache.openjpa.kernel.OrderingMergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 3  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 8  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 7  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 154  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 246  ordering  WARN   [main] openjpa.Runtime - Query "SELECT p FROM PObject
> p WHERE p.value > :v" is removed from cache  excluded permanently. Query
> "SELECT p FROM PObject p WHERE p.value > :v" is not cached because its
> result is not obtained by executing a select statement. This can happen if
> the query was evaluated in-memory. The result was provided by
> org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 6  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 4  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 168  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 267  ordering  WARN   [main] openjpa.Runtime - Query "select a from Address
> a where a.city = :city" is removed from cache  excluded permanently. Query
> "select a from Address a where a.city = :city" is not cached because its
> result is not obtained by executing a select statement. This can happen if
> the query was evaluated in-memory. The result was provided by
> org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> 297  ordering  WARN   [main] openjpa.Runtime - Query "SELECT p FROM Person
> p WHERE p.address = :a" is removed from cache  excluded permanently. Query
> "SELECT p FROM Person p WHERE p.address = :a" is not cached because its
> result is not obtained by executing a select statement. This can happen if
> the query was evaluated in-memory. The result was provided by
> org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 5  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 187  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 294  ordering  WARN   [main] openjpa.Runtime - Query "select c from Car c"
> is removed from cache  excluded permanently. Query "select c from Car c" is
> not cached because its result is not obtained by executing a select
> statement. This can happen if the query was evaluated in-memory. The result
> was provided by org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> 300  ordering  WARN   [main] openjpa.Runtime - Query "select m from
> Manufacturer m" is removed from cache  excluded permanently. Query "select m
> from Manufacturer m" is not cached because its result is not obtained by
> executing a select statement. This can happen if the query was evaluated
> in-memory. The result was provided by
> org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.429 sec
> Running org.apache.openjpa.slice.TestQueryMultiThreaded
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 1  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 4  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 4  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 161  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 274  ordering  WARN   [Thread-2] openjpa.Runtime - Query "SELECT
> MAX(p.value) FROM PObject p" is removed from cache  excluded permanently.
> Query "SELECT MAX(p.value) FROM PObject p" is not cached because it returns
> a single value rather than a list. A query that returns single value can not
> be cached. .
> 279  ordering  WARN   [Thread-2] openjpa.Runtime - Query "SELECT
> MIN(p.value) FROM PObject p" is removed from cache  excluded permanently.
> Query "SELECT MIN(p.value) FROM PObject p" is not cached because it returns
> a single value rather than a list. A query that returns single value can not
> be cached. .
> 286  ordering  WARN   [Thread-2] openjpa.Runtime - Query "SELECT
> SUM(p.value) FROM PObject p" is removed from cache  excluded permanently.
> Query "SELECT SUM(p.value) FROM PObject p" is not cached because it returns
> a single value rather than a list. A query that returns single value can not
> be cached. .
> 295  ordering  WARN   [Thread-2] openjpa.Runtime - Query "SELECT
> MIN(p.value),MAX(p.value) FROM PObject p" is removed from cache  excluded
> permanently. Query "SELECT MIN(p.value),MAX(p.value) FROM PObject p" is not
> cached because it returns a single value rather than a list. A query that
> returns single value can not be cached. .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 1  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 5  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 141  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 227  ordering  WARN   [Thread-7] openjpa.Runtime - Query "SELECT
> MAX(p.value) FROM PObject p WHERE MOD(p.value,2)=0" is removed from cache
>  excluded permanently. Query "SELECT MAX(p.value) FROM PObject p WHERE
> MOD(p.value,2)=0" is not cached because it returns a single value rather
> than a list. A query that returns single value can not be cached. .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 1  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 6  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 4  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 154  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 242  ordering  WARN   [Thread-12] openjpa.Runtime - Query "SELECT p.value,p
> FROM PObject p ORDER BY p.value ASC" is removed from cache  excluded
> permanently. Query "SELECT p.value,p FROM PObject p ORDER BY p.value ASC" is
> not cached because its result is not obtained by executing a select
> statement. This can happen if the query was evaluated in-memory. The result
> was provided by
> org.apache.openjpa.kernel.OrderingMergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 1  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 7  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 7  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 7  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 177  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 248  ordering  WARN   [Thread-17] openjpa.Runtime - Query "SELECT p FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT p FROM
> PObject p" is not cached because its result is not obtained by executing a
> select statement. This can happen if the query was evaluated in-memory. The
> result was provided by
> org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 0  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 4  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 137  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 209  ordering  WARN   [Thread-22] openjpa.Runtime - Query "SELECT p FROM
> PObject p ORDER BY p.value" is removed from cache  excluded permanently.
> Query "SELECT p FROM PObject p ORDER BY p.value" is not cached because its
> result is not obtained by executing a select statement. This can happen if
> the query was evaluated in-memory. The result was provided by
> org.apache.openjpa.kernel.OrderingMergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 1  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 4  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 137  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 217  ordering  WARN   [Thread-27] openjpa.Runtime - Query "SELECT p FROM
> PObject p WHERE p.value > :v" is removed from cache  excluded permanently.
> Query "SELECT p FROM PObject p WHERE p.value > :v" is not cached because its
> result is not obtained by executing a select statement. This can happen if
> the query was evaluated in-memory. The result was provided by
> org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> 0  ordering  WARN   [main] openjpa.Runtime - Slice identifiers are not
> explicitly listed via "openjpa.slice.Names" property.The configuration will
> be scanned to determine slice identifiers.
> 1  ordering  INFO   [main] openjpa.Runtime - Detected slices "[Even, Odd]"
> in configuration.
> 2  ordering  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 5  ordering  INFO   [main] openjpa.Runtime - Starting OpenJPA Slice
> 2.2.0-SNAPSHOT
> 4  ordering.Even  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 4  ordering.Odd  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class
> "org.apache.openjpa.jdbc.sql.DerbyDictionary".
> 158  ordering  WARN   [main] openjpa.Runtime - Query "SELECT COUNT(p) FROM
> PObject p" is removed from cache  excluded permanently. Query "SELECT
> COUNT(p) FROM PObject p" is not cached because it returns a single value
> rather than a list. A query that returns single value can not be cached. .
> 241  ordering  WARN   [Thread-32] openjpa.Runtime - Query "select a from
> Address a where a.city = :city" is removed from cache  excluded permanently.
> Query "select a from Address a where a.city = :city" is not cached because
> its result is not obtained by executing a select statement. This can happen
> if the query was evaluated in-memory. The result was provided by
> org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> 248  ordering  WARN   [Thread-32] openjpa.Runtime - Query "SELECT p FROM
> Person p WHERE p.address = :a" is removed from cache  excluded permanently.
> Query "SELECT p FROM Person p WHERE p.address = :a" is not cached because
> its result is not obtained by executing a select statement. This can happen
> if the query was evaluated in-memory. The result was provided by
> org.apache.openjpa.lib.rop.MergedResultObjectProvider.  .
> Build timed out. Aborting
> killed.
> [HUDSON] Recording test results
> channel stopped
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] channel is already closed
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 158 minutes 59 seconds
> [INFO] Finished at: Sat Feb 12 03:42:36 UTC 2011
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message