Firstly apologies to anyone I have sent an unsolicited reply to
personally, Stupid, tired, It won't happen again
Thanks to all for the responses so far
The problem with using the startup and shutdown scripts is that the
process ends up running as root. As any
server admin worth his salt will tell
Would you mind posting your server.xml, here is the relevant bit from mine.
On 18 March 2016 at 23:35, Daniel Savard wrote:
> I believe all distros have over engineered the scripts to start
> Tomcat. Forget all the scripts
On 17 March 2016 16:06:10 GMT+00:00, Paul Benedict wrote:
>This question is not about Tomcat per se, but it does affect it. It's
>really about the EE specification in regards to any servlet container.
>I'd
>like to get professional opinions on this part of the specification.
>
>I am quoting from E
On 3/17/2016 3:32 PM, Edwin Quijada wrote:
> Hi! I am using Tomcat + APache +Postgres in the same machine server
> with 8GB Ram I wanna know what is the best configuration memory or
> anything else for better performance of my Tomcat?
>
> I have 400 user +-
>
>
> My app is Grails + Vaadin +Postg
Thks, !
For postgres I dont have problem because I have xp with this but for Tomcat and
Java and newbie with big projects .
I am using Java 8
From: Mark Eggers
Sent: Thursday, March 17, 2016 11:30 PM
To: Tomcat Users List
Subject: Re: Memory and resource
Hi everyone,
I noticed a problem with one of my web applications which requires
some cleanup when shutdown. It seems this cleanup isn't happening even
if everything has been put in the contextDestroyed() method of my web
listener. So, to debug this problem I wrote a minimal web listener and
tested
Hi!
I am using Tomcat + APache +Postgres in the same machine server with 8GB Ram I
wanna know what is the best configuration memory or anything else for better
performance of my Tomcat?
I have 400 user +-
My app is Grails + Vaadin +PostgreSQL
Or remove the Type=Forking and just execute catalina.sh run, as I had
suggested days ago. Then you can drop the ExecStop too.
On Fri, Mar 18, 2016 at 7:35 PM, Daniel Savard wrote:
> I believe all distros have over engineered the scripts to start
> Tomcat. Forget all the scripts from your distro,
I believe all distros have over engineered the scripts to start
Tomcat. Forget all the scripts from your distro, learn the
signification of the environment variables from the catalina.sh script
shipped with the default Tomcat version. Define your variables in a
file, this file is not a script, so y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jieryn,
On 3/16/16 1:36 PM, jieryn wrote:
> http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/systemd-house
- -of-horror/tomcat.html
Wow,
>
lots of ranting about environment variables and little-used PID
files.
If the author only understood
On 15/03/2016 20:58, Harish Krishnan wrote:
> Hello There,
>
> I am kind of blocked here in my project while applying your CVE fix in our
> product & verify the fix. Any guidelines on what i am doing (mentioned in
> my previous email) wrong is highly appreciated.
You are failing to follow the hi
Nevermind, the contextDestroyed() method is actually called as
supposed and expected. The problem seems the logger is no longer able
to output anything in the log file at this point even if I configured
it to flush immediately the output. I replaced the log.info()
statement by a System.out.println(
On 18/03/2016 15:06, Theo Sweeny wrote:
> Hi Mark,
> hanks for the reply - the developers are pushing back as they believe Tomcat
> should kill off any rogue webapps after a certain timeframe as this is how
> they have it done in Weblogic.
I believe WebLogic runs each web application in a sep
13 matches
Mail list logo