On 08/12/2011 15:04, Jacob Champlin wrote:
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
On 08/12/2011 18:42, Christopher Schultz wrote:
Jacob,
On 12/8/11 10:04 AM, Jacob Champlin wrote:
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
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.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jacob,
On 12/8/11 10:04 AM, Jacob Champlin wrote:
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
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,
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
On 06/12/2011 18:20, 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
