I'm still up. lol I'm using spring security, weld, primefaces and JPA (hibernate as provider). So far I have already tested regular JSPs, servlets, JSF (pure and getting values from managed bean), primefaces, weld, spring security and JPA one by one, isolated. I didn't get even 2 of these set up at the same time (not even the jars on lib). I followed the exact same configuration I did on my application. So far I was not able to reproduce the error.
Tomorrow I may try combining them and/or try using VisualVM to analyze the error. Peter P. Lupo http://craftnicely.blogspot.com - http://sites.google.com/site/pplupo <http://sites.google.com/site/pplupo>MPS.BR Authorized Implementation Practitioner<http://www.softex.br/mpsbr/_profissionais/MPS.BR_certificados_de_arovacao_prova_P2-MPS.BR.pdf>- Certified ScrumMaster <http://www.scrumalliance.org/pages/certified_scrummaster> <http://www.scrumalliance.org/pages/certified_scrummaster>Oracle Certified Associate, Java SE 5/SE 6<http://in.sun.com/training/certification/java/scja.xml> - Java Black Belt <http://www.blackbeltfactory.com/ui#!User/pplupo> <http://www.blackbeltfactory.com/ui#!User/pplupo>+55 (021) 81742487 On Wed, Mar 16, 2011 at 12:21 AM, Peter P. Lupo <ppl...@gmail.com> wrote: > Oh, yeah, I forgot to mention the logs. They don't show any sign of error. > It's getting quite late here and I have to wake up early tomorrow so I will > just give it a break and keep testing tomorrow. > Thank you for the tips. I'll keep you posted. > > Regards, > > Peter P. Lupo > http://craftnicely.blogspot.com - http://sites.google.com/site/pplupo > <http://sites.google.com/site/pplupo>MPS.BR Authorized Implementation > Practitioner<http://www.softex.br/mpsbr/_profissionais/MPS.BR_certificados_de_arovacao_prova_P2-MPS.BR.pdf>- > Certified > ScrumMaster <http://www.scrumalliance.org/pages/certified_scrummaster> > <http://www.scrumalliance.org/pages/certified_scrummaster>Oracle > Certified Associate, Java SE 5/SE > 6<http://in.sun.com/training/certification/java/scja.xml> - > Java Black Belt <http://www.blackbeltfactory.com/ui#!User/pplupo> > <http://www.blackbeltfactory.com/ui#!User/pplupo>+55 (021) 81742487 > > > > On Tue, Mar 15, 2011 at 11:55 PM, Caldarale, Charles R < > chuck.caldar...@unisys.com> wrote: > >> > From: Peter P. Lupo [mailto:ppl...@gmail.com] >> > Subject: Re: Hard time finding a but on Tomcat 7 (doesn't happen on 6.) >> >> > I told you, the latest one. So it's 1.44. >> >> The problem is that different people have different views of what is >> "latest". We've had at least one user claiming to have the "latest" Tomcat >> installed, only to discover some days later that it was close to a year old >> - always best to provide the specifics. >> >> > The "exact" message is: >> > Exception in thread ""http-bio-8080"-exec-8" >> >> That's the name of a thread used by the <Connector> for port 8080 to >> service requests; the number on the end is simply incremented by one each >> time a new thread is started, up to the maximum configured for that >> <Connector>. The "bio" part indicates you're using the blocking I/O handler >> (which is the default). It's unlikely the message is being displayed by >> Tomcat itself, since Tomcat is pretty good at providing more comprehensive >> information, including a call stack. >> >> > Each new message comes with a higher ending number. >> >> Indicating the threads are getting stuck somewhere, and thus not available >> for reuse. Taking a thread dump might shed some light on the situation; you >> could also use JConsole or VisualVM to examine the presumably stuck threads >> and see where they're stuck and how they got there. >> >> Again, the logs may have some information pertinent to the problem. >> >> - Chuck >> >> >> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY >> MATERIAL and is thus for use only by the intended recipient. If you received >> this in error, please contact the sender and delete the e-mail and its >> attachments from all computers. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >
