Using Kandula in a multi-threaded environment

["Brian Dillon (ext. 944)" <Br...@FINEOS.com>]

Hi,

I have noticed that Transacton management is seems to be done on a per
thread basis. This leads to a situation whereby every request from a
particular client must be routed to the same thread for every request ! Take
the situation where we have two Clients A and B;

Client A starts a transaction.
Client A performs some transacted operation, but hasn't yet
commited/rolledback.
Client B starts a transaction
Client B performs some trasacted operation.

If Client B's transacted operation happens to get serviced by the same
thread that Client A used (which is not uncommon in a Web Service) then you
get an exception; java.lang.IllegalStateException: the thread is already
associated with another transaction.

Is there any known workaround for this, since this would mean that we could
not use Kandula in a multithreaded environment ?

Thanks,

Brian Dillon

**********************************************************************
The information contained in this e-mail is confidential, may be 
privileged and is intended only for the user of the recipient named above.  
If you are not the intended recipient or a representative of the intended 
recipient, you have received this e-mail in error and must not copy, use 
or disclose the contents of this e-mail to anybody else.  If you have 
received this e-mail in error, please notify the sender immediately 
by return e-mail and permanently delete the copy you received.  
This e-mail has been swept for computer viruses.  However, you should 
carry out your own virus checks. 
Registered in Ireland, No. 205721.  http://www.FINEOS.com
**********************************************************************


---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org