Our production environment requires $JBOSS_HOME/bin to be read-only. Apparently 3.2.1 trys to compile jmx-servlet code in a temp directory that it tries to create in $JBOSS_HOME/bin. The following partial trace occurred when I tried to bring up the jmx-console:

I did as you suggested but the problem persisted, however I uncovered the cause. I was using $JBOSS_HOME/bin/jboss_init_redhat.sh. This script changes directory to $JBOSS_HOME/bin before invoking JBOSS. I still got the same error when invoking run.sh from $JBOSS_HOME/bin. The problem goes away when I invoke run.sh from a writable directory, in my case, /tmp.

Curiously, I did not have this problem in 3.2.0.

Thanks for your help.jj

> You can change the jasper servlet> to use a different directory.> This in webdefaults.xml or web.xml> inside jbossweb-xxx.sar>>> <servlet-name>jsp</servlet-name>>>>> <servlet-class>org.apache.jasper.servlet.JspServlet</&gt; ervlet-class>> <init-param>> <param-name>scratchdir</param-name>> <param-value>${path.to.dir}</param-value>> </init-param>> ...>> I have no idea why it would be trying to create> them in bin? Have you changed the jboss temp> directory setting, is it correct?>> Regards,> Adrian

I just downloaded installed the jboss-3.2.1_Tomcat 4.1.24 on window xp. I have my java_home setup. Without modifying anything, I ran jboss. It seems started ok. However, when I go to browser and type in http://localhost:8080/jmx-console, I got "org.apache.jasper.JasperException: Unable to compile class for JSP". What did I do wrong?