Same logic applies to the DatastoreTimeout test(s). The timeout only applies 
to the datastore operation, yet will be imposed against the overall call to 
the JDO API (query execution). Consequently the results are currently 
unreliable. 

DataNucleus 2.0 passes since the JDOQL implementation in use in that version 
doesn't support timeouts or cancelling. The one that will be in DataNucleus 
2.1 will support them.

-- 
Andy
DataNucleus (http://www.datanucleus.org)

Reply via email to