I saw the same behavior with the transaction module.
regards,
-marina
V B Kumar Jayanti wrote:
> Hi,
>
> I was trying to check logstrings in security module and found that
> a LogString somehow appears un-expanded (prints the key) on console
> output (start-domain -v) but when observed in server.log it appears
> properly expanded.
>
>
> ---------------console output---------
> Sep 28, 2008 10:29:12 PM
> com.sun.enterprise.security.auth.login.LoginContextDriv
> er doPasswordLogin
> *INFO: java_security.audit_auth_refused*
> Sep 28, 2008 10:29:12 PM com.sun.web.security.RealmAdapter authenticate
> WARNING: Web login failed: Login failed:
> javax.security.auth.login.LoginExceptio
> n: Failed file login for javajoe.
> ------------------------------------
>
> ---------------server.log---------------
> [#|2008-09-28T22:29:12.682+0530|INFO|GlassFish10.0|javax.enterprise.system.core.security|_ThreadID=15;_ThreadName=Thread-3;javajoe;|SEC5046:
> Audit: Authentication refused for [javajoe].|#]
>
> [#|2008-09-28T22:29:12.682+0530|WARNING|GlassFish10.0|javax.enterprise.system.container.web|_ThreadID=15;_ThreadName=Thread-3;|Web
> login failed: Login failed: javax.security.auth.login.LoginException:
> Failed file login for javajoe.|#]
> -----------------------------------------
>
> So the LogString key : *java_security.audit_auth_refused *appears
> expanded in server.log but not in console output. Can someone explain
> this difference.
>
> regards,
> kumar
>
> *
>
> *