View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820239#3820239
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820239 Yes, that is the behaviour you get "out of the box". We fixed this by naming the tomcat instances (tomcat and apache ends): 1) On distributor in workersX.properties under each worker [channel.socket:nodeX.xxxxx.co.nz:8009] port=8009 host=nodeX.xxxxx.co.nz tomcatId=nodeX <-- jvmRoute name [ajp13:nodeX.xxxxx.co.nz:8009] channel=channel.socket:nodeX.xxxxx.co.nz:8009 2) On each tomcat server inside the tomcat configuration deploy/jbossweb-tomcat41.sar/META-INF/jboss-service.xml look for your tomcat engine ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
