Hey
Sachin Aggarwal wrote:
> We are having problems running simultaneous JTS user transactions . If the
> transactions are from seperate java client programs , or from seperate
> threads in the same VM, it works fine. But when we use a web server (IIS),
> for some reason simultaneous transactional requests from seperate instances
> of web browser hose each other.
>
> We are using weblogic server. I don't know if this is specific to one vendor
> or all EJB servers. Do we need to set some special properties for each
> context or transaction that's created to differentiate which client browser
> started the tx ?
Let me take a wild guess here:
Do you start the tx in one servlet invocation and end it in another? In
that case it wont work:
1. Using tx:s to do long transactions is a Bad Idea. Don't do it. Use
locking or similar instead
2. Consider this:
* The tx initiator servlet is called from client 1. Tx 1 is started
* The tx initiator servlet is called from client 2 and the same handler
thread as above is used.
Since tx:es are thread associated nr 2 will interfere with nr 1 and
hence it wont work (you can only have 1 tx/thread)
/Rickard
--
Rickard �berg
Computer Science student@LiTH
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
