JSP is being recompiled - WL 6.0

          One of our JSPs is always being recompiled, every time a user logs in. This happens
          to be the JSP that handles the login logic. We have even removed the generated
          java file but it still gets re-created, although no change has been made to the
          JSP.
          No other JSP is being re-compiled so this is really odd!
          We have not yet installed SP1.
          Any help is appreciated.
          Thanks.

I also have this problem.
          -chris
          "JimmyL" <[email protected]> wrote in message
          news:[email protected]...
          >
          > By the way, how do you deploy an application elsewhere than under the
          "applications"
          > directory ? I didn't succeed...
          >
          > Kumar Allamraju <[email protected]> wrote:
          > >is your jsp (webpp) deployed under applications directory or outside
          > >of apps dir?
          > >
          > >If it's under apps dir, the behaviour is correct. WLS extracts the
          deployed
          > >webapps to
          > >a w.wl_temp_do_not_delete
          > >directory and this directory gets cleaned up everytime you boot the
          server.
          > >Deploying
          > >applications under apps is
          > >for development purposes only.
          > >
          > >--
          > >Kumar
          > >
          > >
          > >Herbert wrote:
          > >
          > >> One of our JSPs is always being recompiled, every time a user logs
          > >in. This happens
          > >> to be the JSP that handles the login logic. We have even removed the
          > >generated
          > >> java file but it still gets re-created, although no change has been
          > >made to the
          > >> JSP.
          > >> No other JSP is being re-compiled so this is really odd!
          > >> We have not yet installed SP1.
          > >>
          > >> Any help is appreciated.
          > >>
          > >> Thanks.
          > >
          >

Similar Messages

Pre-compiled JSPs not being recognized (WLS 8.1 SP2)

          We're running into a strange problem here, where our pre-compiled JSPs (precompiled
          via an ant target) are being recognized as "stale" and recompiled by Weblogic,
          as the following log message indicates. The strange thing is, on one hand it says
          they were precompiled by a "different" version of Weblogic server, and then right
          after that, immediately contradicts itself by logging the SAME version for the
          JSP and WLS builds:
          ####<Jan 31, 2004 11:24:40 AM PST> <Info> <HTTP> <ladybug> <fwmharris-ms01> <ExecuteThread:
          '11' for
          queue: 'default'> <dhecking> <> <BEA-101295> <Recompiling JSP
          [ServletContext(id=20425572,name=fwmhis-www,context-path=)], resource
          [tiles/table/td_twisty_group_tile.jsp], because it is stale. It was previously
          compiled using a
          different version of WebLogic Server.
          JSP build version: 8.1.2.0
          WLS build version: 8.1.2.0.>
          As can be seen, the two build versions are identical (8.1.2.0) which is the correct
          version (Weblogic 8.1 SP2). Has anyone else run into this problem? If so, is there
          a fix?
          The platform is Solaris btw.
          Thank you.
          ..Hrishi
          Hrishi Dixit
          Finaplex
          [email protected]


Kostas Symeonidis wrote:
          > I have exactly the same problem with 8.1sp2 on Win2000 and I will test it tomorrow on Solaris.
          >
          > It seems that the code checks two things:
          > 1. the version of the JSPC
          > 2. the timestamp of the files
          > In both cases the logged message is the same(!!!) "recompiling because is stale..." but you can see that clearly the version numbers are the same, therefore the stale check failed on step 2.
          >
          > Now my guess is that step 2, either doesn't find the page, or the time check is done erratically. Mind you, in 8.1sp2 BEA changed the isResourceStale method signature and added an extra String parameter for the TimeZone, see code in generated JSPs below:
          > public boolean _isStale() {
          > weblogic.servlet.jsp.StaleChecker sci =(weblogic.servlet.jsp.StaleChecker)(getServletConfig().getServletContext());
          > java.io.File f = null;
          > long lastModWhenBuilt = 0L;
          > if (sci.isResourceStale("/index.jsp", 1082047780159L, "8.1.2.0", "Europe/London")) return true;
          > return false;
          > }
          >
          > I'm also quite sure that we should be waiting for a rolling patch quite soon.
          Your guess is correct. Unfortunately a the message logged is wrong. A
          patch for CR133453 fixes that. Basically its failing (2) and logging the
          same message as (1).

