We see the same problem here with 4.2.0.a2 B6241 and B6288
I was letting the runtime use its default, standalone.xml.
The developers see the same problem when trying a standalone-full.xml setup.
RH: any idea of when this runtime will become fully usable? We have started working on our EAP6.1 migration, and this is rather annoying.
Thanks,
Jesper