Hi ,
I'm having some real issues , running programs in Tomcat on my machine.
I just copied a jakarta folder named jakarta-tomcat-3.3.1a on to my D: drive
(Path : D:\Program Files\jakarta-tomcat-3.3.1a) .
I can run simple jsp programs with no database connection. But whenever I try
to
Jeny V wrote:
Hi ,
I'm having some real issues , running programs in Tomcat on my machine.
I just copied a jakarta folder named jakarta-tomcat-3.3.1a on to my D: drive
(Path : D:\Program Files\jakarta-tomcat-3.3.1a) .
Do you not read the answers you have already been given ?
The current
Hi,
I am embedding Apache Tomcat 7.0.30 in my application. I am using the Tomcat
class,and my application requires dynamic addition and removal of
connectors(HTTP).
Now while removing the connectors,the application gets undeployed but the port
remains occupied and the connector continue to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeny,
On 5/13/13 2:52 AM, Jeny V wrote:
I'm having some real issues , running programs in Tomcat on my
machine.
I just copied a jakarta folder named jakarta-tomcat-3.3.1a on to
my D: drive (Path : D:\Program Files\jakarta-tomcat-3.3.1a) .
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/13/13 11:34 AM, Chirag Dewan wrote:
I am embedding Apache Tomcat 7.0.30 in my application. I am using
the Tomcat class,and my application requires dynamic addition and
removal of connectors(HTTP).
Now while removing the
How do you observe that the connector is still bound to the port?
Yes. I used netstat to observe that. Plus when I try to add another context to
the same port,I get Address already in use exception.
What does it show?
I can see my java process running on that port.
What happens if you make
Chirag Dewan wrote:
How do you observe that the connector is still bound to the port?
Yes. I used netstat to observe that. Plus when I try to add another context to the same
port,I get Address already in use exception.
What does it show?
I can see my java process running on that port.
Hi All,
I need some help with the async context timeout in servlet 3.0 running on
tomcat 7.0.40.
I have set the asynccontext timeout value, but the timeout behaviour is
highly inconsistent. Sometimes the timeouts work, but most of the times
they don't. I am attaching the source code and the
Yeah, it's clear from what's typed below his DB driver is way out of whack with
this ancient version of Tomcat.
It probably got updated along the way by network sorts while the Tomcat version
stayed put.
Go to current, and with current Tomcat, also get a current JDK - I imagine the
one you
If the context was removed, but the Connector was still there, should you not
get a 404
Not Found, rather than a timeout ?
If I am calling the removeConnector,shouldn't it cleanup the context and the
free the port?
I mean is my context blocking the connector even after I removed it? i
Hi,
we've upgraded our linux systems and experience some serious slowdowns
from our antivirus solutions. Expanding large WAR files (e.g. Alfresco)
is blocked by the virus scanner for minutes (!). Now we get tomcats
failing to deploy contexts on startup. Everything was fine when the
From: Stefan Mayr [mailto:ste...@mayr-stefan.de]
Subject: Delayed WAR expansion, timeout on context startup?
Are there any parameters to adjust deployment timeouts for these
contexts with large WAR files?
Want to give us a hint about what Tomcat version, JVM level, and platform
you're
On 13/05/2013 18:01, Rahul Kumar wrote:
Hi All,
I need some help with the async context timeout in servlet 3.0 running
on tomcat 7.0.40.
I have set the asynccontext timeout value, but the timeout behaviour is
highly inconsistent. Sometimes the timeouts work, but most of the times
they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/13/13 1:03 PM, Chirag Dewan wrote:
If the context was removed, but the Connector was still there,
should you not get a 404 Not Found, rather than a timeout ?
If I am calling the removeConnector, shouldn't it cleanup the
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Port still busy after removing connector in Embedded Tomcat
7.0.30
If I am calling the removeConnector, shouldn't it cleanup the
context and the free the port?
In theory, yes, but ...
How long are you
On 13/05/2013 16:34, Chirag Dewan wrote:
Hi,
I am embedding Apache Tomcat 7.0.30 in my application. I am using the Tomcat
class,and my application requires dynamic addition and removal of
connectors(HTTP).
Now while removing the connectors,the application gets undeployed but the
port
From: Caldarale, Charles R
Subject: RE: Port still busy after removing connector in Embedded Tomcat
7.0.30
How long are you waiting? Can you give us the specifics of your
connector configuration? I wonder if the connector is remaining open
for something like a keepalive timeout (I
You need to destroy the connector to close the port.
Mark,
That seems to work. :)
Now the port is free. But is it the right approach? Is this something we need
to do in Tomcat 7 specifically?
Thanks.
From: Mark Thomas ma...@apache.org
To: Tomcat Users
I am curious to know how Tomcat's connectors handle the request processing
internally, especially between the Http11Protocol which i believe acts as a
connector and with every connector there may be a request processor which
is the Http11Processor.
I think there is a pool of Http11Processor
19 matches
Mail list logo
