Re: JSF + tag files problem with new Tomcat

Mark Thomas wrote: In short, no implicit.tld has been defined for the tag library so the spec mandates that a JSP version of 2.0 is used. JSP 2.0 doe snot support the #{...} syntax for EL so it gets treated as template text. Prior to the fix, Tomcat incorrectly used JSP 2.1 for implicit tag libr

Re: JSF + tag files problem with new Tomcat

On 10/07/2010 19:51, Mikolaj Rydzewski wrote: > Hi, > > There's a JSF webapp I maintain. It runs fine on Tomcat 6.0.18. Recently > I wanted to migrate environment to 6.0.26 but I ran into problems. Due > to lack of time I just dropped migration idea. Unfortunately the same > problem exists with To

JSF + tag files problem with new Tomcat

Hi, There's a JSF webapp I maintain. It runs fine on Tomcat 6.0.18. Recently I wanted to migrate environment to 6.0.26 but I ran into problems. Due to lack of time I just dropped migration idea. Unfortunately the same problem exists with Tomcat 6.0.28. Basically, the problem is with handling

Re: Tomcat 7.0, logging configuration

On 10/07/2010 05:22, Caldarale, Charles R wrote: >> From: Pid [mailto:p...@pidster.com] >> Subject: Re: Tomcat 7.0, logging configuration >> >> On 09/07/2010 22:32, André Warnier wrote: >>> >>> I believe the same section is also part of the >>> logging.properties file distributed with Tomcat. >>>

Re: Connecting Tomcat to a database

On 10/07/2010 05:15, Caldarale, Charles R wrote: >> From: Christian Bruckhoff [mailto:christian.bruckh...@gmx.de] >> Subject: Re: Connecting Tomcat to a database >> >> ERROR - GeronimoLog.error(108) | Failed to resolved external >> DataSource at "java:comp/env/jdbc/TestDB". >> javax.naming.NameNot

Re: when memory leak, tomcat can't accept requests?

Pid wrote: On 10/07/2010 10:19, jikai wrote: Because it's already saturated with requests? No server has an infinite capacity. How many threads did jstack report were running? Can you connect with JMX and see what state the connector is in? Are you using an Executor in combination with your

Re: when memory leak, tomcat can't accept requests?

On 10/07/2010 10:19, jikai wrote: >> Because it's already saturated with requests? No server has an infinite >> capacity. How many threads did jstack report were running? >> >> Can you connect with JMX and see what state the connector is in? >> >> Are you using an Executor in combination with you

Re: when memory leak, tomcat can't accept requests?

> Because it's already saturated with requests? No server has an infinite > capacity. How many threads did jstack report were running? > > Can you connect with JMX and see what state the connector is in? > > Are you using an Executor in combination with your Connector? Thanks for your quick repl

Re: when memory leak, tomcat can't accept requests?

On 10/07/2010 08:55, jikai wrote: > I give more details when error occurs: > 1) nginx suddently report lots of " Connection timed out" like this > 2010/07/09 19:26:37 [error] 11558#0: *3067544729 connect() failed (110: > Connection timed out) while connecting to upstream, ... > > 2) there are stil

Re: when memory leak, tomcat can't accept requests?

I give more details when error occurs: 1) nginx suddently report lots of " Connection timed out" like this 2010/07/09 19:26:37 [error] 11558#0: *3067544729 connect() failed (110: Connection timed out) while connecting to upstream, ... 2) there are still a few requests can connect tomcat and well p

Re: when memory leak, tomcat can't accept requests?

On 10/07/2010 06:32, jikai wrote: > Hi all: > > Out web site use Nginx infront of tomcat6.0.28, nio connector, in heavy > load running about 24 hours, tomcat can't accept request, we must restart > tomcat . > > check nginx error log, there are lots of "Connection timed out", print > tomcat js