-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception if transaction timeout occured before partitions complete #20
Comments
JSR define this workflow! So my question is how can I handle long time partition execution if analyzer work in a unique transaction? I excpected that was the single method in transaction not the loop.
|
will look into it next. |
According to the spec section you quoted above (section 11.7), all the work on the main thread by analyzer and reducer are in one single transaction. So I think you will need to adjust tx timeout to allow for time taken by analyzer and reducer processing, partition scheduling and dispatching and communication overhead. The scope of the partition main thread transaction (single-method vs loop), I will check with spec expert group to see why it is designed this way. |
See RI Bug https://java.net/bugzilla/show_bug.cgi?id=6356 |
Yes they admit taht spec need a clarification. By now to solve my problem i've made a fix to jberet and I've updated my Wildfly 8.1 server installation. |
Somewhat related issue: |
If I run a partitioned step with a low transaction timeout (15s) all partitions run well, everyone in a separate transaction that stay alive for max 1s, but the partition analyzer loop is in a unique transaction so if timeout occured then at the end of all partition executions I got this exception:
While partition executions:
Then at partitions end:
The text was updated successfully, but these errors were encountered: