Please post the entire exception stacktrace and more details on how to deploy or trigger the deployment of the .ear. Also, is any IDE (like Eclipse) involved in these deployments?
thanks for the fast reply.
If it can help, here's my JAVA_OPT when starting the WildFly instance:
export JAVA_OPTS="-server -Xms64m -Xmx2048m -XX:MaxPermSize=512m -XX:-UseGCOverheadLimit-Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS-Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/sector/ENV/COTs/TOOLs/wildfly-9.0.2.Final/standalone/log/boot.log -Dlogging.configuration=file:/home/sector/ENV/COTs/TOOLs/wildfly-9.0.2.Final/standalone/configuration/logging.properties -Djboss.home.dir="$SERVERIP" -Dorg.jboss.logmanager.nocolor=false -Djboss.bind.address.management="$SERVERIP" -Dorg.apache.coyote.ajp.MAX_PACKET_SIZE=65536 -Dorg.apache.cxf.logging.enabled=true"
Regarding the IDE I am using:
Eclipse Java EE IDE for Web Developers.
Version: Mars.2 Release (4.5.2)
Build id: 20160218-0600
The EAR is not deployed starting the server via Eclipse.
The container is managed outside the development environment.
Hi all, it's me again.
I was finally able to mange the bug (after 3 stressing days).
Starting from WildFly 8 the EAR components (WAR/JAR) are deployed in parallel. Due to the fact that each WAR we realized share the same XSDS that at runtime are deployed under wildfly data folder, it happened that a concurrent read/write on the same schema file was on stage at each deploy. The SAX reader was trying to read a file that in the meanwhile was in write by another deployment. That’s why the component who failed was totally random and also the type of the message.
The solution has been simply to make sequential the deployment of each of the components composing the EAR.
This has been done by adding to the application.xml of the EAR the following property:
To automatize the process for letting maven generate this value during the EAR generation process you should add
to the maven-ear-plugin configuration
Thank you jaikiran as well for the interest,
All the Best,