Tom,
The exact same design issue is in last week's commit (rev 1.2) to
JpdlParser.java. SaxParserFactory is not threadsafe.
Either each thread needs it's own SaxParserFactory (typically hung off a
ThreadLocal),
... or the newInstance() call in SaxParserFactory.createXmlReader() needs to be
Ed, Tom,
Yes, I do think it is a problem.
In nearly any real-life application the process definition has to be accessed
from many threads, each working with own process instance. For simplicity lets
assume that they are all based on the same process definition. All process
instances are on th
Tom, Andrey,
Either I misunderstand, or Tom did.
Tom, as I understand it, Andrey is reporting a latent bug in JBPM's definition
cache-loading.
Andrey, is that correct?
Given that the frequency of failure will vary from database to database, and
from one Hibernate version to the next, it may
indeed. only use a session in 1 thread.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042308#4042308
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042308
___
jboss-user mai
Hi Roland,
Read-only data doesn't mean read-only Session instance. Session caches all read
data internally (1st level cache), so each select may change its state. I'm not
sure if it applies for the objects that are cached also in the 2nd level cache
but in any case I would follow the recommenda
I'm kind of aware of these, but what I meant to say is that there probably is
no problem when accessing read-only data in a second-level cache from a
non-thread safe session is there??
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041055#4041055
Reply to t
"hibernate session is not thread safe according to the documentation" - see e.g.
http://www.hibernate.org/hib_docs/v3/api/org/hibernate/Session.html
http://www.hibernate.org/42.html
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041049#4041049
Reply to the p
imo (but I'm no expert on databases/hibernate etc...) there is no problem with
simultaneous read-only access to processdefinitions should not be a problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040709#4040709
Reply to the post :
http://www.jboss.co
