[ http://issues.apache.org/jira/browse/OFBIZ-201?page=comments#action_12432935 ] Peter Goron commented on OFBIZ-201: -----------------------------------
Si, It's ok for me to just do rowCount * service.transactiontimeout for now. To be able to configure transaction behavior, I think we could use path parameter to select the transaction mode like it is done for sync/async stuff in ServiceHandler. The difficult part for me is to choose the good terms to describe transaction behaviors. What do you think of : - stop-on-error, with a global transaction (default choice in order to be backward compatible with existing stuff) - continue-on-error, with a new transaction per service call Peter > There is no way to define the timeout of the transaction used by > ServiceMultiEventHandler > ----------------------------------------------------------------------------------------- > > Key: OFBIZ-201 > URL: http://issues.apache.org/jira/browse/OFBIZ-201 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: framework > Affects Versions: SVN trunk > Environment: Linux, postgresql > Reporter: Peter Goron > Attachments: ServiceMulti-Si.patch, ServiceMultiEventHandler.patch, > ServiceMultiEventHandler.patch > > > The transaction created by service-multi event handler uses the default > transaction timeout (60s). I've found no way to increase this value. > I think the default timeout of service-multi should be at least the timeout > defined in the service definition (transaction-timeout) of the service called > (see attached patch). > Maybe the default value should be service's timeout multiply by rowCount ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
