It doesn't come from existing process, I've seen it once installing jetspeed on a new freshed installed tomcat too, the first access to jetspeed did that exception...
Using 1.3a2 and 1.4b1, I never saw it. Started with 1.4b2/3 Also I never saw it on tomcat 3.3.1, only on tomcat 4 (4.1.9, 4.1.12 and 4.1.18) but I don't know if it might be related, since it seems to happen "randomly" ! Weird stuff :) John Wubbel a �crit : > After you do a ./shutdown.sh have you checked to see if the shut down > was clean? Are there any process id(s) left over? Do a before and > after. ps -ax if there anything left over, try doing a kill on it, > then restart tomcat. Seems to me I saw this back when I first started > using Jetspeed 1.3a1 days but I attributed it to my own inexperience > to installation and configuration. > > John Wubbel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
