Web Container

This section describes known web container issues and associated solutions.

Unable to compile JSP page on resource constrained servers. (ID 6184122)

The JSP page is accessed but fails to compile, and the server log contains the error message “Unable to execute command” with the following stack trace:

at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec
(Execute.java:655) at org.apache.tools.ant.taskdefs.Execute.launch
(Execute.java:416) at org.apache.tools.ant.taskdefs.Execute.execute
(Execute.java:427) at org.apache.tools.ant.taskdefs.compilers.
DefaultCompilerAdapter.executeExternalCompile(DefaultCompilerAdapter.
java:448) at org.apache.tools.ant.taskdefs.compilers.JavacExternal.
execute(JavacExternal.java:81) at org.apache.tools.ant.taskdefs.Javac.
compile(Javac.java:842) at org.apache.tools.ant.taskdefs.Javac.execute
(Javac.java:682) at org.apache.jasper.compiler.Compiler.generateClass
(Compiler.java:396)

Solution

Set the JSP compilation switch fork to false.

This can be done either of two ways:

• Globally, by setting the fork init parameter of the JspServlet in ${S1AS_HOME}/domains/domain1/config/default-web.xml to false:

  <servlet\> <servlet-name\>jsp</servlet-name\> <servlet-class\>org.apache.
  jasper.servlet.JspServlet</servlet-class\> .... <init-param\> <param-name\>
  fork</param-name\> <param-value\>false</param-value\> </init-param\> .... 
  </servlet\>

• On a per-web application basis, by setting the fork JSP configuration property in sun-web.xml to false:

  <sun-web-app\> <jsp-config\> <property name="fork" value="false" /\> 
  </jsp-config\> </sun-web-app\>

Either setting will prevent ant from spawning a new process for javac compilation.