Overloaded shibd questions

[Nate Klingenstein]

Two questions:

1)  We have a situation in which I believe a remote, overloaded Shibboleth daemon is causing XML-RPC calls to it from modules to timeout or fail in other ways, resulting in no attributes being appended to the HTTP request by the module before passing the request along to the application for handling.  This is the most suspicious root cause of the looping behavior that I mentioned I was encountering earlier.

The environment will be rearchitected to fix the overloaded shibd, but is there a logging category and level I can set to confirm this is the issue?  Perhaps:

# interprocess message remoting
#log4j.category.Shibboleth.Listener=DEBUG

in both shibd.logger and native.logger?

2)  If my hunch is correct, is the addition of a SessionCache likely to change the module's behavior, and if I want to persist REMOTE_USER, does that need to be done separately from the attribute used to populate it, and if so, what is it named?

Apologies in advance,
Nate.

--------
Signet, Inc.
The Art of Access ®

https://www.signet.id