t; In the output on server 1 it prints:
>>> Cast successful
>>> first call complete
>>> found first SEP786
>>>
>>> It then hangs until the transaction on the second server times out (for
>>> some
>>> strange reason)
>>>
>>>
which it gives a transaction time out
>> message.
>>
>> The thing is that the second call to manager.find"() for an object which
>> is
>> persisted in the remote call causes it to hang. If I comment out the call
>> everything works fine. Also the noticeable th
t; everything works fine. Also the noticeable thing is that after the second
> server gives a time out message for the transaction, I then see the
> remaining sysouts
> i.e
> Found second SEPnull
>
> I am wondering if I'm missing something here. Although I'm not sure
hould have succeeded given that I'm not using a any sort of
distributed cache yet, I don't expect it to hang either. Any ideas? Find the
code attached.
http://n2.nabble.com/file/n3063290/strangebehaviourwithadistributedtransaction_.zip
strangebehaviourwithadistributedtransaction_.zip
--
Vi
