This is the trace that the last call to
createTopicConnection(SpyConnectionFactory.java:78) produces when the
system runs ok.
2003-10-02 12:56:58,796 TRACE
[org.jboss.mq.security.ServerSecurityInterceptor] Autenticating user
null/null
2003-10-02 12:56:58,796 TRACE
[org.jboss.security.plugins.JaasSecurityManager.jbossmq] validateCache,
[EMAIL PROTECTED]
2003-10-02 12:56:58,796 TRACE [org.jboss.mq.security.SecurityManager]
Username: null is authenticated
2003-10-02 12:56:58,796 TRACE [org.jboss.mq.security.SecurityManager]
Adding group : class org.jboss.security.NestableGroup
Roles(members:subscriber,publisher,guest,durpublisher)
2003-10-02 12:56:58,796 TRACE [org.jboss.mq.security.SecurityManager]
Checking authorize on subjectInfo: SubjectInfo {subject=Subject:
Principal: guest
Principal:
Roles(members:subscriber,publisher,guest,durpublisher)
;principal=null;roles=Roles(members:subscriber,publisher,guest,durpublis
her) for rolePrincipals [guest]
2003-10-02 12:56:58,812 TRACE
[org.jboss.mq.security.ServerSecurityInterceptor] Checking receive
authorize on
SpyDistributedConnection:ID:1/7e0aa1fa14d29607fe91f5b99116b5f2
subId=-2147483648
2003-10-02 12:56:58,812 TRACE [org.jboss.mq.security.SecurityManager]
Checking authorize on subjectInfo: SubjectInfo {subject=Subject:
Principal:
Roles(members:subscriber,publisher,guest,durpublisher)
;principal=null;roles=Roles(members:subscriber,publisher,guest,durpublis
her) for rolePrincipals [guest]
2003-10-02 12:56:58,812 TRACE
[org.jboss.mq.security.ServerSecurityInterceptor] Checking receive
authorize on
SpyDistributedConnection:ID:1/7e0aa1fa14d29607fe91f5b99116b5f2
subId=-2147483648
2003-10-02 12:56:58,812 TRACE [org.jboss.mq.security.SecurityManager]
Checking authorize on subjectInfo: SubjectInfo {subject=Subject:
Principal:
Roles(members:subscriber,publisher,guest,durpublisher)
;principal=null;roles=Roles(members:subscriber,publisher,guest,durpublis
her) for rolePrincipals [guest]
This is the result of the stack trace when the system stops working:
2003-10-02 13:00:26,125 TRACE
[org.jboss.mq.security.ServerSecurityInterceptor] Autenticating user
null/null
2003-10-02 13:00:26,125 TRACE [org.jboss.mq.sm.file.DynamicLoginModule]
logout
2003-10-02 13:00:26,125 DEBUG
[org.jboss.security.plugins.JaasSecurityManager.jbossmq] Login failure
javax.security.auth.login.LoginException: No LoginModules configured for
jbossmq
at
javax.security.auth.login.LoginContext.init(LoginContext.java:189)
at
javax.security.auth.login.LoginContext.<init>(LoginContext.java:350)
at
javax.security.auth.login.LoginContext.<init>(LoginContext.java:465)
at
org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurity
Manager.java:486)
at
org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurity
Manager.java:442)
at
org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManag
er.java:244)
at
org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManag
er.java:219)
at
org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:
201)
at
org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecur
ityInterceptor.java:51)
at
org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.j
ava:650)
at
org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:
288)
at
org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:302)
at org.jboss.mq.Connection.authenticate(Connection.java:876)
at org.jboss.mq.Connection.<init>(Connection.java:238)
at org.jboss.mq.Connection.<init>(Connection.java:315)
at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:60)
at
org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFac
tory.java:78)
2003-10-02 13:00:26,125 TRACE [org.jboss.mq.security.SecurityManager]
User: null is NOT authenticated
2003-10-02 13:00:26,125 ERROR
[com.oakgrovesystems.reactor.scheduling.basic.ScheduledEventAction]
Could not send Timer Expiration Event Notification request to
PolicyExecutionService
javax.jms.JMSSecurityException: User: null is NOT authenticated
at
org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:
225)
at
org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecur
ityInterceptor.java:51)
at
org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.j
ava:650)
at
org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:
288)
at
org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:302)
at org.jboss.mq.Connection.authenticate(Connection.java:876)
at org.jboss.mq.Connection.<init>(Connection.java:238)
at org.jboss.mq.Connection.<init>(Connection.java:315)
at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:60)
at
org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFac
tory.java:78)
I think that this trace is very usefull.
Regard, Panagiotis
-----Original Message-----
From: Adrian Brock [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 6:37 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JbossMQ error: 'User: null is NOT
authenticated'
Do you see anything in log/server.log when it fails,
just before the exception you posted.
If not, try enabling TRACE logging in conf/log4j.xml for the following
categories to see whether it shows something useful at the failure.
org.jboss.security
org.jboss.mq.security
org.jboss.mq.sm
Regards,
Adrian
On Tue, 2003-09-30 at 16:23, Panagiotis Korros wrote:
> This is the section in conf/login-config.xml regarding jbossmq. I
> didn't change this file at all.
>
> <!-- Security domain for JBossMQ -->
> <application-policy name = "jbossmq">
> <authentication>
> <login-module code =
"org.jboss.mq.sm.file.DynamicLoginModule"
> flag = "required">
> <module-option name =
> "unauthenticatedIdentity">guest</module-option>
> <module-option name =
> "sm.objectname">jboss.mq:service=StateManager</module-option>
> </login-module>
> </authentication>
> </application-policy>
>
> It seems to me that the server sometimes looses the login module
> configuration.
>
> Regards,
> Panagiotis
>
> -----Original Message-----
> From: Adrian Brock [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 30, 2003 4:16 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] JbossMQ error: 'User: null is NOT
> authenticated'
>
>
> The topic security config is irrelevent at this stage,
> you haven't got to the authorization step.
> You are still trying to authenticate the user.
>
> First, post the conf/login-config.xml snippet for jbossmq,
> it should have an unauthenticated identity,
> the default setting is "guest".
>
> Regards,
> Adrian
>
> On Tue, 2003-09-30 at 13:52, Panagiotis Korros wrote:
> > I am using JBoss 3.2.2RC4 / 3.2.1 with JDK 1.4.2 and i get the
> > following
> > error:
> >
> > javax.jms.JMSSecurityException: User: null is NOT authenticated at
> > org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.j
> > av
> > a:
> > 215)
> > at
> >
> org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSec
> ur
> > ityInterceptor.java:51)
> > at
> >
> org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor
> .j
> > ava:650)
> > At
> >
> org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.jav
> a:
> > 288)
> > at
> > org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:302)
> > at org.jboss.mq.Connection.authenticate(Connection.java:876)
> > at org.jboss.mq.Connection.<init>(Connection.java:238)
> > at org.jboss.mq.Connection.<init>(Connection.java:315)
> > at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:60)
> > at
> >
> org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionF
> ac
> > tory.java:78)
> > at ...
> >
> > I can't predict when the problem appears, but when it appears a
> > server
>
> > restart is required for the jms topic to function correctly.
> >
> > My config file is:
> > <server>
> > <mbean code="org.jboss.mq.il.jvm.JVMServerILService"
> > name="jboss.mq:service=ReactorInvocationLayer,type=JVM">
> > <depends
> > optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
> > <attribute
> > name="ConnectionFactoryJNDIRef">TopicConnectionFactory</attribute>
> > <attribute
> >
name="XAConnectionFactoryJNDIRef">XATopicConnectionFactory</attribute>
> > <attribute name="PingPeriod">0</attribute>
> > </mbean>
> >
> > <mbean code="org.jboss.mq.server.jmx.Topic"
> > name="jboss.mq.destination:service=Topic,name=PolicyExecution">
> > <depends
> >
optional-attribute-name="DestinationManager">jboss.mq:service=Destinat
> > io
> > nManager</depends>
> > <depends
> >
> optional-attribute-name="SecurityManager">jboss.mq:service=SecurityMan
> ag
> > er</depends>
> > <attribute name="SecurityConf">
> > <security>
> > <role name="guest" read="true" write="true" create="true"/>
> > </security>
> > </attribute>
> > </mbean>
> > </server>
> >
> > Does anyone knows what is going on?
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-user
--
xxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Director of Support
Back Office
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
