Re: can't start tomcat5.5.31

2011/1/9 Tim Clotworthy : > Thanks for assistance. I installed the 64bit 6u22. Tomcat still will not > start, and I get the same error as I did with the 32 bit jre. I would be > grateful for any other ideas. Thank you! > Was there an UAC prompt displayed while you were installing it? If not, try

RE: can't start tomcat5.5.31

Thanks for assistance. I installed the 64bit 6u22. Tomcat still will not start, and I get the same error as I did with the 32 bit jre. I would be grateful for any other ideas. Thank you! -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Friday, Janu

Re: Tomcat6 with mod_jk

Hello, What I am trying unsuccessfully to do is - on debian (lenny) with apache2 have multiple instances of tomcat6 each servicing a different domain using a java war/servlet To date I have only loaded one domain "appledorera.org" file /etc/apache2/mods-enabled/jk.load is LoadModule jk_modul

Re: Polling servlet and session expiration - avoid calling request.getSession() ?

On 01/09/2011 12:52 AM, Konstantin Kolinko wrote: > [1] > http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html#Specification Oops! sorry, i've missed that one! Now it's perfectly clear. Thanks for your help. Alberto --

Re: Polling servlet and session expiration - avoid calling request.getSession() ?

2011/1/8 rom : >  hi all, > I have to implement a polling mechanism that repeatedly sends a request > to a servlet. > This servlet doesn't need the user session, and i don't want these > requests to update the session's lastAccessedTime, thus preventing > regular session timeout when the user isn't

RE: Tomcat 6 logging clog

Here is the result of "ps -aef | grep java" timmy15563 1 0 Jan08 pts/100:05:38 /home/timmy/jdk1.6.0_18/bin/java -Djava.util.logging.config.file=/home/timmy/apache-tomcat-7.0.5/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorse

Re: Tomcat 6 logging clog

2011/1/8 Tim Space : > Another problem with this logging situation is that my webapp takes more than > two minutes to load after startup. That is expected. Logging inside Digester takes a lot of time. > org.apache.jasper=SEVERE > org.apache.tomcat.util.file.Matcher=SEVERE > org.apache.tomcat.ut

Re: Tomcat 6 busy threads issue

Christopher, On Thu, 2011-01-06 at 12:23 -0500, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Kobi, > > On 1/6/2011 12:14 PM, Kobi Biton wrote: > > -Tomcat 6.0.22 > > Great. Any opportunities to upgrade? Your version was never released and > is over a year old.

Re: Accessing context information remotely - Context.getAvailable() etc.

Thanks for that - The client tool i am writing is running on the same machine as the application which is firewalled. There is no direct access to the webapp except via an AJP port which is only accessible via Apache Webserver. Thanks On Sat, Jan 8, 2011 at 4:07 PM, Konstantin Kolinko wrote: > 2

Re: Tomcat 6 logging clog

On 1/8/11 7:10 AM, Tim Space wrote: > > > > > As advised I removed every version of tomcat on my system. There were two or > three others besides the version I was running: > /usr/share/java/tomcat5 > /etc/tomcat5 > /var/lib/tomcat5 > I have always started Tomcat with the sh startup.sh script

Re: Accessing context information remotely - Context.getAvailable() etc.

2011/1/8 zigg...@gmail.com : > Yes I guess you are right that launching the jmx every minute could be > expensive resourcewise... i am wondering whether it will be less expensive if > I just start a thread and same it up every minute... this way the jmx engine > will only be started once... One

Polling servlet and session expiration - avoid calling request.getSession() ?

hi all, I have to implement a polling mechanism that repeatedly sends a request to a servlet. This servlet doesn't need the user session, and i don't want these requests to update the session's lastAccessedTime, thus preventing regular session timeout when the user isn't doing anything else. I've

Re: Accessing context information remotely - Context.getAvailable() etc.

Yes I guess you are right that launching the jmx every minute could be expensive resourcewise... i am wondering whether it will be less expensive if I just start a thread and same it up every minute... this way the jmx engine will only be started once... I can't really have the monitoring tool