CompileCommand for Weblogic 6.0

Question

          My JSP pages are failing Weblogic 6.0 with the error
          Couldn't find init param: compileCommand
          Any ideas why?
          

Answer 1

          A solution finally !!!!!
          When converting weblogic.properties from 5.1, it automatically places the JSPServlet
          registration in web.xml of the default application. For whatever reason this makes
          it not work.
          Remove the JSPServlet registration from the web.xml file. It will be automatically
          registered (I guess default behavior) and will then work.
          Sanjeev
          "Sanjeev Mishra" <[email protected]> wrote:
          >
          >I am getting the same problem after migrating from 5.1 to 6.0. I have specified
          >the
          >full path to javac.exe in weblogic.xml (default application), and config.xml.
          >Is
          >there any resolution to this? Is there any way to turn more debugging on
          >to let us
          >know exactly what is happening?
          >
          >Sanjeev
          >
          >Dana Jeffries <[email protected]> wrote:
          >>I looked at a couple of other things but didn't make any progress.
          >>
          >>I'll enter a CR.
          >>
          >>Charlie Crook wrote:
          >>
          >>> web.xml does not have any compileCommands entries.
          >>>
          >>> "Dana Jeffries" <[email protected]> wrote in message
          >>> news:[email protected]...
          >>> > Check out the web.xml and see if there's an init-param
          >>> weblogic.jsp.compileCommand there. Perhaps it
          >>> > has an empty value.
          >>> >
          >>> > Charlie Crook wrote:
          >>> >
          >>> > > The setting in weblogic.xml is the same as in config.xml, so it doesn't
          >>> > > really matter which one takes effect. The solaris machines have
          >a
          >>> standard
          >>> > > directory layout, so it is in fact already portable and not
          >>> > > machine-dependent. And javac is on the path of the unix user account
          >>> which
          >>> > > runs WL.
          >>> > >
          >>> > > I think you're missing the point.
          >>> > >
          >>> > > javax.servlet.UnavailableException: Couldn't find init param:
          >>> compileCommand
          >>> > >
          >>> > > "Dana Jeffries" <[email protected]> wrote in message
          >>> > > news:[email protected]...
          >>> > > > Maybe you're overriding the compile command in the webogic.xml
          >file
          >>> (it's
          >>> > > the <session-param>
          >>> > > > compileCommand?
          >>> > > >
          >>> > > > Ah...... yes I see that now in your weblogic.xml file below. I
          >didn't
          >>> see
          >>> > > it in the exception noise
          >>> > > > the first time.
          >>> > > >
          >>> > > > weblogic.xml defines the compile command as javac which means it
          >>must
          >>> be
          >>> > > on the path. The value in
          >>> > > > the weblogic.xml file overrides any setting set in the server.
          >I'd
          >>> suggest
          >>> > > that, for portability,
          >>> > > > you remove the compileCommand from weblogic.xml as you probably
          >>don't
          >>> have
          >>> > > a reason for overriding
          >>> > > > the default compiler. (Jikes or WebGain's sj.exe will cut the JSP
          >>> compile
          >>> > > times dramatically (>4X).
          >>> > > >
          >>> > > > If you do need the override, I'd still recommend that you keep
          >it
          >>> generic
          >>> > > so that it doesn't need
          >>> > > > updating on a machine basis.
          >>> > > >
          >>> > > > -dana
          >>> > > >
          >>> > > >
          >>> > > > Charlie Crook wrote:
          >>> > > >
          >>> > > > > In the config.xml, we had:
          >>> > > > > /jdk130/bin/javac
          >>> > > > >
          >>> > > > > yet the admin Console reported only
          >>> > > > > javac
          >>> > > > >
          >>> > > > > So where was the Console reading from?
          >>> > > > >
          >>> > > > > So, we set the Console to the value in the config.xml, rebooted
          >>and
          >>> have
          >>> > > the
          >>> > > > > same error. If we register the jsp, it works, but we didn't
          >have
          >>to
          >>> > > > > register the jsp files in 5.1; why now?
          >>> > > > >
          >>> > > > > "Dana Jeffries" <[email protected]> wrote in message
          >>> > > > > news:[email protected]...
          >>> > > > > > If you migrated weblogic.properties, then check config.xml
          >in
          >>the
          >>> > > domain
          >>> > > > > directory
          >>> > > > > > (config/mydomain/config.xml). You can also check it out using
          >>the
          >>> > > Console
          >>> > > > > under the
          >>> > > > > > Servers/<domain>/Compilers
          >>> > > > > >
          >>> > > > > > Under the <Server ... check out JavaCompiler and make sure
          >it's
          >>> set
          >>> > > right.
          >>> > > > > >
          >>> > > > > > Charlie Crook wrote:
          >>> > > > > >
          >>> > > > > > > We are having the same problem after migrating from 5.1 (
          >>where
          >>> it
          >>> > > > > worked )
          >>> > > > > > > , and the javac compiler is in the path ( which was unchanged
          >>).
          >>> > > > > > >
          >>> > > > > > > from the domain's log:
          >>> > > > > > > ####<Jan 16, 2001 2:08:03 PM EST> <Error> <HTTP>
          >>> > > > > <p5adv.nielsenmedia.com>
          >>> > > > > > > <myserver> <ExecuteThread-12> <> <> <101018>
          >>> > > > > > > <[WebAppServletContext(4057696,monitorplus)] Servlet failed
          >>with
          >>> > > > > > > ServletException>
          >>> > > > > > > javax.servlet.UnavailableException: Couldn't find init param:
          >>> > > > > compileCommand
          >>> > > > > > > at
          >>> > > > > > >
          >>> > > > >
          >>> > >
          >>> weblogic.servlet.jhtmlc.PageCompileServlet.init(PageCompileServlet.java:82)
          >>> > > > > > > at weblogic.servlet.JSPServlet.init(JSPServlet.java:50)
          >>> > > > > > > at
          >>> > > > > > >
          >>> > > > >
          >>> > >
          >>> weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
          >>> > > > > > > :687)
          >>> > > > > > > at
          >>> > > > > > >
          >>> > > > >
          >>> > >
          >>> weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.ja
          >>> > > > > > > va:625)
          >>> > > > > > > at
          >>> > > > > > >
          >>> > > > >
          >>> > >
          >>> weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
          >>> > > > > > > a:573)
          >>> > > > > > > at
          >>> > > > > > >
          >>> > > > >
          >>> > >
          >>> weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:29
          >>> > > > > > > 5)
          >>> > > > > > > at
          >>> > > > > > >
          >>> > > > >
          >>> > >
          >>> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          >>> > > > > > > :204)
          >>> > > > > > > at
          >>> > > > > > >
          >>> > > > >
          >>> > >
          >>> weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          >>> > > > > > > ntext.java:1127)
          >>> > > > > > > at
          >>> > > > > > >
          >>> > > > >
          >>> > >
          >>> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          >>> > > > > > > :1529)
          >>> > > > > > > at
          >>> weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          >>> > > > > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >>> > > > > > >
          >>> > > > > > > in the application's weblogic.xml:
          >>> > > > > > >
          >>> > > > > > > <jsp-descriptor>
          >>> > > > > > > <jsp-param>
          >>> > > > > > > <param-name> compileCommand </param-name>
          >>> > > > > > > <param-value> javac </param-value>
          >>> > > > > > > </jsp-param>
          >>> > > > > > > <!-- default is false -->
          >>> > > > > > > <jsp-param>
          >>> > > > > > > <param-name> precompile </param-name>
          >>> > > > > > > <param-value> true </param-value>
          >>> > > > > > > </jsp-param>
          >>> > > > > > >
          >>> > > > > > > <!-- default is jsp_servlet -->
          >>> > > > > > > <jsp-param>
          >>> > > > > > > <param-name> packagePrefix </param-name>
          >>> > > > > > > <param-value> jsp_servlet </param-value>
          >>> > > > > > > </jsp-param>
          >>> > > > > > >
          >>> > > > > > > <!-- default is false -->
          >>> > > > > > > <jsp-param>
          >>> > > > > > > <param-name> keepgenerated </param-name>
          >>> > > > > > > <param-value> false </param-value>
          >>> > > > > > > </jsp-param>
          >>> > > > > > >
          >>> > > > > > > <!-- default is true -->
          >>> > > > > > > <jsp-param>
          >>> > > > > > > <param-name> verbose </param-name>
          >>> > > > > > > <param-value> true </param-value>
          >>> > > > > > > </jsp-param>
          >>> > > > > > >
          >>> > > > > > > <!-- default is 1 second. Set to 0 to check on every request.
          >>> Set
          >>> > > > > to -1 to
          >>> > > > > > > disable -->
          >>> > > > > > > <jsp-param>
          >>> > > > > > > <param-name> pageCheckSeconds </param-name>
          >>> > > > > > > <param-value> 1 </param-value>
          >>> > > > > > > </jsp-param>
          >>> > > > > > >
          >>> > > > > > > <!-- Default encoding is the default encoding for the
          >>> platform -->
          >>> > > > > > > <!-- <jsp-param>
          >>> > > > > > > <param-name> encoding </param-name>
          >>> > > > > > > <param-value> Cp1252 </param-value>
          >>> > > > > > > </jsp-param>
          >>> > > > > > > -->
          >>> > > > > > >
          >>> > > > > > > <!-- default is true; session tracking is enabled -->
          >>> > > > > > > <jsp-param>
          >>> > > > > > > <param-name> TrackingEnabled </param-name>
          >>> > > > > > > <param-value> true </param-value>
          >>> > > > > > > </jsp-param>
          >>> > > > > > >
          >>> > > > > > > </jsp-descriptor>
          >>> > > > > > >
          >>> > > > > > > "Dana Jeffries" <[email protected]> wrote in message
          >>> > > > > > > news:[email protected]...
          >>> > > > > > > > Maybe javac.exe isn't on your system path.
          >>> > > > > > > >
          >>> > > > > > > > Provide more information.
          >>> > > > > > > >
          >>> > > > > > > > Karen Van Bemmel wrote:
          >>> > > > > > > >
          >>> > > > > > > > > My JSP pages are failing Weblogic 6.0 with the error
          >>> > > > > > > > > Couldn't find init param: compileCommand
          >>> > > > > > > > > Any ideas why?
          >>> > > > > > > >
          >>> > > > > >
          >>> > > >
          >>> >
          >>
          >