JSP Execution Problem

We have implemented a servlet that uses a RequestDispatcher to forward to a JSP. The JSP instantiates an object (passing the Request and Response as parameters) that uses the RequestDispatcher once again to include another JSP.
This has been working fine in a Sun Solaris single-server environment using Apache as webserver and BroadVision as application server. After moving our application to a multi-server HP-UX environment with iPlanet as webserver and BroadVision as application server we have experienced a problem with our included JSPs. They are not executed but inserted as plain text. The first JSP that we use forward to execute still get executed.
The first time each JSP is included an ServletException is thrown: Failed to set include attributes.
I suspect that the problem has to do with the url mapping in web.xml. The web.xml file from the application server is included below.
Any help and information on how to solve this problem would be appreciated.
Thanks,
Magnus
<web-app>
<servlet-mapping>
<servlet-name>jspCompiler</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Main</servlet-name>
<url-pattern>/main</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>jspCompiler</servlet-name>
<servlet-class>org.apache.jasper.runtime.JspServlet
</servlet-class>
<init-param><param-name>scratchdir</param-name>
<param-value>myscratchdir</param-value>
</init-param>
</servlet>
<servlet>
<servlet-name>Main</servlet-name>
<servlet-class>
myclass
</servlet-class>
</servlet>
</web-app>

I don't know if you using Servlet2.3 but if you are, then try using correct order
<servlet
<servlet
<servlet-mapping
<servlet-mapping
Please consult the DTD

