When I change the delay parameter to:
public static final int RETRY_DELAY_MILLIS = 3 * 1000;
public static final int RESPONSE_DELAY_MILLIS = 1 * 1000;
// public static final int RETRY_DELAY_MILLIS = 20 * 1000;
// public static final int RESPONSE_DELAY_MILLIS = 3 * 1000;
// FIXME:
public static final int DEFAULT_TIMEOUT_MILLIS = 2 * 1000;
<======== (1)
//public static final int DEFAULT_TIMEOUT_MILLIS = 180 * 1000;
I meet the following exception:
[ATCoordinatorImpl] timeout PREPARING_DURABLE
javax.transaction.xa.XAException
at
org.apache.geronimo.transaction.manager.TransactionManagerImpl.rollback(TransactionManagerImpl.java:239)
at org.apache.kandula.geronimo.Mediator.rollback(Mediator.java:123)
at
org.apache.kandula.coordinator.at.AbstractParticipant.rollbackOperation(AbstractParticipant.java:191)
======================================================
When I change the delay parameter to:
public static final int RETRY_DELAY_MILLIS = 3 * 1000;
public static final int RESPONSE_DELAY_MILLIS = 1 * 1000;
// public static final int RETRY_DELAY_MILLIS = 20 * 1000;
// public static final int RESPONSE_DELAY_MILLIS = 3 * 1000;
// FIXME:
public static final int DEFAULT_TIMEOUT_MILLIS = 1 * 1000;
<======== (2)
//public static final int DEFAULT_TIMEOUT_MILLIS = 180 * 1000;
I meet the following exception:
[HelloWorldAction] result 1000
[TransactionManagerImpl] tx 0
[TransactionManagerImpl] forget() 0
[TransactionImpl] tm.suspend() 0
[CallbackRegistry] registerCallback: timeout= 1000
[TransactionImpl] 47
[TransactionImpl] 1 47
[TransactionImpl] 2 94
[ATCoordinatorImpl] timeout PREPARING_VOLATILE
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.ATCoordinatorImpl.timeout(ATCoordinatorImpl.java:491)
at
org.apache.kandula.coordinator.CallbackRegistry$1.run(CallbackRegistry.java:63)
at java.util.TimerThread.mainLoop(Timer.java:512)[TransactionImpl] 3
1453
at java.util.TimerThread.run(Timer.java:462)
[AbstractParticipant] timeout NONE
org.apache.kandula.coordinator.TimedOutException
at
org.apache.kandula.coordinator.at.TransactionImpl.commit(TransactionImpl.java:203)
at
org.apache.kandula.coordinator.at.TransactionManagerImpl.commit(TransactionManagerImpl.java:74)
at
example.helloWorld.HelloWorldAction.execute(HelloWorldAction.java:100)
...
[HelloWorldAction] Exception java.lang.RuntimeException:
org.apache.kandula.coordinator.TimedOutException
[HelloWorldAction] wstm.commit() total time：2563
DEBUG --- ServletDispatcherResult.doExecute(55) | Forwarding to location
/test/greetings.jsp
======================================================
But when I change the delay parameter to:
(same as above)
// FIXME:
public static final int DEFAULT_TIMEOUT_MILLIS = 5 * 1000;
<======== (3)
//public static final int DEFAULT_TIMEOUT_MILLIS = 180 * 1000;
Kandula will run success with no exception, and the total time is 4969ms, it is
better then
9578ms.
So my question is in a product environment, how should I change the timeout
parameter in the
condition with no exception occurs and as soon as quickly to excute the global
tx ? Is there any
self adaptive method in kandula, i.e. kandula do it, not I change the timeout
parameter ?
Is there other method to improve kandula's performance ?
If the tcpmon out put is needed, I will send later. Now I only use 8080 port.
Thanks.
--- Dasarath Weeratunge <[EMAIL PROTECTED]>写道:
> Quoting Jack Wang <[EMAIL PROTECTED]>:
>
> > I have read Hannes's email. He giva another time test to kandula. I think
> > they are the same
> > problem. Please help.
>
> try reducing the delays in ATCoordinatorImpl. Look at the prepare/commit
> methods. with webservices, delays shouldn't be a problem.
>
> --dasarath
>
>
Jack Wang
____________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
