Adding and changing Mod JK JVM route, URI encoding and thread settings for JBoss

In your JBoss server there is a file that can be amended to alter the URI encoding and the number of threads used by JBoss. Additionally if you’re using mod_JK to link Apache HTTP and JBoss/Tomcat you can specify a JVM route parameter here that allows Apache to route incoming requests to the correct node.

To do this we need to look at the following file:

\jboss\server\[SERVER NAME]\deploy\jbossweb-tomcat55.sar\server.xml

In here we can amend a couple of parameters and add in a few extra values. For thread numbers and URI encoding look in the file

Adding and changing Mod JK JVM route, URI encoding and thread settings for JBoss

Setting the JDK version and compiler in JBoss for JSP pages

If you need to run Java 1.5 in your JSP’s in JBoss 4.0.5.GA you can do so by editing a small setting in an XML file in your server directory:

\jboss\server\[SERVER NAME]\deploy\jbossweb-tomcat55.sar\conf\web.xml

You can then change the compiler version by un-commenting the code below which you will find in the web.xml.

Setting the JDK version and compiler in JBoss for JSP pages

Running multiple instances of Jboss on one server.

To run multiple Jboss instances on the one server is pretty easy – but remember that if you’re running something like ATG commerce you’re going to need a few Gb of memory to run just the one JBoss instance let alone multiples. So you may want seriously consider keeping separate VM’s for each server in your production environment depending on your application requirements e.g for heavyweight commerce keep them all as separate as possible. But for quickly building a development environment this is the way to go.

Anyway, the main thing to worry about with JBoss is the network ports setting as each instance needs it’s own port range, once you’ve done this then it’s all down to your application as to which port set it needs to use. So here’s how to set multiple instances and their respective ports. You’ll see that most if not all config for JBoss is done with XML files.

Running multiple instances of Jboss on one server.

ATG Log Colorizer for JBoss

A very useful utility to add on to ATG when launched in JBoss (or probably any other platform like Weblogic). Displays logs in nice pretty colours – avoid the red, no one wants to see it!

Can be found here on source forge

.

Download, install/ move to suitable directory and the run on the end of your JBoss/ATG start up script.

e.g. for the default ATG startup in windows command prompt use:

C:\ATG\ATG2007.1\home\bin\startDynamoOnJBOSS -c default -f -run-in-place -m myProjectName | C:\ATG\ATGLogColorizer.exe