This will be fixed in 6.3.1.
This has been fixed in upstream 4.2 branch.
verified on EAP 6.3.1.CP.CR1