Apache2 Web Management tool broke. (HTTP Status 500 error)

[bruc...@ngent.com]

Hi,
I just applied NW6.5SP1a to my GW6.5.1/WEB box. When I login to the
Apaches Web Management tool, I can't change anything because every page
has the following error on the left side:

HTTP Status 500 -

--------------------------------------------------------------------------
------

type Exception report

message

description The server encountered an internal error () that prevented it
from fulfilling this request.

exception

org.apache.jasper.JasperException
at org.apache.jasper.servlet.JspServletWrapper.service
(JspServletWrapper.java:254)
at org.apache.jasper.servlet.JspServlet.serviceJspFile
(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service
(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke
(StandardContext.java:2416)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service
(CoyoteAdapter.java:193)
at org.apache.jk.server.JkCoyoteHandler.invoke
(JkCoyoteHandler.java:309)
at org.apache.jk.common.HandlerRequest.invoke
(HandlerRequest.java:386)
at org.apache.jk.common.ChannelSocket.invoke
(ChannelSocket.java:673)
at org.apache.jk.common.ChannelSocket.processConnection
(ChannelSocket.java:615)
at org.apache.jk.common.SocketConnection.runIt
(ChannelSocket.java:786)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:666)
at java.lang.Thread.run(Thread.java:534)

root cause

java.lang.ClassCastException
at org.apache.jsp.SingleServerStatus_jsp._jspService
(SingleServerStatus_jsp.java:49)
at org.apache.jasper.runtime.HttpJspBase.service
(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServletWrapper.service
(JspServletWrapper.java:210)
at org.apache.jasper.servlet.JspServlet.serviceJspFile
(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service
(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke
(StandardContext.java:2416)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv
okeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service
(CoyoteAdapter.java:193)
at org.apache.jk.server.JkCoyoteHandler.invoke
(JkCoyoteHandler.java:309)
at org.apache.jk.common.HandlerRequest.invoke
(HandlerRequest.java:386)
at org.apache.jk.common.ChannelSocket.invoke
(ChannelSocket.java:673)
at org.apache.jk.common.ChannelSocket.processConnection
(ChannelSocket.java:615)
at org.apache.jk.common.SocketConnection.runIt
(ChannelSocket.java:786)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:666)
at java.lang.Thread.run(Thread.java:534)

--------------------------------------------------------------------------

Does anyone have any insight into what caused this, or how I might fix it?

Thanks,
Bruce

[Joseph Moore [SysOp]]

:

> HTTP Status 500 -
>

lots of people are reporting this, am asking Novell - but you might try
running PKIDIAG to make sure you certificates are ok

Joe Moore
Novell Support Connection Volunteer Sysop
http://just.fdisk-it.com
for an e-book on NetWare Enterprise Web Server,
see http://www.caledonia.net/nesadmin.html

NO EMAIL PLEASE!!!!!

[bruc...@ngent.com]

> :
>
> > HTTP Status 500 -
> >
>
> lots of people are reporting this, am asking Novell - but you might try
> running PKIDIAG to make sure you certificates are ok

Well, I wasn't having a problem with certificates yesterday. Today
however, nothing using them will come up. Not ifolder or any https
resources. Do I have to recreate them? If so, how?

Thanks,
Bruce

[bruc...@ngent.com]

> Well, I wasn't having a problem with certificates yesterday. Today
> however, nothing using them will come up. Not ifolder or any https
> resources. Do I have to recreate them? If so, how?

Please ignore the above statement. Router problem. The certifictaes are
fine and passed the pkidiag without any problems. All web services seem
to be working fine. Just the Apache web admin tool and it's http status
500 acting up.

Thanks,
Bruce

[Joseph Moore [SysOp]]

:

From Novell:

did they look at TID.. 10090444
also if they reload tomcat4.ncf and the other tomcat ncf file do they
still get the error... I had the same problems but reloaded the 2
tomcat ncf files I had no problems after that..

[Joseph Moore [SysOp]]

:

> Just the Apache web admin tool and it's http status
> 500 acting up.
>

hopefully the new answer I posted for you will help :)

[bruc...@ngent.com]

> :
>
> From Novell:
>
> did they look at TID.. 10090444
> also if they reload tomcat4.ncf and the other tomcat ncf file do they
> still get the error... I had the same problems but reloaded the 2
> tomcat ncf files I had no problems after that..

Joe,
The server in question is also running GW Webaccess and it runs fine. Is
it possible for Tomcat to run that app fine and then fail when running
the Apache web admin? If so, I'll give the work around in the TID a try.
Just wanted to be sure before I made any changes.

I really appreciate all the help,
Bruce

[Joseph Moore [SysOp]]

:

> Is
> it possible for Tomcat to run that app fine and then fail when running
> the Apache web admin? If so, I'll give the work around in the TID a try.
>

yes, it is possible :)

[Timothy Leerhoff]

I recently had the opposite, iManager worked, GW WebAccess didn't.

Basically I had a load order issue. I had to load GWWA after tomcat.

--
Timothy Leerhoff
Principal Consultant
Independant Experts
Novell Support Forums Sysop

[bruc...@ngent.com]

> I recently had the opposite, iManager worked, GW WebAccess didn't.
>
> Basically I had a load order issue. I had to load GWWA after tomcat.

Yea, I've heard of that happening. I load all the GW componets last, with
Webaccess the last in line.

Thanks for the info Joe. I am going to try it today.

Bruce

[bruc...@ngent.com]

> :
>
> > Is
> > it possible for Tomcat to run that app fine and then fail when
running
> > the Apache web admin? If so, I'll give the work around in the TID a
try.
> >
>
> yes, it is possible :)

Joe,
I checked the NCF file for Tomcat, per the TID, and mine is exactly as it
should be. So there isn't anything for me to change.

Thanks,
Bruce

[Joseph Moore [SysOp]]

:

> So there isn't anything for me to change.
>

ugh - so you are still stuck?

[Joseph Moore [SysOp]]

:

> Thanks for the info Joe. I am going to try it today.
>

FYI, a user reports that the following info fixes the manager stuff:

1. tomcat4 -stop
2. tcadmdn
3. admsrvdn
4. ap2webdn
5. Go to tomcat/4/work and have him delete the 2 directories in there
the nwadmin and standalone
6. reversed the process

[bruc...@ngent.com]

> :
>
> > Thanks for the info Joe. I am going to try it today.
> >
>
> FYI, a user reports that the following info fixes the manager stuff:
>
> 1. tomcat4 -stop
> 2. tcadmdn
> 3. admsrvdn
> 4. ap2webdn
> 5. Go to tomcat/4/work and have him delete the 2 directories in there
> the nwadmin and standalone
> 6. reversed the process

Joe!!!!
You are the man. Not only did that work, but it seems to have killed a
small issue I was having with GW Webaccess. Is it safe to assume those
directories are some kind of cached files and that deleting them cleaned
out any corruption? After that Apache Web Admin was a little slow, like it
was caching or something, and steadily got faster. It worked though. :)

I was having a problem with GW Webaccess not display e-mail or replies when
clicked. Give a page not found, but a refresh or two would fix it. After
this operation it stopped doing it. Which made me think, again, that this
was some type of cache that may need emptying from time to time if web
services burps.

Thanks again Joe,
Bruce