Found it. Turns out it wasn't a caching problem at all. I have a threaded job manager that was being used by this action class. There was a weird exception being thrown that wasn't getting caught which was locking the thread. This action was getting reused by Struts, but never did anything because it was still blocking on the locked thread.
I've fixed it and learned much, but is there any way to get more control over the caching? Do you have to subclass ActionServlet or the RequestProcessor to do that? I would think there would be instances where you would want a pool of actions instead of only one instance of each. Once this release gets out I'm going to look at it more, but I was just curious about whether anybody has looked into this. Jeff. -----Original Message----- From: Whitmire, Jeffrey [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2003 4:07 PM To: '[EMAIL PROTECTED]' Subject: ActionServlet Action caching problem I've got a weird one. I'm hoping that somebody else has encountered this before and can help. We are in the midst of load testing our app before rolling it out to production. I have one action class (only one) that starts failing well over an hour into the test. It appears that the instance of that action class cached by the ActionServlet becomes invalid. I can see no reason why the change in behaviour, but at some point the RequestProcessor gets an instance to the Action that is no longer valid. It is not null, but it never executes it. The rest of the app works perfectly, but that button (tied to that specific Action) never works again until the tomcat instance is restarted. It just hangs, and the last indication in the log is the RequestProcessor finding and returning an instance of that action class. Has anyone ever had problems with Action instances going stale? or some other config problem that could cause this? Thanks, I'm a bit desparate, Jeff. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
