Announce: Database Backed Storage Service

[Wessel, Keith]

Just so I understand, before I go looking at hibernate debug output that doesn't sound like it'll help...

Your code is first creating the session in the database with a session-expire_time and a session_id but no login_id since it doesn't have one yet. Then, after it has the principal, it tries to update the existing session row to add it.

Is that correct? I'm wondering if this is something as simple as our DBA accidentally removing update perms on the table.

If my take isn't right, at least understanding the interaction better might help me know where to go next.

Thanks,
Keith


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Paul Hethmon
Sent: Wednesday, January 08, 2014 2:00 PM
To: Shib Users
Subject: Re: Announce: Database Backed Storage Service

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

>[session=e83a97a96ad586796aae9ea704f4bffca6abaf2d39e81bea3c55e1725605d2
>f4]
> - Key is a string = [kwessel]
>13:37:17.613 - DEBUG
>[net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl:272]
>[session=e83a97a96ad586796aae9ea704f4bffca6abaf2d39e81bea3c55e1725605d2
>f4]
> - Searching for [kwessel] in system [shibboleth]
>13:37:17.617 - DEBUG
>[net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl:64]
>[session=e83a97a96ad586796aae9ea704f4bffca6abaf2d39e81bea3c55e1725605d2
>f4]
> - No session object found, performing insert on [kwessel].
>13:37:17.622 - DEBUG
>[net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl:120]
>[session=e83a97a96ad586796aae9ea704f4bffca6abaf2d39e81bea3c55e1725605d2
>f4]
> - 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



--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net