Announce: Database Backed Storage Service

[Paul Hethmon]

On 1/8/14 2:50 PM, "Wessel, Keith" <kwessel at illinois.edu> wrote:

>[session=e83a97a96ad586796aae9ea704f4bffca6abaf2d39e81bea3c55e1725605d2f4]
> - Key is a string = [kwessel]
>13:37:17.613 - DEBUG
>[net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl:272]
>[session=e83a97a96ad586796aae9ea704f4bffca6abaf2d39e81bea3c55e1725605d2f4]
> - Searching for [kwessel] in system [shibboleth]
>13:37:17.617 - DEBUG
>[net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl:64]
>[session=e83a97a96ad586796aae9ea704f4bffca6abaf2d39e81bea3c55e1725605d2f4]
> - No session object found, performing insert on [kwessel].
>13:37:17.622 - DEBUG
>[net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl:120]
>[session=e83a97a96ad586796aae9ea704f4bffca6abaf2d39e81bea3c55e1725605d2f4]
> - New persistent session save to db [null]
>
>Does this mean the database is somehow rejecting the update and I should
>talk to my DBA? If so, is there any good way for me to get the exact SQL
>being sent to add the login_id? I know this is buried under hibernate
>abstraction, and I think our DBA can turn on trace logging on the Oracle
>side, but if there's an easier way... such as debug logging for hibernate?

This makes me think it can't write to the DB. We see the ID prior to the
write, but not after. You can log "org.hibernate" to get the Hibernate
debug. It can be huge. However, if there were an exception thrown, my code
would catch that and report it right after the last statement. So no
exception, which probably means Hibernate won't tell you anything useful.

Paul