Hi dear list, oh yes, I did have a look at first in tomcat-user and found a similar question (but without any answer). So pls let me ask you: (1) everything seems to be fine at last, except the manager application. Sometimes I get the login panel, sometimes not even that. What I get on the browser is a white empty page. I do have a tomcat-user.xml with the manager-role defined. I tried it with and without a seaparate context definition. I also defined a manager log and in this log nothing seems to be wrong.
What I get in catalina-log at the moment I try /manager/html/ (or manager/list) is as follows: 2003-11-10 12:51:45 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.ArrayIndexOutOfBoundsException at org.apache.catalina.util.Base64.decode(Base64.java:288) at org.apache.catalina.authenticator.BasicAuthenticator.parseUsername(BasicAuthenticator.java:201) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:159) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:528) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.StandardContext.invoke(StandardContext.java:2416) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.invokeNext(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.coyote.http11.Http11Processor.process(Http11Processor.java:780) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:549) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:578) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666) at java.lang.Thread.run(Thread.java:512) (2) Either the admin or the manager or both applications seem to want to have persisted sessions. If I don't delete the files that get allocated under /work and /temp, I get terrible messages in my log (IO-Exceptions all the way). I tried to use persistent manager but it did not help so I stopped it again. Is there an intelligent way to handle this (besides deleting all the files under /work and /temp)? Question (1) is the one excites me more. If we have the manager - well then we could have a Real Living Tomcat Under Omvs :-)) (there are not many of them) Anyone inclined to help me? Thanks, Anna and that
