JBoss AS 7.1.1

[Richard Briceno]

Good night team,

Currently it is trying to monitor a Jboss AS 7.1.1, on a redhat server, but when configuring the standalone.conf the application does not work.

It is being configured:

JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager"
JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:/www/preproduccion/jboss-as-7.1.1.Final/modules/org/jboss/logmanager/log4j/main/jboss-logmanager-log4j-1.0.0.GA.jar;/www/preproduccion/jboss-as-7.1.1.Final/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager,com.wily,com.wily.*"
JAVA_OPTS="$JAVA_OPTS -javaagent:/www/preproduccion/agenteapm/jboss.unix/wily/Agent.jar"
JAVA_OPTS="$JAVA_OPTS -DagentProfile=/www/preproduccion/agenteapm/jboss.unix/wily/core/config/IntroscopeAgent.profile"

When reviewing the log, it is observed that:

See http://www.oracle.com/technetwork/java/javase/documentation/index.html for more details.
/www/preproduccion/jboss-as-7.1.1.Final/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar: line 1: PK: command not found
/www/preproduccion/jboss-as-7.1.1.Final/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar: line 2: ¦^B@: command not found
/www/preproduccion/jboss-as-7.1.1.Final/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar: line 4: syntax error near unexpected token `)'
/www/preproduccion/jboss-as-7.1.1.Final/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar: line 4: `¦¦?¦2¦¦¦h(¦T2p>¦¦O?.7¦:¦¦z¦¦3X¦X¦¦`¦¦tY)u?H?¦knR¦¦¦¦¦y?`t¦¦l¦m¦¦h¦k¦o¦¦?!+_°\¦f¦¦¦¦¦¦p¦¦¦]t¦}¦$¦34)¦<A¦¦¦¦?¦,,¦¦.¦BT&t'¦w¦¦Dr2¦#2¦¦8<¦?¦¦¦¦¦7¦¦c¦'

PuTTY./standalone.sh: line 178: /www/preproduccion/jboss-as-7.1.1.Final/modules/org/apache/log4j/main/log4j-1.2.16.jar: cannot execute binary file

The jboss-logmanager-1.2.2.GA.jar file was downloaded from the Jboss page, and the same error still occurs.

Has anyone happened to you?

Richard

[Haruhiko Davis]

First:

• Is your JBoss running in standalone or domain mode?
• The JAR files needed for logging will depend on your build version, so you need to walk through your $JBOSS_HOME/modules directory to make sure they match the ones you have.
• You should not have to download any additional JARs that are not present with the JBoss archive, unless something was corrupt or completely missing during the packaging.

------------------------------
Custom Solution Architect
Broadcom
------------------------------

[Richard Briceno]

Hi Davis,

• Is your JBoss running in standalone or domain mode?

           A: My Jboss running in standolone

• The JAR files needed for logging will depend on your build version, so you need to walk through your $JBOSS_HOME/modules directory to make sure they match the ones you have.

          A: Ok, perfect

• You should not have to download any additional JARs that are not present with the JBoss archive, unless something was corrupt or completely missing during the packaging.

           A:I'm going to try downloading the jboss again, and copying the jar to the application server, maybe they are corrupt

[Richard Valdez]

Hello Richard:

Try adding the variables in this way

WILY_OPTS="-javaagent:/www/preproduccion/agenteapm/jboss.unix/wily/Agent.jar -Dcom.wily.introscope.agentProfile=/www/preproduccion/agenteapm/jboss.unix/wily/core/config/IntroscopeAgent.profile -Djboss.modules.system.pkgs=org.jboss.byteman,com.wily,com.wily.*"

JAVA_OPTS="$JAVA_OPTS $WILY_OPTS"


Regards

------------------------------
Sr. Analyst
OSDE
------------------------------

[Richard Briceno]

Good Morning,

I will try, and I tell him. But without adding the lines of the logManager?

Thanks,
Richard

[Haruhiko Davis]

Make sure your arguments are actually in $JBOSS_HOME/bin/standalone.conf, otherwise you will create duplicate properties and cause issues.

You only need to specify the logmanager JARs if your application server complains about needing them. Start with Just updating the system packages variables and the agent JAR and profile.

As a reminder, if you're using 10.5+, you can shorten the property for agentProfile to -DagentProfile=<path-to-profile>. These shortcuts are documented in the wiki for reference.

------------------------------
Custom Solution Architect
Broadcom
------------------------------

[Richard Briceno]

Hi Richard,

Thank you very much, it worked with the recommendation given.

Richard!