Package org.apache.ofbiz.service.test
Class ServiceEngineTestServices
java.lang.Object
org.apache.ofbiz.service.test.ServiceEngineTestServices
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptiontestServiceDeadLockRetry
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceDeadLockRetryThreadA
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceDeadLockRetryThreadB
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceEcaGlobalEventExec
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceEcaGlobalEventExecOnCommit
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceEcaGlobalEventExecOnRollback
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceEcaGlobalEventExecToRollback
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceLockWaitTimeoutRetry
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceLockWaitTimeoutRetryCantRecover
(DispatchContext dctx, Map<String, ? extends Object> context) NOTE that this is a funny case where the auto-retry in the service engine for the call to testServiceLockWaitTimeoutRetryCantRecoverWaiter would NOT be able to recover because it would try again given the new transaction and all, but the lock for the waiting thread would still be there...testServiceLockWaitTimeoutRetryCantRecoverWaiter
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceLockWaitTimeoutRetryGrabber
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceLockWaitTimeoutRetryWaiter
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceOwnTxSubServiceAfterSetRollbackOnlyInParent
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceOwnTxSubServiceAfterSetRollbackOnlyInParentErrorCatchWrapper
(DispatchContext dctx, Map<String, ? extends Object> context) testServiceOwnTxSubServiceAfterSetRollbackOnlyInParentSubService
(DispatchContext dctx, Map<String, ? extends Object> context)
-
Constructor Details
-
ServiceEngineTestServices
public ServiceEngineTestServices()
-
-
Method Details
-
testServiceDeadLockRetry
-
testServiceDeadLockRetryThreadA
-
testServiceDeadLockRetryThreadB
-
testServiceLockWaitTimeoutRetry
-
testServiceLockWaitTimeoutRetryGrabber
-
testServiceLockWaitTimeoutRetryWaiter
-
testServiceLockWaitTimeoutRetryCantRecover
public static Map<String,Object> testServiceLockWaitTimeoutRetryCantRecover(DispatchContext dctx, Map<String, ? extends Object> context) NOTE that this is a funny case where the auto-retry in the service engine for the call to testServiceLockWaitTimeoutRetryCantRecoverWaiter would NOT be able to recover because it would try again given the new transaction and all, but the lock for the waiting thread would still be there... so it will fail repeatedly.TODO: there's got to be some way to do this, but how?!? :(
NOTE: maybe this will work: create a list that the service engine maintains of services it will run after the current service run is complete, and AFTER it has committed or rolled back its transaction; if a service finds it has a lock wait timeout, add itself to the list for its parent service (somehow...) and off we go!
- Parameters:
dctx
- the dispatch contextcontext
- the context- Returns:
- returns the results of the service execution
-
testServiceLockWaitTimeoutRetryCantRecoverWaiter
-
testServiceOwnTxSubServiceAfterSetRollbackOnlyInParentErrorCatchWrapper
-
testServiceOwnTxSubServiceAfterSetRollbackOnlyInParent
-
testServiceOwnTxSubServiceAfterSetRollbackOnlyInParentSubService
-
testServiceEcaGlobalEventExec
-
testServiceEcaGlobalEventExecOnCommit
-
testServiceEcaGlobalEventExecToRollback
-
testServiceEcaGlobalEventExecOnRollback
-