[JIRA] Updated: (SSPCPP-515) Make /Status handler report SessionCache
Scott Cantor (JIRA)
noreply at shibboleth.net
Mon Oct 29 15:49:07 EDT 2012
[ https://issues.shibboleth.net/jira/browse/SSPCPP-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Cantor updated SSPCPP-515:
--------------------------------
Fix Version/s: 2.5.1
Remaining Estimate: 2 hours
Original Estimate: 2 hours
> Make /Status handler report SessionCache
> ----------------------------------------
>
> Key: SSPCPP-515
> URL: https://issues.shibboleth.net/jira/browse/SSPCPP-515
> Project: Shibboleth SP - C++
> Issue Type: New Feature
> Components: Session Cache
> Affects Versions: 2.5.0
> Environment: shib on IIS in Windows 2008 R2 with ODBC plugin talking to MSSQL
> Reporter: pbrears at idp.protectnetwork.org
> Assignee: Scott Cantor
> Labels: Session
> Fix For: 2.5.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In V2.5 if the ODBC connector can't talk to the database at service start-up it backs off and uses mem:
> (I think in 2.4.x it didn't back off and just gave #500 errors?)
> CRIT Shibboleth.Config : failed to instantiate StorageService (db): ODBC StorageService failed to connect to database.
> INFO Shibboleth.Config : no StorageService plugin(s) installed, using (mem) in-memory instance
> This is good in that the server starts and works; however if the app relies on ODBC for reliability (say due to non sticky LB) then it's likely to result in a unreliable app.
> The /Shibboleth.sso/Status reports the following even when it's using memory when it was told to use the db.
> <SessionCache><OK/></SessionCache>
> It would be great if the status handler would report it was faulty. (Or report the type in use mem/db/etc and allow the monitoring system polling the status page to alert that all wasn't well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list