Servlet plugin is throwing an error

[Matt Sommer]

We have a custom plugin servlet. It's throwing errors but we aren't sure what they mean. The plugin seems to be working as needed but we're worried about the error messages. Any idea what could be causing this error?

The servlet is performing gets and posts.

2014-01-31 12:12:01,884 http-bio-8080-exec-5560 ERROR anonymous 732x654908x2 l1fg3m xx.xx.xx.xxx /plugins/servlet/hrmobility [filters.steps.requestcleanup.WebworkActionCleanupStep] Thread corrupted! ActionContext still references a HttpSession. URL: 'https://issues.xxxxxxxx.com/plugins/servlet/hrmobility'

2014-01-31 12:38:44,195 http-bio-8080-exec-5579 ERROR anonymous 758x658075x2 1k8j9u4 xx.xx.xx.xxx /plugins/servlet/hrmobility [filters.steps.requestcleanup.WebworkActionCleanupStep] Thread corrupted! ActionContext still references a HttpSession. URL: 'https://issues.xxxxxxxx.com/plugins/servlet/hrmobility'

2014-01-31 12:43:58,470 http-bio-8080-exec-5577 ERROR anonymous 763x658527x2 173oe7p xx.xx.xx.xxx /plugins/servlet/hrmobility [filters.steps.requestcleanup.WebworkActionCleanupStep] Thread corrupted! ActionContext still references a HttpSession. URL: 'https://issues.xxxxxxxx.com/plugins/servlet/hrmobility'

[JPB]

Hello Matt.

Look at this post: https://answers.atlassian.com/questions/292563/createworklog-thread-corrupted-actioncontext-still-references-a-httpsession

There, I gave some answer to that, that's what I could find. Greetings.

[Matt Sommer]

Unfortunately, no. I think it might have went away from uninstalling, reinstalling, then restarting the web server but I don't know that for sure. I don't have access to the logs anymore so I'm not sure if we are still getting the error. Good luck!

[JPB]

Hello Matt, could you solve this?

I got a similar problem.

[John Garcia]

Matt,

This is a Context that was cleaned by the system because its http context was abandoned. It seems likely to be a timeout on something.

Please consider increasing logging on webwork.util.ServletValueStack to DEBUG to get more information. This should expose the session that was involved with the call that was abandoned.

Thanks!