aspose file tools*
The moose likes Servlets and the fly likes logs filled with exceptions in Solaris Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "logs filled with exceptions in Solaris" Watch "logs filled with exceptions in Solaris" New topic
Author

logs filled with exceptions in Solaris

senthil loganathan
Greenhorn

Joined: Aug 07, 2001
Posts: 11
Dear All,
I have some tested JSP's working fine in NT Machine in Websphere 3.5 application server.
i have moved this code to websphere present in solaris.
In Solaris when i see the error logs lot of exceptions are thrown.
[02.04.23 15:47:55:868 GMT+08:00] e0491b ServletInstan X Uncaught service() exception thrown by servlet {0}: {1}
"JSP 1.0 Processor"
com.sun.jsp.JspWithNoErrorPageException: Server caught unhandled exception from JSP [ldregistration.jsp]
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
Like the above... in many screes it is writing exceptions like this, unhandled exception thrown from JSP. But in NT Server logs.. no exceptions like this are written in the logs..
can anybody explain the problem??


Senthil.L
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16070
    
  21

I'm not a Solaris expert, but as I read this, the service() method threw an exception and it appears that for some reason the error reporting mechanism isn't reporting is very well.
Try wrapping the service() code with this:

If it works better, use System.out.println or the servlet log method, instead.
If you're not directly implementing service(), you might want to apply the above to your doGet() and doPost() methods.


Customer surveys are for companies who didn't pay proper attention to begin with.
Mike Curwen
Ranch Hand

Joined: Feb 20, 2001
Posts: 3695

The error: com.sun.jsp.JspWithNoErrorPageException is pretty suspicious to me. I've never heard of this error, and when I googled it, all I got were google's cached pages of this error. ie: Sites that threw that error. And guess what? All of them were websphere.

Also, the "JSP 1.0 Processor" in the stack trace is not so good.

Are you sure the JSPs you're porting over to websphere are the same version that your websphere instance supports?
BJ Grau
Ranch Hand

Joined: Jul 10, 2001
Posts: 234
If you are using Websphere, you might have the Error Reporting facility servlet deployed in your web app. Open your console, select your webapp, go to advanced properties and set default error page to /ErrorReporter (or whatever URL pattern will invoke your Error Reporting servlet).
This should help you get rid of the error about not having an erro page configured and maybe you will see your real error.
Oh and I almost forgot, the error that you are seeing is in the service() method of your JSP 1.0 Processor, not one of your own servlets so it wouldn't be trivial to modify the code for it, and you shouldn't have to anyway. I think if you get the Error Reporting Facility configured, you will see what is going on.
[ April 23, 2002: Message edited by: BJ Grau ]
 
 
subject: logs filled with exceptions in Solaris