JSP XML Problem
Hi !
i am creating a program using JSP Ajax that read PUBLIC enteries of Google calender but when i run to check the JSP file [that is Server Side process & return result to HTML] i got the following result:
375/-+1750/-Bunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/n21nl92hsg9mljbv0ntsrlrhp42006-11-14T10:12:59.000Z2006-11-14T10:13:22.000ZWhen: 2006-11-14 <br> <br>Event Status: confirmedWhen: 2006-11-14 <br> <br>Event Status: confirmedBunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/o7ttfhhs2fbsjl34m08026h2102006-11-14T10:11:31.000Z2006-11-14T10:12:05.000ZWhen: 2006-11-17 13:00 to 14:00 IST <br> <br>Event Status: confirmedWhen: 2006-11-17 13:00 to 14:00 IST <br> <br>Event Status: confirmedBunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/kir9gd7c9gkf6va0283oicbivc2006-10-04T14:00:37.000Z2006-10-04T14:00:37.000ZWhen: 2006-10-15 17:00 to 18:30 IST <br> <br>Event Status: confirmedWhen: 2006-10-15 17:00 to 18:30 IST <br> <br>Event Status: confirmedBunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/6d628dcmei9f3kd2c705i282o02006-09-28T09:08:26.000Z2006-10-04T13:59:43.000ZWhen: 2006-10-07 10:00 to 11:00 IST <br> <br>Event Status: confirmedWhen: 2006-10-07 10:00 to 11:00 IST <br> <br>Event Status: confirmedBunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/i4o0s31ia8cuau5gn3l6ecvd582006-09-19T11:04:10.000Z2006-09-25T10:16:06.000ZWhen: 2006-10-15 15:00 to 16:00 IST <br> <br>Where: Rajouri Garden <br>Event Status: confirmedWhen: 2006-10-15 15:00 to 16:00 IST <br> <br>Where: Rajouri Garden <br>Event Status: confirmedBunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/vfu1bbrickckleptoh46m3v09k2006-09-25T10:15:19.000Z2006-09-25T10:15:19.000ZRecurring Event<br> First start: 2006-09-27 IST <br> Duration: 86400 <br>Event Status: confirmedRecurring Event<br> First start: 2006-09-27 IST <br> Duration: 86400 <br>Event Status: confirmedBunty
IE Error while executing
XML document must have a top level element. Error processing resource
But it should be a proper XML file.....
HTML Code:
function RSSRequest() {
// change the status to requesting data
HideShow('status');
document.getElementById("status").innerHTML = "Requesting data ...";
// Prepare the request
RSSRequestObject.open("GET", rssReader.jsp, true);
// Set the onreadystatechange function
RSSRequestObject.onreadystatechange = ReqChange;
// Send
RSSRequestObject.send(null);
<body onload="RSSRequest();">
<h2>Google Calendar Events - RSS Reader- BuntyIndia</h2>
<div id="status" style="display:none"></div>
<div id="ajaxreader"></div>
JSP Code:
<%@ page import = "java.io.*, java.util.*,java.net.URL,java.net.*,java.awt.*" %>
<%
response.setContentType("text/xml");
response.setHeader("Cache-Control", "no-cache");
response.setHeader("pragma","no-cache");
URL url = new URL(" http://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031e071629562bb68d446f5f2b59/basic");
URLConnection urlConnection = url.openConnection ( ) ;
StringBuffer stringbuffer = new StringBuffer("");
String news =new String();
try {
BufferedReader in = new BufferedReader ( new InputStreamReader (url.openStream())) ;
while((in.readLine())!= null)
//s2=in.readLine();
stringbuffer.append(in.readLine());
in.close();
catch(Exception e) {
System.out.println(e.getMessage());
//news=stringbuffer.toString();
//out.println(news);
response.getWriter().write(in);
%>Please Help
Bunty India
you don't want a scriptlet, you want an expression
<input type="TEXT" name="Product" value="<%= Product %>">
Similar Messages
-
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, XML, XSLT: applying XSL on JSP-generated XML doc
Hello,
I am currently trying to figure out how to do the following:
let's consider (that's not entirely hypothetical :) ) a web application working with JSP (on apache/tomcat 3.1) and oracle BC4J Application modules.
The JSPs call oracle webbeans to perform updates and retrieve data from an 8.1.6 database.
Now I'm thinking of moving to a combination of JSP, XML and XSL, which (hopefully) would allow to customize the application depending on the user's browser, language etc...(that's the point isn't it?)
It doesn't seem to be a problem to produce XML from a jsp, send it directly to the client browser, which in turn goes to look for the proper XSL file and does all the transformation stuff.
However this only works with I.E 5 for the moment right? and most website need to support various kinds of browsers...
The need is:
* When a non XML-capable browser is detected, apply the proper XSL(s) on the server side before sending the result back, in html/wml/whatever...
* For XML-capable browsers, produce raw XML, maybe apply some XSL(s), and eventually send the result to the browser which handles the rest of the XSL stuff itself.
Therefore, I'd like to:
- Have the jsp produce the raw xml data (maybe adding extra tags, to indicate the browser and/or the language that the jsp engine has detected).
- Pass the output to a first XSLT engine which would take care of the language stuff
- Feed the result into a second XSLT engine to handle browser specificities for instance...
- Send the final output to the client browser.
Now, there are 2 problems:
* 1/ I have seen various engines capable of chaining XSL transforms, and it is easy to produce XML from a jsp, but I don't know how to feed a jsp's output into an XML engine. is that possible? how?
* 2/ I'm a bit concerned about the cost of applying three (or more) process stages, does anyone have insight on the performance issues this could raise?
bonus question ;) : is there a simpler approach?
Thanks a lot in advance, Remi
nullHello,
I am currently trying to figure out how to do the following:
let's consider (that's not entirely hypothetical :) ) a web application working with JSP (on apache/tomcat 3.1) and oracle BC4J Application modules.
The JSPs call oracle webbeans to perform updates and retrieve data from an 8.1.6 database.
Now I'm thinking of moving to a combination of JSP, XML and XSL, which (hopefully) would allow to customize the application depending on the user's browser, language etc...(that's the point isn't it?)
It doesn't seem to be a problem to produce XML from a jsp, send it directly to the client browser, which in turn goes to look for the proper XSL file and does all the transformation stuff.
However this only works with I.E 5 for the moment right? and most website need to support various kinds of browsers...
The need is:
* When a non XML-capable browser is detected, apply the proper XSL(s) on the server side before sending the result back, in html/wml/whatever...
* For XML-capable browsers, produce raw XML, maybe apply some XSL(s), and eventually send the result to the browser which handles the rest of the XSL stuff itself.
Therefore, I'd like to:
- Have the jsp produce the raw xml data (maybe adding extra tags, to indicate the browser and/or the language that the jsp engine has detected).
- Pass the output to a first XSLT engine which would take care of the language stuff
- Feed the result into a second XSLT engine to handle browser specificities for instance...
- Send the final output to the client browser.
Now, there are 2 problems:
* 1/ I have seen various engines capable of chaining XSL transforms, and it is easy to produce XML from a jsp, but I don't know how to feed a jsp's output into an XML engine. is that possible? how?
* 2/ I'm a bit concerned about the cost of applying three (or more) process stages, does anyone have insight on the performance issues this could raise?
bonus question ;) : is there a simpler approach?
Thanks a lot in advance, Remi
null -
What changes i should made in web.xml for using jsp/xml using weblogic
Hi all,
I just know some changes has to made in web.xml or weblogic.xml if i have to use weblogic for jsp/xml.
Pls. anybody post the steps to intereaction with xml using weblogic.
I am using jdk1.4The problem is solved.
The information is given at
http://e-docs.bea.com/wls/docs61/webapp/webappdeployment.html -
HELP: JSP + XML + XSLT = HTML?
Hello, all.
I am trying out Weblogic 6 and I am trying to get the JSP + XML + XSLT =>
HTML chain working.
I am coming from using Orion and SAXON.. and in that situation I had a JSP
that contained XML tags... they were filled in at runtime and then using
Servlet-Chaining was passed along to the SAXON XSLT Processer. SAXON checked
for the inline XSL specified and then used that to transform the document
into HTML.
It worked well, but there were some other features missing/not documented
that we now need.
With Weblogic I am trying to use the XSLT Tag Library that comes with the
distribution, but it seems to be very finicky. I followed the directions and
I got it to do a sort of roundabout transformation. But it doesn't seem to
work quite right.
The best I can get is the following:
I have an 'xslt' directory url-pattern-mapped to xslt.jsp (as instructed)...
but can't figure out how to specify the xsl file on-the-fly... that is, if I
don't hard-code the XSL file in the x:xslt element in the xslt.jsp it
complains about some XML file not having a root element.
Ideal situation:
1. I have a JSP that includes XML elements.
2. It is filled from a database at runtime and specifys (using a PI) what
XSL stylesheet it is to be processed with.
3. Somehow (fingers crossed) the XML is processed and transformed into HTML
by the appropriate XSL file.
I think I am mostly stuck moving between steps 2 and 3.
Can anyone give me some hints? Are there some Weblogic specific
elements/tags that I have to include in the XML file that Weblogic will
catch and re-direct to the XSL Parser?
Please, anyone, if you have some information, I would much appreciate it.
Dylan Parker
PS - I apologize for the cross-post, I hope it doesn't cause too much
traffic.Craig,
I've since discovered how to do it with the WL Taglibrary... and have
moved on =)
It has to do with the EXTREMELY BADLY documented x:xml tag that can
appear within the x:xslt tag body...
So the WL Tag Library allows something like the following.
(Please note, angled brackets are omitted in this post to prevent html
parsing)
[x:xslt stylesheet="sheet.xsl"]
[x:xml]
Here is the XML to run the sheet on.
This should have all relevant XML syntax: the PIs, the doctype,
root elements etc...
[x:xml]
[x:xslt]
And that DOES work. But not very well. WL, a little prematurely
incorporated versions 1.2 of Xerces and Xalan in their product -- and
these versions have some irritating bugs.
Also -- There tag library doesn't copy the source XML across as UTF-8
.. so a lot of the Japanese I have embedded there (from a DB) gets
mangled somewhere in their code...
AND -- If you hammer a little bit on an JSP/XML that uses the WL Tag
Library (eg clicking refresh lots of times in IE)... I get huge
amounts of irritating exceptions appearing in the log files.
NullPointerExceptions
XSL Parsing Exceptions
XML Parsing Exceptions
but completely unpredictably...
In my eyes.. the WL XML/XSL Tag Library using the incorporated and
untouchable Xalan and Xerces (v1.2) is virtually unusable.
What a pain.
BUT! Apache offers a similar OPEN SOURCE XSL Tag Library available
here:
http://jakarta.apache.org/taglibs/doc/xsl-doc/intro.html
And it uses the standard, non-weblogic-incorporated, Xerces and Xalan
(which means you can provide whatever version you want).. and it works
impressively well.
It has almost identical performance as the WL Taglib, and without all
of the bizarre exceptions being thrown.
And it does proper passing of the character encoding type!
If only the taglib did caching though =(
The performance hit over pure JSP is huge. Almost two orders of
magnitude. On my desktop box I can get around 500Requests/Sec if I am
returning HTML direct from a JSP... while if I produce XML that gets
processed by XSL into HTML the Requests/Sec drops to 5!!!!
Caching. Caching. And more Caching. A lot of DiskIO is going on with
the XML/XSL/XHTML chain of events.
I hope this helps!
I'd be curious as to what you find out as well.
Dylan Parker
On 5 Mar 2001 07:20:00 -0800, "Craig Macha"
<[email protected]> wrote:
>
Yep, I feel Dylan's pain.
I am trying to accomplish the same thing. A JSP page generating
dynamic XML content and then utilizing an XSLT stylesheet to transform
all the content into XHTML.
Does anyone have some examples that show exactly how to accomplish
this? Can I do this with WLS and the XML taglib that comes with
it? Or do I have to move on to something like Cocoon to get this
capability?
Any insight would be greatly appreciated.
Thanks,
Craig Macha
"Dylan Parker" <[email protected]> wrote:
Hello, all.
I am trying out Weblogic 6 and I am trying to get the
JSP + XML + XSLT =>
HTML chain working.
I am coming from using Orion and SAXON.. and in that situation
I had a JSP
that contained XML tags... they were filled in at runtime
and then using
Servlet-Chaining was passed along to the SAXON XSLT Processer.
SAXON checked
for the inline XSL specified and then used that to transform
the document
into HTML.
It worked well, but there were some other features missing/not
documented
that we now need.
With Weblogic I am trying to use the XSLT Tag Library
that comes with the
distribution, but it seems to be very finicky. I followed
the directions and
I got it to do a sort of roundabout transformation. But
it doesn't seem to
work quite right.
The best I can get is the following:
I have an 'xslt' directory url-pattern-mapped to xslt.jsp
(as instructed)...
but can't figure out how to specify the xsl file on-the-fly...
that is, if I
don't hard-code the XSL file in the x:xslt element in
the xslt.jsp it
complains about some XML file not having a root element.
Ideal situation:
1. I have a JSP that includes XML elements.
2. It is filled from a database at runtime and specifys
(using a PI) what
XSL stylesheet it is to be processed with.
3. Somehow (fingers crossed) the XML is processed and
transformed into HTML
by the appropriate XSL file.
I think I am mostly stuck moving between steps 2 and 3.
Can anyone give me some hints? Are there some Weblogic
specific
elements/tags that I have to include in the XML file that
Weblogic will
catch and re-direct to the XSL Parser?
Please, anyone, if you have some information, I would
much appreciate it.
Dylan Parker
PS - I apologize for the cross-post, I hope it doesn't
cause too much
traffic. -
IOError in IE but not in Firefox (possible crossdomain.xml problem)
Yesterday, I hopefully debugged a problem that is occuring for our application in IE but not in Firefox.
It has to do with accessing remote content from a separate domain.
In every aspect it APPEARS to be a crossdomain.xml issue but the fact that this issue only arrises in IE is what has prompted me to post here.
We have a solution in the works (bureaucratically speaking) but I want to double check here.
Our application is on domain "a.domain".
It access an xml file on "b.domain/xml/".
And finally (this is the tricky part) it also accesses an xml file at "b.domain/forwardingPath/" which is actually forwarded to "c.domain/xml/".
The crossdomain.xml is located at "b.domain/crossdomain.xml".
The request for "b.domain/xml/anXMLFile.xml" works without any problem.
The request for "b.domain/forwardingPath/anotherXMLFile.xml" succeeds in Firefox but not in IE (remember, the ACTUAL request is forwarded to "c.domain/xml/anotherXMLFile.xml").
In IE I get an IOError.
I believe we need an appropriate crossdomain.xml file also located at "c.domain/crossdomain.xml" and have put in that request. What I want to confirm is whether this understanding is correct. I am not a server-side person at all. It's all elves and fairies to me. And then finally, why the hell is this behavior inconsistent between IE and Firefox? Is the Firefox version of flash player violating its own security standards?!
I am cross-posting this at stack overflow. http://stackoverflow.com/questions/7395931/ioerror-in-ie-but-not-in-firefox-possible-cross domain-xml-problemI've pinged our developers about this and here's what they have to say:
"We did some work for the plugin around redirects andhence the correct behavior on Firefox.
AFAIK, on IE we don't get notified of the redirect and can't participate in making security decisions during redirect scenarios. This behavior is out of our control.
There is a workaround documented in the AS3docs here: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/system/LoaderCont ext.html#checkPolicyFile
Here is the pertinent paragraph:
Be careful with checkPolicyFile if you are downloading anobject from a URL that may use server-side HTTP redirects. Policy files arealways retrieved from the corresponding initial URL that you specify inURLRequest.url. If the final object comes from a different URL because of HTTPredirects, then the initially downloaded policy files might not be applicableto the object's final URL, which is the URL that matters in security decisions.If you find yourself in this situation, you can examine the value ofLoaderInfo.url after you have received a ProgressEvent.PROGRESS orEvent.COMPLETE event, which tells you the object's final URL. Then call theSecurity.loadPolicyFile() method with a policy file URL based on the object'sfinal URL. Then poll the value of LoaderInfo.childAllowsParent until it becomes true."
Chris -
Web.xml problem in Enterprise Manager 10g
I got an error while deploying to Enterprise Manager 10g
My platform: Windows XP
OC4J 9.0.4
Enterprise Manager 10g
And I even have the web.xml in the correct directory. i.e
cpd.ear
./META-INF/application.xml
./cpd-ejb.jar/WEB-INF/web.xml
./cpd-webapp.war/WEB-INF/web.xml
./cpd-webapp.war/WEB-INF/classes
The error I get while deploying on a Enterprise Manager 10g is:
Invalid J2EE application file specified - Jar file: :\WINNT\TEMP\jar47575.tmp is missing its standard xml descriptor located at WEB-INF/web.xml
Incidently the *.ear file built by my fellow's machine is deploying perfectly. I've compared the directories n useful files of both the *.ears down to the very last bit n they are the same.
I can imagine that guys with only high IQ can solve this mysteryThe above message is a duplicate of another message by Sim.
web.xml problem in Enterprise Manager 10g -
HELP.....!!!!! Chinese jsp compilation problem.....
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();
%> -
Log-Configuration.xml Problems
Hi, I have been trying to use log-configuration.xml but it seems like i cannot get it to work at all.
From what i understand, once i deploy my application, i should be able to edit the config via the Visual Administrator. However, after i deploy my app, i am still unable to see it with visual administrator. furthermore, i cannot find the file anywhere on the sever. Also, my settings are not reflected in the behaviour of the defaultTrace.
Am i suppose to be able to find the "log-configuration.xml" file in the server if i have done the correct steps? If so, what are the likely mistakes i have made? I am at my wits end, anyone can help me?
Just to add, this post seems to describe exactly my situation except i have no idea how to "manually" correct it... log-configuration.xml outside META-INF due to NWDS
TIA!
Ah Beng
Message was edited by: ah bengHi Rajeshkr,
Sorry, i am kinda new to web dynpro and sap in general so i may need you to be more explicit
I am not quite sure what this part means or how to check "...has been deployed successfully in the deploy node of the visual Node and check for the Log Configuratior Node and check for your deployed application...."
What i did do is go to the server to and search the entire directory structure for the log-configuration.xml but could not find it. Also, the config cannot be seen via the log-configurator in visual administration engine which its supposed too i think. and lastly the behavoiur i set in the log-configuration.xml is not reflected in the defaultTrace
Then i saw this post so i went to check the EAR file in my workspace and found that it was just like Manik described.
Maybe u could check this link where i posted more about my problem Log-Configuration.xml Problems
I would love to award points if it helps -
Web.xml + jsp deployment problem
Hi people,
I have an eclipse project that has 1 servlet and 1 jsp page. I'm having problem in deployment. The servlet works fine but jsp is not accessible. The structure of my web.xml file is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>IBNSubscriberServlet</display-name>
<servlet>
<description></description>
<display-name>SubscriberServlet</display-name>
<servlet-name>SubscriberServlet</servlet-name>
<servlet-class>com.ibn.servlets.SubscriberServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>SubscriberServlet</servlet-name>
<url-pattern>/SubscriberServlet</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>MonitoringG7</servlet-name>
<jsp-file>/com.ibn.view.MonitoringG7.jsp</jsp-file>
</servlet>
<servlet-mapping>
<servlet-name>MonitoringG7</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.html</welcome-file>
<welcome-file>default.htm</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
</web-app>On requesting this JSP url, http://localhost:8080/IBNSubscriberServlet/MonitoringG7.jsp the http 404 status message comes which says the resource is not found. Cn someone please check the above jsp mappings in the web.xml file?
Inside my "src", folder I have "com.ibn.view" which contains jsp file.
thanks.this is how my web.xml looks like now.
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>IBNSubscriberServlet</display-name>
<servlet>
<description></description>
<display-name>SubscriberServlet</display-name>
<servlet-name>SubscriberServlet</servlet-name>
<servlet-class>com.ibn.servlets.SubscriberServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>SubscriberServlet</servlet-name>
<url-pattern>/SubscriberServlet</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.html</welcome-file>
<welcome-file>default.htm</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
</web-app>If there is a mapping problem then the JSP should not work in tomcat as well, but it is. And i have just one servlet in the project and that is mapped my eclipse as above. -
JSP file not found. server.xml/web.xml problem?
Hi there,
I have a login.jsp that accepts username and password. Once login is approve, it calls main.jsp file as follows using <jsp:forwards>:
if (login != null){
out.println("Login Successful!");
session.setAttribute("sessionUsername", username);
session.setAttribute("sessionPassword", password);
out.println("session started!");%>
<jsp:forward page="main.jsp" />
Problem is that the server returns "file not found", when I'm sure the main.jsp is right there! I suspect there is some configuration problem with the Tomcat, but I donno what. Do I need to edit the server.xml or web.xml, coz I didn't?please check that the jsp file to which you are forwarding the request exist at the same location where forwarding jsp exists.
-
XML Validation..in JSP (Exception Problem)
Hello all,
Below is a .JSP program, which validates an .XML ("validate.xml") file residing in the same container as the JSP. It throws all the possible exception for all possible errors in an XML file(& prints them in a TextArea), but it terminates as soon as it catches the first one.
HOW CAN I MAKE IT CATCH ALL THE POSSIBLE EXCEPTIONS BEFORE TERMINATING??
Please suggest/help. Any help would be thoroughly appreciated. Thanks!
<%@ page session = "false" %>
<%@ page import = "java.io.*" %>
<%@ page import = "java.net.*" %>
<%@ page import = "java.text.*" %>
<%@ page import = "java.util.*" %>
<%@ page import = "javax.xml.parsers.*" %>
<%@ page import = "org.w3c.dom.*" %>
<%@ page import = "org.xml.sax.*" %>
<%@ page import = "org.xml.sax.helpers.*" %>
<%@ page import = "org.apache.xerces.parsers.DOMParser" %>
<%@ page import = "org.apache.xerces.parsers.SAXParser" %>
<HTML>
<HEAD>
</HEAD>
<%
try{
XMLReader parser = new org.apache.xerces.parsers.SAXParser();
DefaultHandler handler= new ProductParser();
parser.setContentHandler(handler);
parser.setErrorHandler(handler);
parser.setFeature ("http://xml.org/sax/features/validation", true);
StringBuffer requestURL = HttpUtils.getRequestURL(request);
URL jspURL = new URL(requestURL.toString());
URL url = new URL(jspURL, "validate.xml");
InputSource is = new InputSource(url.openStream());
parser.parse(is);
catch (SAXException e) {}
%>
<%!
String warn = "";
String err = "";
String fatal = "";
class ProductParser extends DefaultHandler
public void warning (SAXParseException e) throws SAXException // Warning Event Handler
warn = ("Warning: At Line Number " + e.getLineNumber() + " \nError Reason: " + e.getMessage() + "\n");
public void error (SAXParseException e) throws SAXException // Error Event Handler
err = ("Error: At Line Number " + e.getLineNumber() + " \nError Reason: " + e.getMessage() + "\n");
public void fatalError (SAXParseException e) throws SAXException // Fatal Error Event Handler
fatal = ("Fatal Error: At Line Number " + e.getLineNumber() + " \nError Reason: " + e.getMessage() + "\n");
%>
<Body>
The Errors in your XML file are as beloW: <br>
<%=(warn + err + fatal)%>
</Body>
</HTML>somebody please answer!
-
Hi !
i am creating a program using JSP Ajax to read PUBLIC enteries of Google calender but when i run to check the JSP file that is Server Side process & return result to HTML i got the following result:
375/-+1750/-Bunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/n21nl92hsg9mljbv0ntsrlrhp42006-11-14T10:12:59.000Z2006-11-14T10:13:22.000ZWhen: 2006-11-14 <br> <br>Event Status: confirmedWhen: 2006-11-14 <br> <br>Event Status: confirmedBunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/o7ttfhhs2fbsjl34m08026h2102006-11-14T10:11:31.000Z2006-11-14T10:12:05.000ZWhen: 2006-11-17 13:00 to 14:00 IST <br> <br>Event Status: confirmedWhen: 2006-11-17 13:00 to 14:00 IST <br> <br>Event Status: confirmedBunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/kir9gd7c9gkf6va0283oicbivc2006-10-04T14:00:37.000Z2006-10-04T14:00:37.000ZWhen: 2006-10-15 17:00 to 18:30 IST <br> <br>Event Status: confirmedWhen: 2006-10-15 17:00 to 18:30 IST <br> <br>Event Status: confirmedBunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/6d628dcmei9f3kd2c705i282o02006-09-28T09:08:26.000Z2006-10-04T13:59:43.000ZWhen: 2006-10-07 10:00 to 11:00 IST <br> <br>Event Status: confirmedWhen: 2006-10-07 10:00 to 11:00 IST <br> <br>Event Status: confirmedBunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/i4o0s31ia8cuau5gn3l6ecvd582006-09-19T11:04:10.000Z2006-09-25T10:16:06.000ZWhen: 2006-10-15 15:00 to 16:00 IST <br> <br>Where: Rajouri Garden <br>Event Status: confirmedWhen: 2006-10-15 15:00 to 16:00 IST <br> <br>Where: Rajouri Garden <br>Event Status: confirmedBunty [email protected]://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031eeb071629562bb65d8d446f5f2b59/basic/vfu1bbrickckleptoh46m3v09k2006-09-25T10:15:19.000Z2006-09-25T10:15:19.000ZRecurring Event<br> First start: 2006-09-27 IST <br> Duration: 86400 <br>Event Status: confirmedRecurring Event<br> First start: 2006-09-27 IST <br> Duration: 86400 <br>Event Status: confirmedBunty
But it should be a proper XML file.....
HTML Code:
function RSSRequest() {
// change the status to requesting data
HideShow('status');
document.getElementById("status").innerHTML = "Requesting data ...";
// Prepare the request
RSSRequestObject.open("GET", rssReader.jsp, true);
// Set the onreadystatechange function
RSSRequestObject.onreadystatechange = ReqChange;
// Send
RSSRequestObject.send(null);
<body onload="RSSRequest();">
<h2>Google Calendar Events - RSS Reader- BuntyIndia</h2>
<div id="status" style="display:none"></div>
<div id="ajaxreader"></div>JSP Code:
<%@ page import = "java.io.*, java.util.*,java.net.URL,java.net.*,java.awt.*" %>
<%
URL url = new URL(" http://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031e071629562bb68d446f5f2b59/basic");
URLConnection urlConnection = url.openConnection ( ) ;
StringBuffer stringbuffer = new StringBuffer("");
String news =new String();
try {
BufferedReader in = new BufferedReader ( new InputStreamReader (url.openStream())) ;
while((in.readLine())!= null)
//s2=in.readLine();
stringbuffer.append(in.readLine());
in.close();
catch(Exception e) {
System.out.println(e.getMessage());
news=stringbuffer.toString();
out.println(news);
//response.setContentType("text/xml");
//response.setHeader("Cache-Control", "no-cache");
//response.getWriter().write(in);
%>Please Help
Bunty Indiadisplaying blank page....
where to check LOG file what's the path?
i changed my code little bit placed response.setContentType at top know my page is displaying XML error
XML document must have a top level element. Error processing resource
<%@ page import = "java.io.*, java.util.*,java.net.URL,java.net.*,java.awt.*" %>
<%
response.setContentType("text/xml");
response.setHeader("Cache-Control", "no-cache");
response.setHeader("pragma","no-cache");
URL url = new URL("http://www.google.com/calendar/feeds/bunty.india%40gmail.com/public-031e071629562bb68d446f5f2b59/basic");
URLConnection urlConnection = url.openConnection ( ) ;
StringBuffer stringbuffer = new StringBuffer("");
String news =new String();
try {
BufferedReader in = new BufferedReader ( new InputStreamReader (url.openStream())) ;
while((in.readLine())!= null)
//s2=in.readLine();
stringbuffer.append(in.readLine());
in.close();
catch(Exception e) {
System.out.println(e.getMessage());
//news=stringbuffer.toString();
//out.println(news);
//log(news);
//System.out.println(news);
response.getWriter().write(news);
%>
Message was edited by:
bunty_india
Message was edited by:
bunty_india
Message was edited by:
bunty_india -
Jsp taglib problems in J2ee server of j2sdkee1.3
Fresh from solving the problems with usebean in jsp, I again got a problem with the custom tags of JSP
I am using Jdk1.3 and j2sdkee1.3, windows98
The class file is stored in a package called my in the c:\j2sdkee1.3\lib\classes\my folder
and the tld and jsp file stored in c:\j2sdkee1.3\public_html folder
when I access the atm.jsp page, I got this error message
A Servlet Exception Has Occurred
org.apache.jasper.compiler.ParseException: End of content reached while more parsing required: tag nesting error?
Here is the ATMJsp.tld code
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE taglib PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN" "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
<taglib>
<tlibversion>1.0</tlibversion>
<jspversion>1.1</jspversion>
<shortname>ATMJsp</shortname>
<info>a tag library for the atm details</info>
<tag>
<name>ATM</name>
<tagclass>my.atmtag</tagclass>
<bodycontent>JSP</bodycontent>
<info>Outputs of the ATM Counter</info>
</tag>
</taglib>
I try:
When I put the <bodycontent> tags below the <info> tags, I got the error message that the tag doesn't allow "bodycontent" here
I don't know what caused the problem ... is there some mistake in the above code?
Include other file to make it more clear---* atm.jsp and atmtag.java
atm.jsp
<%@ page import="my.atmtag" %>
<%@ taglib uri="ATMJsp.tld" prefix="atmjsp" %>
<%@ page errorPage="errorpage.jsp" %>
<!DocType HTML Public "-//W3C//DTD// HTML 4.0 Translational//EN">
<html>
<head></head>
<body>
<h3 align=center>ATM counters that need cash</h3>
<table><tr>
<td></td>
<td><atmjsp:ATM></td>
</tr>
</body>
</html>
atmtag.java
package my;
import javax.servlet.jsp.*;
import javax.servlet.jsp.tagext.*;
import java.io.*;
import java.sql.*;
import java.math.*;
import java.util.*;
//tag handler
public class atmtag extends TagSupport
Connection connect=null;
Statement state=null;
ResultSet result=null;
public atmtag() throws ClassNotFoundException
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
public int doStartTag() throws JspTagException
return EVAL_BODY_INCLUDE;
public int doEndTag() throws JspTagException
try
JspWriter out=pageContext.getOut();
connect=DriverManager.getConnection("jdbc:odbc:EarnestBank","","");
String strquery="select cCounter_id, cAddress, mCashBalance from Counter where mCashBalance<=10000";
state=connect.createStatement();
ResultSet result=state.executeQuery(strquery);
String sid=null;
String saddress=null;
String sbalance=null;
Vector v=new Vector();
while(result.next())
sid=result.getString(1);
saddress=result.getString(2);
sbalance=result.getString(3);
v.add(sid);
v.add(saddress);
v.add(sbalance);
for (int i=0; i<v.size();i++)
String str=(String)v.elementAt(i);
pageContext.getOut().write(str);
catch(Exception ex)
return EVAL_PAGE;
Pls help me to get through this hurdle
Thanks1) To handle <bodycontent> you should inherit from BodyTagSupport
class
2) You should use your bean like: <td><atmjsp:ATM/></td>
with closing slash - it's bodyless tag - this mistake
causes JSP compiler to report error
Enjoy!
Paul -
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
Maybe you are looking for
-
Report needed - Open materials on PO, sorted by material and not PO number
Hello, I've been trying to obtain a report that can give me a list of materials that are open for all PO numbers. Instead of this being sorted by PO number, I want it sorted by material number. I've gone through all the ME2 transactions (i.e. ME2L,
-
Hi , I have a created an textbox with date picker as (dd-mon-yyyy) . Now i want to create a validation on it for the format (dd-mon-yyyy) . I have created a pl/sql code with type "function returning error text". Begin If :P4_END_DATE IS NOT NULL THEN
-
Gatekeeper ruined my dashboard development completely. No security certificate for Dashboard Widgets. Here are some tips to fix this: “App can’t be opened because it is from an unidentified developer” Since OS X Mountain Lion, the Mac defaults to pre
-
Using a polymorphic view object with binding
Hi, I'm hoping there's something simple I'm missing when trying to setup up the bindings for a ADF/struts page using a polymorphic view object. I'm using Entity and VO polymorphism to create a Question which has different types - boolean, multi-choic
-
I am trying to save a html document as a template but am receiving an unbalanced body tag message. I appear to have both an opening <body> and closing </body> tag and no further body tags. Could you please help? The code is below: <!DOCTYPE HTML> <ht