] [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 23. März 2007 23:46
An: open-jpa-dev@incubator.apache.org
Betreff: Re: AW: Forgot subject: Strange Could not locate metadata
for the
classError?
Marc Prud'hommeaux wrote:
Hans-
I don't see how the error could be data-related.
One thi
tithreaded" property remain by this
usage scenario?
Hans
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 23. März 2007 23:46
> An: open-jpa-dev@incubator.apache.org
> Betreff: Re: AW: Forgot subject: Strange Could not l
Marina-
OK, then it's probably not the Multithreaded property.
I'm stumped :(
On Mar 23, 2007, at 2:56 PM, Marina Vatkina wrote:
Marc,
No, in GlassFish (GF) it shouldn't be the case, but there could be
more than 1 EMF created at the same time. The test case uses
stateless session bean f
Marc Prud'hommeaux wrote:
Hans-
I don't see how the error could be data-related.
One thing: if you are using the same EMF from multiple threads,
do you have the "openjpa.Multithreaded" property explicitly
set to "true" in your persistence.xml (or however you are
configuring the EMF)?
Marc,
No, in GlassFish (GF) it shouldn't be the case, but there could be more than 1
EMF created at the same time. The test case uses stateless session bean for
accessing EM, so there is no guarantee that the same bean instance serves the
1st method (with a successful persist) and the 2nd (wit
Marina-
In a normal J2EE app, the same EntityManager will never be used
concurrently from multiple threads. That might also be the case in
your environment, but it would be interesting to see if the problem
ever crops up after you enable this property.
On Mar 23, 2007, at 2:36 PM, Marin
Marc,
Does OpenJPA figures out by itself that it is running in a multithreaded
environment when used in an app- or web-server? Or do you expect users to always
specify this setting when they decide to deploy it to a multi-threaded container?
thanks,
-marina
Marc Prud'hommeaux wrote:
Hans-
Hans-
I don't see how the error could be data-related.
One thing: if you are using the same EMF from multiple threads, do
you have the "openjpa.Multithreaded" property explicitly set to
"true" in your persistence.xml (or however you are configuring the
EMF)? Failure to do this means that a
It looks very similar to what I saw yesterday, and I also couldn't reproduce it
later.
-marina
Hans J. Prueller wrote:
hm.. sounds strange. could it bet he case that the error message openjpa is
printing is only a subsequent error of another one below/before?
as the JNDI binding did not rea
hm.. sounds strange. could it bet he case that the error message openjpa is
printing is only a subsequent error of another one below/before?
as the JNDI binding did not really work (as you can remember: everytime I am
accessing the EMF from JNDI it is initialized again and again) so I did a
quick
10 matches
Mail list logo
