How do you turn on optimistic locking in JBoss 4.2.1 ?
Thanks,
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246057#4246057
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246057
Many thanks for the reply.
I'm using mysql.
So all I have to do is edit the datasource to make the cache use optimistic
locking ? I probably should have said I meant in the cache ?
Thanks,
Gerry Smith
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246271#424
I was referring to JBoss cache, I think I need to do something like this:
http://www.redhat.com/docs/manuals/jboss/jboss-eap-4.2/doc/cache/Tree_Cache_Guide/Configuration-Sample_XML_Based_Configuration.html
Thanks again,
Gerry Smith
View the original post :
http://www.jboss.org/index.html?modul
- or upgrade to 5.1 and use MVCC, but I had other problems upgrading the app to
5.0.
(obviously I'm getting deadlocks with pessimistic locking)
Gerry Smith
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246290#4246290
Reply to the post :
http://www.jboss.o
I am using JBoss 4.2.1, EJB 2.1.
I have a session bean which uses a finder to get a collection of entities and
creates a list of data transfer objects. The entities have CMR Collections that
need to be accessed.
I am trying to make this work without a transaction, and I'm using XDoclet, so
I've
Solved the root cause of the problem by using read-only for get* and commit
option A.
Gerry
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260969#4260969
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260969
_
Our app works great in production on AS 4.2.1.
We are trying to migrate to AS 5.0.1.
In the middle of a method in a session bean, it seems like it forgets the
security domain.
Even calling a create method on the local home of an EJB 2.1 which has already
been called earlier in the method can caus
I am having the same problem, anyone figured this out ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223578#4223578
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223578
__
pcarrollnf suggested copying the security policy, and naming the copy
BYPASSED-SECURITY. This works at the point where I was getting an error, but
it's in a complex chain of events and towards the end the security principal
suddenly becomes 'guest', like this is the next fallback position when i
