RE: Question about Tomcat memory leaks

Hi Guenter, You could have a look at: http://wiki.apache.org/tomcat/FAQ/Memory But since you describe "server" memory exhaustion, you should use Windows perfmon tool to log process memory (see HOW TO: Create and Configure Performance Monitor Trace Logs, http://support.microsoft.com/?kbid=302552

Content of Thumbs.db files (was RE: [VOTE] Release build 6.0.16)

I think that it is safe to ship the thumbs.db inside the archives. Thumbs.db is the image thumbnail database generated by Windows Explorer when you display images in Explorer. So it will only deliver information about the images in the directory where it sits. You can use http://www.dmthumbs.com/

What about 6.0.16 ?

There was a discussion about tagging 6.0.16 at the same time as 5.5.26. Any news ? Christophe -Message d'origine- De : Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Envoyé : dimanche 27 janvier 2008 21:12 À : Tomcat Developers List Objet : reminder 5.5.26 reminder, I will be tagging

RE: new year, new version? 6.0.16

Maybe some patches could be prioritized and planned to different releases (6.0.17, ...), the amount of available pending patches should not prevent from delivering a much awaited release. In my case, it is very much awaited, I am currently using unofficial 6.0.15 for my product , despite the neg

RE: max number of concurrent requests

. Best regards, Christophe Pierret -Message d'origine- De : brien colwell [mailto:[EMAIL PROTECTED] Envoyé : samedi 1 décembre 2007 23:23 À : dev@tomcat.apache.org Objet : max number of concurrent requests hi all, I'm building a framework that needs to block on HTTP requests. Tha

RE: PKCS11 and server.xml

Luis, If you want to maximize your chances to get your patch into the tomcat codebase, the usual method is: 1) Submit an issue to tomcat bugzilla 2) Develop and test a patch that fixes the issue you submitted 3) Submit the patch against your version to bugzilla (and also submit a version of your

RE: trunk development

I would very gladly test the comet write implementation (as well as NIO improvements) ! This is a feature I will use if stable. Christophe Pierret -Message d'origine- De : Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Envoyé : vendredi 14 décembre 2007 20:53 À : Tomcat Devel

Executing user code in Poller Thread for NIO connector on timeout (executor is specified in server.xml)

ocketStatus.TIMEOUT ) return; // don't close on comet timeout to: processSocket(ka.getChannel(), status, status == SocketStatus.TIMEOUT);//don't dispatch if the lines below are cancelling the key if (status == SocketStatus.TIMEOUT ) return; // don't close on comet timeout Best regards, Christophe Pierret

RE: Re: reload on demand

JetBrains IntelliJ IDEA supports reloading classes when you decide by the menu "Run"/"Reload Changed classes". This option only works if you did not modify the structure of the classes (e.g.: by adding methods). It uses support from the JVM debugging APIs so it works very well, it will manage ex

RE: Re: reload on demand

> Kent Tong writes: > > Yoav Shapira apache.org> writes: > > > There's reloadable as a Context attribute, documented at > > http://tomcat.apache.org/tomcat-5.5-doc/config/context.html, and you > > can also define a list of static resources (not classes) to be watched > > to trigger a reload

RE: [VOTE] Release build 6.0.9

I am not a committer, but for the purpose of a quite big web application (more than 15 man-years of dev effort) tested on 6.0.9 code level, both with APR and NIO HTTPS connectors, some parts using Comet API, I found that 6.0.9 was at least as good as 5.5.20 in terms of stability, performance an

RE: Comet API and InputStream.available()

EMAIL PROTECTED] Envoyé : mercredi 24 janvier 2007 14:48 À : Tomcat Developers List Objet : Re: Comet API and InputStream.available() Christophe Pierret wrote: > Here is what I understood: > > Assumption #1: When you receive a > CometEvent.EventType.READ event, you can

RE: Comet API and InputStream.available()

data to be read -1 end of stream reached I don't think we have -1 in our values, as that would only happen if the client closed the connection, and at that point we will probably call another event, although initially I know the NIO connector calls read with 0 data to be read Filip C

Comet API and InputStream.available()

NPIOException; byte get() throws NPIOException; void get(byte[] dst, int offset, int length) throws NPIOException; } Sorry, it was a bit long, but shorter would not have been quite clear... Even if I don't think this is very clear yet ;-) Christophe Pierret -Message d'

Congratulations to tomcat developers for the Comet API

sion versus previous version... Keep on the good work ! Christophe Pierret