+1 I would say we need a reproducer for that behaviour. I am not even sure how it would be possible. What are you doing in EJB1? I assume some other transactional work?
What Puneet is saying is that the connection that is started/used in the parent transaction, if it is used in a REQUIRES_NEW child transaction, then the changes done by child transaction on top that connection is only visible when the parent transaction commits.
I think this behaviour might be due to the Parent transaction not delisting the resource when it calls the REQUIRES_NEW child transaction and so the changes done by both parent and child on top of same connection is visible only when the parent transaction is committed.
Work Around that i tried is using a new connection for very transaction in this case REQUIRES_NEW behaviour is correct.
So i think its a problem with the transaction and its resource associations. Something is going wrong here. enlist/delist or JCA issue or do JBOSS demands new connection for very transaction?
I think you will need to try to reproduce this on WFLY. There are many many enhancements since EAP 5.2 and it would be difficult to be sure its not something that has been subsequently modified. Alternatively if you have a support contract I would recommend raising a ticket with the support team to get it looked into.
Sorry I can't be more help,