Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Verified in EAP 6.3.0.ER7.
Hi Scott, I changed the doc to reflect that this is a bugfix, not a known issue in EAP 6.3.0. Could you make sure this change gets reflected in the next build of release notes? Thanks.
The resolution of this issue was to change the hardcoded timeout from 300 seconds (5 minutes) to Integer.MAX_VALUE.
See also https://bugzilla.redhat.com/show_bug.cgi?id=1265300 for a subsequent refinement.