I am working on a project with specifications to bundle Tomcat7 with a
Web Application. I am having trouble with the initial package setup, as
this is my first time bundling Tomcat7. I've developed WAR files that
have been deployed before.
I'm trying to start basic and get the bundle instan
> -Original Message-
> From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
> Sent: Wednesday, October 17, 2012 7:33 AM
> To: Tomcat Users List
> Subject: Java 6u37, 7u09 are available
>
> Hi!
>
> Just noting that Java 6u37, 7u09 were released by Oracle
> http://www.oracle.com/technet
James Lampert wrote:
We have a situation:
A Tomcat server with a number of contexts.
One of those contexts should be available unsecured on port 8080.
The others should only be available secured, on port 443.
Is there a way we can restrict 8080 to the one unsecured context?
I am not specia
S Ahmed wrote:
For my deployment, I have a set directory structure that I use.
Is it possible to tell tomcat to look at a specific folder for the ROOT
website, instead of in the ../../webapps/ folder?
my folder structure is like:
/www/myappname/website/
/www/myappname/otherstuff/
I want tomc
Mark Thomas wrote:
On 16/10/2012 18:54, David Wall wrote:
By the way, the web.xml change we made was suggested in the bug report
and seems to resolve it for our IE site visitors.
Glad to head that disabling support for range requests works. That seems
like a reasonable short-term workaround un
On 16/10/2012 17:52, Shanti Suresh wrote:
> Greetings.
>
> I have some questions on finding the number of active threads in Tomcat.
> (1) On our QA system, I notice that the currenthreadsBusy MBean is
> either zero or one for the 8443 and 8080 connectors.
ThreadCount != currentThreadsBusy
One
Hi,
Ok so it turned out to be a simple fix. I had not named the servlet (in
web.xml) that same as the access url (war).
Cheers,
Stuart
On 17 Oct 2012, at 10:03, Stuart Broad wrote:
> Hi,
>
> Sorry to keep replying to my own question but I gathered two stack traces
> from each of the calls
On 17/10/2012 11:36, André Warnier wrote:
> Mark Thomas wrote:
>> http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Connector_Comparison
> Thanks.
> Yes, I saw that table, but it is may be a bit "summarised" for the
> average Tomcat user (or sysadmin). Is there somewhere a more
> global/i
Mark Thomas wrote:
On 17/10/2012 11:02, André Warnier wrote:
Mark Thomas wrote:
On 17/10/2012 10:49, André Warnier wrote:
1) So it means that if a client connects to the server, but does not
send any request line for a while on that connection, the server will
allocate a thread to serve the re
On 17/10/2012 11:02, André Warnier wrote:
> Mark Thomas wrote:
>> On 17/10/2012 10:49, André Warnier wrote:
>>> 1) So it means that if a client connects to the server, but does not
>>> send any request line for a while on that connection, the server will
>>> allocate a thread to serve the request;
>You've configured a separate pool for connectors on ports 80 and 443. Why?
I thought it was better this way... Normally, the port 80 should automatically
redirect to the port 443 and https only should be authorized. Is there any
proper way to do that?
>You've reduced the acceptCount to 50. W
Mark Thomas wrote:
On 17/10/2012 10:49, André Warnier wrote:
1) So it means that if a client connects to the server, but does not
send any request line for a while on that connection, the server will
allocate a thread to serve the request; this thread will wait up to 20 s
(on HTTP) or 60 s. (on
On 17/10/2012 10:49, André Warnier wrote:
> 1) So it means that if a client connects to the server, but does not
> send any request line for a while on that connection, the server will
> allocate a thread to serve the request; this thread will wait up to 20 s
> (on HTTP) or 60 s. (on HTTPS), before
Pid wrote:
...
connectionTimeout="2" redirectPort="443" server="lighthttpd/2.0.0" enableLookups="false" acceptorThreadCount="4" socket.directBuffer="false"
compression="off" compressableMimeType="text/html,text/xml,text/plain,text/javascript,text/css,image/jpeg,
On 10/17/2012 1:28 AM, Mark Thomas wrote:
On 17/10/2012 07:59, Romain Van der Keilen wrote:
Hi There,
I'm quiet new to this mailing list as I encounter some configuration
problems with Tomcat 7.0.30.
It is unlikely to help but you may as well upgrade to 7.0.32.
We are currently developing a
Hi,
Sorry to keep replying to my own question but I gathered two stack traces from
each of the calls to init that may be useful:
On startup (and this is the servlet also used by the post):
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
at
org.apache
On 17/10/2012 08:59, Romain Van der Keilen wrote:
> Hi There,
>
> I'm quiet new to this mailing list as I encounter some configuration problems
> with Tomcat 7.0.30.
> We are currently developing a web application, and we wish to have a good
> response time with about 200 parallel sessions. My p
On 17/10/2012 07:59, Romain Van der Keilen wrote:
> Hi There,
>
> I'm quiet new to this mailing list as I encounter some configuration
> problems with Tomcat 7.0.30.
It is unlikely to help but you may as well upgrade to 7.0.32.
> We are currently developing a web
> application, and we wish to ha
Hi,
I wanted to add that I am accessing the servlet via a javascript request from
Apache HTTP. As such I am setting the following in the header of the POST
response:
resp.setHeader( "Access-Control-Allow-Origin", mAllowedHost );
Just wanted to mention this just in case it had anything
I have faced similar issues as well! I have quite similar tomcat6 over a
similar hardware infrastructure and sometimes we noticed some unavailable
issues as well!
I already tried tuning tomcat but not success! The only thing I did last time
was increase the maxthread from 200 to 500 and another
On 16.10.2012, at 15:26, majin_clo...@t-online.de wrote:
> Thanks for your reply. :)
>
> my web.xml looks like this:
>
>
> http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
> http
Hi There,
I'm quiet new to this mailing list as I encounter some configuration problems
with Tomcat 7.0.30.
We are currently developing a web application, and we wish to have a good
response time with about 200 parallel sessions. My problem is that starting
from 70 users, the system does not re
22 matches
Mail list logo
