----- Forwarded message from Valerio Vianello <[EMAIL PROTECTED]> -----
Date: Fri, 7 Jul 2006 15:47:45 +0200
From: Valerio Vianello <[EMAIL PROTECTED]>
Reply-To: Valerio Vianello <[EMAIL PROTECTED]>
Subject: Re: problem with kandula1
To: Dasarath Weeratunge <[EMAIL PROTECTED]>
Thanks a lot.
I followed your suggestion, so I published my original client class on the
server and invoke it by an other client.
All seem to work
the only suspect thing is a coupleof message that I get from the server at
the end of execution:
[CallbackRegistry] registerCallback: timeout= 180000
[CallbackRegistry] registerCallback: timeout= 180000
Risorsa isSameRM
Risorsa start
Operazini : somma
Risorsa end
ris = 3
Risorsa start
Operazioni : prodotto
Risorsa end
ris2 = 12
[CallbackRegistry] registerCallback: timeout= 180000
Risorsa end
Risorsa prepare
Risorsa commit
[ATCoordinatorImpl] timeout NONE <===
[AbstractParticipant] timeout NONE <===
Whath do they stand for
Thanks Valerio
----- Original Message -----
From: "Dasarath Weeratunge" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, July 07, 2006 3:29 PM
Subject: Re: problem with kandula1
> Quoting Valerio Vianello <[EMAIL PROTECTED]>:
>
> Does your client run in a web container? I suspect your client is waiting
> for a response from the server (either COMMITTED or ABORTED) but is not
> getting
> that. Also, the response to COMMIT message comes on a different HTTP
> channel.
>
> thanks,
> --dasarath
>
>> I'm a new kandula user. I have developed an example starting from the
>> bankone
>> exemple that comes from the distribution. Client starts the transection
>> invokes two methods of the simpleservice and commit the transaction. The
>> problem that I have met is that the client after commit request remains
>> blocked as if it is waiting for a replay. Monitoring the comunication
>> with
>> webScarab I have noticed that after the commit request from the client
>> the
>> server answers with an http 200 OK.
>>
>> Can you suggest me what to do ????
>>
>> Valerio
>>
>> P.S. this is the client stacktrace:
>>
>> [CallbackRegistry] registerCallback: timeout= 180000
>> org.apache.kandula.coordinator.TimedOutException
>> at
>> org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionI
>> mpl.java:184)
>> at
>> org.apache.kandula.coordinator.at.TransactionManagerImpl.commit(Trans
>> actionManagerImpl.java:63)
>> at
>> kandulaMio.ServizioTransazionale.main(ServizioTransazionale.java:93)
>> java.lang.RuntimeException:
>> org.apache.kandula.coordinator.TimedOutException
>> at
>> org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionI
>> mpl.java:191)
>> at
>> org.apache.kandula.coordinator.at.TransactionManagerImpl.commit(Trans
>> actionManagerImpl.java:63)
>> at
>> kandulaMio.ServizioTransazionale.main(ServizioTransazionale.java:93)
>> Caused by: org.apache.kandula.coordinator.TimedOutException
>> at
>> org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionI
>> mpl.java:184)
>> ... 2 more
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
----- End forwarded message -----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
