|
From: Bin_Duan/<Cla...@cl...> - 2003-09-23 18:42:21
|
We'd like to start JBoss currently hosting our J2EE application using
Wrapper. I followed the step-by-step instruction from the website to setup
JBoss wrapper. And the JBoss started up fine, but when I tried to access
our application, I got an error indicating unable to compile class for JSP
as follows:
org.apache.jasper.JasperException: Unable to compile class for JSP
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:479)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:184)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
Looks like I missed some classpath setup, but I did follow exactly from the
instruction on Wrapper website. Anyone has any idea what I missed? Thanks.
The following is the copy of my wrapper.conf file
#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=java
# Java Main class. This class must implement the WrapperListener interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=../lib/wrappertest.jar
wrapper.java.classpath.3=c:/java/jdk1.3/lib/tools.jar
wrapper.java.classpath.4=C:/JBoss/jboss-3.0.4/bin/run.jar
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib
# Java Additional Parameters
wrapper.java.additional.1=-Dprogram.name=run.bat
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=256
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=256
# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=org.jboss.Main
wrapper.app.parameter.2=-c
wrapper.app.parameter.3=mms
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console. (See docs for formats)
wrapper.console.format=PM
# Log Level for console output. (See docs for log levels)
wrapper.console.loglevel=INFO
# Log file to use for wrapper output logging.
wrapper.logfile=../logs/wrapper.log
# Format of output for the log file. (See docs for formats)
wrapper.logfile.format=LPTM
# Log Level for log file output. (See docs for log levels)
wrapper.logfile.loglevel=INFO
# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=0
# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0
# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE
#********************************************************************
# Wrapper NT Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
# Name of the service
wrapper.ntservice.name=MMS
# Display name of the service
wrapper.ntservice.displayname=MMS
# Description of the service
wrapper.ntservice.description=MMS
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
Bin Duan
|
|
From: Sal I. <sal...@sy...> - 2003-09-24 00:16:22
|
sounds like you're missing tools.jar from your path.
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=../lib/*.jar
wrapper.java.classpath.2=../bin/run.jar
wrapper.java.classpath.3=%JAVA_HOME%/lib/tools.jar
note that sun's java license prevents you from deploying the jdk to a
*production* system, and tools.jar is part of the jdk.
indirectly this means you can't deploy non-precompiled jsps.
-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of
Bin_Duan/Cla...@cl...
Sent: Tuesday, September 23, 2003 11:34 AM
To: wra...@li...
Subject: [Wrapper-user] JSP Compiling Error When Starting JBoss Using
Wrapper
We'd like to start JBoss currently hosting our J2EE application using
Wrapper. I followed the step-by-step instruction from the website to setup
JBoss wrapper. And the JBoss started up fine, but when I tried to access
our application, I got an error indicating unable to compile class for JSP
as follows:
org.apache.jasper.JasperException: Unable to compile class for JSP
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:4
79)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:1
84)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
Looks like I missed some classpath setup, but I did follow exactly from the
instruction on Wrapper website. Anyone has any idea what I missed? Thanks.
The following is the copy of my wrapper.conf file
#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=java
# Java Main class. This class must implement the WrapperListener interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=../lib/wrappertest.jar
wrapper.java.classpath.3=c:/java/jdk1.3/lib/tools.jar
wrapper.java.classpath.4=C:/JBoss/jboss-3.0.4/bin/run.jar
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib
# Java Additional Parameters
wrapper.java.additional.1=-Dprogram.name=run.bat
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=256
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=256
# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=org.jboss.Main
wrapper.app.parameter.2=-c
wrapper.app.parameter.3=mms
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console. (See docs for formats)
wrapper.console.format=PM
# Log Level for console output. (See docs for log levels)
wrapper.console.loglevel=INFO
# Log file to use for wrapper output logging.
wrapper.logfile=../logs/wrapper.log
# Format of output for the log file. (See docs for formats)
wrapper.logfile.format=LPTM
# Log Level for log file output. (See docs for log levels)
wrapper.logfile.loglevel=INFO
# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=0
# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0
# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE
#********************************************************************
# Wrapper NT Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
# Name of the service
wrapper.ntservice.name=MMS
# Display name of the service
wrapper.ntservice.displayname=MMS
# Description of the service
wrapper.ntservice.description=MMS
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
Bin Duan
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
|
|
From: <da...@ix...> - 2003-09-24 16:44:59
|
In article <014501c38230$ec847290$6502a8c0@fs1>,
Sal Ingrilli <wra...@li...> wrote:
>note that sun's java license prevents you from deploying the jdk to a
>*production* system, and tools.jar is part of the jdk.
I think this is no longer true. At least from my reading of the 1.4.*
licenses. I do agree this was true with 1.3.* and earlier, but I am pretty
sure they changed it.
I may have missed it, of course, and if you could point out where in the
current licenses that this is forbidden, I'd appreciate it.
Cheers,
mrc
--
Mike Castle da...@ix... www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
|
|
From: Sal I. <sal...@sy...> - 2003-09-24 18:29:29
|
i was talking about 1.3
i should have mentioned it.
thanks for clarifying it.
-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Mike
Castle
Sent: Wednesday, September 24, 2003 9:45 AM
To: wra...@li...
Subject: Re: [Wrapper-user] JSP Compiling Error When Starting JBoss
Using Wrapper
In article <014501c38230$ec847290$6502a8c0@fs1>,
Sal Ingrilli <wra...@li...> wrote:
>note that sun's java license prevents you from deploying the jdk to a
>*production* system, and tools.jar is part of the jdk.
I think this is no longer true. At least from my reading of the 1.4.*
licenses. I do agree this was true with 1.3.* and earlier, but I am pretty
sure they changed it.
I may have missed it, of course, and if you could point out where in the
current licenses that this is forbidden, I'd appreciate it.
Cheers,
mrc
--
Mike Castle da...@ix... www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); --
gcc
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
|
|
From: <da...@ix...> - 2003-09-29 21:56:24
|
In article <015601c382c9$6fd45690$6502a8c0@fs1>,
Sal Ingrilli <wra...@li...> wrote:
>i was talking about 1.3
>i should have mentioned it.
>thanks for clarifying it.
Ahh. I looked back at the original post and saw the 1.3 reference. Sorry
about that.
mrc
--
Mike Castle da...@ix... www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
|
|
From: Leif M. <le...@ta...> - 2003-09-25 02:42:27
|
Bin Duan,
I was not clear from you later posts, but were you able to get this
working correctly?
As Sal said, these problems are usually caused by the tools.jar file
missing from your
classpath. However, I see that you have specified it in the classpath
in your
wrapper.conf. Other than verifying the location of the tools.jar file,
try looking for any
other hints in other log files.
Leif
Bin_Duan/Cla...@cl... wrote:
>We'd like to start JBoss currently hosting our J2EE application using
>Wrapper. I followed the step-by-step instruction from the website to setup
>JBoss wrapper. And the JBoss started up fine, but when I tried to access
>our application, I got an error indicating unable to compile class for JSP
>as follows:
>
>org.apache.jasper.JasperException: Unable to compile class for JSP
> at
>org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:479)
>
> at
>org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:184)
>
> at
>org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
> at
>org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
> at
>javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at
>org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
>
> at
>org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
>
>
|