Jsp compilation fails...
Hi ..
I have jsp pages which when converted to java gets huge due to presence of lot
of custom tags and java components..
I get a BEA "code too large for try statement" when this jsp page is compiled...I
am aware of the 64k/method limit on the jvm methods...I am using WLS70sp1..is
there any way I can use one jsp page itself(without breaking into jsp:includes)
and solve this problem ?
Thanx,
Krish
I don't think so.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"Krish Venkataraman" <[email protected]> wrote in message
news:3e4ab3bb$[email protected]..
>
>
> Hi ..
>
> I have jsp pages which when converted to java gets huge due to presence of
lot
> of custom tags and java components..
> I get a BEA "code too large for try statement" when this jsp page is
compiled...I
> am aware of the 64k/method limit on the jvm methods...I am using
WLS70sp1..is
> there any way I can use one jsp page itself(without breaking into
jsp:includes)
> and solve this problem ?
>
> Thanx,
> Krish
>
>
Similar Messages
-
JSP compilation failed with java.lang.IllegalStateException: zip file close
Hi,
I have a web app successfully deployed on Weblogic7.0 and HP UX 11.0, which uses jdk 1.3.1_02
In this application, when i invoke a jsp (this exception occurs on any jsp not to any specific jsp), i found the following exception trace on wl-domain.log file and server crashes: -
java.lang.IllegalStateException: zip file closed
at java.util.zip.ZipFile.getEntry(Unknown Source)
at weblogic.servlet.internal.WarClassFinder.getSource(WarClassFinder.java, Compiled Code)
at weblogic.servlet.internal.WarClassFinder.getSource(WarClassFinder.java, Compiled Code)
at weblogic.utils.classloaders.MultiClassFinder.getSource(MultiClassFinder.java, Compiled Code)
at weblogic.utils.classloaders.MultiClassFinder.getSource(MultiClassFinder.java, Compiled Code)
at weblogic.utils.classloaders.MultiClassFinder.getClassSource(MultiClassFinder.java, Compiled Code)
at weblogic.utils.classloaders.ChangeAwareClassLoader.upToDate(ChangeAwareClassLoader.java, Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java, Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.checkForReload(ServletStubImpl.java, Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java, Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java, Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java, Compiled Code)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java, Compiled Code)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java, Compiled Code)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java, Compiled Code)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java, Compiled Code)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java, Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
Can anyone help me in figuring out this problem urgently?
thanks in advance
manojHi Manoj.I am also getting the same problem in the weblogicserver version-6.1 SP2.It is also using the jdk 1.31.
here is my stack trace.Help i smuch appreciated.!!
java.lang.IllegalStateException: zip file closed
at java.util.zip.ZipFile.getEntry(ZipFile.java:141)
at weblogic.servlet.internal.WarClassFinder.getSource(WarClassFinder.java:197)
at weblogic.servlet.internal.WarClassFinder.getSource(WarClassFinder.java:106)
at weblogic.utils.classloaders.MultiClassFinder.getSource(MultiClassFinder.java:53)
at weblogic.utils.classloaders.MultiClassFinder.getSource(MultiClassFinder.java:53)
at weblogic.utils.classloaders.MultiClassFinder.getClassSource(MultiClassFinder.java:45)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:265)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:156)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:65)
at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at com.slfc.framework.service.ServiceMessageFactory.createServiceResult(ServiceMessageFactory.java:58)
at sunlife.nexus.admin.SecPro.establishSupportSession(Unknown Source)
at sunlife.nexus.admin.Page_secPro_extAppLoader.processPageRequest(Unknown Source)
at sunlife.wis.servlets.WISServlet.redirect(WISServlet.java:63)
at sunlife.wis.servlets.WISServlet.doExec(WISServlet.java:107)
at sunlife.wis.servlets.WISServlet.doGet(WISServlet.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) -
JSP compilation: code too large on SP14
Hello,
I developed EP application based on JSPDynPage on SP13 with big jsp file. This application was running on SP13 without problem.
Later, we upgraded to SP14 and application logged exception: "code too large" when compiling jsp.
I tried to devide the big jsp to several jsp, but problems remains the same.
I searched SDN. I tried set jsp.bigmode.delimit.size to 10000, 20000 and 1. Nothing helps.
I followed OSS Note:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/bc-jas/~form/handler{5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383230323832}
Best regards,
Josef MotlHi Detlev,
the OSS number is 820282. But I was unable to wiew this message on http://service.sap.com. So below I put snapshot of this message.
Regards,
Josef
Portal JSP compiler fails when code generated is too long
SAP Note Number: 820282
Symptom
In a few cases, the compilation of jsp files fails (if their size is very large) because the generated Java code exceeds the 65K limitation (per method) of SUN JVM or the system crashes when it tries to load a class file that was not correctly constructed (method size > 65K).
Other terms
JSP, Portal, too long, compilation, compiler, over size, try
Reason and Prerequisites
SUN JVM and othes do not support a method which has more than 65K of byte code.
Solution
The fix is available in +SP2 PL 31 and +EP6 SP11 Patch 2.
Once you have installed the fix, you need to edit the file irj\root\WEB-INF\portal\system\properties\prtCentral.properties.bak.
Check if the property "jsp.bigmode.delimit.size" is present. Otherwise add the line "jsp.bigmode.delimit.size=10000", rename the file to "prtCentral.properties" and restart the server.
The number is the limit size in bytes when the big jsp mode is enabled (you should therefore change the Java template generated from the jsp file to a size larger than the limit)
In rear cases where JSP files are including sources prior to their compilation you should set the parameter to a lower value. In the extreme case you can use jsp.bigmode.delimit.size=1 and enable the big mode jsp optimization for all files.
To deactive the big jsp mode, set jsp.bigmode.delimit.size=-1
Header Data
Release Status Released for Customer
Released on 21.07.2005
Priority Correction with medium priority
Category Advance development
Primary Component BC-JAS-PIN-PRT Portal Runtime -
Weblogic 10.3 & AIX -- Compilation of JSP File Failed!!!!
Hi,
We try to deploy an war to the weblogic 10.3 server. Error happed under AIX.
The War can be deployed successfully but JSP compile under AIX? I verify that Solaris 9&10, Red hat, HP IA, the war works well after deployed.
Is there any special setting for AIX? Both 5.3 and 6.1 have the problem.
Here is my jsp:
<%@ page import="com.acta.webapp.mdreport.*" contentType="text/html" language="java" pageEncoding="UTF-8"%>
<%@ taglib uri="/WEB-INF/mdreport.tld" prefix="md" %>
<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>
<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
<%
AwWebMetaDataContext ctxt = new AwWebMetaDataContext (request,response);
String logonButton = ctxt.getMessage(DIMetaDataResource.IDS_LOGON_LABEL);
%>
<html>
<head>
Here is the error message:
logon.jsp:2:5: Invalid tag library.
<%@ taglib uri="WEB-INF/mdreport.tld" prefix="md" %>
^----^
logon.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="WEB-INF/mdreport.tld" prefix="md" %>
^----^
logon.jsp:2:5: Invalid tag library.
<%@ taglib uri="WEB-INF/mdreport.tld" prefix="md" %>
^----^
logon.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="WEB-INF/mdreport.tld" prefix="md" %>
^----^
logon.jsp:3:5: Invalid tag library.
<%@ taglib uri="WEB-INF/struts-html.tld" prefix="html" %>
^----^
logon.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib uri="WEB-INF/struts-html.tld" prefix="html" %>
^----^
logon.jsp:3:5: Invalid tag library.
<%@ taglib uri="WEB-INF/struts-html.tld" prefix="html" %>
Here is the stack trace from the log:
at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:328)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:237)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:182)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:235)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:251)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1063)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:386)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:229)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3495)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Here is the JDK information.
Java(TM) SE Runtime Environment (build pap6460sr4-20090219_01(SR4))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460-20090215_29883 (JIT enabled, AOT enabled)I am having a similar error but with a different tld...
From my home-framed.jsp:
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<%@ taglib prefix='tiles' uri='struts-tiles'%>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
From my web.xml:
<jsp-config>
<taglib>
<taglib-uri>struts-tiles</taglib-uri>
<taglib-location>WEB-INF/struts-tiles.tld</taglib-location>
</taglib>
</jsp-config>
Trace from server log:
####<Oct 6, 2009 3:20:46 PM EDT> <Error> <HTTP> <aixtd3> <appdev_cinciview_aixtd3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1254856846253> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@6fc66fc6 - appName: 'cinciview', name: 'cinciview.war', context-path: '/cinciview'] Root cause of ServletException.
weblogic.servlet.jsp.CompilationException: Failed to compile JSP /jsp/home-framed.jsp
home-framed.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib prefix='tiles' uri='struts-tiles'%>
^----^
home-framed.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@ taglib prefix='tiles' uri='struts-tiles'%>
^----^
at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:298)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:165)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:235)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:394)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:309)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:261)
at org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:145)
at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:251)
at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1144)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:880)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:793)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:476)
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
This code works on WLS 10.0 MP 1 on Windows but not on AIX.
I've tried the suggested fix to add a library reference in the weblogic xml without success.
Has anyone discovered a fix for this yet? -
Re: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text
substitution situations, and as a completely independent tool its use is not
restricted to migration situations (or file types for that matter).
Second, I sympathize with the unfortunate trouble you are experiencing due to
Jasper's (perhaps more strict) compilation, but in what way did the iMT
automated translation contribute to these inconsistencies that you cited?
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a
translation situation, the only way "OnClick" would have been introduced was if
it had been part of the pre-existing project's "extraHTML" (which was written
by the original customer and just passed through unchanged by the iMT) or if it
was added manually by the post-migration developer.
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
similar to the OnClick situation described above?
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no
equivalent in the NetDynamics world, so any content tags in your code must have
been introduced by your developers manually. Its a shame that jasper is so
particular, but the iMT could not help you out here even if we wanted to. The
constants that are used by the iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
[Non-text portions of this message have been removed]Thanks a lot Matt and Mike for your prompt replies.
I agree completely that iMT doesn't introduce the inconsistencies.
About the three cases I mentioned, the third one happens only in
manually created JSPs. So it has nothing to do with iMT. The first
two are mainly due to the existing HTML code, as you rightly pointed
out.
The reason I made the suggestion is since we know that case 1 and 2
won't pass the japser compiler in sp3, we have to do something about
it. The best place to do this, in my mind, is iMT. Of course, there
might be some twists that make it impossible or difficult to do this
kind of case manipulation or attribute discard.
Weiguo
--- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
tool its use is not restricted to migration situations (or file types
for that matter).
>
Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
in what way did the iMT automated translation contribute to these
inconsistencies that you cited?
>
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
introduced was if it had been part of the pre-existing
project's "extraHTML" (which was written by the original customer and
just passed through unchanged by the iMT) or if it was added manually
by the post-migration developer.
>
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
>
>
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
in your code must have been introduced by your developers manually.
Its a shame that jasper is so particular, but the iMT could not help
you out here even if we wanted to. The constants that are used by the
iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
see, the only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
>
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as
what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
>>
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
Service.
>
>
>
[Non-text portions of this message have been removed] -
JSP compilation problem when upgrading JVM fron JDK1.2.2 to JDK1.3 on Solaris with WLS5.1
Hi
I am trying to upgrade our JVM from JDK1.2.2 to JDK1.3.
When i finally got a clean compile of the code, i get the following error when i try to access the
index.jsp of our site.
ti mai 01 10:33:24 WEST 2001:<I> <WebLogicServer> WebLogic Server started
ti mai 01 10:35:22 WEST 2001:<I> <ServletContext-General> Generated java file:
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java
ti mai 01 10:35:22 WEST 2001:<E> <ServletContext-General> Compilation of
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java failed:
java.io.IOException: Not enough space
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:54)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:551)
at java.lang.Runtime.exec(Runtime.java:477)
at java.lang.Runtime.exec(Runtime.java:443)
at weblogic.utils.Executable.exec(Executable.java:170)
at weblogic.utils.Executable.exec(Executable.java:107)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:423)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
java.io.IOException: Compiler failed executable.exec([Ljava.lang.String;[/usr/bin/javac, -classpath,
/usr/java1.3/jre/lib/rt.jar:/usr/java1.3/jre/lib/i18n.jar:/usr/java1.3/jre/lib/sunrsasign.jar:/usr/j
ava1.3/jre/classes:/usr/local/weblogic/510/9/weblogic510sp9boot.jar:/usr/local/weblogic/510/weblogic
/classes/boot::/usr/local/weblogic/510/9/telenormobilHTTP302.jar:/usr/local/weblogic/510/9/weblogic5
10sp9.jar:./djuicecluster/wamp/lib/client.jar:/usr/local/weblogic/510/weblogic/license:/usr/local/we
blogic/510/weblogic/classes:/usr/local/weblogic/510/weblogic/myserver/serverclasses:/usr/local/weblo
gic/510/weblogic/lib/weblogicaux.jar:./djuicecluster/serverclasses:./djuicecluster/serverclasses/lda
pjdk.jar:./djuicecluster/serverclasses/nslookup.jar:./djuicecluster/serverclasses/activation.jar:./d
juicecluster/serverclasses/bsfengines.jar:./djuicecluster/serverclasses/bsf.jar:./djuicecluster/serv
erclasses/mail.jar:./djuicecluster/serverclasses/xalan.jar:./djuicecluster/serverclasses/xerces.jar:
./djuicecluster/serverclasses/jsse.jar:./djuicecluster/serverclasses/Acme.jar:./djuicecluster/server
classes/xml.jar:./djuicecluster/serverclasses/poppers.jar:./djuicecluster/serverclasses/com_telenor.
jar:./djuicecluster/serverclasses/smpp.jar:./djuicecluster/serverclasses/smpputils.jar:./djuiceclust
er/serverclasses/entrust.jar:./djuicecluster/projects/djuice/lib/djuice_common.jar:./djuicecluster/s
erverclasses/oreilly.jar:./djuicecluster/projects/djuice/lib:./djuicecluster/projects/djuice/lib/Men
uBean.jar:./djuicecluster/projects/djuice/lib/CategoryContentBean.jar:./djuicecluster/projects/djuic
e/servletsnclasses:/usr/local/weblogic/510/weblogic/lib/jConnect.jar:/usr/local/weblogic/510/weblogi
c/lib/jconn2.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15392.jar:/db
dump/weblogic/510/weblogic/lib/persistence/WebLogic_RDBMS.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15393.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15394.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15395.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15396.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15397.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15398.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15399.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15400.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15401.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15402.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15403.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15404.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15405.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15406.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15407.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15408.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15409.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15410.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15411.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15412.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15413.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15414.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15415.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15416.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15417.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15418.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15419.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15420.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15421.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15422.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15423.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15424.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15425.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15426.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15427.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15428.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15429.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15430.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15431.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15432.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15433.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15434.jar:./djuicecluster/projects/djuice/servletsnclasses:./djuicecluster/projects/djui
ce/servletclasses:/dbdump/djuice/djuice.17b/djuicecluster/classfiles, -d,
/dbdump/djuice/djuice.17b/djuicecluster/classfiles,
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java])
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:439)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
ti mai 01 10:35:22 WEST 2001:<E> <ServletContext-General> Servlet failed with Exception
java.io.IOException: Compiler failed executable.exec([Ljava.lang.String;[/usr/bin/javac, -classpath,
/usr/java1.3/jre/lib/rt.jar:/usr/java1.3/jre/lib/i18n.jar:/usr/java1.3/jre/lib/sunrsasign.jar:/usr/j
ava1.3/jre/classes:/usr/local/weblogic/510/9/weblogic510sp9boot.jar:/usr/local/weblogic/510/weblogic
/classes/boot::/usr/local/weblogic/510/9/telenormobilHTTP302.jar:/usr/local/weblogic/510/9/weblogic5
10sp9.jar:./djuicecluster/wamp/lib/client.jar:/usr/local/weblogic/510/weblogic/license:/usr/local/we
blogic/510/weblogic/classes:/usr/local/weblogic/510/weblogic/myserver/serverclasses:/usr/local/weblo
gic/510/weblogic/lib/weblogicaux.jar:./djuicecluster/serverclasses:./djuicecluster/serverclasses/lda
pjdk.jar:./djuicecluster/serverclasses/nslookup.jar:./djuicecluster/serverclasses/activation.jar:./d
juicecluster/serverclasses/bsfengines.jar:./djuicecluster/serverclasses/bsf.jar:./djuicecluster/serv
erclasses/mail.jar:./djuicecluster/serverclasses/xalan.jar:./djuicecluster/serverclasses/xerces.jar:
./djuicecluster/serverclasses/jsse.jar:./djuicecluster/serverclasses/Acme.jar:./djuicecluster/server
classes/xml.jar:./djuicecluster/serverclasses/poppers.jar:./djuicecluster/serverclasses/com_telenor.
jar:./djuicecluster/serverclasses/smpp.jar:./djuicecluster/serverclasses/smpputils.jar:./djuiceclust
er/serverclasses/entrust.jar:./djuicecluster/projects/djuice/lib/djuice_common.jar:./djuicecluster/s
erverclasses/oreilly.jar:./djuicecluster/projects/djuice/lib:./djuicecluster/projects/djuice/lib/Men
uBean.jar:./djuicecluster/projects/djuice/lib/CategoryContentBean.jar:./djuicecluster/projects/djuic
e/servletsnclasses:/usr/local/weblogic/510/weblogic/lib/jConnect.jar:/usr/local/weblogic/510/weblogi
c/lib/jconn2.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15392.jar:/db
dump/weblogic/510/weblogic/lib/persistence/WebLogic_RDBMS.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15393.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15394.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15395.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15396.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15397.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15398.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15399.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15400.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15401.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15402.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15403.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15404.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15405.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15406.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15407.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15408.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15409.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15410.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15411.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15412.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15413.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15414.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15415.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15416.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15417.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15418.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15419.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15420.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15421.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15422.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15423.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15424.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15425.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15426.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15427.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15428.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15429.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15430.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15431.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15432.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15433.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15434.jar:./djuicecluster/projects/djuice/servletsnclasses:./djuicecluster/projects/djui
ce/servletclasses:/dbdump/djuice/djuice.17b/djuicecluster/classfiles, -d,
/dbdump/djuice/djuice.17b/djuicecluster/classfiles,
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java])
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:439)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
None of my filesystems are full. Why does this error occur then.
I have tried to check the jsp configuration but there is nothing to see there ...
Can annyone help me with this problem ?
Thanks
Ståle TomtenHi
I solved the problem.
The server did not have enough memory available to spawn the javac process... Therefor: Not enough
space.
I just reduced the memory set up for weblogic and it worked.
regards
Ståle Tomten
"Ståle Tomten" <[email protected]> wrote in message news:[email protected]...
Hi
I am trying to upgrade our JVM from JDK1.2.2 to JDK1.3.
When i finally got a clean compile of the code, i get the following error when i try to access the
index.jsp of our site.
ti mai 01 10:33:24 WEST 2001:<I> <WebLogicServer> WebLogic Server started
ti mai 01 10:35:22 WEST 2001:<I> <ServletContext-General> Generated java file:
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java
ti mai 01 10:35:22 WEST 2001:<E> <ServletContext-General> Compilation of
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java failed:
java.io.IOException: Not enough space
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:54)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:551)
at java.lang.Runtime.exec(Runtime.java:477)
at java.lang.Runtime.exec(Runtime.java:443)
at weblogic.utils.Executable.exec(Executable.java:170)
at weblogic.utils.Executable.exec(Executable.java:107)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:423)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
java.io.IOException: Compiler failedexecutable.exec([Ljava.lang.String;[/usr/bin/javac, -classpath,
>
/usr/java1.3/jre/lib/rt.jar:/usr/java1.3/jre/lib/i18n.jar:/usr/java1.3/jre/lib/sunrsasign.jar:/usr/j
>
ava1.3/jre/classes:/usr/local/weblogic/510/9/weblogic510sp9boot.jar:/usr/local/weblogic/510/weblogic
>
/classes/boot::/usr/local/weblogic/510/9/telenormobilHTTP302.jar:/usr/local/weblogic/510/9/weblogic5
>
10sp9.jar:./djuicecluster/wamp/lib/client.jar:/usr/local/weblogic/510/weblogic/license:/usr/local/we
>
blogic/510/weblogic/classes:/usr/local/weblogic/510/weblogic/myserver/serverclasses:/usr/local/weblo
>
gic/510/weblogic/lib/weblogicaux.jar:./djuicecluster/serverclasses:./djuicecluster/serverclasses/lda
>
pjdk.jar:./djuicecluster/serverclasses/nslookup.jar:./djuicecluster/serverclasses/activation.jar:./d
>
juicecluster/serverclasses/bsfengines.jar:./djuicecluster/serverclasses/bsf.jar:./djuicecluster/serv
>
erclasses/mail.jar:./djuicecluster/serverclasses/xalan.jar:./djuicecluster/serverclasses/xerces.jar:
>
./djuicecluster/serverclasses/jsse.jar:./djuicecluster/serverclasses/Acme.jar:./djuicecluster/server
>
classes/xml.jar:./djuicecluster/serverclasses/poppers.jar:./djuicecluster/serverclasses/com_telenor.
>
jar:./djuicecluster/serverclasses/smpp.jar:./djuicecluster/serverclasses/smpputils.jar:./djuiceclust
>
er/serverclasses/entrust.jar:./djuicecluster/projects/djuice/lib/djuice_common.jar:./djuicecluster/s
erverclasses/oreilly.jar:./djuicecluster/projects/djuice/lib:./djuicecluster/projects/djuice/lib/Men>uBean.jar:./djuicecluster/projects/djuice/lib/CategoryContentBean.jar:./djuicecluster/projects/djuic>e/servletsnclasses:/usr/local/weblogic/510/weblogic/lib/jConnect.jar:/usr/local/weblogic/510/weblogi>c/lib/jconn2.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15392.jar:/db>dump/weblogic/510/weblogic/lib/persistence/WebLogic_RDBMS.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15393.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15394.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15395.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15396.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15397.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15398.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15399.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15400.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15401.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15402.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15403.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15404.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15405.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15406.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15407.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15408.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15409.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15410.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15411.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15412.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15413.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15414.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15415.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15416.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15417.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15418.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15419.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15420.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15421.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15422.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15423.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15424.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15425.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15426.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15427.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15428.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15429.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15430.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15431.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15432.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15433.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15434.jar:./djuicecluster/projects/djuice/servletsnclasses:./djuicecluster/projects/djui> ce/servletclasses:/dbdump/djuice/djuice.17b/djuicecluster/classfiles, -d,> /dbdump/djuice/djuice.17b/djuicecluster/classfiles,> /dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java)at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:439)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
ti mai 01 10:35:22 WEST 2001:<E> <ServletContext-General> Servlet failed with Exception
java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[/usr/bin/javac, -classpath,
>
/usr/java1.3/jre/lib/rt.jar:/usr/java1.3/jre/lib/i18n.jar:/usr/java1.3/jre/lib/sunrsasign.jar:/usr/j
>
ava1.3/jre/classes:/usr/local/weblogic/510/9/weblogic510sp9boot.jar:/usr/local/weblogic/510/weblogic
>
/classes/boot::/usr/local/weblogic/510/9/telenormobilHTTP302.jar:/usr/local/weblogic/510/9/weblogic5
>
10sp9.jar:./djuicecluster/wamp/lib/client.jar:/usr/local/weblogic/510/weblogic/license:/usr/local/we
>
blogic/510/weblogic/classes:/usr/local/weblogic/510/weblogic/myserver/serverclasses:/usr/local/weblo
>
gic/510/weblogic/lib/weblogicaux.jar:./djuicecluster/serverclasses:./djuicecluster/serverclasses/lda
>
pjdk.jar:./djuicecluster/serverclasses/nslookup.jar:./djuicecluster/serverclasses/activation.jar:./d
>
juicecluster/serverclasses/bsfengines.jar:./djuicecluster/serverclasses/bsf.jar:./djuicecluster/serv
>
erclasses/mail.jar:./djuicecluster/serverclasses/xalan.jar:./djuicecluster/serverclasses/xerces.jar:
>
./djuicecluster/serverclasses/jsse.jar:./djuicecluster/serverclasses/Acme.jar:./djuicecluster/server
>
classes/xml.jar:./djuicecluster/serverclasses/poppers.jar:./djuicecluster/serverclasses/com_telenor.
>
jar:./djuicecluster/serverclasses/smpp.jar:./djuicecluster/serverclasses/smpputils.jar:./djuiceclust
>
er/serverclasses/entrust.jar:./djuicecluster/projects/djuice/lib/djuice_common.jar:./djuicecluster/s
>
erverclasses/oreilly.jar:./djuicecluster/projects/djuice/lib:./djuicecluster/projects/djuice/lib/Men
>
uBean.jar:./djuicecluster/projects/djuice/lib/CategoryContentBean.jar:./djuicecluster/projects/djuic
>
e/servletsnclasses:/usr/local/weblogic/510/weblogic/lib/jConnect.jar:/usr/local/weblogic/510/weblogi
>
c/lib/jconn2.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15392.jar:/db
>
dump/weblogic/510/weblogic/lib/persistence/WebLogic_RDBMS.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15393.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15394.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15395.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15396.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15397.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15398.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15399.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15400.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15401.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15402.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15403.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15404.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15405.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15406.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15407.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15408.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15409.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15410.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15411.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15412.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15413.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15414.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15415.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15416.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15417.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15418.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15419.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15420.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15421.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15422.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15423.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15424.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15425.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15426.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15427.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15428.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15429.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15430.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15431.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15432.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15433.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15434.jar:./djuicecluster/projects/djuice/servletsnclasses:./djuicecluster/projects/djui
ce/servletclasses:/dbdump/djuice/djuice.17b/djuicecluster/classfiles, -d,> /dbdump/djuice/djuice.17b/djuicecluster/classfiles,> /dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java)at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:439)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
None of my filesystems are full. Why does this error occur then.
I have tried to check the jsp configuration but there is nothing to see there ...
Can annyone help me with this problem ?
Thanks
Ståle Tomten -
Jsp compile error in weblogic 10.3
When i run the project, an error has occured. The jsp page only contains few words.
weblogic.servlet.jsp.CompilationException: Failed to compile JSP /deployed/SYSTEM/Function_List/1/resources/List Functions.jsp
List Functions.jsp:1:1: The public type __list_32_functions must be defined in its own file
This is a JSP page.
^-----------------^
at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:328)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:237)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:182)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:235)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
Could somebody help me.Add this tag to your weblogic.xml file and deploy the application and check it ,it should work
<jsp-descriptor>
<jsp-param>
<param-name>
compileCommand
</param-name>
<param-value>
sj
</param-value>
</jsp-param>
</jsp-descriptor> -
EAR and long CLASSPATH at JSP compilation time
Hi all,
we have an EAR-packaged application with over 260 jars (mainly
EJB) that is deployed to a managed server WL6.1SP3(AIX). Then
we hit a JSP page of this app. and Weblogic generates the
adecuate .java file that is passed as an argument to a forked
process for the javac compiler with a CLASSPATH that is more
than 22KB!! of length because of the EAR classloader schema
(it must include all the jars of the EJB level).
The problem is that the EAR deployment in WL6.1 generates a fixed and very long
path for every jar that it is composed of:
$WL_HOME/./config/DOMAIN/applications/.wl_notdelete_EARNAME
/wlap#####/ejbjarname.jar
and the invoke of the compiler fails with argument too long.
We can control the EJB jar name, EARNAME, WL_HOME
and DOMAIN to shorten the CLASSPATH, but that is not enough
giving that the fixed part of the PATH is very long, for example:
with DOMAIN=DOM1, WL_HOME=W, ejbjar name=EJB1, EARNAME=EAR1
you get:
/w/./config/DOM1/applications/.wl_notdelete_EAR1/wlap#####/EJB1.jar: that is
68 chars * 260 jars = more than 17KB only with the
EJB part of the CLASSPATH (plus the standard SYSTEM CLASSPATH
and WARS CLASSPATH.)
As workarounds we can:
1.- Use an "pseudo exploded" EAR with EJBREMOTE and EJBHOME in clientclasses path
with every jar and war by their own. Not very
clean and we've lost the benefits of EAR deployment.
2.- Consolidate a bunch of EJB in every jar. More administrative
tasks (common xml descriptors:ejb-jar.xml,...) and less isolation
between developer teams.
3.- Consolidate at functionality level (source) a bunch of EJB
in a few one. :(
4.- Precompile every JSP outside of WEBLOGIC and generate
the corresponding class and entries at web.xml and weblogic.xml
5.- ...?
or maybe:
6.- configure this very long directory of deployment
to a shorter deployer choosen and use relative paths.
Is this possible? :)
PacoG.
You may try to use JSP compiler class. Please specify 'compilerclass'
option in weblogic.xml. This option specifies name of a Java compiler
that is executed in WebLogic Servers's virtual machine. (Used in place of
an executable compiler such as javac or sj.)
Please see
http://e-docs.bea.com/wls/docs61/webapp/weblogic_xml.html#jsp-descriptor.
Paco Garcia wrote:
> oops!
>
> >$WL_HOME/./config/DOMAIN/applications/.wl_notdelete_EARNAME
> >/wlap#####/ejbjarname.jar
>
> >with DOMAIN=DOM1, WL_HOME=W, ejbjar name=EJB1, EARNAME=EAR1
> >you get:
> >/w/./config/DOM1/applications/.wl_notdelete_EAR1/wlap#####/EJB1.jar:
>
> please read SERVERNAME instead of EARNAME
>
> PacoG.
Regards,
Ann
Developer Relations Engineer
BEA Support
-
Newbie: jsp compile error w/ tomcat 5.0.19
Hello there, this is my first time try to write something in jsp/ servlets, and i encounter a minor installation problem:
using mdk linux with j2sdk1.4.2 (locate at /usr/local/), tomcat is also locate at /usr/local.
I am able to see HelloServlet.java, and HelloWorld.html at http://localhost:8080/servlet/HelloServlet
and http://localhost:8080/testing/HelloWorld.html
but i'm unable to see HelloWorld.jsp at http://localhost:880/HellowWorld.jsp (my HelloWorld.html and HellowWorld.jsp are locate at the same dir)
here's are the things i added in my /etc/profile so far:
CATALINA_HOME="/usr/local/Tomcat"
export CATALINA_HOME
JAVA_HOME="/usr/local/j2sdk1.4.2"
export JAVA_HOME
JavaPath="/usr/local/j2sdk1.4.2/bin"
export JavaPath
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
export PKG_CONFIG_PATH
CLASSPATH=$CLASSPATH:/usr/local/Tomcat/common/lib/servlet-api.jar:/usr/local/Tomcat/
common/lib/jsp-api.jar:/home/allen/programming/j2ee/:./
export CLASSPATH
when do java -verison, i see:
[root@localhost local]# java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
when start tomcat, i got:
[root@localhost bin]# ./startup.sh
Using CATALINA_BASE: /usr/local/Tomcat
Using CATALINA_HOME: /usr/local/Tomcat
Using CATALINA_TMPDIR: /usr/local/Tomcat/temp
Using JAVA_HOME: /usr/local/j2sdk1.4.2
i thought i did everything that was told, yet i can't see jsp page on my browser, while i can see servlets and html,
thank you for your time in advance ^_^sorry, it was a typo, yea...it was for http://localhost:8080/testing/Hello.jsp
this morning, i copied "tool.jar" from j2sdk1.4.2 to my /usr/local/tomcat/common/lib, restarted, fire it up again using "./catalina.sh" just to see where the problems came from, and here's where the compile error occue:
Compile failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:978)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:799)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:387)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:458)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:553)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:291)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:284)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:257)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:245)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:199)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:156)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:833)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:732)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:619)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:688)
at java.lang.Thread.run(Thread.java:534)
Mar 16, 2005 7:28:37 AM org.apache.jasper.compiler.Compiler generateClass
SEVERE: Env: Compile: javaFileName=/usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_//org/apache/jsp/testing/Hello_jsp.java
classpath=/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/classes/:/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/lib/catalina-root.jar:/usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_:/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/classes/:/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/lib/catalina-root.jar:/usr/local/jakarta-tomcat-5.0.19/shared/classes/:/usr/local/jakarta-tomcat-5.0.19/common/classes/:/usr/local/jakarta-tomcat-5.0.19/common/endorsed/xercesImpl.jar:/usr/local/jakarta-tomcat-5.0.19/common/endorsed/xmlParserAPIs.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/ant.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-collections.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-dbcp-1.1.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-el.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-pool-1.1.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/jasper-compiler.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/jasper-runtime.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/jmx.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/jsp-api.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-common.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-factory.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-java.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-resources.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/servlet-api.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/tools.jar:/usr/local/j2sdk1.4.2/lib/tools.jar:/usr/local/jakarta-tomcat-5.0.19/bin/bootstrap.jar:/usr/local/jakarta-tomcat-5.0.19/bin/commons-logging-api.jar:/usr/local/j2sdk1.4.2/jre/lib/ext/sunjce_provider.jar:/usr/local/j2sdk1.4.2/jre/lib/ext/dnsns.jar:/usr/local/j2sdk1.4.2/jre/lib/ext/ldapsec.jar:/usr/local/j2sdk1.4.2/jre/lib/ext/localedata.jar
cp=/usr/local/j2sdk1.4.2/lib/tools.jar:/usr/local/Tomcat/bin/bootstrap.jar:/usr/local/Tomcat/bin/commons-logging-api.jar
cp=/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/classes
cp=/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/lib/catalina-root.jar
cp=/usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_
cp=/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/classes
cp=/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/lib/catalina-root.jar
cp=/usr/local/jakarta-tomcat-5.0.19/shared/classes
cp=/usr/local/jakarta-tomcat-5.0.19/common/classes
cp=/usr/local/jakarta-tomcat-5.0.19/common/endorsed/xercesImpl.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/endorsed/xmlParserAPIs.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/ant.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-collections.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-dbcp-1.1.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-el.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-pool-1.1.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/jasper-compiler.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/jasper-runtime.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/jmx.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/jsp-api.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-common.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-factory.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-java.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-resources.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/servlet-api.jar
cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/tools.jar
cp=/usr/local/j2sdk1.4.2/lib/tools.jar
cp=/usr/local/jakarta-tomcat-5.0.19/bin/bootstrap.jar
cp=/usr/local/jakarta-tomcat-5.0.19/bin/commons-logging-api.jar
cp=/usr/local/j2sdk1.4.2/jre/lib/ext/sunjce_provider.jar
cp=/usr/local/j2sdk1.4.2/jre/lib/ext/dnsns.jar
cp=/usr/local/j2sdk1.4.2/jre/lib/ext/ldapsec.jar
cp=/usr/local/j2sdk1.4.2/jre/lib/ext/localedata.jar
work dir=/usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_
extension dir=/usr/local/j2sdk1.4.2/jre/lib/ext
srcDir=/usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_
include=org/apache/jsp/testing/Hello_jsp.java
Mar 16, 2005 7:28:37 AM org.apache.jasper.compiler.Compiler generateClass
SEVERE: Error compiling file: /usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_//org/apache/jsp/testing/Hello_jsp.java [javac] Compiling 1 source file
[javac] /usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_/org/apache/jsp/testing/Hello_jsp.java:48: cannot resolve symbol
[javac] symbol : class Data
[javac] location: package util
[javac] out.print( new java.util.Data() );
[javac] ^
[javac] 1 error
Mar 16, 2005 7:32:34 AM org.apache.jasper.compiler.Compiler generateClass
looking over the compiler error, it seems to me tomcat is able to recongize /usr/local/j2sdk1.4 's location. which i assume it implied JAVA_HOME and CLASSPATH are setup correctly.
Dunno why it just won't display jsp pages and kept saying compiler error...
thank you for helping -
JSP compiler error (WL 4.5.1, RH Linux 6.1, JDK 1.1.8)
I am new to WebLogic, and have been trying to get it setup to serve JSP
files. I followed the instructions in the documentation. However, when
I try to access a JSP, I get the following errors. It looks like my
java compiler doesn't like the syntax WebLogic uses to call the
compiler. From the documentation, I have found that syntax is:
java weblogic.jspc -d /working/directory /path/to/jsp/file
I have tried this on the command line with the correct paths to my
files, only to result in a series of class not found errors (e.g.,
antlr.CharScanner, antlr.Tokenizer,
com.sun.java.util.collections.ArrayList, etc.). I keep downloading more
packages but everytime I try again, I need to download yet another
class. I'm at the point where I cannot find the class it currently
needs (antlr.Tokenizer).
I have these questions:
1. Should it really be this difficult & complicated to compile jsps?
2. Are these problems happening because I'm running the WL server on
Linux?
3. Why are the errors so totally different between running a JSP on the
web and running one on the command line?
4. What should I do?
The log below contains the error messages when attempting to compile
from the web browser:
Tue Feb 15 13:45:48 EST 2000:<I> <ServletContext-Servlets>
weblogic.servlet.JSPServlet: Generated java file:
/usr/local/weblogic/myserver/classfiles/jsp_servlet/_jax/_test.java
Tue Feb 15 13:45:49 EST 2000:<E> <ServletContext-Servlets>
weblogic.servlet.JSPServlet: Compilation of
/usr/local/weblogic/myserver/classfiles/jsp_servlet/_jax/_test.java
failed: -d: illegal argument
Usage: java [-options] class
where options include:
-help print out this message
-version print out the build version
-fullversion print out the full version information
-v -verbose turn on verbose mode
-debug enable remote JAVA debugging
-noasyncgc don't allow asynchronous garbage collection
-verbosegc print a message when garbage collection occurs
-noclassgc disable class garbage collection
-cs -checksource check if source is newer when loading classes
-ss<number> set the maximum native stack size for any thread
-oss<number> set the maximum Java stack size for any thread
-ms<number> set the initial Java heap size
-mx<number> set the maximum Java heap size
-D<name>=<value> set a system property
-classpath <directories separated by colons>
list directories in which to look for classes
-prof[:<file>] output profiling data to ./java.prof or ./<file>
-verify verify all classes when read in
-verifyremote verify classes read in over the network [default]
-noverify do not verify any class
-nojit disable JIT compiler
DEFAULTS:
-ss: 256K, -oss: 400K, -ms: 1M, -mx: 32M
Tue Feb 15 13:45:49 EST 2000:<E> <ServletContext-Servlets>
java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[/usr/local/jdk118/bin/java,
-classpath,
/usr/local/jdk118/lib/classes.zip:/usr/local/weblogic/classes/boot:/usr/local/weblogic/classes:/usr/local/weblogic/license:/usr/local/weblogic/lib/weblogicaux.jar:/usr/local/weblogic/myserver/serverclasses:/weblogic/myserver/servletclasses:/usr/local/weblogic/myserver/classfiles,
-d, /usr/local/weblogic/myserver/classfiles,
/usr/local/weblogic/myserver/classfiles/jsp_servlet/_jax/_test.java])
<and so on>
If it helps, I will post the error messages from the command line, which
are all, basically, class not found exceptions; I do not wish to make
this an unnecessarily long email, though.
Thank you for your help!
JacquiRun the command like this:
java -classpath /opt/weblogic/classes:/opt/weblogic/lib/weblogicaux.jar:/usr/java/lib/classes.zip weblogic.jspc -d /working/directory /path/to/jsp/file
Hope this helps,
Robert
Jacqui Maher wrote:
I am new to WebLogic, and have been trying to get it setup to serve JSP
files. I followed the instructions in the documentation. However, when
I try to access a JSP, I get the following errors. It looks like my
java compiler doesn't like the syntax WebLogic uses to call the
compiler. From the documentation, I have found that syntax is:
java weblogic.jspc -d /working/directory /path/to/jsp/file
I have tried this on the command line with the correct paths to my
files, only to result in a series of class not found errors (e.g.,
antlr.CharScanner, antlr.Tokenizer,
com.sun.java.util.collections.ArrayList, etc.). I keep downloading more
packages but everytime I try again, I need to download yet another
class. I'm at the point where I cannot find the class it currently
needs (antlr.Tokenizer).
I have these questions:
1. Should it really be this difficult & complicated to compile jsps?
2. Are these problems happening because I'm running the WL server on
Linux?
3. Why are the errors so totally different between running a JSP on the
web and running one on the command line?
4. What should I do?
The log below contains the error messages when attempting to compile
from the web browser:
Tue Feb 15 13:45:48 EST 2000:<I> <ServletContext-Servlets>
weblogic.servlet.JSPServlet: Generated java file:
/usr/local/weblogic/myserver/classfiles/jsp_servlet/_jax/_test.java
Tue Feb 15 13:45:49 EST 2000:<E> <ServletContext-Servlets>
weblogic.servlet.JSPServlet: Compilation of
/usr/local/weblogic/myserver/classfiles/jsp_servlet/_jax/_test.java
failed: -d: illegal argument
Usage: java [-options] class
where options include:
-help print out this message
-version print out the build version
-fullversion print out the full version information
-v -verbose turn on verbose mode
-debug enable remote JAVA debugging
-noasyncgc don't allow asynchronous garbage collection
-verbosegc print a message when garbage collection occurs
-noclassgc disable class garbage collection
-cs -checksource check if source is newer when loading classes
-ss<number> set the maximum native stack size for any thread
-oss<number> set the maximum Java stack size for any thread
-ms<number> set the initial Java heap size
-mx<number> set the maximum Java heap size
-D<name>=<value> set a system property
-classpath <directories separated by colons>
list directories in which to look for classes
-prof[:<file>] output profiling data to ./java.prof or ./<file>
-verify verify all classes when read in
-verifyremote verify classes read in over the network [default]
-noverify do not verify any class
-nojit disable JIT compiler
DEFAULTS:
-ss: 256K, -oss: 400K, -ms: 1M, -mx: 32M
Tue Feb 15 13:45:49 EST 2000:<E> <ServletContext-Servlets>
java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[/usr/local/jdk118/bin/java,
-classpath,
/usr/local/jdk118/lib/classes.zip:/usr/local/weblogic/classes/boot:/usr/local/weblogic/classes:/usr/local/weblogic/license:/usr/local/weblogic/lib/weblogicaux.jar:/usr/local/weblogic/myserver/serverclasses:/weblogic/myserver/servletclasses:/usr/local/weblogic/myserver/classfiles,
-d, /usr/local/weblogic/myserver/classfiles,
/usr/local/weblogic/myserver/classfiles/jsp_servlet/_jax/_test.java])
<and so on>
If it helps, I will post the error messages from the command line, which
are all, basically, class not found exceptions; I do not wish to make
this an unnecessarily long email, though.
Thank you for your help!
Jacqui -
Hello Everyone,
I've a some JSP's that work some times and fail sometime with
<head>
<title>Javelin JSP compilation error</title>
</head>
<body>
<b>Compilation of JSP File '/jsp/temp/Index.jsp' <font color=#FF0000>failed</font>:</b><HR>
<pre>
I tried restarting the server, removing .wlnotdelete and couple of other things.
Why the JSP is compiled everytime(even if the server is not restarted) and Why a good looking no error JSP failis loading everytime.
Can anyone please help.
~ALAPATII'm using bea weblogic 8.1 SP5.
Java - jrockit81sp5_142_08
<head>
<title>Javelin JSP compilation error</title>
</head>
<body>
<b>Compilation of JSP File '/jsp/output/Index.jsp' <font color=#FF0000>failed</font>:</b><HR>
<pre>
Errors found in <PATH TO THE FILE>/Index.jsp:
Error at line 397 column 55:
Description: Type <MyClass> contains no field with this name.
Error at line 399 column 13:
Description: Type <Another Class> contains no methods with this name.
Found 2 error(s) and 0 warning(s).
</pre>
</body></html>
>
weblogic.servlet.jsp.CompilationException: Failed to compile JSP /jsp/output/Index.jsp<html>
<head>
<title>Javelin JSP compilation error</title>
</head>
<body>
<b>Compilation of JSP File '/jsp/output/Index.jsp' <font color=#FF0000>failed</font>:</b><HR>
<pre>
Errors found in <PATH TO FILE>/Index.jsp:
Error at line 397 column 55:
Description: Type <MyClass> contains no field with this name.
Error at line 399 column 13:
Description: Type <Another Class> contains no methods with this name.
Found 2 error(s) and 0 warning(s).
</pre>
</body></html>
at weblogic.servlet.jsp.WlwJspStub.compilePage(WlwJspStub.java:208)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:246)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:196)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:598)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:406)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:526)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:265)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
2 errors javelin complaining is because of this.
1) I'm trying to access MyClass.SHOW_ME_TEXT
2) I'm trying to create an object of AnotherClass by new AnotherClass();
Please let me know if you want more details. -
Jsp compile exception in WL 8.1
Hi all
i was trying to deploy the external war(jstl.war from www.manning.com) file in
my weblogic server .
I just copied the *.war file into C:\TestDrive\MyDomain\mydomain\application
directory and restarted the weblogic server.
i got following error.
Compilation of 'C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java'
failed:
C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:142:
'try' without 'catch' or 'finally'
probably occurred due to an error in /index.jsp line 3:
<c:import url="header.jsp"/>
C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:132:
'try' without 'catch' or 'finally'
(No more information available, probably caused by another error)
C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:178:
'}' expected
(No more information available, probably caused by another error)
Full compiler error(s):
C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:142:
'try' without 'catch' or 'finally'
try { // TryCatchFinally begin //[ /index.jsp; Line: 3]
^
C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:132:
'try' without 'catch' or 'finally'
try { // error page try block
^
C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:178:
'}' expected
^
3 errors
Thu Sep 25 15:59:58 GMT+05:30 2003
Same file when i deployed in Tomcat4.1 was working fine i.e. copying the *.war
into <tomcathome>/webapps directory. I got index page without touching the code!
Is there any extra settings has to be done for running jsp's from war files in
WL?
THanks in advance
Manjunath
manjunath wrote:
> further to my previous mail here's the log
>
> weblogic.servlet.jsp.CompilationException: Compilation of C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java
> failed.
> at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:446)
> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:220)
> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:172)
> at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:504)
> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:349)
> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:431)
> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
> at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
> Caused by: java.io.IOException: Compiler failed executable.exec
> at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:470)
> at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:329)
> at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:337)
> at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:322)
> at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:419)
> ... 13 more
>
> Here's my weblogic.xml file
>
> <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
> "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
> <weblogic-web-app>
> <jsp-descriptor>
> <jsp-param>
> <param-name>
> compileFlags
> </param-name>
> <param-value>
> -g
> </param-value>
> </jsp-param>
>
>
> <jsp-param>
> <param-name>
> keepgenerated
> </param-name>
> <param-value>
> true
> </param-value>
> </jsp-param>
>
>
> </jsp-descriptor>
> </weblogic-web-app>
>
> In this URL http://e-docs.bea.com/wls/docs81/jsp/reference.html#57794 there's
> option to use -webapp for jsp compiler. How to implement same in weblogic.xml
> <jsp-descriptor> file?
>
> Thanks
>
> "Manjunath B" <[email protected]> wrote:
>
>>Hi all
>>
>>i was trying to deploy the external war(jstl.war from www.manning.com)
>>file in
>>my weblogic server .
>>
>>I just copied the *.war file into C:\TestDrive\MyDomain\mydomain\application
>>directory and restarted the weblogic server.
>>
>>i got following error.
>>
>>**********************************************************
>>Compilation of 'C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java'
>>failed:
>>--------------------------------------------------------------------------------
>>C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:142:
>>'try' without 'catch' or 'finally'
>>probably occurred due to an error in /index.jsp line 3:
>><c:import url="header.jsp"/>
>>
>>C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:132:
>>'try' without 'catch' or 'finally'
>>(No more information available, probably caused by another error)
>>
>>C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:178:
>>'}' expected
>>(No more information available, probably caused by another error)
>>
>>
>>--------------------------------------------------------------------------------
>>Full compiler error(s):
>>C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:142:
>>'try' without 'catch' or 'finally'
>> try { // TryCatchFinally begin //[ /index.jsp; Line: 3]
>> ^
>>C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:132:
>>'try' without 'catch' or 'finally'
>> try { // error page try block
>> ^
>>C:\TestDrive\MyDomain\mydomain\.\myserver\.wlnotdelete\extract\myserver__appsdir_jstlbook_war_jstlbook\jsp_servlet\__index.java:178:
>>'}' expected
>> }
>> ^
>>3 errors
>>
>>
>>--------------------------------------------------------------------------------
>>Thu Sep 25 15:59:58 GMT+05:30 2003
>>*******************************************************************
>>
>>
>>Same file when i deployed in Tomcat4.1 was working fine i.e. copying
>>the *.war
>>into <tomcathome>/webapps directory. I got index page without touching
>>the code!
>>
>>Is there any extra settings has to be done for running jsp's from war
>>files in
>>WL?
>>
>>THanks in advance
>>
>>Manjunath
>>
>
>
Please contact customer support [email protected] and request a patch for
CR112789. AT_END tags do not work correctly in 81sp1
-
Originally I post it to weblogic.developer.interst. But I guess this may be a better space to post the JSP related question. Sorry for the double post
Hi, there,
I tried to use the weblogic.jspc to compile my JSP files for debug purpose. However, it doesn't give me detailed information.
For example, for JSP file test.jsp:
<%
out.println(5) // miss ; at the end
%>
If I use browser to access it, it will give the error information, like:
Compilation of ../public_html/jsp_servlet/_test.java' failed:
/weblogic/appserver/public_html/jsp_servlet/_test.java:74: Invalid type expression.
probably occurred due to an error in /test.jsp line 2:
out.println("4")
/weblogic/appserver/public_html/jsp_servlet/_test.java:76: Invalid declaration.
(No more information available, probably caused by another error)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
But if I use weblogic.jspc to compile it, it only tells you:
Exec failed .. exiting
That message is not helpful at all. I tried to use verbose option, it gave me more garbage information, like:
[jspc] parsing /usr/export/docroot/test.jsp:
[jspc] parsed test.jsp in 603 ms.
[jspc] generated java file /usr/export/docroot/test.java, invoking java compiler:
Exec failed .. exiting
Then what's the use of that JSP compiler? Is there anyway to get the same error inforamtion on the web page?
Thanks
This was fixed around service pack 6 in WL 5.1.
mike
Rob Woollen <[email protected]> wrote:
>It looks like it cannot find javac (or whatever java compiler you
>specified) in the path.
>
>-- Rob
>
>Lan wrote:
>>
>> Originally I post it to weblogic.developer.interst. But I guess this may be a better space to post the JSP related question. Sorry for the double post
>>
>> Hi, there,
>>
>> I tried to use the weblogic.jspc to compile my JSP files for debug purpose. However, it doesn't give me detailed information.
>>
>> For example, for JSP file test.jsp:
>> <%
>> out.println(5) // miss ; at the end
>> %>
>>
>> If I use browser to access it, it will give the error information, like:
>> Compilation of ../public_html/jsp_servlet/_test.java' failed:
>>
>> --------------------------------------------------------------------------------
>>
>> /weblogic/appserver/public_html/jsp_servlet/_test.java:74: Invalid type expression.
>> probably occurred due to an error in /test.jsp line 2:
>> out.println("4")
>>
>> /weblogic/appserver/public_html/jsp_servlet/_test.java:76: Invalid declaration.
>> (No more information available, probably caused by another error)
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
>>
>> But if I use weblogic.jspc to compile it, it only tells you:
>>
>> Exec failed .. exiting
>>
>> That message is not helpful at all. I tried to use verbose option, it gave me more garbage information, like:
>>
>> [jspc] parsing /usr/export/docroot/test.jsp:
>> [jspc] parsed test.jsp in 603 ms.
>> [jspc] generated java file /usr/export/docroot/test.java, invoking java compiler:
>> Exec failed .. exiting
>>
>> Then what's the use of that JSP compiler? Is there anyway to get the same error inforamtion on the web page?
>>
>> Thanks
-
Jsp compile seems to stop in between
We have about 30 jsp in our application ....what happens is when we try to run
the application and access some of jsp pages , it gives the error attached below.
Everytime 6-7 jsp pages gets compiled and renmaining it gives an error ie .it's
not able to compile. If we manualyy go and compile it , it works fine.
I am not able to understand as to why jsp pages are not compiled properly . Does
this has t do with security et all??
Message attached below :
java.io.IOException: Compiler failed executable.exec(java.lang.String[javac, -classpath,
/usr/opt/java130/jre/lib/rt.jar:/usr/opt/java130/jre/lib/i18n.jar:/usr/opt/java130/jre/lib/sunrsasign.jar:/usr/opt/java130/jre/classes:/opt/bea/wlserver6.0/libjava.io.IOException:
Compiler failed executable.exec(java.lang.String[javac, -classpath, /usr/opt/java130/jre/lib/rt.jar:/usr/opt/java130/jre/lib/i18n.jar:/usr/opt/java130/jre/lib/sunrsasign.jar:/usr/opt/java130/jre/classes:/opt/bea/wlserver6.0/lib/ya/Core.jar:/opt/bea/wlserver6.0/lib/ya/RemoteEncrypt.jar:/opt/bea/wlserver6.0/lib/ya/thirdparty.jar:/opt/bea/wlserver6.0/lib/ya/versions.jar:/opt/ant/lib/xalan.jar:/opt/ant/lib/xerces.jar:/opt/ant/lib/ant.jar:/opt/bea/wlserver6.0/lib/weblogic_sp.jar:/opt/bea/wlserver6.0/lib/weblogic.jar:/opt/bea/wlserver6.0/lib/ejb20.jar:/usr/opt/java130/lib/tools.jar:/opt/bea/wlserver6.0/lib/directv:/opt/bea/wlserver6.0/lib/directv/egate.jar:/opt/bea/wlserver6.0/lib/directv/SeeBeyondConnectionTest.jar:/opt/bea/wlserver6.0/lib/directv/jdom.jar:/usr/users/qa6/config/app-core.jar:/usr/users/qa6/config/qa6WL/applications/DTVAPP/WEB-INF/classes:/usr/users/qa6/./config/qa6WL/applications/.wl_temp_do_not_delete/wl_local_comp18138.war:/usr/users/qa6/./config/qa6WL/applications/.wl_temp_do_not_delete/WEB-INF/_tmp_war_qa6DTV_qa6DTV_DTVAPP:/usr/users/qa6/config/qa6WL/applications/.wl_temp_do_not_delete/WEB-INF/_tmp_war_qa6DTV_qa6DTV_DTVAPP,
-d, /usr/users/qa6/config/qa6WL/applications/.wl_temp_do_not_delete/WEB-INF/_tmp_war_qa6DTV_qa6DTV_DTVAPP,
/usr/users/qa6/config/qa6WL/applications/.wl_temp_do_not_delete/WEB-INF/_tmp_war_qa6DTV_qa6DTV_DTVAPP/jsp_servlet/_mydirectv/_MySystem.java])
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java,
Compiled Code)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java, Compiled
Code)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java, Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java,
Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java,
Compiled Code)
at com.directv.www.DTVServlet.forwardTo(DTVServlet.java, Compiled Code)
at com.directv.www.accountmanagement.AccountManagerServlet.handleViewSystem(AccountManagerServlet.java,
Compiled Code)
at com.directv.www.accountmanagement.AccountManagerServlet.doPost(AccountManagerServlet.java,
Compiled Code)
at com.directv.www.accountmanagement.AccountManagerServlet.doGet(AccountManagerServlet.java,
Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java, Compiled Code)
at com.directv.www.DTVServlet.service(DTVServlet.java, Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java, Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java,
Compiled Code)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java,
Compiled Code)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java, Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
>
please help.Have you tried something like...
<jsp:setProperty name="Bean2" property="B" value="<jsp:getProperty name="Bean1" property="A" />" /> -
Hello,
I have my jsp pages deployed in a war in an ear. The manifest in the war lists my dependent jars. In my orion-web.xml, I have the include-war-manifest-class-path parameter set to "true". This seems to work at runtime in that the jsp pages can locate the dependent jars. However my problem is at compile time. The compiler doesn't seem to find the jars and the compile fails. If I move the jars to web-inf/lib the compile will work, however that kind of defeats the purpose of having them in the Manifest.mf file.
Anyone have any suggestions?
Thanks,
Mike Sander<p>Sebastian,</p>
<p>Its unclean to include your java files in a jar. I can't remember reading anything about not including java files in the jar file spec though. In your jar file are the java files in the correct package structure?</p>
<p>
Hussein Badakhchani</br>
</p>
Maybe you are looking for
-
Scheduler privileges in trigger
My database version is 10.2.0.3. I have created a trigger which attempts to schedule a job for x minutes time when a batch starts in our application. The trigger is created under the SYSTEM user which has the DBA role and consequently the MANAGE_SCHE
-
EJB slow response time in cluster
We have 2 clusters : cluster 1(3 managed servers) and cluster2( 2 managed servers). We have an EJB deployed on cluster2 which is being called by an application on cluster1. Issue is that this EJB gives a very slow response time (in the order of minut
-
[Evolution Mail and Gnome Keyring] keeps asking passwords
Hi, I can't use my mail boxes in Evolution since more than one week. Here is what "$ LANG=C env CAMEL_DEBUG=all evolution" says: http://pastebin.archlinux.fr/500794 (passwords and personal mail addresses and information removed). I am prompted for th
-
Still seeing "new" photos AFTER folder syncing
I just right-clicked on my main folder (top level) so I could then select "Synchronize Folder." It shows that there are 124 new photos to import. I assume this is because I just combined some folders in an attempt to "neaten things up." So I click on
-
How to update the expired software update from OS 10.7.5 to the newest one
Hi, I am Dewi. I missed to update my software from OS 10.7.5 to its newest one on my macbook air, now i can't update my software though I have tried many times.Is there anyone could help me to solve this problem?Thanks. I also have problem when I hav