So I digged into this and discovered something strange. On the server that was working it had jre 6u24 and on the one not working it had jre 6u29. I could'nt restart the server, but after installing jdk 6u25 it actually worked..
This is not good. It could prove hard to replicate with other framework stacks, Im using a combo of mybatis, guice 3, wicket 1.5.3.. Anybody else using this on jre 6u29 on tomcat 7? regards Nino 2011/11/17 nino martinez wael <nino.martinez.w...@gmail.com> > THANKS! > > > 2011/11/17 Andrea Del Bene <adelb...@ciseonweb.it> > >> Profile the stalled server with Visual VM? It should detect existing >> deadlocks... >> >>> Hi >>> >>> I have a very strange problem. At a customers site we have 2 servers >>> with 1 >>> Tomcat 7 installed each. One day on one of the servers our application >>> just >>> stalled after loading the sign in page, when you click the login button. >>> Im >>> not sure this is a wicket problem. Heres what I've tried so far: >>> >>> >>> - Restart Tomcat >>> - Point the working application at the non working servers sql >>> database, >>> it still works. >>> - Purge Tomcats session storage and temporary files >>> - Restart the server >>> - Redeploy the application, with the war from the working server (just >>> >>> to be sure) >>> >>> I've even tried setting up SQL Profiler and sniffing on the database >>> connections, nothing strange goes on here. Just seems like the >>> application >>> stalls when you try to login. Keep in mind that this works without >>> problems >>> from the other server. >>> >>> >>> >>> regards Nino >>> >>> >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> users-unsubscribe@wicket.**apache.org<users-unsubscr...@wicket.apache.org> >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >
