-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 8/1/12 5:55 AM, André Warnier wrote:
> Without for a minute questioning the technical competence and
> intellectual brilliance of the actors involved, for me the above
> perfectly illustrates a phenomenon that is common in the computer
>
Am 01.08.2012 19:10, schrieb Shaw, Ray V CTR (US):
I'm starting up Tomcat 7.0 on RHEL6 with the following init script:
#!/bin/bash
#
# chkconfig: 235 80 20
# description: Takes care of starting and stopping Tomcat.
CATALINA_HOME="/opt/tomcat7"
export JAVA_HOME="/usr/java/jdk6-64/"
case "$1" in
Am 31.07.2012 23:28, schrieb André Warnier:
To be more explicit : my bet at this stage would be a bug in the
XP+IE+Acrobat9 combination (as being "the usual suspects"), but a bug
that gets triggered only because Tomcat 7.0.27+ send the response just a
bit differently than 7.0.26.
How about APR
2012/8/1 Shaw, Ray V CTR (US) :
> I'm starting up Tomcat 7.0 on RHEL6 with the following init script:
>
> #!/bin/bash
> #
> # chkconfig: 235 80 20
> # description: Takes care of starting and stopping Tomcat.
>
> CATALINA_HOME="/opt/tomcat7"
> export JAVA_HOME="/usr/java/jdk6-64/"
>
> case "$1" in
>
On 01.08.2012 09:54, André Warnier wrote:
Konstantin Kolinko wrote:
2012/8/1 Jose María Zaragoza :
The Content-Length header in the above 206 response is not from Tomcat.
Tomcat's DefaultServlet does not calculate the whole size of the parts
and does not set content-length, and the file size i
I'm starting up Tomcat 7.0 on RHEL6 with the following init script:
#!/bin/bash
#
# chkconfig: 235 80 20
# description: Takes care of starting and stopping Tomcat.
CATALINA_HOME="/opt/tomcat7"
export JAVA_HOME="/usr/java/jdk6-64/"
case "$1" in
'start')
/bin/su tomcat -c "
On 01.08.2012 18:52, Rainer Jung wrote:
Mark, is there a way we can influence the EG to change this?
I'm not Mark and don't want to preempt any answer from him, but there is
the following public discussion available:
http://java.net/jira/browse/SERVLET_SPEC-36
and
http://java.net/jira/browse
Thanks for the input. Just figured out the problem. Permissions weren't set
up correctly for the temp directory.
-Original Message-
From: Daniel Mikusa [mailto:dmik...@vmware.com]
Sent: Wednesday, August 01, 2012 1:02 PM
To: Tomcat Users List
Subject: Re: Error within Tomcat
- Orig
- Original Message -
> Has anyone seen this error before or can cast any light on what the
> issue may be?
>
> RuntimeException: Could not create the temp file for upload:
> /opt/econtent/tomcat/latest/temp/upload***.tmp
Looks like the specified file cannot be created. My first thought w
On 01.08.2012 18:10, Andreas Pålsson wrote:
I have been thinking about this issue all day, and I think the
specification needs more work on this area.
There is certainly no need for a container to wade through hundreds
maybe even thousands of classes in search of something that does not exist.
Has anyone seen this error before or can cast any light on what the issue may
be?
RuntimeException: Could not create the temp file for upload:
/opt/econtent/tomcat/latest/temp/upload***.tmp
-Isaac
This e-mail and any attachments are intended only for the use of
"Terence M. Bandoian" wrote:
>To make the context documentation page more readable, I suggest
>replacing the last preformatted block on the page with something like
>the following:
>
>
>
>docBase="/Users/theuser/mywebapp/src/main/webapp">
>
>
>className="
I have been thinking about this issue all day, and I think the
specification needs more work on this area.
There is certainly no need for a container to wade through hundreds
maybe even thousands of classes in search of something that does not exist.
It is an unnecessary task which consumes both
To make the context documentation page more readable, I suggest
replacing the last preformatted block on the page with something like
the following:
Re: Large webapps in 7.0.29 and Annotation Scanning not respecting "metadata-complete"
On 01.08.2012 09:51, Mark Thomas wrote:
On 01/08/2012 02:53, andreas palsson wrote:
Good morning.
After upgrading to 7.0.29, one of my larger webapps could no longer be deployed due to
"OutOfMemoryError".
As far as I know, this is related to the new feature of annotation scanning
which was e
Mark Thomas wrote:
On 01/08/2012 02:53, andreas palsson wrote:
Good morning.
After upgrading to 7.0.29, one of my larger webapps could no longer be deployed due to
"OutOfMemoryError".
As far as I know, this is related to the new feature of annotation scanning
which was enabled in v7.0.29 (see
On 01/08/2012 08:54, André Warnier wrote:
> Konstantin Kolinko wrote:
>> 2012/8/1 Jose María Zaragoza :
The Content-Length header in the above 206 response is not from Tomcat.
Tomcat's DefaultServlet does not calculate the whole size of the parts
and does not set content-length,
On 01/08/2012 09:35, andreas palsson wrote:
>
> Thank you Mark for explaining this. I'll see if I can get my hands on
> a 7.0.30 and see how it works out.
You'll need to wait until all the issues have been fixed and then build
from trunk. Keep an eye on the dev list.
> One thing though, would it
Thank you Mark for explaining this.
I'll see if I can get my hands on a 7.0.30 and see how it works out.
One thing though, would it be possible to allow Tomcat to _only_ scan for SCI's
in WEB-INF/classes and exclude WEB-INF/lib (even for parent classes inherited
in the former)?
It would be gre
Konstantin Kolinko wrote:
2012/8/1 Jose María Zaragoza :
The Content-Length header in the above 206 response is not from Tomcat.
Tomcat's DefaultServlet does not calculate the whole size of the parts
and does not set content-length, and the file size is much more than
fits into the buffer.
So i
On 01/08/2012 02:53, andreas palsson wrote:
>
> Good morning.
>
> After upgrading to 7.0.29, one of my larger webapps could no longer be
> deployed due to "OutOfMemoryError".
> As far as I know, this is related to the new feature of annotation scanning
> which was enabled in v7.0.29 (see the st
21 matches
Mail list logo
