Hello, I'm encountering this bug, but with a different stack than the one
reported in https://cwiki.apache.org/jira/browse/OPENJPA-1001.
I'm using OpenJPA 1.3.0-SNAPSHOT and am accessing it through OpenEJB. I
will attempt to reproduce this bug with a simpler test case than the one I'm
currently
)
at
org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:285)
Again, I hope this helps.
Best,
Laird
--
View this message in context:
http://n2.nabble.com/OPENJPA-1001-tp3437948p3437992.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
)
at org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:896)
at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:854)
Hope this helps.
Best,
Laird
--
View this message in context:
http://n2.nabble.com/OPENJPA-1001-tp3437948p3438119.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
.
openjpa.jdbc.QuerySQLCache = false
Good luck,
Kevin
[1] https://issues.apache.org/jira/browse/OPENJPA-1001
[2]
http://openjpa.apache.org/builds/1.2.1/apache-openjpa-1.2.1/docs/manual/manual.html#ref_guide_cache_querysql
On Thu, Aug 13, 2009 at 8:57 AM, ljnelson ljnel...@gmail.com wrote:
ljnelson
should be able to turn off this property and get around the problem.
Thanks; I'll give that a shot.
Best,
Laird
--
View this message in context:
http://n2.nabble.com/OPENJPA-1001-tp3437948p3438293.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
the problem.
Indeed, that fixed it. I look forward to the 2.0 fix being backported to
the 1.3 line.
Best,
Laird
--
View this message in context:
http://n2.nabble.com/OPENJPA-1001-tp3437948p3438431.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
It looks like Mike just took ownership of OPENJPA-1001. My guess is that
the first approach at resolving this issue will be to resolve this specific
issue, and not the whole QuerySQLCache re-architecture. I would monitor
that JIRA and comment directly on that JIRA.
Thanks,
Kevin
On Thu, Aug 13
