Debug Mode for CustomRealm

Question

( maybe see as well entry #27 in this list)
For debugging / logging from my ( now working) CustomRealm implements DebugableRealm, i tried to set DebugSecurityRealm=true. Starting WL Server gives the behaviour, described in thread 27.
As well instanciating a new LogOutoustream results in runtime Stackoverflow.
The same thing works well wit a custom AuditProvider.
Are there sulutions to this problem ?
Thanks,
Paul

Answer 1

Thanks for the comment. i implmented my own debug file, so i can live with it for now.
Paul
"Suresh Vallabhaneni" <[email protected]> wrote:
>
Hi Paul
Sorry for the late reply. First of all, thank you for uncovering an untested part of ServerDebug MBean. The Debug Mode for Security Realms currently works for fileRealm but doesnot work for alternate realms(e.g., LDAP realm). We're in the process of fixing this in the future releases(may not be Beta Refresh but will definitely be fixed in GA). I'm attaching a working config.xml(with fileRealm) and the only change you've to make to your config.xml is
<Server
<ServerDebug
DebugSecurityRealm="true"
Name="myserver"
/>
</Server>
If you're debugging a fileRealm then I belive, this serves your purpose. But if you're debugging a Security Realm other than fileRealm and this is blocking you, plz let us know so that this will be fixed with a higer priority. Thanks again for uncovering this.Will let you know as soon as this is fixed.
regards
"Paul Hettl" <[email protected]> wrote:
( maybe see as well entry #27 in this list)
For debugging / logging from my ( now working) CustomRealm implements DebugableRealm, i tried to set DebugSecurityRealm=true. Starting WL Server gives the behaviour, described in thread 27.
As well instanciating a new LogOutoustream results in runtime Stackoverflow.
The same thing works well wit a custom AuditProvider.
Are there sulutions to this problem ?
Thanks,
Paul