maybe the two tomcats are sharing a work dir so the two wicket apps might be sharing disk store files...
-igor On Tue, Oct 18, 2011 at 7:35 AM, Jonathan Locke <jonathan.lo...@gmail.com> wrote: > I have two wicket applications running on the same box (my laptop, for > example) with one on port 8880 and one on port 8881. Each application does > ajax-self-updating. Now, if I start the first application, all is well and > will stay well forever as far as I can tell. But the exact moment i start up > the second application, the first application suddenly gets either a page > expired error (under wicket 1.4) or an error regarding behaviors (under > wicket 1.5). I've tried this over and over and it's not a fluke. Anyone have > any idea what's going on? My best guess is that somehow Tomcat is > misconfigured (I'm starting it embedded)? But how might that be? > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/page-expire-ajax-error-tp3915594p3915594.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
