I forgot to say that I'm using commit option A for performance reasons, with the default bean locking.

Beau

Alex Loubyansky wrote:

what is the problem? what locking policy are you using?

alex

Wednesday, January 22, 2003, 8:43:05 PM, you wrote:

BC> I have a Swing app which is essentially single-threaded, accessing the BC> server in the usual way through a session facade. I'd like to do some BC> background loading of certain data for performance reasons, but when I BC> try to do this by using a separate thread (and separate session BC> instance), I get various transaction collision problems if these two BC> threads access the server at the same time.

BC> I'm obviously missing something here--shouldn't different remote client BC> threads from the same client be able to access JBoss simultaneously in BC> the same way that entirely different clients can? I.e., shouldn't they BC> spawn separate transactions which are scheduled appropriately by JBoss?

BC> Any clarification appreciated,

BC> Beau Cronin




-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user





-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to