JBoss 4.2.x

The following VM option is required to run JConsole without clutter of JBoss JMX beans

-Dcom.sun.management.jmxremote

Add the following as Program Arguments if you want the clutter of JBoss JMX beans.

Unfortunately, you have to drill down to the standard VM JMX beans.

-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl -Djboss.platform.mbeanserver
-Dcom.sun.management.jmxremote

To run multiple instances under one install copy the jboss-4.2.x/server/<serverName> to new instance names.

To change ports to eliminate conflicts, edit jboss-4.2.x/server/<serverName>/deploy/conf/jboss-service.xml

To change default 8080 web port, edit and change the connector:
jboss-4.2.2.GA\server\default\deploy\jboss-web.deployer\server.xml

edit and change the invoker:
jboss-4.2.2.GA\server\default\deploy\http-invoker.sar\META-INF\jboss-service.xml

To create custom startup scripts, copy and edit jboss-4.2.x/bin/ run.sh and run.conf

Enabling logging of load balancer http header x-forward-for in jboss access.log:

edit: jboss-4.2.2.GA\server\default\deploy\jboss-web.deployer\server.xml

uncomment: <Valve className="org.apache.catalina.valves.AccessLogValve"
change pattern="common" to: pattern="%{X-Forwarded-for}i %l %u %t %r %s %b"

Comments

Popular posts from this blog

Oracle JDBC ReadTimeout QueryTimeout

Generically load enum mapping via properties file

ActiveMQ https