StorageCleaner and java:comp/UserTransaction in JBoss EAP 6.1

[Brian Reindel]

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.


On Wed, Nov 20, 2013 at 7:00 PM, Paul Hethmon
<paul.hethmon at clareitysecurity.com> wrote:
> Brian,
>
> So is the problem that it does log an ERROR level? Because it runs once
> and then exits, so it will only happen on startup.
>
> Paul
>
>
> On 11/19/13 4:41 PM, "Brian Reindel" <brian at reindel.com> wrote:
>
>>The java:comp/UserTransaction is not exposed by the container to
>>independent threads. So when the server starts up we get the following
>>exception:
>>
>>16:25:57,318 ERROR [org.hibernate.transaction.JTATransaction]
>>(Thread-100) Could not find UserTransaction in JNDI:
>>javax.naming.NameNotFoundException: java:comp/UserTransaction
>>        at
>>org.jboss.as.naming.InitialContext.findContext(InitialContext.java:198)
>>        at
>>org.jboss.as.naming.InitialContext.lookup(InitialContext.java:118)
>>        at
>>org.jboss.as.naming.NamingContext.lookup(NamingContext.java:183)
>>        at
>>org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
>>        at javax.naming.InitialContext.lookup(InitialContext.java:411)
>>[rt.jar:1.7.0_25]
>>        at
>>org.hibernate.transaction.JTATransaction.<init>(JTATransaction.java:60)
>>[hibernate-3.2.6.ga.jar:3.2.6.ga]
>>        at
>>org.hibernate.transaction.JTATransactionFactory.createTransaction(JTATrans
>>actionFactory.java:57)
>>[hibernate-3.2.6.ga.jar:3.2.6.ga]
>>        at
>>org.hibernate.jdbc.JDBCContext.getTransaction(JDBCContext.java:197)
>>[hibernate-3.2.6.ga.jar:3.2.6.ga]
>>        at
>>org.hibernate.impl.SessionImpl.getTransaction(SessionImpl.java:1315)
>>[hibernate-3.2.6.ga.jar:3.2.6.ga]
>>        at
>>org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1325)
>>[hibernate-3.2.6.ga.jar:3.2.6.ga]
>>        at
>>net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl.openSession(Sessio
>>nObjectDAOImpl.java:343)
>>[db-storage-service-1.1.3.jar:]
>>        at
>>net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl.getExpiredSessions
>>(SessionObjectDAOImpl.java:243)
>>[db-storage-service-1.1.3.jar:]
>>        at
>>net.clareitysecurity.shibboleth.storage.StorageCleaner.run(StorageCleaner.
>>java:50)
>>[db-storage-service-1.1.3.jar:]
>>        at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
>>
>>We have our own session cleanup scheduled within the application using
>>a Spring task. Is it possible to disable this in the storage service
>>configuration?
>>--
>>To unsubscribe from this list send an email to
>>users-unsubscribe at shibboleth.net
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net