Pre-compiled JSPs with main_mode = recompile

I would like to precompile JSPs and allow changes to be recompiled after an application has been deployed. In other words, I want to use ojspc to precompile my JSPs and set main_mode to recompile in web.xml. In such a scenario, I would like changes to JSPs in the web folder to be reflected. Otherwise, it should just take the precompiled JSP. Does anyone know if that is possible?
I have tried it out and this is what I have found. If I set main_mode to recompile in the web.xml and include the jar of precompiled JSPs in the WEB-INF/lib folder then it never recompiles any changes to JSPs in the web application. Is that the way it is supposed to behave or should it be recompiling the changed JSP?

          Yes it is possible to do this; you can package up the classes and WebLogic will
          attempt to load them - if the class load works, no recompile is needed.
          But there's a bug in weblogic.servlet.jsp.Precompiler.java - it's looking for
          a classname with a single leading underscore (e.g. myjsp.class), but ejbc outputs
          classes with a double leading underscore (e.g. __my_jsp.class).
          I've done a patch for Precompiler.java, and now it all works as it ought to.
          simon.

Problem with jsp:element being ignored by my jspx

Hello,
!Please note that this is a JSP problem even though it is located in a jsf page!
I have the following code:
<jsp:element xmlns:jsp="http://java.sun.com/JSP/Page" name="link">
<jsp:attribute name="href">${pageContext.request.contextPath}/css/xp/xp.css</jsp:attribute>
<jsp:attribute name="rel">stylesheet</jsp:attribute>
<jsp:attribute name="type">text/css</jsp:attribute>
</jsp:element>which is not being evaluated. I just get nothing in lieu of the above code fragment.
Here is part of my web.xml:
<jsp-config>
        <jsp-property-group>
            <display-name>Expression Language</display-name>
            <url-pattern>*.jspx</url-pattern>
            <el-ignored>false</el-ignored>
            <scripting-invalid>false</scripting-invalid>
            <is-xml>true</is-xml>
        </jsp-property-group>
    </jsp-config>Here is the entirety of my jspx:
<f:view xmlns:h="http://java.sun.com/jsf/html"
        xmlns:f="http://java.sun.com/jsf/core"
        xmlns:jsp="http://java.sun.com/JSP/Page"
        xmlns:ice="http://www.icesoft.com/icefaces/component">
     <jsp:directive.page isELIgnored="false"/>
    <ice:outputDeclaration
        doctypeRoot="HTML"
        doctypePublic="-//W3C//DTD XHTML 1.0 Strict//EN"
        doctypeSystem="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"/>
    <html
     xmlns:jsp="http://java.sun.com/JSP/Page">
        <head>
            <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
            <title>JSP Page{9+1} - 05</title>
            <jsp:element xmlns:jsp="http://java.sun.com/JSP/Page" name="link">
                <jsp:attribute name="href">${pageContext.request.contextPath}/css/xp/xp.css</jsp:attribute>
                <jsp:attribute name="rel">stylesheet</jsp:attribute>
                <jsp:attribute name="type">text/css</jsp:attribute>
            </jsp:element>
            
        </head>
        <body>
            <ice:outputConnectionStatus/>
            <ice:form>
                <ice:inputFile
                    progressListener="#{consoleInputFile.progress}"
                    actionListener="#{consoleInputFile.action}"/>
                <ice:outputProgress
                    indeterminate="true"
                    value="#{consoleInputFile.percent}" />
                <ice:messages
                    showDetail="true"
                    styleClass="consoleInputFileMessages"/>
            </ice:form>
        </body>
    </html>
</f:view>Can anyone help please,
Julien.

