× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It works a lot better now.  Here is what I changed

<tomcat-users>
  <user name="tomcat" password="tomcat" roles="tomcat" />
  <user name="role1"  password="tomcat" roles="role1"  />
  <user name="both"   password="tomcat" roles="tomcat,role1" />
  <user name="admin" password="admin" roles="admin,tomcat" />
</tomcat-users>


<Context path="/admin"
                  docBase="webapps/admin"
                  crossContext="true"
                  debug="99"
                  reloadable="true"
                  trusted="true" >
</Context>

JSP crashes with the following errors.  I read a note to fix related to
slash character last night.  I will fix this bug.


Thank you very much for your help.

CL

Error: 500
Location: /admin/contextAdmin/contextAdmin.jsp
Internal Servlet Error:
javax.servlet.ServletException: URL contains encoded special chars.
           at java.lang.Throwable.(Throwable.java:96)
           at java.lang.Exception.(Exception.java:44)
           at javax.servlet.ServletException.(ServletException.java:161)
           at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:459)

           at contextAdmin.
_0002fcontextAdmin_0002fcontextAdmin_0002ejspcontextAdmin_jsp_0._jspService
(_0002fcontextAdmin_0002fcontextAdmin_0002ejspcontextAdmin_jsp_0.java(Compiled

Code))
           at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
           at
org.apache.jasper.servlet.JspServlet$JspCountedServlet.service(JspServlet.java:130)

           at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
           at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:282)

           at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:429)
           at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java(Compiled
Code))
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
           at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
           at org.apache.tomcat.core.Handler.service(Handler.java:287)
           at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
           at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:812)

           at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:758)
           at
org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:166)

           at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java(Compiled

Code))
           at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
           at java.lang.Thread.run(Thread.java:481)

Root cause:
java.lang.IllegalArgumentException: URL contains encoded special chars.
           at java.lang.Throwable.(Throwable.java:96)
           at java.lang.Exception.(Exception.java:44)
           at java.lang.RuntimeException.(RuntimeException.java:49)
           at
java.lang.IllegalArgumentException.(IllegalArgumentException.java:45)
           at
org.apache.tomcat.util.RequestUtil.URLDecode(RequestUtil.java(Compiled
Code))
           at ContextAdmin.getContextInfo(ContextAdmin.java:100)
           at contextAdmin.
_0002fcontextAdmin_0002fcontextAdmin_0002ejspcontextAdmin_jsp_0._jspService
(_0002fcontextAdmin_0002fcontextAdmin_0002ejspcontextAdmin_jsp_0.java(Compiled

Code))
           at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
           at
org.apache.jasper.servlet.JspServlet$JspCountedServlet.service(JspServlet.java:130)

           at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
           at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:282)

           at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:429)
           at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java(Compiled
Code))
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
           at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
           at org.apache.tomcat.core.Handler.service(Handler.java:287)
           at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
           at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:812)

           at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:758)
           at
org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:166)

           at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java(Compiled

Code))
           at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
           at java.lang.Thread.run(Thread.java:481)






                    "David Morris"
                    <David.Morris@plum        To:     <java400-l@midrange.com>
                    creek.com>                cc:
                    Sent by:                  Subject:     Re: TOMCAT
                    java400-l-admin@mi
                    drange.com


                    10/18/2001 04:49
                    AM
                    Please respond to
                    java400-l






CL,

You should have something like:
<user name="admin" password="admin" roles="admin,tomcat" />
You have to stop and restart tomcat. There are a couple of email lists
for Tomcat. They are listed off of the Jakarta pages. Tomcat user is
tomcat-user@jakarta.apache.org and the developers list is
tomcat-dev@jakarta.apache.org. For more information go to:
http://jakarta.apache.org/site/mail2.html
There is also an online book that is in its infancy at Source Forge.

David Morris


>>> Chanh_Le@countrywide.com 10/17/01 04:38PM >>>

I only found user ID/ password defined in Tomcat-users.xml.  This file has
three usersID/password (tomcat/tomcat,  role1/tomcat, and both/tomcat).

I created user ID and password (tomcat/tomcat).  But I still fail the
authenticating check when I go to the following site

http://myserver.com/admin/contextAdmin/contextAdmin.html  (I do not use any
special port)

When I click "View All Contexts", I get userID/password dialog, I put
tomcat/tomcat.  It does not work.

I feel a little bit frustrated because Tomcat does not provide good
documentation and no news group.  I got a reference to news-group.  But it
shows me a blank page.

Thanks,
CL




                    "David Morris"
                    <David.Morris@plum        To:
<Chanh_Le@countrywide.com>,
                    creek.com>                <JAVA400-L@midrange.com>
                    Sent by:                  cc:
                    java400-l-admin@mi        Subject:     Re: TOMCAT
                    drange.com


                    10/17/01 07:59 AM
                    Please respond to
                    java400-l







CL,


_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.







As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.