EAP 6.0.1 domain BROKEN PIPE
alexval-es opened this issue · comments
Hi, I first tryed with jboss7.1.1 standalone and zorka started ok
Now I'm using:
zorka-1.0.7
RHEL-6.4
EAP-6.0.1.zip
zabbix-2.2.6
I followed zorka configuration instrucctions for jboss7 domain mode (http://zorka.io/install/jboss7.html), and started domain.sh, then host-controller and process-controller processes started, but server instance didn't start.
On ../domain/log/process-controller.log showed java.IO.Exception BROKEN PIPE.
And ../domain/servers/as0/log/boot.log and server.log were not touched on the try.
This is not a desired configuration, but I could start ok, with only one server instance, by adding -javaagent:/path_to/zorka.jar=/path_to on JAVA_OPTS in file domain.conf.
Zabbix is even reading data from zorka agent ;-)
Maybe is something that I'm missing after reading the instrucctions.
Please can you provide more detailed instruccions on how to configure zorca to work with jboss domain for multiple instances.
I can make any test you need.
Thanks.
This is additional info on how it's working:
[root@as0-c2-pre ~]# ps -ef | grep java
jboss 32352 32292 1 19:35 ? 00:00:55 java -D[Process Controller] -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman,com.jitlogic.zorka.core.spy -Djava.awt.headless=true -Djboss.domain.default.config=domain.xml -Djboss.host.default.config=host.xml -javaagent:/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/servers/as0.8080/zorka/zorka.jar=/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/servers/as0.8080/zorka -Dorg.jboss.boot.log.file=/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/log/process-controller.log -Dlogging.configuration=file:/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/configuration/logging.properties -jar /home/jboss/EAP-6.0.1/jboss-eap-6.0/jboss-modules.jar -mp /home/jboss/EAP-6.0.1/jboss-eap-6.0/modules org.jboss.as.process-controller -jboss-home /home/jboss/EAP-6.0.1/jboss-eap-6.0 -jvm java -mp /home/jboss/EAP-6.0.1/jboss-eap-6.0/modules -- -Dorg.jboss.boot.log.file=/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/log/host-controller.log -Dlogging.configuration=file:/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/configuration/logging.properties -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman,com.jitlogic.zorka.core.spy -Djava.awt.headless=true -Djboss.domain.default.config=domain.xml -Djboss.host.default.config=host.xml -javaagent:/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/servers/as0.8080/zorka/zorka.jar=/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/servers/as0.8080/zorka -- -default-jvm java --host-config=host-as0.Master.xml --pc-port=9898 -b as0-c2-pre -bmanagement as0-c2-pre
jboss 32372 32352 1 19:35 ? 00:00:59 java -D[Host Controller] -Dorg.jboss.boot.log.file=/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/log/host-controller.log -Dlogging.configuration=file:/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/configuration/logging.properties -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman,com.jitlogic.zorka.core.spy -Djava.awt.headless=true -Djboss.domain.default.config=domain.xml -Djboss.host.default.config=host.xml -javaagent:/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/servers/as0.8080/zorka/zorka.jar=/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/servers/as0.8080/zorka -jar /home/jboss/EAP-6.0.1/jboss-eap-6.0/jboss-modules.jar -mp /home/jboss/EAP-6.0.1/jboss-eap-6.0/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.host-controller -mp /home/jboss/EAP-6.0.1/jboss-eap-6.0/modules --pc-address 127.0.0.1 --pc-port 9898 -default-jvm java --host-config=host-as0.Master.xml -b as0-c2-pre -bmanagement as0-c2-pre -Djboss.home.dir=/home/jboss/EAP-6.0.1/jboss-eap-6.0
jboss 32435 32352 1 19:35 ? 00:01:49 /usr/lib/jvm/java-1.6.0-sun-1.6.0.45.x86_64/jre/bin/java -D[Server:as0.8080] -XX:PermSize=512m -XX:MaxPermSize=512m -Xms512m -Xmx2048m -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.bind.address=as0-c2-pre -Dsun.rmi.dgc.client.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Dorg.apache.el.parser.COERCE_TO_ZERO=false -Djboss.host.default.config=host.xml -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.apache.tomcat.util.http.Parameters.MAX_COUNT=5000 -Djboss.modules.system.pkgs=org.jboss.byteman,com.jitlogic.zorka.core.spy -Doracle.jdbc.ReadTimeout=900000 -Des.odec.server.identity=172.16.125.150:8080 -Djboss.domain.default.config=domain.xml -Djava.net.preferIPv4Stack=true -Djboss.bind.address.management=as0-c2-pre -Dorg.apache.tomcat.util.net.MAX_THREADS=1200 -D[Host=true -Djboss.home.dir=/home/jboss/EAP-6.0.1/jboss-eap-6.0 -DuseJK=true -Dorg.quartz.scheduler.skipUpdateCheck=true -Dcom.arjuna.ats.arjuna.allowMultipleLastResources=true -Djboss.server.log.dir=/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/servers/as0.8080/log -Djboss.server.temp.dir=/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/servers/as0.8080/tmp -Djboss.server.data.dir=/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/servers/as0.8080/data -Dorg.jboss.boot.log.file=/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/servers/as0.8080/log/boot.log -Dlogging.configuration=file:/home/jboss/EAP-6.0.1/jboss-eap-6.0/domain/configuration/logging.properties -jar /home/jboss/EAP-6.0.1/jboss-eap-6.0/jboss-modules.jar -mp /home/jboss/EAP-6.0.1/jboss-eap-6.0/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.server
root 32681 31729 0 21:06 pts/0 00:00:00 grep java
Possibly agent broke down before it was even able to start, so it crashed whole JVM process. Check console logs for server instance, maybe there are some hints. Note that com.jitlogic.zorka.core.spy package has to be added to jboss modules system classpath not only in domain controller process but also for started instances.
I'm closing this for now (sorry it took so long), it you're still interested in solving this issue please reopen.