That's a convoluted way to write out an image input field... Also, are you aware that by defining the variables in the <%! %> block you are making them class fields, and thus likely to be altered by any request at any time? In that case, it probably doesn't matter...
anImage= "<INPUT TYPE=\"IMAGE\" NAME=\"WEB\" VALUE=\"GO\" SRC=\"" + imageDir + "go.gif\" WIDTH=\"26\" HEIGHT=\"24\" ALIGN=\"TOP\" BORDER=\"0\" ALT=\"GO\">";
Anyway, I see nothing wrong with that. But I'd check the quotes and whatever in your code, cuz as I said, it's quite hard to see that the quotes are correct and all.

JSP/JSF Not Recompiling

Current Setup:
JSF RI 1.0
Tomcat 5.5.09
JSP 2.4
Whenever I make a change to one of my jsp pages, and I hit refresh on my browser, the changes are not reflected. I have to go into the Tomcat manager application and restart the application.
The weird thing is, I think the servlet recognizes the changes (when I make changes and hit reload, it takes some time to redisplay the page). However, the changes that I made are not reflected.
I've looked around the web and have seen various posts - all of which have not helped me. I've checked server.xml and made sure that the developer init param is set to true (as well as in my web app's web.xml file)
Does anyone have any thoughts on this? Much thanks in advance

Sometime happens to me. You can "make" simple wrong syntax error in JSF page, any place in your code, like
<f:view ererere>
then page will recompile with error, then change back. JSF page will be recompiled. It works always for me. :-)

Jsps are not recompiled automatically

I use WebLogic 5.1, and have this in my properties-file:
          weblogic.httpd.register.*.jsp=\
          weblogic.servlet.JSPServlet
          weblogic.httpd.initArgs.*.jsp=\
          pageCheckSeconds=0,\
          compileCommand=d:/jdk1.3/bin/javac.exe,\
          workingDir=d:/weblogic/myserver/classfiles,\
          verbose=true
          Still my jsp-files don't recompile automatically. In fact, sometimes they do, sometimes they don't. How come? What can I do to make sure WebLogic compiles the new jsps?
          Please email any answers.
          Regards, Hågen
          [att1.html]


That configuration should recompile them whenever they are modified.
          It will NOT reload them if d:/weblogic/myserver/classfiles is also in your WEBLOGIC_CLASSPATH.
          Mike
          Hågen Hasle <[email protected]> wrote in message news:3ab10b0b$[email protected]..
          I use WebLogic 5.1, and have this in my properties-file:
          weblogic.httpd.register.*.jsp=\
          weblogic.servlet.JSPServlet
          weblogic.httpd.initArgs.*.jsp=\
          pageCheckSeconds=0,\
          compileCommand=d:/jdk1.3/bin/javac.exe,\
          workingDir=d:/weblogic/myserver/classfiles,\
          verbose=true
          Still my jsp-files don't recompile automatically. In fact, sometimes they do, sometimes they don't. How come? What can I do to make sure WebLogic compiles the new jsps?
          Please email any answers.
          Regards, Hågen
          [att1.html]

JSP locked after recompile

Just moved to 6.1sp3 from 6.0sp2 on win2k, and I have discovered that, after
          modifying a jsp and recompiling it, I get an exception from the system when
          trying to modify the JSP again. This is true inside Dreamweaver, but also
          when trying to delete the file in the directory, so it seems as if Weblogic
          has locked the file. Looking through the newsgroups suggests others have had
          this trouble, but with no solutions. This is a showstopper for me, as
          iterative development of JSP code is fundamental to the workflow of building
          a site.
          We are using 6.0sp2 on production, but were looking to move our license to
          6.1 or 7.0.
          Michael Greer
          [email protected]


Please follow steps below.
file to modify :/etc/default/login
parameter to set : RETRIES (here 3)
file to modify : /etc/security/policy.conf
parameter to set : LOCK_AFTER_RETRIES (to yes)
command to run : usermod -K lock_after_retries=yes <user>
I hope this will solve your problem

Can we precompile JSPs to avoid Weblogic Recompile JSPs

