JAR file modules/system/layers/base/org/jboss/ironjacamar/impl/main/ironjacamar-deployers-common.jar contains different class content of org/jboss/jca/deployers/DeployersLogger_$logger.class and !org/jboss/jca/deployers/DeployersBundle_$bundle.class compared to ZIP. This JAR file contains also *.java and these are different compared to ZIP. We shouldn't mix compiled files with source JAVA files. JAR file modules/system/layers/base/org/jboss/ironjacamar/impl/main/ironjacamar-common-impl.jar contains different class content of org/jboss/jca/common/CommonBundle_$bundle.class and org/jboss/jca/common/CommonLogger_$logger.class compared to ZIP. JAR file modules/system/layers/base/org/jboss/ironjacamar/impl/main/ironjacamar-core-impl.jar contains different class content of org/jboss/jca/core/CoreBundle_$bundle.class and org/jboss/jca/core/CoreLogger_$logger.class compared to ZIP. All (not only above mentioned) IronJamacar JAR files contain different META-INF/MANIFEST.MF compared to ZIP.
Still valid for EAP-6.1.1-ER3 on RHEL5.
The fix consists in moving to an ironjacamar-eap6 repolib wrapper on 6.2
nack is for 6.1.1 only. High risk
Created ironjacamar-eap6 package which will ensure that content is the same across different distros (RHEL 5 and RHEL 6).
Fixed in EAP-6.2.0-ER3.