REMOVE THE MAILING LIST FROM YOUR SUPPORT EMAIL ADDRESSSSSS Re: DO NOT REPLY [Bug 36518] New: -

--- [EMAIL PROTECTED] wrote: > We heartily thank you for your support & interest in > our offerings. We appreciate & value your mails. We > will soon contact you to take this further, as > appropriate. > > Thank you, > > mie consultants inc. > > > > ---

Re: DO NOT REPLY [Bug 36541] - session getAttribute/setAttribute and removeAttribute are NOT Thread safe.

--- Remy Maucherat <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > I'm not even sure if I've been bitten by this > either, but I have seen on the > > list numerous people speaking of running out of > Tomcat threads and setting their > > connections to the max. If this issue were > causi

Re:ACTUAL EMAIL .... - session getAttribute/setAttribute and removeAttribute are NOT Thread safe.

--- Remy Maucherat <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR > BUG· > > RELATED COMMENTS THROUGH THE WEB INTERFACE > AVAILABLE AT > > > . > > ANY REPLY MADE TO THIS MESSAGE WIL

Re: commons-logging infinite loop w/5.5.9

--- Nathan Bubna <[EMAIL PROTECTED]> wrote: > On 8/23/05, Remy Maucherat <[EMAIL PROTECTED]> wrote: > > Nathan Bubna wrote: > > > hey folks, > > > > > > i'm a developer on the VelocityTools subproject, > and we recently came > > > across an issue with the use of commons-logging > in Tomcat 5.5.9.

Re: Input stream

You can use different things, but directly programming you can use SAX2, XMLReader, and XMLReaderFactory.createXMLReadersee JDK javax.xml package documentation. You could use a DOM object, but I wouldn't recommend it because of memory usage. You can change the underlying XML parser impls for