We'll prevent Weblogic 10.3 to Recompile JSPs when deployment and running. So we precompile JSPs when build by weblogic.jspc and added staments below in weblogic.xml, but we failed, weblogic will recompile JSPs as before. Anybody can help me?
<jsp-param>
<param-name>precompile</param-name>
<param-value>false</param-value>
</jsp-param>
<jsp-param>
<param-name>pageCheckSeconds</param-name>
<param-value>-1</param-value>
</jsp-param>
Comman in ANT build file is below:
<java classname="weblogic.jspc" fork="yes" classpath="${esc2.classpath}">
               <arg line="-webapp ${esc.buildwardir} -compileAll -compiler javac -d ${esc.buildwardir.classes} -k"/>
               <arg line="-J-mx256m"/>
          </java>

Hi,
If the classes are still being recompiled then you are running different WLS versions - make sure you are compiling your classes using the same release & version as the one to which you are deploying
You can have a look at the below URL for further information
http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/jsp/reference.html

JSPs always recompiling even with pageCheckSeconds -1

I have sent the jsp-descriptor pageCheckSeconds to -1
          indicating that I don't want my jsps to ever be recompiled
          (I include the generated class files in the war and so they
          should never need recompilation). I see from the weblogic.log
          that this setting has taken effect, however, the jsps are still
          being recompiled when referenced.
          Somehow the installed petstore.ear file manages to avoid
          recompilation, but I can't seem to make this work for my ear files;
          the jsps are always recompiled.
          Is there something special done in the distributed petstore.ear?
          If I take the petstore.war and replace any one of its class files
          with a newly recompiled one and put this back in the original
          petstore.ear, then restarting the server and referencing
          the page will again recompile the page. Is there any way
          to avoid this recompilation? Is the isStale method not working correctly?
          Does setting pageCheckSeconds -1 not work?
          M. Borkan
          [email protected]


Hi again. That is a good idea. Check if router can grab an ip from your modem since wireless local connection through the router is working. If it can grab an ip and works fine on wireless, then you might have a problem with the ethernet ports. You might want to try assigning an ip address on the wired connection and see if ip of router is pingable. If really not working at all, possibility that router is not working properly anymore.

BUG: OC4J recompiled JSPs can not be debugged in JDev 10.1.3.2

We are having problems on JSP which are modified while running on OC4J within JDev 10.1.3.2. The modified JSP are not correctly recompiled.
A similar thread discussing this problem is here:
Oracle JDeveloper 10.1.3.1's Internal OC4J JSP Recompile
We consider this to be a problem that may be related more to OC4J than to JDev and therefore I am asking for suggestions in this forum.
To explain what we observe:
In JDev 10.1.3.1 we found that big/complex JSP would not recompile after changes were made while OC4J was running. The compiled JSP files under \.jsps\_web_2d_inf\... changed from myfile.class and myfile.java to myfile.class, myfile.java and (a new file) myfile.jpa.
After installing JDev 10.1.3.2 we now observe that for any JSP that gets changed (also the small/simple ones) the constellation of three files (with the additional .jpa) gets created. Small files are compiled and can be used after changed in real time but code insight and variable inspection and modification needed for debugging no longer work. (Note that they worked on the unchanged file, and would work again if we stop and recompile the whole project).
I could certainly appreciate if someone has found a solution to this problem as migrating back to a JDev version previous to 10.1.3.1 is not wanted.
Thanks in advance!
Gonzalo

I have openned a SR with this issue.
Does nobody else has this problem?
To reproduce it try:
Run any application in JDeveloper which contains a JSP file where a scriptlet declares
and use some variables.
Run the application and set a breakpoint after some of the variables. Call the JSP from the browser to start its execution and after stopping at the breakpoint inspect the variables content. It works, you can see the variable contents.
Now make a change in the JSP (anything) and call it again from the browser without restarting OC4J.
After stopping at the breakpoint you will see that the variables can no longer be inspected, their content is no longer available.
Thanks for any suggestions,
Gonzalo

Jsp code not being executed in browser

