Hi all;
I am migrating to tomcat 7 from 6.
In tomcat 6 urls like
http://68.169.51.83:8080/gallery/wave_surfing_gallery_thumb_652.jpg;jses
sionid=A859D830090798F238DABADC713C1327 would load an image but in
tomcat 7 I get the following response: The Image . cannot be
displayed because it
Hi All,
I am using Apache Tomcat 7.0 (7.0.14 version) server. I have a
requirement such that Once i make a HTTP request, and get back the response,
i want to keep that connection alive indefinitely. What is the configuration
i need to make on the server side. By default, client uses
adarsh thimmappa wrote:
Hi All,
I am using Apache Tomcat 7.0 (7.0.14 version) server. I have a
requirement such that Once i make a HTTP request, and get back the response,
i want to keep that connection alive indefinitely. What is the configuration
i need to make on the server side. By
Hi Andre,
I am using the below Connector tag configuration in the
server.xml.I am still facing the same problem.
Connector port=80
protocol=org.apache.coyote.http11.Http11NioProtocol
socket.soKeepAlive=true
Hi,
I am changing the log level of tomcat to Level.WARNING. In this case I'm
trying to restart tomcat and see the logs, I can see the info level logs
like INFO: Server startup in 50516 ms .
I guess info level logs should not appear if log level set to warning.
Kindly let me know how exactly it
2011/6/22 Roshni Basu roshni...@gmail.com:
I am changing the log level of tomcat to Level.WARNING. In this case I'm
trying to restart tomcat and see the logs, I can see the info level logs
like INFO: Server startup in 50516 ms .
I guess info level logs should not appear if log level set to
I don't think that az this stage you should be playing with the socket.* attributes, which
refer to the low-level JVM TCP socket, and have quite another meaning and other side-effects.
Re-read the description of the keepAliveTimeout attribute instead, which does refer to
the HTTP protocol
The equivalent basic scheme worked perfectly fine in tomcat6. In
Tomcat7, it looks like:
solrContext = tomcat.addWebapp(/solr,
solrWebapp.getCanonicalPath());
WebappLoader solrLoader = new
WebappLoader(LSHDemoLauncher.class.getClassLoader());
On 22/06/2011 14:47, Benson Margulies wrote:
The equivalent basic scheme worked perfectly fine in tomcat6. In
Tomcat7, it looks like:
solrContext = tomcat.addWebapp(/solr,
solrWebapp.getCanonicalPath());
WebappLoader solrLoader = new
On 21/06/2011 22:58, Jess Holle wrote:
If I alter JarFactory to always use FileUrlJar, then my startup is
around 20 seconds faster, i.e. the speed is fully back to that of 7.0.12.
It turns out the issue is the large jars I have in my WEB-INF/lib
directory -- and FileUrlJar is still much
Solr has a particularly bizarre class loading environment. The class
causes the problem is the FileUploadServlet from commons-fileupload. I
doubt that the problem is validation, but I'll check.
My experience is that, in the stock Tomcat class, the new context gets
called through .start() before
On 22/06/2011 15:18, Benson Margulies wrote:
Solr has a particularly bizarre class loading environment. The class
causes the problem is the FileUploadServlet from commons-fileupload. I
doubt that the problem is validation, but I'll check.
My experience is that, in the stock Tomcat class, the
On 22/06/2011 15:08, Mark Thomas wrote:
On 21/06/2011 22:58, Jess Holle wrote:
If I alter JarFactory to always use FileUrlJar, then my startup is
around 20 seconds faster, i.e. the speed is fully back to that of 7.0.12.
It turns out the issue is the large jars I have in my WEB-INF/lib
I agree with your preference. Patch to follow later today.
On Wed, Jun 22, 2011 at 10:27 AM, Mark Thomas ma...@apache.org wrote:
On 22/06/2011 15:18, Benson Margulies wrote:
Solr has a particularly bizarre class loading environment. The class
causes the problem is the FileUploadServlet from
Tomcat version is 6.0.9.
Here is my snippet of code:
LogManager logManager = LogManager.getLogManager();
EnumerationString e = logManager.getLoggerNames();
while (e.hasMoreElements())
{
String loggername = e.nextElement();
Logger logger =
On 22/06/2011 16:03, Roshni Basu wrote:
Tomcat version is 6.0.9.
Here is my snippet of code:
LogManager logManager = LogManager.getLogManager();
EnumerationString e = logManager.getLoggerNames();
while (e.hasMoreElements())
{
String loggername =
I have created a java file. And running this. Could you elaborate what
exactly you want to know?
Mark Thomas wrote:
On 22/06/2011 16:03, Roshni Basu wrote:
Tomcat version is 6.0.9.
Here is my snippet of code:
LogManager logManager = LogManager.getLogManager();
On 6/22/2011 9:08 AM, Mark Thomas wrote:
Another issue is that WEB-INF/lib is visible to the parent classloader
embedding Tomcat and to Tomcat as part of the web application and thus
I'm probably getting double scanning -- though really Tomcat should be
avoiding this by detecting that the same
On 22/06/2011 16:16, Roshni Basu wrote:
I have created a java file. And running this. Could you elaborate what
exactly you want to know?
I want to know how this code is being executed. When does it run? What
triggers it?
Mark
Mark Thomas wrote:
On 22/06/2011 16:03, Roshni Basu wrote:
My understanding is that I should *not* close the servlet input/output
streams (if you don't open them - you shouldn't close them)
But what if I have wrapped those streams inside other streams that I want to
close? Let's say I have several layers of object streams, cipher streams,
compression
I just run it when I need to change the log level.
Mark Thomas wrote:
On 22/06/2011 16:16, Roshni Basu wrote:
I have created a java file. And running this. Could you elaborate what
exactly you want to know?
I want to know how this code is being executed. When does it run? What
Basically I have an web application running on tomcat.
Mark Thomas wrote:
On 22/06/2011 16:16, Roshni Basu wrote:
I have created a java file. And running this. Could you elaborate what
exactly you want to know?
I want to know how this code is being executed. When does it run? What
I'm using Tomcat 6.0.0.29 and am also experiencing a similar issue where I
am seeing Drop message SESSION-EXPIRED inside GET_ALL_SESSIONS sync phase
start date 6/21/11 3:22 PM message date 12/31/69 6:00 PM when I restart a
node in the cluster.
What concerns me is that the message date is 13/31/69
Hi,
I'm really confused with Apache; Apache/Tomcat; Tomcat.
Please correct me if I'm wrong:
When I install Apache/Tomcat, I install Apache web sever and Tomcat application
sever at the same time.I could do the same thing by installing Apache web
sever, and Tomcat application
server
Apache = Apache Software Foundation. This is the legal organization which
has all the wonderful bureaucracy in setting up rules for
software development and making sure projects adhere to various countries
laws.
Tomcat - Actually Apache Tomcat - the implementation of the servlet spec. A
project
From: Roshni Basu [mailto:roshni...@gmail.com]
Subject: Re: Tomcat Logging level change
I just run it when I need to change the log level.
(This is like pulling teeth.) You're providing virtually no useful information
here. You run the program where? As a servlet? Standalone? In some
Yes.
And someone else please explains better - at a high level:
- the functionality where they overlap
- the functionality where they differ
- what is to be done if they are to be integrated
Home page:
Application is running on tomcat.
n828cl wrote:
From: Roshni Basu [mailto:roshni...@gmail.com]
Subject: Re: Tomcat Logging level change
I just run it when I need to change the log level.
(This is like pulling teeth.) You're providing virtually no useful
information here. You run
Its working fine when I set to Fine. In catalina.out i can see fine and
info logs butwhen I set to warning, even info level logs appear.
n828cl wrote:
From: Roshni Basu [mailto:roshni...@gmail.com]
Subject: Re: Tomcat Logging level change
I just run it when I need to change the log
From: Dennis de Champeaux [mailto:atlantisic...@yahoo.com]
Subject: Re: Apache/Tomcat_means...?
And someone else please explains better - at a high level:
- the functionality where they overlap
- the functionality where they differ
- what is to be done if they are to be integrated
Tomcat 6.0.x looks to be OK. There is a copy/paste problem in 7.0.x that
I'll fixed shortly.
If you are willing to build Tomcat 7.0.x from source (not hard) then it
will be easy for you to test the patch.
Mark
-
To
2011/6/22 Roshni Basu roshni...@gmail.com:
Tomcat version is 6.0.9.
You know, 6.0.32 is out there...
http://tomcat.apache.org/security-6.html
Here is my snippet of code:
LogManager logManager = LogManager.getLogManager();
EnumerationString e = logManager.getLoggerNames();
It won't
On 6/22/2011 10:16 AM, Jess Holle wrote:
On 6/22/2011 9:08 AM, Mark Thomas wrote:
Another issue is that WEB-INF/lib is visible to the parent classloader
embedding Tomcat and to Tomcat as part of the web application and thus
I'm probably getting double scanning -- though really Tomcat should be
From: Jess Holle [mailto:je...@ptc.com]
Subject: Re: Slower start with Tomcat 7.0.14 and higher
Well the classloaders are clearly hierarchical, so only one Class
instance is loaded. The fact that both ClassLoaders can see the jar
does not result in 2 Class objects
I think we need some
Since delegation is downwards the only issue that should possibly occur
is if a class gets loaded in the parent classloader that then needs a
class in the child (e.g. web app) classloader. That will fail, of
course, but that's ok as this should never occur.
On 6/22/2011 12:27 PM, Caldarale,
From: Jess Holle [mailto:je...@ptc.com]
Subject: Re: Slower start with Tomcat 7.0.14 and higher
Since delegation is downwards
Only for the webapp classloader.
the only issue that should possibly occur is if a class gets
loaded in the parent classloader that then needs a class in
the
Hi All,
Can anyone please confirm this is an issue or not. I have visited this
link
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Common_Attributeslot
more timesi feel like nothing left w.r.t going back to this link
again. If anyone is having configuration which is working
On 22/06/2011 19:03, adarsh thimmappa wrote:
Hi All,
Can anyone please confirm this is an issue or not. I have visited this
link
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Common_Attributeslot
more timesi feel like nothing left w.r.t going back to this link
again.
From: adarsh thimmappa [mailto:adarsh.tm...@gmail.com]
Subject: Re: Apache Tomcat 7.0.14
Can anyone please confirm this is an issue or not.
Not directly. Can you get Wireshark (or equivalent) traces of the traffic
between the client and the server? You can use those to determine which end
Hi Mark,
Let me investigate further. I will definitely get back on this.
On Wed, Jun 22, 2011 at 11:37 PM, Mark Thomas ma...@apache.org wrote:
On 22/06/2011 19:03, adarsh thimmappa wrote:
Hi All,
Can anyone please confirm this is an issue or not. I have visited
this
Mark,
Thanks for looking into this and working to get the patch in for future
versions. It will allow us to use later versions of Tomcat and not be stuck
on 7.0.10.
If you would like me to test the patch, I can rebuild from patched source
and test locally.
Martin
On Wed, Jun 22, 2011 at 12:46
On 6/22/2011 12:44 PM, Caldarale, Charles R wrote:
I think it can happen, without detection, if you have the same class directly
visible to multiple classloaders - which I recall that you do (but perhaps I
misunderstood this statement: the base classloader includes a lot more than
Hi All,
In the entire source file of *
org.apache.coyote.http11.Http11NioProtocol* class in *tomcat server 7.0.14*,
there are no setters to set any of these properties such as
connectionTimeout,socket reuseaddress, keepalivetimeout etc. I compared the
same file with the *tomcat server
On 22/06/2011 20:03, Martin Dubuc wrote:
Mark,
Thanks for looking into this and working to get the patch in for future
versions. It will allow us to use later versions of Tomcat and not be stuck
on 7.0.10.
If you would like me to test the patch, I can rebuild from patched source
and test
You really need to read
http://www.catb.org/~esr/faqs/smart-questions.html before folks here
just start ignoring your messages.
On 22/06/2011 20:59, adarsh thimmappa wrote:
Hi All,
In the entire source file of *
org.apache.coyote.http11.Http11NioProtocol* class in *tomcat server 7.0.14*,
Hi all;
I sure that is going to turnout to be a stupid question but I've played with
it for two days and made no progress. I can create a JULI handler as long
as I don't apply a prefix, here is the logging.properties file (keeping it
as simple as possible):
THIS WORKS FINE
2011/6/23 throwsCode donmillho...@yahoo.com:
I sure that is going to turnout to be a stupid question but I've played with
it for two days and made no progress. I can create a JULI handler as long
as I don't apply a prefix, here is the logging.properties file (keeping it
as simple as
2011/6/22 Guy Katz gk...@allot.com:
Hi all;
I am migrating to tomcat 7 from 6.
In tomcat 6 urls like
http://68.169.51.83:8080/gallery/wave_surfing_gallery_thumb_652.jpg;jses
sionid=A859D830090798F238DABADC713C1327 would load an image but in
tomcat 7 I get the following response: The Image
Thanks Konstantin:
I thought the JULI Classes automatically replaced the java.util.logging
Classes with the same name. Thanks for catching that, I'll checkout
catalina.sh and try to figure this out.
TC
throwsCode wrote:
Hi all;
I sure that is going to turnout to be a stupid question
Hi
You may use decorator pattern to decorate the input output stream from
Servlet to a UnclosableInputStream UnclosableOutputStream,
public class UnclosableInputStream extends java.io.FilterInputStream {
public UnclosableInputStream(InputStream inputStream) {
super(inputStream);
}
@Override
So what exactly I can use to make it work in 6.0.9?
Konstantin Kolinko wrote:
2011/6/22 Roshni Basu roshni...@gmail.com:
Tomcat version is 6.0.9.
You know, 6.0.32 is out there...
http://tomcat.apache.org/security-6.html
Here is my snippet of code:
LogManager logManager =
Ok..Thanks.
On Thu, Jun 23, 2011 at 3:02 AM, Mark Thomas ma...@apache.org wrote:
You really need to read
http://www.catb.org/~esr/faqs/smart-questions.html before folks here
just start ignoring your messages.
On 22/06/2011 20:59, adarsh thimmappa wrote:
Hi All,
In the entire source
Hi Mark,
I would be sorry if that was aggressive. I was testing the NIO
connector and was monitoring the TCP connections between the client(Here the
client is Apache MINA based) and the tomcat server(tomcat 7.0.14) through
the tool (CurrPorts v1.91 - Monitoring Opened TCP/IP network ports
From: adarsh thimmappa [mailto:adarsh.tm...@gmail.com]
Subject: Re: Apache Tomcat 7.0.14
I observed that the TCP connection suddenly disappears after
the response is sent.
Connections don't suddenly disappear - someone (possibly the client) closes
it. Again, you need to look at TCP/IP
54 matches
Mail list logo
