StorageCleaner and java:comp/UserTransaction in JBoss EAP 6.1

[Paul Hethmon]

It only runs on start up to handle orphaned sessions. Shib runs a
SessionCleaner process but it only knows about in-memory sessions. So a
restart drops all of the in-memory sessions, hence the need for a one-time
manual cleanup. Since that task can take a measurable amount of time, I
throw it into another thread to prevent delays.

I do tend to believe it's being a bit paranoid to prevent a separate
thread from accessing the DB. Instead, the access should only allow it to
manipulate the session table which the storage service owns (lock, stock
and barrel).

However, it's not much trouble to add an option to disable it, so I'll get
that added.

Paul


On 11/21/13 9:29 AM, "Brian Reindel" <brian at reindel.com> wrote:

>I think an ERROR level is the right level to log if it is expected
>behavior that a session cleanup routine be run at startup. However, I
>also think that I should be able to turn it off in the storage service
>configuration. If it is only running once at startup then it wouldn't
>be robust enough for our purposes. If we left the server up for a week
>then nothing is getting cleaned anyhow until we restart. It's not a
>huge deal. Just one of those things where if another developer or
>administrator were to come across it they may spend unnecessary time
>trying to track down why. So I figured I would at least ask if there
>is a configuration option somewhere, but it sounds like there isn't.
>