This content has been marked as final. Show 2 replies
I have a seam 2.0 app deployed on websphere 6.1 that is going down every few days. To build it I started from the JPA example.
After the application goes down I notice that the App server process using 99% CPU and in the server logs I get a
IllegalStateException: could not acquire lock on @Synchronized component : searchAction
the stack trace shows that it is originating from the
This is pretty frustrating since it seems to be a concurrency thing and is only happening in production.