Even though my applications deploy and redeploy, I can see .html files but not .jsp files. The server presents the path, i.e. http://localhost:7001/ITDC/index.jsp, but the jsp code is either not being compiled and exceuted in a client browser or the .jsp is being compiled but not executed in the client broswer.


          Akilah <[email protected]> wrote:
          >Even though my applications deploy and redeploy, I can see .html files
          >but not .jsp files. The server presents the path, i.e. http://localhost:7001/ITDC/index.jsp,
          >but the jsp code is either not being compiled and exceuted in a client
          >browser or the .jsp is being compiled but not executed in the client
          >broswer.
          How about you tell us exactly what happens, and what you expected to happen. I
          can't tell if you're getting error messages, or whether you just don't see what
          you expect on the screen.
          Note that JSP code is not ever executed in the browser. It's only ever executed
          in the appserver, and the generated output is viewed in the browser.

BEA-101360 Recompiling JSP because it is stale

We are trying to precompile the jsps, but whenever we deploy, the pages are recompiled when first accessed.
We use weblogic.appc on war file, and all the class files are generated under WEB-INF/classes.
I also set page-check-seconds to -1 in weblogic.xml.
But when the pages are first accessed, the jsp's are recompiled.
<Info> <HTTP> <BEA-101360> <Recompiling JSP [ServletContext@8514003[app:ultranet module:my.war path:/portal spec-version:2.5]], resource [html/view.jsp], because it is stale.>
We are using weblogic 10.3.1.0 on Solaris 10.
The server is in development mode...does production mode make a difference?

Hi,
In Development mode of Server the JSP Page Check Second default value is 1-Second. Please set it to "-1". below entry need to be added in *"WEB-INF/weblogic.xml"* file
<font color=maroon><b>
<jsp-descriptor>
<precompile>true</precompile>
<page-check-seconds>-1</page-check-seconds>
<jsp-descriptor>
</b></font>
Better try to deploy your Applications After compiling it using APPC Compiler as mentioned in the following Link: http://jaysensharma.wordpress.com/2010/02/08/weblogic-specific-appc-ant-task/
Thanks
Jay SenSharma

JSPs are always being regenerated

I have just migrated my application from
          WL 5.1 to 7.0.2. I am using exploded format
          and the application is the "DefaultWebApp"
          I have set the pageCheckSeconds in the
          weblogic.xml to be -1. However the JSP is
          always recompiled. I set it to a positive
          number too and it is always recompiled (after the server restart).
          Any ideas?
          Thanks!
          -Lori


          Well I tried putting them under the <app home>/Web-inf/classes
          directory and it still regenerates them. I am using exploded
          format right now and would like it to work with this.
          Any other ideas before I contact support?
          Thanks!
          -Lori
          "Xiang Rao" <[email protected]> wrote:
          >
          >From my personal experience with WL7.0, I believe you also set JSP precompile
          >flag.
          >My experience with this flag is not good either. Every time I started
          >the server
          >or redploy my WAR files, I found WL7 will do what you have experienced
          >and it
          >is very painful for me to deploy web applications with hundreds of JSP
          >in the
          >cluster environment, and I have to disable such flag.
          >
          >From the petstore example, I found that all JSPs are precompiled to /WEB-INF/classes/jsp_servlet
          >directory. (Surprisingly, in its weblogic.xml, there is no single JSP
          >related
          >flag.) Perhaps that is the way.
          >
          >Weblogic document site does not provide step by step details to deploy
          >JSP in
          >precompiled form. The only thing I can find is that it suggestes to precompile
          >JSPs to /WEB-INF/classes in a WAR file.
          >
          >From Weblogic doc:
          >You can configure WebLogic Server to precompile your JSPs when a Web
          >Application
          >is deployed or re-deployed or when WebLogic Server starts up by setting
          >the precompile
          >parameter to true in the <jsp-descriptor> element of the weblogic.xml
          >deployment
          >descriptor. To avoid recompiling your JSPs each time the server restarts
          >and when
          >you target additional servers, precompile them using weblogic.jspc and
          >place them
          >in the WEB-INF/classes folder and archive them in a .war file.
          >
          >
          >
          >"Lori Ronning" <[email protected]> wrote:
          >>
          >>I have that set. And it is set to the directory to where
          >>they were already pre-compiled. So everytime they are generated
          >>they overwrite the pre-compiled ones.
          >>
          >>"Xiang Rao" <[email protected]> wrote:
          >>>
          >>>I think you need set working directory for your JSP.
          >>>
          >>>
          >>>Lori Ronning <[email protected]> wrote:
          >>>>I have just migrated my application from
          >>>>WL 5.1 to 7.0.2. I am using exploded format
          >>>>and the application is the "DefaultWebApp"
          >>>>I have set the pageCheckSeconds in the
          >>>>weblogic.xml to be -1. However the JSP is
          >>>>always recompiled. I set it to a positive
          >>>>number too and it is always recompiled (after the server restart).
          >>
          >>>
          >>>>Any ideas?
          >>>>Thanks!
          >>>>-Lori
          >>>
          >>
          >