Similar Messages

  • How to terminate the jsp execution

    Hi, I've an problem to terminate the jsp execution.
    I've tried to use the following code: out.close();
    but the jsp (I use the servlet engine version 2.0) page continue the execution.
    How I can terminate this execution?
    Thanks

    Hello,
    i haven't this tried out yet, and i even do not have Time to test it,
    but if you use a Custom Jsp Tag, then you can set the return Type of
    the doEndTag() Method to SKIP_PAGE.
    This should stop the Evaluation of the Rest of Page.
    Good Luck !
    Best regards
    jherunter

  • 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]

  • Second Time, RFC execution Problem!

    Hi all,
    Has any one encountered this problem, when calling RFC First time fine and getting data from BAPI, when i call same RFC again, Second Time, RFC execution Problem!. Any idea!, Now i restarted server, that may cause the problem. Other than this, please give me your idea.
    Thanks
    Ravi Golla

    Hi Bhavik,
    <b>In View Controller:</b>
    public void onActionCreateProject(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
        //@@begin onActionCreateProject(ServerEvent)
        wdThis.wdGetArchCompController().CreateProject();
         wdThis.wdFirePlugOutToProjectCreationResult();
        //@@end
    <b>In Custom Controller:
    </b>
    wdDoInit()
    __Arch__Arm_Project_Create_Input create = new __Arch__Arm_Project_Create_Input();
         wdContext.node__Arch__Arm_Project_Create_Input().bind(create);
    public void CreateProject( )
        //@@begin CreateProject()
         try
                             wdContext.current__Arch__Arm_Project_Create_InputElement().modelObject().execute();
                             wdContext.nodeOutput().invalidate();
                        catch(WDDynamicRFCExecuteException ex)
                             wdThis.wdGetAPI().getComponent().getMessageManager().reportSuccess(ex.toString());
                             ex.printStackTrace();
        //@@end
    I am using other functional modules they all working fine, this is one only has problem
    Thanks  Bhavic.
    Regards
    Ravi

  • 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();
    %>

  • QA08 execution problem

    Hi all,
    QA08 execution problem, one material lying in QA32 stock that is cancel condition only (qa32 status for the material is LTCA, CALC) so I canu2019t deactivate the insp type through QA08, kindly help me to solve the problem.

    Hi,
    Thanks a lot your suggestion is 100% correct, problem has solved.
    Regards,
    Karthick.

  • Re: execution problem with oracle jsp under apache

    i followed the instruction to install oracle jsp running on apache 1.3.9 and apacheJServ/1.1b3 under win nt 4.0 with sp5. i created a servlet zone to hold the jsp file but for some reason it will not look the the dir specified in the jserv.conf. it look at the dir under apache document root dir.. therefore, i created a dir under the apache root dir and then it was able to compile the hellouser.jsp correctly. when i run lotto.jsp, the image files would not display. why?

    Apache Servlet zones allow you separate servlet (sets) into distinct classloaders. The OJSP servlet needs to exist in a servlet zone. However the content the OJSP servlet operates on (the .jsp file) lives in the document root directory just like your other web content. OJSP does support a configuration/init parameter whereby you can explicitly specify a physical directory other than what is mapped via the Apache settings. Please consult the documentation if you want to do this.
    As for why the lottery images aren't being displayed, more information is needed. The generated page should create local references to the images files. Are the images in where they are expected to be? Can you be more explicit about the URI you send and the physical structure of the Lottery sample in the file system?

  • Redirect jsp page problem

              I have problem when I want to redirect a page, inputparam2test.jsp back to the perious
              page, inputparam1test.jsp. Everything works until I
              add a "if" statement in the inputparam1test.jsp.
              The error is "Error 500--Internal Server Error".
              Can anybody help me out? Thanks a lot!
              inputparam1test.jsp:
              <html>
              <head>
              <title>create a patameter input form</title>
              </head>
              <body>
              <%!
              String dataset;
              String modeltype;
              %>
              <%
              dataset = request.getParameter("dataset");
              modeltype = request.getParameter("modeltype");
              %>     
              <center>
              <form action="inputparam2test.jsp" method="post">
              <table cellspacing=10>
              <tr>
              <td colspan=2>
                        Please enter model parameters
                   </td>
                   </tr>     
              <tr>
                   <td>
                        Dell LRI
                   </td>
                   <td>     
                        <select name="DellLRI">
                        <option value="1">1
                        <option value="0">0
                        </select>
                   </td>
                   </tr>
                   <%
                   if(modeltype.equals("Direct")) {
              out.println("in if");
              %>
                   <tr>
                   <td>
                   </td>
                   <td>     
                        <input type="submit" value="Next>" name="Next>">
                   </td>
                   </tr>
              </form>
              </center>
              </body>
              </html>
              inputparam2test.jsp:
              <html>
              <head>
              <title>continue input parameters </title>
              </head>
              <body>
              <%
              response.sendRedirect("inputparam1test.jsp");
              %>
              </body>
              </html>
              

    You do not check if the modelType is null and
              if(modeltype.equals("Direct")) {
              out.println("in if");
              will result in a NullPointerException when it is null.
              Almond Huang <[email protected]> wrote:
              > I have problem when I want to redirect a page, inputparam2test.jsp back to the perious
              > page, inputparam1test.jsp. Everything works until I
              > add a "if" statement in the inputparam1test.jsp.
              > The error is "Error 500--Internal Server Error".
              > Can anybody help me out? Thanks a lot!
              > inputparam1test.jsp:
              > <html>
              > <head>
              > <title>create a patameter input form</title>
              > </head>
              > <body>
              > <%!
              > String dataset;
              > String modeltype;
              > %>
              > <%
              > dataset = request.getParameter("dataset");
              > modeltype = request.getParameter("modeltype");
              > %>     
              > <center>
              > <form action="inputparam2test.jsp" method="post">
              > <table cellspacing=10>
              > <tr>
              > <td colspan=2>
              >           Please enter model parameters
              >      </td>
              >      </tr>     
              > <tr>
              >      <td>
              >           Dell LRI
              >      </td>
              >      <td>     
              >           <select name="DellLRI">
              >           <option value="1">1
              >           <option value="0">0
              >           </select>
              >      </td>
              >      </tr>
              >      <%
              >      if(modeltype.equals("Direct")) {
              > out.println("in if");
              >      }
              > %>
              >      <tr>
              >      <td>
              >      </td>
              >      <td>     
              >           <input type="submit" value="Next>" name="Next>">
              >      </td>
              >      </tr>
              > </form>
              > </center>
              > </body>
              > </html>
              > inputparam2test.jsp:
              > <html>
              > <head>
              > <title>continue input parameters </title>
              > </head>
              > <body>
              > <%
              > response.sendRedirect("inputparam1test.jsp");
              > %>
              > </body>
              > </html>
              Dimitri
              

  • JSP include problem

    I am facing problems with the JSP include functionality in my project.
    What I want to do is to include jsp files on the fly i.e depending on the business need I should be able to swap in and out jsps from the main jsp.
    I plan to do this by feeding the file names in a request attribute and then including the files in the order given.
    But on using the jsp:include there is no output generated by the included jsp.
    There is no error either in the log or in the page directly.
    Please help me in finding out what exactly is the issue here.
    the files are index.jsp --> rightRailIncludeFiles.jsp --> dynamically loaded jsps (These may themselves contain other included files)
    index.jsp
    <div id="right" class="testRight">
        <%@ include file="rightRailIncludeFiles.jsp" %>
    </div>
    rightRailIncludeFiles.jsp
    <%
        out.println("<h1>Dyna Include</h1>");
        String fileNames = (String)request.getAttribute("jspFiles");
        String[] fileList = fileNames.split(",");
        out.println("<!-- Files : " + fileNames + " -->");
    %>
    <%
    for(int i=0;i<fileList.length;i++) {
        try {
             out.print("<!-- "+fileList[i]+" -->");
    %>
        <jsp:include page="<%=fileList%>" flush="true"/>
    <%
    } catch(javax.servlet.ServletException e) {
    out.println("<h3 style=\"color:red\"> Error :"+e.getMessage()+"</h3>");
    %>
    *inlude_1.jsp (This file includes another file which has some common code)*<jsp:include page="include/inlude_1.jsp" flush="true">
    <jsp:param name="magicNumberText" value="${request.adMagicNumberText}" />
    <jsp:param name="setType" value="${request.adSetType}" />
    <jsp:param name="width" value="${request.adWidth}" />
    <jsp:param name="height" value="${request.adHeight}" />
    <jsp:param name="adOuterDivClass" value="${request.adOuterDivClass}" />
    </jsp:include>
    Edited by: danbrown on Feb 9, 2009 2:49 AM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    Good morning,
    I am not sure that could be the real problem , but I guess your app server does not like the fact that you broke the try catch in two parts. In any case, you should not do that :) Mixing code and display is very painful for maintenance :)
    Have you tried to remove the jsp:include and see if the output is correctly produced?
    Best Regards
    Edmondo

  • 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
    Thanks

    1) 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

  • Package execution problem with SQLSERVERAGENT

    Hello,
    I'm having a problem with the execution of SSIS packages: I created locally a package with SQL Server Data Tools, then I deployed it on my server in the SSISDB database. Then I created a job to execute periodically this package with SQL Server Agent. The
    package works fine and does everything I want, but I always get a failed notification. In the global view of the execution I can see:
    Result: "failed"
    Package name: "Package.dtsx"
    Task name: "Package"
    Execution access path: "\Package"
    Every other task returns a success and their execution access path is a subfolder of "\Package". I tried everything I found on the web, check the "Runtime 32bits" box, create a "Job Account" user to execute the package via a
    "Job Account Proxy", modify the ProtectionLevel of the package to "DontSaveSensitive", give the "Job Account" user full rights on everything, nothing works.
    Do you have an idea of what my problem is and how to solve it?
    I must precise that all my packages do the same thing: I have a loop on all the csv files in a folder that for each file loads the contents of the file in my database and the delete the file. I observed that the error message do not appear when there is
    no file in the folder when the package executes.
    Thanks in advance.

    Not sure what error message, is the one "est introuvable.
    Cette erreur est retournée par la collection Connections lorsque l'élément de connexion spécifique est introuvable"?
    So, here is in short: the ForEach Loop once in its beginning of operation "senses" the files currently present in the working folder. If a new file arrives after this stage, it will not see it.
    In your case it seems that the ForEach "saw" a file at the beginning, but it was gone at the time the processing wanted it for execution.
    Like many above indicated, the common practice, call
    it elegant or not is to indeed move the files to a different directory (working folder). This is done to avoid collisions with some other activity in that folder.
    Furthermore, you can have all the files deleted using a ForEach against the working folder as say in
    http://beyondrelational.com/modules/2/blogs/88/posts/10178/ssis-delete-files-from-specified-folder-using-file-system-task-in-sql-server.aspx And there is no need to delete the working folder
    itself.
    The job is run in SQL Server's Agent
    need to be set to run using a domain proxy account as it needs write access to the file system.
    Arthur My Blog

  • 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 Tomten

    Hi
    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 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.
    -Nilesh

    Show me the code

  • Command line program execution problem.

    Hey there, I'm about to complete my Java thesis project, but I can't fix a problem: i have to find a command line programme (which is in python but i think its not a big deal) through a java programme. Getting some information around I ended up i could execute the program with the command:
    Process proc = Runtime.getRuntime().exec("...");
    and create the streams:
    OutputStream out = proc.getOutputS 14.49
    InputStream in = proc.getInputStream();
    the problem is that calling a programme which prints on screen something and then it ends (ex. ipconfig) the following sequence works out:
    do
    int i=in.read();
    if(i==-1) break;
    System.out.print((char)i);
    }while(true);
    instead in the specific case of the programme that i need to execute it canno't work because this programme after its opening prints a couple of lines, at this stage you need to type the input in and when the eof font is sent the output is printed. i've tried to send the input thru OutputStream but the execution gets stuck when it reads the output (in.read());
    Can you guys help me out? What do i need to do? Please it's very important, let me know ASAP.
    Thanks very much,
    Fabio

    I would not recommend the use of raw "InputStream" for much of anything.
    Try Scanner if you can use JDK5, if not, try BufferedReader.
    Scanner:
    Process proc = Runtime.getRuntime().exec("...");
    BufferedOutputStream out = new BufferedOutputStream(proc.getOutputStream());
    Scanner in = new Scanner(proc.getInputStream());
    while(in.hasNextLine()) {
         String s = in.nextLine();
         System.out.println(s);
    }BufferedReader:
    Process proc = Runtime.getRuntime().exec("...");
    BufferedOutputStream out = new BufferedOutputStream(proc.getOutputStream());
    BufferedReader in = new BufferedReader(new InputStreamReader(proc.getInputStream()));
    String l = " ";
    while(l != null) {
         l = r.nextLine();
         System.out.println(s);
    }

Maybe you are looking for

  • No data for a week now, why?

    I just came to Verizon a week ago. I got the Droid Razr for my wife and i had to order the Razr Maxx for me. Well i took some time to get my phone but once i did i had it one day and the next we had no data service. Both our phones have no data and s

  • Network Setup app for Nokia Lumia phones

    Network Setup 2.4.0.0 is available in the Microsoft Marketplace for Lumia 610, Lumia 800, Lumia 710, and Lumia 900 in all countries except USA, Canada, Columbia, India and Iceland.  The app is also not currently available for the Lumia models sold in

  • Connecting 6280 to PC Suite - having trouble - hel...

    Can anyone help me with connecting my 6280 to my PC? My PC is recognising the connection but PC Suite isn't. I am stumped and have read the Nokia Troubleshooting pages, but to no avail. My iPod has packed it in and I really want to transfer some musi

  • Adding Partner into Purchase Order (ME21N, ME22N)

    Hi, I want to add a parnter into purchase order. Logic of determining of partner is very complex and I have to write a program for this purpose. Are there any user exit where I can include this program and add additional line into EKPA? Thanks in adv

  • What are the New features in OBPM in performance, integration & dev level

    Hi, Could someone help me I would like to know what are the new features in Oracle BPM that will improve the performance of appln, and new features in integration and development level.Thanks in advance.