[sanne]

O.k.,

Great.

I'm also in this thread:

http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t= securing JMX access.

[sanne]

O.k. Securing rmi access boils down to disabling the org.jboss.jmx.connector/adaptor classes.

Most likely candidates would be:

jmx-ejb-connector-server.sar
jmx-rmi-adaptor.sar
jmx-invoker-adaptor-server.sar
jmx-ejb-adaptor.jar

Removing these would disable anyone from getting into the jmx services.

Sanne

[sanne]

Some tips on the basic integration with Apache/IIS could also be included.

[jonlee]

We already have a tech note at http://www.amitysolutions.com.au/documents/JK2-technote.pdf on Apache 2.0/JK2 for Jetty/Tomcat in JBoss.

[sanne]

O.k.,

Let's see if there is any way getting this all together so people can find it.

Having good install/maintenance instructions eases adaptation of technology I think.

Sanne

[sanne]

And just to remind myself: the java policies file.

[sanne]

Hi jonlee and Jeff,

Attached is a first proposal to a production quick guide on linux including most points and some additional ones mentioned in this thread.

I've asked the JBoss group whether there is any interest in this guide, no answers yet.

There is still a lot todo, but the main points are mentioned and somtimes filled in.

Sanne

[jonlee]

Looks good. Will go through in more detail tomorrow.

JK isn't too bad but JK2 is supposed to be more scalable - in-line with Apache 2.0 that has better scalability than the 1.3 series. So it depends on your production load. There is an alternative proposal to JK2 (can't remember what it is) but it hasn't been implemented in Tomcat or Jetty AFAIK.

[sanne]

O.k.

If you want to team up, I saw similar downloads at amity solutions, your're more then welcome.

At the moment I'm working in Word. Drop me a line if you're interested.

Sanne