Jsp compilation problem in weblogic
HI
i am using weblogicn server in our application
while hitting jsp page directly from browser it is compiling and working fine but while calling jsp file fron workbench like cartrige in endeca it is not compiling and getting as it is same page without compiling
please resolve my problem
HI
i am using weblogicn server in our application
while hitting jsp page directly from browser it is compiling and working fine but while calling jsp file fron workbench like cartrige in endeca it is not compiling and getting as it is same page without compiling
please resolve my problem
Similar Messages
-
JSP compilation errors in weblogic 6.1
I'm getting these JSP compilation errors in weblogic 6.1 on Solaris. Please help.
Full compiler error(s):
error: Invalid class file format:
^
/opt/projects/redherring/beahome/wlserver6.1/config/mydomain/applica
tions/.wlnotdelete/WEB-INF/_tmp_war_myserver_myserver_redherring/jsp_servlet/_w
eb/_jsp/_event/__eventForm.java:34: Class
com.ford.redherring.model.PropertiesAttributesModel not found in import.
import com.ford.redherring.model.PropertiesAttributesModel; <file://[>
/web/jsp/event/eventForm.jsp; Line: 64]
^
/opt/projects/redherring/beahome/wlserver6.1/config/mydomain/applica
tions/.wlnotdelete/WEB-INF/_tmp_war_myserver_myserver_redherring/jsp_servlet/_w
eb/_jsp/_event/__eventForm.java:38: Class com.ford.redherring.util.DialogHeader
not found in import.
import com.ford.redherring.util.DialogHeader; <file://[> /web/jsp/event/eventForm.jsp;
Line: 68]
^
/opt/projects/redherring/beahome/wlserver6.1/config/mydomain/applica
tions/.wlnotdelete/WEB-INF/_tmp_war_myserver_myserver_redherring/jsp_servlet/_w
eb/_jsp/_event/__eventForm.java:39: Class com.ford.redherring.util.DialogFooter
not found in import.
import com.ford.redherring.util.DialogFooter; <file://[> /web/jsp/event/eventForm.jsp;
Line: 69]
^
/opt/projects/redherring/beahome/wlserver6.1/config/mydomain/applica
tions/.wlnotdelete/WEB-INF/_tmp_war_myserver_myserver_redherring/jsp_servlet/_w
eb/_jsp/_event/__eventForm.java:40: Class com.ford.redherring.model.DDContainer
not found in import.
import com.ford.redherring.model.DDContainer; <file://[> /web/jsp/event/eventForm.jsp;
Line: 70]
^
/opt/projects/redherring/beahome/wlserver6.1/config/mydomain/applica
tions/.wlnotdelete/WEB-INF/_tmp_war_myserver_myserver_redherring/jsp_servlet/_w
eb/_jsp/_event/__eventForm.java:41: Class
com.ford.redherring.model.DDValidationModel not found in import.
import com.ford.redherring.model.DDValidationModel; <file://[>
/web/jsp/event/eventForm.jsp; Line: 71]
This appears to be a CLASSPATH problem (you are missing references to
'com.ford.redherring.model.*' and 'com.ford.redherring.util.*'). The
CLASSPATH may be set in the server startup script. Hope this helps.
Wade.
"Katri Alur" <[email protected]> wrote in message news:<[email protected]>...
> I'm getting these JSP compilation errors in weblogic 6.1 on Solaris. Please help.
>
> ----------------------------------------------------------------------------
> ----
> Full compiler error(s):
> error: Invalid class file format:
>
>
> ^
> /opt/projects/redherring/beahome/wlserver6.1/config/mydomain/applica
> tions/.wlnotdelete/WEB-INF/_tmp_war_myserver_myserver_redherring/jsp_servlet/_w
> eb/_jsp/_event/__eventForm.java:34: Class
> com.ford.redherring.model.PropertiesAttributesModel not found in import.
> import com.ford.redherring.model.PropertiesAttributesModel; <file://[>
> /web/jsp/event/eventForm.jsp; Line: 64]
> ^
> /opt/projects/redherring/beahome/wlserver6.1/config/mydomain/applica
> tions/.wlnotdelete/WEB-INF/_tmp_war_myserver_myserver_redherring/jsp_servlet/_w
> eb/_jsp/_event/__eventForm.java:38: Class com.ford.redherring.util.DialogHeader
> not found in import.
> import com.ford.redherring.util.DialogHeader; <file://[> /web/jsp/event/eventForm.jsp;
> Line: 68]
> ^
> /opt/projects/redherring/beahome/wlserver6.1/config/mydomain/applica
> tions/.wlnotdelete/WEB-INF/_tmp_war_myserver_myserver_redherring/jsp_servlet/_w
> eb/_jsp/_event/__eventForm.java:39: Class com.ford.redherring.util.DialogFooter
> not found in import.
> import com.ford.redherring.util.DialogFooter; <file://[> /web/jsp/event/eventForm.jsp;
> Line: 69]
> ^
> /opt/projects/redherring/beahome/wlserver6.1/config/mydomain/applica
> tions/.wlnotdelete/WEB-INF/_tmp_war_myserver_myserver_redherring/jsp_servlet/_w
> eb/_jsp/_event/__eventForm.java:40: Class com.ford.redherring.model.DDContainer
> not found in import.
> import com.ford.redherring.model.DDContainer; <file://[> /web/jsp/event/eventForm.jsp;
> Line: 70]
> ^
> /opt/projects/redherring/beahome/wlserver6.1/config/mydomain/applica
> tions/.wlnotdelete/WEB-INF/_tmp_war_myserver_myserver_redherring/jsp_servlet/_w
> eb/_jsp/_event/__eventForm.java:41: Class
> com.ford.redherring.model.DDValidationModel not found in import.
> import com.ford.redherring.model.DDValidationModel; <file://[>
> /web/jsp/event/eventForm.jsp; Line: 71]
-
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] -
Hi,
Could someone please help on the above mentioned?
I'm using JDeveloper 3.2.3 for my program development under Chinese windows platform. I have created a simple JSP page, which contains few static Chinese words and I have included the line
<%@ page contentType="text/html;charset=UTF-8"%>
at the top of the page. When I tried to compile it using encoding "UTF8" (under compiler option), the compiler gave me this error:
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.jsp
Error: (0) sun.io.MalformedInputException.
Btw, when I have removed the line <%@ page contentType="text/html;charset=UTF-8"%> from the page and compile, I've got this error:
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.jsp
Warning: (0) ISO-8859-1 character set may not match project compiler setting.
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.java
Error: (0) malformed input character in C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.java.
I do appreciate your help on this. Thank you.Here's some info one of the JSP Developers sent me:
1. HELP.....!!!!! Chinese jsp compilation problem.....
The customer is trying to parse a document generated by
Windows's notepad. When saved in UTF-8, the byte
order mark is saved too. We have a know bug that
JSP parser doesn't recognize Byte Order Mark. The
bug is : 1915285.
2. CHINESE CHARACTER ON JSP
. SQLPLUS depends on NLS_LANG setting. If you
check the windows registry, the default of NLS_LANG
depends on the OS. The user environment is Traditional
Chinese, so does NLS_LANG. If we set NLS_LANG
to .UTF8, SQLPLUS dumps the data in UTF8, however,
the command prompt will have problem displaying them.
. For JSP, as mentioned in a previous mail:
<%@ page contentType="text/html;charset=UTF-8" %> for all languages
<%@ page contentType="text/html;charset=GB2312" %> for simplified Chinese
<%@ page contentType="text/html;charset=Big5" %> for traditional Chinese
. When you enter Chinese characters on a browser,
the data is automatically converted to page encoding
(UTF-8 in your case) before sent back to the server.
But your receiving servlet/JSP needs to have request
encoding set correctly.
I'm not sure about the JDeveloper environment,
but here is a simple JSP you may try to verify your
OC4J environment:
a. To set up the schema:
connect scott/tiger
create table tab01(col varchar2(100));
b. Edit the connect string in nls.jsp
c. Run the nls.jsp in oc4j instance.
<!-- nls.jsp -->
<%@ page contentType="text/html; charset=UTF-8" %>
<%@ page import="oracle.jdbc.*,java.sql.*,java.io.*"%>
<HTML>
<HEAD>
<TITLE>Hello</TITLE></HEAD>
<BODY>
<%
request.setCharacterEncoding("UTF-8");
String sampledata="\u7D20";
String paramValue = request.getParameter("myparam");
String connStr = "jdbc:oracle:thin:@dlsun478:5521:j2ee01";
String user = "scott";
String passwd = "tiger";
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection(connStr, user, passwd);
if (paramValue == null || paramValue.length() == 0) { %>
<FORM METHOD="GET">
Please input your name: <INPUT TYPE="TEXT" NAME="myparam"
value="<%=sampledata%>" size=20>
<BR>
<INPUT TYPE="SUBMIT" value="Insert Data">
</FORM>
<%
selectData(conn, out);
else
%>
<H1> Insert Data: <%= paramValue %> </H1>
<br/>
<%
insertData(conn, paramValue);
%>
<a href="nls.jsp">back</a>
<%
%>
</BODY>
</HTML>
<%!
public void insertData(Connection aConn, String myval)
try {
PreparedStatement stmt = aConn.prepareStatement("insert into tab01
values(?)");
stmt.setString(1, myval);
stmt.executeUpdate();
aConn.close();
catch (SQLException e) {
e.printStackTrace();
public void selectData (Connection aConn, JspWriter out)
try {
Statement stmt = aConn.createStatement( );
ResultSet r = stmt.executeQuery("SELECT col FROM tab01");
out.println("<H1>List of Data:</H1>");
while (r.next()) {
out.println(r.getString(1)+"<br/>");
aConn.close();
catch (SQLException e) {
e.printStackTrace();
catch (IOException e) {
e.printStackTrace();
%> -
Weblogic 6.0 jsp compile problem
I'm having a problem with weblogic 6.0sp1 creating the java source files from a
jsp file. The first 3 lines of the jsp are:
<%@ page import="javax.naming.*"%>
<%@ page import="java.util.Properties"%>
<%@ page import="com.cicons.expenses.business.*"%>
the first 2 imports work, but the 3rd does not. The compiler indicatesd the package
is not found. The package com.cicons.expenses.business is located in a deployed
ejb jar file targeted to the same server as the jsp. The jsp is in a war file
also targeted to this server. Is it a requirement to create an ear combining the
jar and war?
Dave,
The only way I have been able to successfully access an EJB from a JSP page in
WLS 6 is to package everything up in their respective ear, war, and jar files.
So I think that's what you need to do at the moment.
-Todd
"Dave Sailer" <[email protected]> wrote:
>
>I don't think that's my problem. I think I found the answer to my problem
>at http://e-docs.bea.com/wls/docs60/////programming/packaging.html.
>This states that, in order for a jsp to find an ejb, they must be packaged
>in
>jar/war/ear files. I just had the jsp sitting out there standalone and
>the ejb
>in a jar.
>"Rick Joi" <[email protected]> wrote:
>>I have not worked with WebLogic 6, but the following would be the issue
>>for
>>5.1.
>>
>>The war and the jar are being loaded in different ClassLoaders underneath
>>the WebLogic ClassLoader (which is underneath the System ClassLoader).
>> If
>>you want to use your EJB as a client from JSP, you'll need to have your
>>EJB
>>client classes either in the WebLogic classpath or in your JSP
>>classpath/war.
>>
>>The documentation on this for 5.1 is at
>>http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_deployover.html#1056431
>>
>>Rick
>>[email protected]
>>www.rickanddonna.com/ips
>>
>>
>>
>>"Dave Sailer" <[email protected]> wrote in message
>>news:[email protected]...
>>>
>>> I'm having a problem with weblogic 6.0sp1 creating the java source
>>files
>>from a
>>> jsp file. The first 3 lines of the jsp are:
>>> <%@ page import="javax.naming.*"%>
>>> <%@ page import="java.util.Properties"%>
>>> <%@ page import="com.cicons.expenses.business.*"%>
>>>
>>> the first 2 imports work, but the 3rd does not. The compiler indicatesd
>>the package
>>> is not found. The package com.cicons.expenses.business is located
>in
>>a
>>deployed
>>> ejb jar file targeted to the same server as the jsp. The jsp is in
>>a war
>>file
>>> also targeted to this server. Is it a requirement to create an ear
>>combining the
>>> jar and war?
>>
>>
>
-
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> -
JSP Compile problem with WLS 5.1 sp9
Hi All,
The attached, simple JSP file uses a custom tag, and some JavaScript. When
this is compiled into Java, the Java that is created is Bad. It seems as if
WLS is having problems properly escaping single-quotes and double-quotes.
Also attached, is the generated Java file. Note around line 82, and compare
that to around line 15 of the JSP.
Does anyone have an idea what can be done to fix this? This JSP compiles
fine under Tomcat 3.2.
Thanx!
Will Hartung
([email protected])
[test.jsp]
[_test.java]
Hi All,
The attached, simple JSP file uses a custom tag, and some JavaScript. When
this is compiled into Java, the Java that is created is Bad. It seems as if
WLS is having problems properly escaping single-quotes and double-quotes.
Also attached, is the generated Java file. Note around line 82, and compare
that to around line 15 of the JSP.
Does anyone have an idea what can be done to fix this? This JSP compiles
fine under Tomcat 3.2.
Thanx!
Will Hartung
([email protected])
[test.jsp]
[_test.java]
-
JSP Compilation Problems With JSTL tags
My JSP worked well when I used JSP expressions, scriptlets, .... I tried to use JSTL instead and encountered some compilation problems. I am unable to see my mistakes and need help:
Problme #1:
int offset = 0;
try
<c:set var="offset" value="${requestScope.offset}" />
catch ( Exception e )
// do nothing
}The above code has two compilation errors:
Generated servlet error:
[javac] Compiling 1 source file
illegal start of expression
<c:set var="offset" value="${requestScope.offset}" />
^
Generated servlet error:
';' expected
<c:set var="offset" value="${requestScope.offset}" />
^
Problem #2:
<c:set var="threadBean" value="${requestScope.ThreadBean}" />
int threadID_int = ParamUtil.getParameterInt( request, "thread" );
<c:if test="${threadBean.threadID} != threadID_int">
throw new AssertionException( "The two threadID are not the same." );
</c:if>Generated servlet error:
illegal start of expression
<c:if test="${threadBean.threadID != threadID_int}">
^I have deleted the Java code around the JSTL tags. Now, what is wrong with this <c:if test=" ... "> tag? It seems that I have problems to get JSTL tags right.
It seems that I have problems to get JSTL tags right....
<c:if test="${attachBean.attachMimeType.startsWith('image/')}">
<html:img page="getattachment?attach=<c:out value='${attachBean.attachID}' />" alt="<c:out value='${attachBean.attachFilename}' />" title="<c:out value='${attachBean.attachFilename}' />" border="0" />
</c:if>error message:
74: tag = 'if' / attribute = 'test': An error occurred while parsing custom action attribute "test" with value "${attachBean.attachMimeType.startsWith('image/')}": Encountered "(", expected one of ["}", ".", ">", "gt", "<", "lt", "==", "eq", "<=", "le", ">=", "ge", "!=", "ne", "[", "+", "-", "*", "/", "div", "%", "mod", "and", "&&", "or", "||"] -
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 -
UTF-8 encoded JSPs compilation problem
Hi,
I'm using Weblogic 9.0 Beta. I have an XML-format UTF-8 encoded JSP (with the proper encoding declarations). I can see that this is compiled into a UTF-8 Java servlet by WebLogic.
At the compilation to a class file though, the encoding is corrupted. I guess that the Java compiler is assuming a system-encoded (which would be ISO-8859-1) Java file instead of the actual UTF-8 encoding.
This problem did not occur with WebLogic 8.1.
I have tried to explicitly tell the Java compiler to treat the source files as UTF-8 in weblogic.xml, i.e.
<jsp-param>
<param-name>compileFlags</param-name>
<param-value>-encoding UTF8</param-value>
</jsp-param>
but that had no effect.
Anyone else noticed this?
I assume that correct behaviour is for WebLogic to preserve encoding from JSP to servlet to class file, rather than for me to set encoding in weblogic.xml. Is that correct?
Is there a workaround?
Thanks for any help you can offer!Solved
It is about Tomcat's character encoding not about the codes..
For more info:
[http://wiki.apache.org/tomcat/Tomcat/UTF-8] -
JSP compile Error in Weblogic 5.1 server
My application is running well in Weblogic 5.1 sp10 server. I am trying to run my application as NT service. The NT service installed and started with no problem. But I got following error messages when I try to access my JSP. Can anyboby help me out? Thanks in advance.
James
Compilation of ' D:\applica\middleware1\Server\lib\WEBINF\_tmp_war_paygo\jsp_servlet\_login.java' failed:
Failed to parse compiler output:
java.io.IOException: CreateProcess: javac -classpath d:\jdk1.3.1_02\jre\lib\rt.jar;d:\jdk1.3.1_02\jre\lib\i18n.jar;d:\jdk1.3.1_02\jre\lib\sunrsasign.jar;d:\jdk1.3.1_02\jre\classes;d:\rogers\weblogic51\weblogic510sp10\lib\weblogic510sp10boot.jar;d:\rogers\weblogic51\classes\boot;d:\rogers\weblogic51\eval\cloudscape\lib\cloudscape.jar;d:\applica\middleware1\lib\crimson.jar;d:\applica\middleware1\lib\xalan.jar;d:\applica\middleware1\lib\msbase.jar;d:\applica\middleware1\lib\mssqlserver.jar;d:\applica\middleware1\lib\msutil.jar;d:\applica\middleware1\lib\classes12_01.zip;d:\applica\middleware1\lib\mail.jar;d:\rogers\weblogic51\license;d:\rogers\weblogic51\weblogic510sp10\lib\weblogic510sp10.jar;d:\rogers\weblogic51\classes;d:\rogers\weblogic51\lib\weblogicaux.jar;d:\rogers\weblogic51\myserver\serverclasses;d:\applica\middleware1\itspServer\lib\paygo_server_classes.jar;d:\applica\middleware1\APILink\apiclasses.jar;d:\applica\middleware1\APILink\ejbInfra.jar;d:\applica\middleware1\APILink\ObjectManager.jar;d:\applica\middleware1\APILinD
at java.lang.Win32Process.create(Native Method)
at java.lang.Win32Process.(Win32Process.java:66)
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:443)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:249)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:366)
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.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:922)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:886)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)check PATH
or register full path for javac
at weblogic.properties -
JSP compile problem - Scriptlet
Hello,
I'm using weblogic 10.3.
I have problem when i run a web application.
The problem is accured when weblogic try to compile jsp page that contains such syntax :
*<jsp:param name="messageKey" value="<%=request.getParameter("noCebMessageKey")%>" />*
When i change this assertion to :
*<%String msg = request.getParameter("noCebMessageKey");%>*
*<jsp:param name="messageKey" value="<%=msg%>" />*
It works fine..
This problem is general with all syntax like this : value="<%=<java instruction>%>
It's a big problem, becaus the application contains more than 2000 jsp pages..
Are there any special config to add to weblogic configuration files to resolve this problem ?
ThanksHi WhietacapeTech ,
Normally you cannot do the following which u are trying currently because of the Double Quote Mark Opening and Closing...will awlsya create the issue...:
<jsp:param name="messageKey" value="<%=request.getParameter("noCebMessageKey")%>" />
Alternate option: (Use JSTL [*Java Standard Tag Library]*)
Example:
*<%@ taglib uri="/WEB-INF/tld/c.tld" prefix="c" %>*
*<jsp:param name="messageKey" value="<c:out value='${param.noCebMessageKey}' " />*
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are here) -
JSP Refresh Problems with Weblogic 8.1
While Integration testing with Weblogic 8.1, when I make any changes in the Java classes (like interface changes), the JSPs are not able to recognize them. If the interface being used by a JSP changes, the JSP starts giving compilation errors. The other Java classes of the project though, run fine with the changes.
Have wasted a lot of time in this situation . PLEASE ANY1 HELP!!!
regards,
SRNot sure on the first problem, store-version-in-cache is a valid element. Make sure you are using the same version of the Mapping Workbench and the runtime library. Please attach the XML for the version locking policy that was generated and the error message.
The abstract method error seems to indicate that the setFetchSize method is missing on your driver.
setFetchSize has been part of JDBC and JDK since JDBC 2.0/JDK 1.2, how old is the driver that you are trying to use? I noticed the COM is uppercase, so I assume this is a very old driver, can you use the more update version? TopLink requires JDK 1.3 support as a minimum. -
JSP compiler problems/Weird NullPointerException in JSP
[weblogic 4.5.1 sp 10 on NT 4.0 sp4 w/Netscape 4.72, jdk 1.2.2]
I recently began trying to compile all of my jsp files externally rather
than depending on the dependency detection. Because I have multiple
levels of nested files included, I have had a lot of problems making the
compile work. For example, I have a subdirectory called include. Jsp
files in the include directory are included from the directory above
using '<%@ include file="include/filename.jsp" %>'. This works for one
level of nesting, but there are problems when a file in the include
subdirectory includes another file in the include subdirectory. Prior
to installing service packs, specifying 'include/secondfile.jsp' for the
file parameter worked. After service packs, this code had to be changed
to just plain 'secondfile.jsp'. Imagine my surprise when I started
compiling externally and only 'include/secondfile.jsp' would work. If I
ever touch a jsp file after compiling them all, then the compile invoked
by the JspServlet will NOT include secondfile unless I also modify the
include line before the compile happens. This is a MAJOR PAIN, and I
would like an explanation. How come invoking weblogic.jspc does
something different than invoking JspServlet through file timestamp
checking? Also, any ideas for a workaround?
This leads to my second really annoying problem. After compiling all
JSPs and restarting weblogic, I get a NullPointerException accessing a
static method in a particular class. Many pages display correctly until
this point in the processing, none of which access the problem class. A
log message before the static method call is printed. A try/catch block
surrounds the call. The first line in the static message prints another
log message. This static method log message is not reached, and the
try/catch block catches a NullPointerException. It seems the class
reference is null, a situation I have not previously encountered in
java. The generated java file looks fine, with no other code between
the log message and the static call. Now here is the rub - if I touch
the jsp file containing the class reference, with no code change,
weblogic recompiles it using JspServlet, and then everything works as
expected. It seems the external compilation is the only factor that
varies in the failure. I am quite frustrated trying to track this
'impossible to occur' exception. Any suggestions, advice, or
workarounds?
I have searched newsgroups and seen some similar behaviors reported, but
with no solutions. One person mentioned that the external compile
should take place with the current directory set to the root. This
fails completely to find the relative include files.
Bryan Helm
The includes only work if you invoke the compilation when you are on top of
the hierrcahy,
ex foo/bar.jsp
do a jspc foo/bar.jsp,
not cd foo
jscp bar.jsp
Bryan Helm <[email protected]> wrote in message
news:[email protected]...
> [weblogic 4.5.1 sp 10 on NT 4.0 sp4 w/Netscape 4.72, jdk 1.2.2]
>
> I recently began trying to compile all of my jsp files externally rather
> than depending on the dependency detection. Because I have multiple
> levels of nested files included, I have had a lot of problems making the
> compile work. For example, I have a subdirectory called include. Jsp
> files in the include directory are included from the directory above
> using '<%@ include file="include/filename.jsp" %>'. This works for one
> level of nesting, but there are problems when a file in the include
> subdirectory includes another file in the include subdirectory. Prior
> to installing service packs, specifying 'include/secondfile.jsp' for the
> file parameter worked. After service packs, this code had to be changed
> to just plain 'secondfile.jsp'. Imagine my surprise when I started
> compiling externally and only 'include/secondfile.jsp' would work. If I
> ever touch a jsp file after compiling them all, then the compile invoked
> by the JspServlet will NOT include secondfile unless I also modify the
> include line before the compile happens. This is a MAJOR PAIN, and I
> would like an explanation. How come invoking weblogic.jspc does
> something different than invoking JspServlet through file timestamp
> checking? Also, any ideas for a workaround?
>
> This leads to my second really annoying problem. After compiling all
> JSPs and restarting weblogic, I get a NullPointerException accessing a
> static method in a particular class. Many pages display correctly until
> this point in the processing, none of which access the problem class. A
> log message before the static method call is printed. A try/catch block
> surrounds the call. The first line in the static message prints another
> log message. This static method log message is not reached, and the
> try/catch block catches a NullPointerException. It seems the class
> reference is null, a situation I have not previously encountered in
> java. The generated java file looks fine, with no other code between
> the log message and the static call. Now here is the rub - if I touch
> the jsp file containing the class reference, with no code change,
> weblogic recompiles it using JspServlet, and then everything works as
> expected. It seems the external compilation is the only factor that
> varies in the failure. I am quite frustrated trying to track this
> 'impossible to occur' exception. Any suggestions, advice, or
> workarounds?
>
> I have searched newsgroups and seen some similar behaviors reported, but
> with no solutions. One person mentioned that the external compile
> should take place with the current directory set to the root. This
> fails completely to find the relative include files.
>
> Bryan Helm
>
-
JSP Compilation Problem in Tomcat 5.0.28
I am having problem after i deploy my applcation in tomcat 5.0.28. While accessing a jsp an excpetion is generated:
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
Note: Recompile with -Xlint:unchecked for details.
1 error
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:332)
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:412)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:472)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Help on this is appricated.
-NileshShow me the code
Maybe you are looking for
-
Shrink database is not active in SQL SERVER Enterpriser manager
Dear guru Shrink database is not active in SQL SERVER Enterpriser manager what to do Rupesh SAP BASIS Consultant
-
How do I transfer my contacts from my old Powerbook G4 to my new Macbook Pro?
how do I transfer my contacts from my old Powerbook G4 to my new one Macbook Pro? new Macbook Pro is operating on OSX 10.8.2 When I save it as an export then try to open it on the new computer it wants me to delete all my current contacts before it w
-
Will this really install itunes 10.7?
http://support.apple.com/kb/DL1577 will this link really install 10.7 ??? I'd really like to go back to that version I have windows 7, 64 bit... iTunes 10.7 for Windows 64 About iTunes 10.7 for Windows 64 iTunes 10.7 adds support for iOS 6 running on
-
Teststand message box larger font for 95 years old
Hi I am working with people > 90 yrs. the message pop up window occupied on top of the screen. How can I help them by changing the font and/or color of the message pop up. the real estate of the screen is there. message pop up dominates the screen, n
-
Firefox 3.6.14 shows URl but displays nothing, changing URLs crashes it
After Firefox 3.6.14 installed itself on my Mac, I have not been able to see any page and if I change URLs, it crashes. How can I get a back copy of Firefox?