Problem with JSP Tag class

[Jacek Laskowski]

Hi,

After some time of work, WLS ends up with the following error message:

weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
'cm': There is no setter method for property 'limit', for Tag
class 'com.hp.module.cm.tag.GetDocumentsTag'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at
weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:272)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
at
weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3811)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3561)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3422)
at
weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1760)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1601)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1491)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:880)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at
weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:302)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:217)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:164)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:101)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)

The class does contain the setter, so we don't know why the message pops
up. After rebooting the server, the page works properly (!) Does anyone
know how to get rid of it ? We're running out of ideas, and rebooting
the server every 2-3 days is not acceptable.

The configuration consists of BEA WebLogic 5.1.0 SP8 + JDK 1.2.2_07 +
HPUX 11.0.

Any help is greatly appreciated.

Jacek Laskowski

[Jacek Laskowski]

[Mike Reiche]

Is it possible that the tag was changed - an attribute was added in the .tld and
to the class?

The new .tld is seen immediately. The new class is not - not until you restart
WL.

Mike

[Jacek Laskowski]

Hi Mike,

Thanks for the response. Unfortunatelly, it's happening on a production
server and nobody's changing anything. The error message pops up every
2-3 days and the only way to get rid of that is to reboot the server.
Hmmm...I could even say it's hitting us quite regularly.

The first time I've seen this I thought that there might be somewhere a
class which does not really have the necessary setter. It might've been
a case, but it's not. Even though we assume it might happen, what's
going on with the WLS classloaders that they pick up the right class at
the startup and after some time they change their mind and pick up the
wrong one. That would be a bug, shouldn't it ?

What's more annoying is the fact that we're *not* able to open a case in
the support as there is nothing to be shown. There is merely the error
message which anybody can clearly explain that it relates to a wrong
class - no setter in it.

The only way I can think of would be to enable remote debugging and as
soon as it's happend, connect to the WLS JVM and see what's wrong. We
don't have the WLS sources, though.

-Jacek

[Srinagesh Susarla]

so doesn you bean have a
void setLimit(String) {}
String getLimit() {}
or does it have mismatched getter and setter?
like
setLimit(String) {}
int getLimit() {}

take a look at :
http://developer.java.sun.com/developer/bugParade/bugs/4407050.html

-Nagesh

[Sam Pullara]

This might be a masked file descriptor problem but it is hard to say. This
code should only be run when the .jsp is being recompiled. Are you changing
the .jsp files at runtime? If this is really in production and you are
seeing recompiles it is even more mysterious.

Sam

"Jacek Laskowski" <jacek_l...@hp.com> wrote in message
news:3B7C2B24...@hp.com...