Filename case issue in precompilation of JSPs for Windows

Hello,
          I have determined why my JSP pages have been recompiling
          despite including the corresponding compiled class files in
          my application package.
          It seems as though on Windows, any jsp files that have
          filenames that have upper
          case letters are being recompiled, even if their precompiled pages
          are included in the .war file. JSP files that have filenames that are all
          lower case
          are not recompiled, which is expected behavior.
          The UNIX version of BEA does not seem to have this bug
          related to the case of JSP filenames.
          Could someone from BEA please give us more information
          on this issue and when we can see it fixed?
          Thank you very much,
          Peter Kim
          p.s. I am using Weblogic Server version 7.0.1.0.


I'm seeing something slightly different here.
          I'm including __MyJsp.class (with the proper case) in my
          packaged .war file, but when a request is made for MyJsp.jsp,
          BEA looks for __myjsp.class instead of __MyJsp.class--
          therefore it recompiles MyJsp.jsp.
          -peter
          "Simon Spruzen" <[email protected]> wrote in message
          news:[email protected]...
          >
          > You get the same behaviour on 6.1 SP2 as well. MyJsp.jsp gets turned into
          __myjsp.class
          > (all lower case), but WebLogic looks for __MyJsp.class. This works just
          fine on
          > NTFS which is case-preserving/case-insensitive, but is hosed on Unix.
          Hence the
          > recompile.
          >
          > But the generated class file refers to the correctly cased Jsp page in its
          _isStale()
          > method. Sigh.
          >
          >
          > simon.
          >
          >
          > "Peter Kim" <[email protected]> wrote:
          > >Hello,
          > >
          > >I have determined why my JSP pages have been recompiling
          > >despite including the corresponding compiled class files in
          > >my application package.
          > >
          > >It seems as though on Windows, any jsp files that have
          > >filenames that have upper
          > >case letters are being recompiled, even if their precompiled pages
          > >are included in the .war file. JSP files that have filenames that are
          > >all
          > >lower case
          > >are not recompiled, which is expected behavior.
          > >
          > >The UNIX version of BEA does not seem to have this bug
          > >related to the case of JSP filenames.
          > >
          > >Could someone from BEA please give us more information
          > >on this issue and when we can see it fixed?
          > >
          > >Thank you very much,
          > >
          > >Peter Kim
          > >
          > >p.s. I am using Weblogic Server version 7.0.1.0.
          > >
          > >
          >

JSP output does not change on Weblogic 5.1 / Visual Age 3.5

I'm making developmen on Weblogic 5.1 and Visual Age 3.5.
          I change a JSP and when I reload it in my browser, I can see that the
          page is actually being recompiled, and if there are errors in the
          page, error messages are being displayed.
          However, if the page compiles without the error, it displays the
          output of the previous version of the page. No matter what I do, the
          page does not reflect the changes. The only solution is restarting
          the server.
          What might be the cause of this problem?
          Thanks,
          Sadik


I'm making developmen on Weblogic 5.1 and Visual Age 3.5.
          I change a JSP and when I reload it in my browser, I can see that the
          page is actually being recompiled, and if there are errors in the
          page, error messages are being displayed.
          However, if the page compiles without the error, it displays the
          output of the previous version of the page. No matter what I do, the
          page does not reflect the changes. The only solution is restarting
          the server.
          What might be the cause of this problem?
          Thanks,
          Sadik

JSP is being recompiled - WL 6.0

Similar Messages

Maybe you are looking for