The request was rejected because its size (102811565) exceeds the configured maximum (52428800)

2010-08-25 Thread Razvan Poenaru
type Exception report
message
description The server encountered an internal error () that prevented it from 
fulfilling this request.
exception
java.lang.IllegalStateException: 
org.apache.tomcat.util.http.fileupload.FileUploadBase$SizeLimitExceededException:
 the request was rejected because its size (102811565) exceeds the configured 
maximum (52428800)
org.apache.catalina.connector.Request.parseParts(Request.java:2567)
org.apache.catalina.connector.Request.parseParameters(Request.java:2775)
org.apache.catalina.connector.Request.getParameter(Request.java:1097)

org.apache.catalina.connector.RequestFacade.getParameter(RequestFacade.java:365)

org.apache.catalina.filters.CsrfPreventionFilter.doFilter(CsrfPreventionFilter.java:161)
root cause
org.apache.tomcat.util.http.fileupload.FileUploadBase$SizeLimitExceededException:
 the request was rejected because its size (102811565) exceeds the configured 
maximum (52428800)

org.apache.tomcat.util.http.fileupload.FileUploadBase$FileItemIteratorImpl.init(FileUploadBase.java:801)

org.apache.tomcat.util.http.fileupload.FileUploadBase.getItemIterator(FileUploadBase.java:284)

org.apache.tomcat.util.http.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:304)

org.apache.tomcat.util.http.fileupload.servlet.ServletFileUpload.parseRequest(ServletFileUpload.java:129)
org.apache.catalina.connector.Request.parseParts(Request.java:2540)
org.apache.catalina.connector.Request.parseParameters(Request.java:2775)
org.apache.catalina.connector.Request.getParameter(Request.java:1097)

org.apache.catalina.connector.RequestFacade.getParameter(RequestFacade.java:365)

org.apache.catalina.filters.CsrfPreventionFilter.doFilter(CsrfPreventionFilter.java:161)
note The full stack trace of the root cause is available in the Apache 
Tomcat/7.0.2 logs.


Regards,

Razvan  Poenaru | Sr.Programmer/Analyst | Space Missions - MDA
(905) 790 2800 x4626|razvan.poen...@mdacorporation.com|www.mdacorporation.com
Canada - 9445 Airport Road, Brampton, ON - L6S 4J3



Getting an error with the Tomcat Manager on version 6.0.14.

2009-10-07 Thread Razvan Poenaru
I am getting the following error when trying to access the Tomcat
Manager on Tomcat 6.0.14:
 

type Exception report
message 
description The server encountered an internal error () that prevented
it from fulfilling this request.
exception javax.servlet.ServletException: Error allocating a servlet
instance
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
java.lang.Thread.run(Thread.java:619)

root cause java.lang.SecurityException: Servlet of class
org.apache.catalina.manager.HTMLManagerServlet is privileged and cannot
be loaded by this web application
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
java.lang.Thread.run(Thread.java:619)

note The full stack trace of the root cause is available in the Apache
Tomcat/6.0.14 logs.Apache Tomcat/6.0.14

Regards,
 
Razvan  Poenaru |Sr.Programmer/Analyst |Space Missions -MDA
(905) 790 2800
x4626|razvan.poen...@mdacorporation.com|www.mdacorporation.com
Canada – 9445 Airport Road, Brampton, ON – L6S 4J3

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Getting an error with the Tomcat Manager on version 6.0.14.

2009-10-07 Thread Razvan Poenaru
Hi Chuck,
 
Thanks a lot for the answer.
 
This is the manager.xml file I have in \webapps\manager directory:
 
!--
 
Context configuration file for the Tomcat Manager Web App
 
$Id: manager.xml 303123 2004-08-26 17:03:35Z remm $
 
--
 

Context docBase=${catalina.home}/server/webapps/manager
 privileged=true antiResourceLocking=false
antiJARLocking=false
 
  !-- Link to the user database we will get roles from --
  ResourceLink name=users global=UserDatabase
type=org.apache.catalina.UserDatabase/
 
/Context
 
 
I do not have any contex.xml file in \webapps\manager\MET-INF
 
I am new to Tomcat. We can not upgrade due to SOX requirements. Lots of
Testing involved.
 

Regards,
 
Razvan  Poenaru |Sr.Programmer/Analyst |Space Missions -MDA
(905) 790 2800
x4626|razvan.poen...@mdacorporation.com|www.mdacorporation.com
Canada – 9445 Airport Road, Brampton, ON – L6S 4J3


 Caldarale, Charles R chuck.caldar...@unisys.com 10/7/2009 1:44
PM 
 From: Razvan Poenaru [mailto:razvan.poen...@mdacorporation.com] 
 Subject: Getting an error with the Tomcat Manager on version 6.0.14.
 
 I am getting the following error when trying to access the Tomcat
 Manager on Tomcat 6.0.14:

Access it how?

 root cause
 java.lang.SecurityException: Servlet of class
 org.apache.catalina.manager.HTMLManagerServlet is privileged and
cannot
 be loaded by this web application

Looks like you may have lost the privileged=true attribute in the
manager's Context element.  Look in
[appBase]/manager/META-INF/context.xml and see what it says.  Also check
if there's a conf/Catalina/[host]/manager.xml that might be overriding
the one packaged with the webapp.

Any reason you can't move up to a newer version?

- Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
PROPRIETARY MATERIAL and is thus for use only by the intended recipient.
If you received this in error, please contact the sender and delete the
e-mail and its attachments from all computers.



RE: Getting an error with the Tomcat Manager on version6.0.14.

2009-10-07 Thread Razvan Poenaru
Hi Chuck,
 
I downloaded the 6.0.14 version, installed it on an other machine and
copy the wrong or missing files to the bad installation. It is working
now.
 
Thanks a lot for help.
 

Regards,
 
Razvan  Poenaru |Sr.Programmer/Analyst |Space Missions -MDA
(905) 790 2800
x4626|razvan.poen...@mdacorporation.com|www.mdacorporation.com
Canada – 9445 Airport Road, Brampton, ON – L6S 4J3


 Caldarale, Charles R chuck.caldar...@unisys.com 10/7/2009 3:05
PM 
 From: Razvan Poenaru [mailto:razvan.poen...@mdacorporation.com] 
 Subject: RE: Getting an error with the Tomcat Manager on
version6.0.14.
 
 This is the manager.xml file I have in \webapps\manager directory:
 Context docBase=${catalina.home}/server/webapps/manager
  privileged=true antiResourceLocking=false
 antiJARLocking=false

The above appears to have been left over from a version of Tomcat prior
to 6.0.x; the docBase attribute is incorrect (and shouldn't actually be
there at all); there is no ${catalina.home}/server directory on Tomcat
6.  The above file does not exist on a current Tomcat download.

   !-- Link to the user database we will get roles from --
   ResourceLink name=users global=UserDatabase
 type=org.apache.catalina.UserDatabase/
 /Context

I don't think the above ResourceLink is of much use.

 I do not have any contex.xml file in \webapps\manager\MET-INF

There should be one - it's part of the standard Tomcat download, so
someone has removed it.  The proper one looks like this:

Context antiResourceLocking=false privileged=true /

and is located in
${catalina.home}/webapps/manager/META-INF/context.xml.

You might want to download a copy of 6.0.14 from the archives and
compare it with what you have; looks like someone has improperly mucked
around with the structure.
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.14/bin/ 


- Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
PROPRIETARY MATERIAL and is thus for use only by the intended recipient.
If you received this in error, please contact the sender and delete the
e-mail and its attachments from all computers.