Changing the log level of the category org.apache.openjpa in log4j could
probably help. Also I've fixed the source of this exception in the
1.1branch if you don't mind updating.

Cheers,
Matthieu

On Dec 3, 2007 3:05 PM, jbi joe <[EMAIL PROTECTED]> wrote:

>
> What is this coming to my runtime window
> and how do I shut it off?   TIA
>
> INFO  - Query                          - This query on type "class
> org.apache.ode.dao.jpa.ScopeDAOImpl" must load the entire candidate class
> extent and evaluate the query in-memory.  This may be very slow.  The
> query
> must be executed in memory because OpenJPA is configured with
> IgnoreCache=false and FlushBeforeQueries=false and there are dirty
> instances
> that may affect the query's outcome in the cache.
> --
> View this message in context:
> http://www.nabble.com/Excessive-INFO-output-from-OpenJPA-tf4939752.html#a14140388
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>

Reply via email to