Hi all,
since tomcat 7 is a stable release, I am wondering if it's ready for a
production use?
Which one (tomcat 6 or tomcat 7) is recommended for a production use?
Best regards,
Daniel
-
To unsubscribe, e-mail:
On 28/02/2011 08:31, Daniel Plappert wrote:
Hi all,
since tomcat 7 is a stable release, I am wondering if it's ready for a
production use?
Which one (tomcat 6 or tomcat 7) is recommended for a production use?
Tomcat 7. The ASF has been using it since 7.0.6 (the first stable
release) for
continue to the discussion-
How can I encrypt the password inside the xml file?
Thanks
Hila
בתאריך 27 בפברואר 2011 19:37, מאת הילה hilavalen...@gmail.com:
Original:
Does this happen all the time? Under what conditions? Are you able to
build a patched version of Tomcat in a test environment
From: הילה [mailto:hilavalen...@gmail.com]
Subject: Re: [OT] Memory Leak in Tomcat
How can I encrypt the password inside the xml file?
Short answer: pointless exercise.
Long answer: search the archives.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
On Friday 25 February 2011 17:21:07 Mark Thomas wrote:
On 25/02/2011 16:14, chris derham wrote:
Oliver said that the defect I was asking about was 50700. This appears to
have been fixed now. So when is the next release of tomcat scheduled? I
searched the tomcat pages, but can't see a page
Is there a programmatic way to retrieve it from within
a webapp, more exactly from within Servlet.init()? I
can't find one. Same question for the actual command.
As you may have guessed, I want to shut down Tomcat by
opening a socket and sending it a SHUTDOWN or whatever.
Maybe there is a less
Hi,
We are using Tomcat 6.0.24 running on two different machines. In our
workers.properties file, we have
worker.worker1.fail_on_status=500,503
to cause instances to gracefully fail over if there is a problem on one
instance. This is great, but if one app server is repeatedly failing over
to
On 28/02/2011 14:51, Rainer Frey wrote:
On Friday 25 February 2011 17:21:07 Mark Thomas wrote:
On 25/02/2011 16:14, chris derham wrote:
Oliver said that the defect I was asking about was 50700. This appears to
have been fixed now. So when is the next release of tomcat scheduled? I
searched
On 28/02/2011 15:34, Olivier Lefevre wrote:
Is there a programmatic way to retrieve it from within
a webapp, more exactly from within Servlet.init()? I
can't find one. Same question for the actual command.
As you may have guessed, I want to shut down Tomcat by
opening a socket and sending
On 28/02/2011 15:50, laredotornado wrote:
Hi,
We are using Tomcat 6.0.24 running on two different machines. In our
workers.properties file, we have
worker.worker1.fail_on_status=500,503
to cause instances to gracefully fail over if there is a problem on one
instance. This is great,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antonios,
On 2/24/2011 11:28 AM, Antonios Kogias wrote:
And I would like some clarification on Depending on exactly where the
Valve falls within the Valve chain and how the RequestDispatcher works
with Valves, it may or may not include time to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
הילה,
On 2/28/2011 5:17 AM, הילה wrote:
How can I encrypt the password inside the xml file?
0. $file = conf/server.xml
1. Use your favorite encryption tool to encrypt the password and shove
it into $file
2. Use that same tool in some code you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it may concern,
On 2/24/2011 8:34 AM, maven apache wrote:
Good question. What are PV, ip, and PU?
Thanks for your attention and Sorry for my negligence.
PV: page view, how many people visit a page.
IP: how many ips visitor the
Doing this from a servlet begs the question how you are going
to restart it.
Not an issue: I want to shut it down at startup if some needed
resources cannot be found. No pint restarting it then.
I'm also curious why you want tot do this but System.exit() will
have exactly the same result as
On 28/02/2011 16:12, Olivier Lefevre wrote:
Doing this from a servlet begs the question how you are going
to restart it.
Not an issue: I want to shut it down at startup if some needed
resources cannot be found. No pint restarting it then.
Fair enough. I wouldn't do it in a Servlet.init()
Your application may be on a shared Tomcat instance someday
and System.exit is really bad in that case.
True. So let's kill the servlet instead. But it's still unclear
how you'd do that because from the ServletConfig you can get the
ServletContext but from the ServletContext you can no longer
On 28/02/2011 16:59, Olivier Lefevre wrote:
Your application may be on a shared Tomcat instance someday
and System.exit is really bad in that case.
True. So let's kill the servlet instead.
If you want to stop a single Servlet then Servlet.init() is the place to
it. See section 2.3.2 of the
From: Olivier Lefevre [mailto:lefev...@yahoo.com]
Subject: Re: Getting the Tomcat shutdown port
Your application may be on a shared Tomcat instance someday
and System.exit is really bad in that case.
So let's kill the servlet instead.
The servlet, or the webapp?
But it's still unclear
Good Afternoon:
I am attempting to run a Windows x64 server with IIS7 and Tomcat 7. I have
64 bit versions of JDK (1.6.26) and Tomcat (7.0.8). The server is set up
with IIS using ajp1.3 to a local cluster of Tomcat servers. In performance
tests I have found the configuration runs
From: Bruce Pease [mailto:bpe...@wth.com]
Subject: IIS7/isapi/tomcat performance
In performance tests I have found the configuration runs
dramatically slower than it's corresponding server in 32
bit Windows on 2000 Server and Tomcat 6.
Until you quantify dramatically, better describe your
I agree with Charles. I run a performance Testing group for a fortune 50
company
and do alot of performance testing for different designs/implementation for my
own startup and we can not help you without further info.
Client side setup (Browser/version?)
Test cases
Network speed
Tomcat Setup
Perhaps my point is being missed here. The issue is moving from 32 bit is
slower in 64 bit (4-500% if you need a number). Components are the same,
setup is the same, database is the same, environment is the same, tests are
the same, network is the same. I'm basically looking to see if anyone is
On 2/28/2011 6:06 PM, Mark Thomas wrote:
If you want to stop a single Servlet then Servlet.init() is the
place to it. See section 2.3.2 of the Servlet 3.0 spec.
I.e., the exception throwing approach suggested by C. Caldarale in
the next answer. Yes, it's neat. So I was overcomplicating it.
On 28/02/2011 19:13, Olivier Lefevre wrote:
I know it's an interface I have to implement but without some
concrete class close to my problem to look at for guidance
LifecycleListener in and of itself does not help me much.
Ah, OK. Try this:
On 2/28/2011 6:09 PM, Caldarale, Charles R wrote:
The servlet, or the webapp?
The webapp in this case: the servlet that might fail is the
worker servlet, the others more in a supporting role (e.g.,
UI). So if it fails the whole webapp should shut down.
Why don't you simply throw a
JVM settings should not be the same.
Regards,
-Tony
- Original Message
From: Bruce Pease bpe...@wth.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Mon, February 28, 2011 11:46:35 AM
Subject: RE: IIS7/isapi/tomcat performance
Perhaps my point is being missed here. The issue
Since the memory pointers are larger you may need to increase your heap size
but
you can compress the address pointers.
Also, if you use JNI and it is 32-bit then you will have unexpected issues same
thing with any native libs your try to use.
Generally it will be up to 20% slower due to the
I forgot to mention new versions of Windows are slower than XP. So that would
contribute to your issues. Windows 7 got better but not as fast as 32-bit.
Also, you might want to measure from tomcat perspective so you have a new
baseline.
Regards,
-Tony
- Original Message
From: Tony
Thanks for the insight. It looks like we are going to go with server 2003 32
bit. I found some references that suggest ajp 1.3 has a performance issue in
64 bit server 2008.
-Original Message-
From: Tony Anecito [mailto:adanec...@yahoo.com]
Sent: Monday, February 28, 2011 3:01 PM
To:
Thank you Konstantin, for the clarification of details - now I got a
much better understanding of the issues involved.
My understanding is that the logAccess(...) call happens when the output
buffer has been flushed and closed (in http/1.0 that would also close
the tcp connection, thus I
?Which performance issue
2011/2/28 Bruce Pease bpe...@wth.com
Thanks for the insight. It looks like we are going to go with server 2003
32
bit. I found some references that suggest ajp 1.3 has a performance issue
in
64 bit server 2008.
-Original Message-
From: Tony Anecito
Sure no problem. I also use Native APR with Tomcat 7 which eliminates AJP and
supposidly is faster than Apache Web Server but then you use IIS probably for
good reason so it would not help you to use APR.
Good luck,
-Tony
- Original Message
From: Bruce Pease bpe...@wth.com
To:
A security audit of my site indicated a Missing HttpOnly attribute in Session
Cookie problem. If this is a security problem, then why does the useHttpOnly
attribute in Context default to false? I'm not specifically setting any
cookies...
On 28/02/2011 21:31, Leo Donahue - PLANDEVX wrote:
A security audit of my site indicated a Missing HttpOnly attribute in
Session Cookie problem. If this is a security problem,
In and off itself a missing httpOnly attribute is not a security
vulnerability. It is, however, a good idea to enable
Does Tomcat 7.0.8 support the Servlet 3.0 security annotations?
@RolesAllowed
@DeclareRoles
@ServletSecurity
, etc.?
thanks,
Mike
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail:
On Monday 28 February 2011 16:53:00 Mark Thomas wrote:
On 28/02/2011 14:51, Rainer Frey wrote:
On Friday 25 February 2011 17:21:07 Mark Thomas wrote:
6.0.33 is likely to be several months away. I don't see anything in the
change log that is likely to prompt an earlier release.
Ouch.
36 matches
Mail list logo
