Re: Tomcat 7.0.23 won't start
Add a Realm definition or wait until 7.0.24. There's a bug in 7.0.23. I am waiting for 7.0.24. I'm wincing as I ask: is there a particular reason that you're defining the Context in server.xml - it's been strongly recommended to not do that for quite a while. Okay, I will byte. Practical: This was my sandbox config file. I switch between 6 different applications. I do this by switching server.xml files when I switch projects. This keeps things minimal (not starting up 6 connection pools), its easier to switch one file, and it makes restarts faster. Opinion: I hate over decomposition and I preferred the days when tomcat was only configured with server.xml. Tomcat's configuration is not that complicated, do we really need a bunch of configuration files. Its bad when one thing becomes two, and hence good when two things become one. I bet your also in the micro kernel camp. I know lots of people clamored for being able to configure the connection pool in there war file. I don't know why anyone would do this, our WAR file runs in any environment where the jndi name is present. They have to build separate WAR files for each environment. Basicly I think the context.xml is stupid. If it matters so much change the document definition. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Re: Tomcat 7.0.23 won't start
Chris, Flame bait ignored. Your a better man than me :) I couldn't ignore the attack on my server.xml when I was working a bug. Jacob - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 7.0.23 won't start
Is anyone else having trouble getting 7.0.23 to start up? I am trying to migrate from 7.0.22 to 7.0.23 and Tomcat hangs on: INFO: Starting Servlet Engine: Apache Tomcat/7.0.23 If I use the default server.xml it starts up, but if I use our custom server.xml it doesn't (See Below). We have been using the same config since the 7.0 release, so I am not sure what is going on. There are no errors thrown, it just hangs. OS: openSuSE 11.4 Java: 1.7.0_01 (64 bit) ?xml version='1.0' encoding='utf-8'? Server port=8005 shutdown=SHUTDOWN Service name=Catalina Connector port=8009 protocol=AJP/1.3 tomcatAuthentication=false / Engine name=Catalina defaultHost=localhost Host name=localhost appBase=webapps Context path=/company docBase=/home/jacobc/workspace/company/web reloadable=false allowLinking=true processTlds=false Manager className=org.apache.catalina.session.StandardManager pathname= / Resource name=jdbc/company auth=Container type=javax.sql.DataSource maxActive=10 maxIdle=1 maxWait=12 username=webapp password= driverClassName=org.postgresql.Driver url=jdbc:postgresql://widow:5432/company validationQuery=SELECT 1 + 1 / /Context /Host /Engine /Service /Server - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7.0.23 won't start
Found the answer here: http://www.mail-archive.com/users@tomcat.apache.org/msg94574.html Sorry I missed this, we are experiencing the no Realm locking and will be skipping 7.0.23 . On 12/06/2011 01:20 PM, Jacob Champlin wrote: Is anyone else having trouble getting 7.0.23 to start up? I am trying to migrate from 7.0.22 to 7.0.23 and Tomcat hangs on: INFO: Starting Servlet Engine: Apache Tomcat/7.0.23 If I use the default server.xml it starts up, but if I use our custom server.xml it doesn't (See Below). We have been using the same config since the 7.0 release, so I am not sure what is going on. There are no errors thrown, it just hangs. OS: openSuSE 11.4 Java: 1.7.0_01 (64 bit) ?xml version='1.0' encoding='utf-8'? Server port=8005 shutdown=SHUTDOWN Service name=Catalina Connector port=8009 protocol=AJP/1.3 tomcatAuthentication=false / Engine name=Catalina defaultHost=localhost Host name=localhost appBase=webapps Context path=/company docBase=/home/jacobc/workspace/company/web reloadable=false allowLinking=true processTlds=false Manager className=org.apache.catalina.session.StandardManager pathname= / Resource name=jdbc/company auth=Container type=javax.sql.DataSource maxActive=10 maxIdle=1 maxWait=12 username=webapp password= driverClassName=org.postgresql.Driver url=jdbc:postgresql://widow:5432/company validationQuery=SELECT 1 + 1 / /Context /Host /Engine /Service /Server - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
7.0.21 Redirects failing randomly
Last night we went to 7.0.21, and this morning I had to roll it back because very randomly redirects were failing. It was very much like all parameters to the redirect were lost. I am still trying to debug this, but its clear its not happening in 7.0.20, which leads me to believe its: 41718: Include a response body when sending a redirect. (markt) or one of the AJP changes. We are running Apache 2.2.21 with mod_ajp. Our servlet framework is Stripes MVC and it seems to conform to the requirement in 41718. Is anyone else having this issue? Thank you, Jacob Champlin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: 7.0.21 Redirects failing randomly
We have finished debugging this issue. It turns out that what is happening is in 7.0.21 responses are returning to the client before the filter chain is complete. In 7.0.20 all filters complete before the response is returned to the client. In our particular case, we have a TransactionFilter managing our DB transactions, so the response page was rendering before the DB transaction was commited giving the appearance that the post didn't succeed. I think this is a MAJOR regression in 7.0.21. Jacob Champlin On 09/27/2011 10:35 AM, Jacob Champlin wrote: Last night we went to 7.0.21, and this morning I had to roll it back because very randomly redirects were failing. It was very much like all parameters to the redirect were lost. I am still trying to debug this, but its clear its not happening in 7.0.20, which leads me to believe its: 41718: Include a response body when sending a redirect. (markt) or one of the AJP changes. We are running Apache 2.2.21 with mod_ajp. Our servlet framework is Stripes MVC and it seems to conform to the requirement in 41718. Is anyone else having this issue? Thank you, Jacob Champlin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: 7.0.21 Redirects failing randomly
Konstantin, I believe the new flushBuffer() call you added to Response.java sendRedirect() line #1340. Is breaking all ServletFilters but sending buy flushing the response before filters have a chance to modify the response. Jacob On 09/27/2011 10:35 AM, Jacob Champlin wrote: Last night we went to 7.0.21, and this morning I had to roll it back because very randomly redirects were failing. It was very much like all parameters to the redirect were lost. I am still trying to debug this, but its clear its not happening in 7.0.20, which leads me to believe its: 41718: Include a response body when sending a redirect. (markt) or one of the AJP changes. We are running Apache 2.2.21 with mod_ajp. Our servlet framework is Stripes MVC and it seems to conform to the requirement in 41718. Is anyone else having this issue? Thank you, Jacob Champlin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: 7.0.21 Redirects failing randomly
Konstantin, Ok, so I see now why you added the flushBuffer() from spec: http://java.sun.com/javaee/6/docs/api/javax/servlet/http/HttpServletResponse.html#sendRedirect%28java.lang.String%29 Sends a temporary redirect response to the client using the specified redirect location URL and clears the buffer. Its just we have been running Tomcat, for 5 years and we have lots of code that relied on the fact that sendRedirect did not flush the buffer. I will drop it, but going to be a while before we can go to 7.0.21. Jacob On 09/27/2011 02:32 PM, Jacob Champlin wrote: Konstantin, I believe the new flushBuffer() call you added to Response.java sendRedirect() line #1340. Is breaking all ServletFilters but sending buy flushing the response before filters have a chance to modify the response. Jacob On 09/27/2011 10:35 AM, Jacob Champlin wrote: Last night we went to 7.0.21, and this morning I had to roll it back because very randomly redirects were failing. It was very much like all parameters to the redirect were lost. I am still trying to debug this, but its clear its not happening in 7.0.20, which leads me to believe its: 41718: Include a response body when sending a redirect. (markt) or one of the AJP changes. We are running Apache 2.2.21 with mod_ajp. Our servlet framework is Stripes MVC and it seems to conform to the requirement in 41718. Is anyone else having this issue? Thank you, Jacob Champlin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
