-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger,
Roger Parkinson wrote:
> Useful stuff, thanks. We don't use any filters in the app, but we do
> have a db. I'll get them to check it out for deadlocks and get a
> stacktrace.
> Still a puzzle why a little demo setup gives this and the live apps
Useful stuff, thanks. We don't use any filters in the app, but we do
have a db. I'll get them to check it out for deadlocks and get a stacktrace.
Still a puzzle why a little demo setup gives this and the live apps
don't. It will be interesting when we know.
Anyway, good general approach advice.
Looks like a deadlock occuring at your db. You probably have a filter
that applies to each request and is deadlocking in some way. The reason
you can still reach the login page is that login page is served by
tomcat without getting through the filters.
The best way, if you have remote access to ap
Sorry this is question is so terse, but general approach kind of help
would be very welcome.
I get to the login page every time, but after that there's no response.
Seems to be nothing relevant in the logs.
The machine is remote from me and in a 12 hours different timezone
(yawn...zzz) so gett
