Re: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
So the jbossmq login configuration still exists then. Create a bug report on sourceforge with more info on what your doing so we can try to look into what could be going on. -- Scott Stark Chief Technology Officer JBoss Group, LLC Panagiotis Korros wrote: The result before the error is: jbossmq LoginConfiguration LoginModule Class: org.jboss.mq.sm.file.DynamicLoginModule ControlFlag: LoginModuleControlFlag: required Options:name=sm.objectname, value=jboss.mq:service=StateManager name=unauthenticatedIdentity, value=guest The result after the error is: jbossmq LoginConfiguration LoginModule Class: org.jboss.mq.sm.file.DynamicLoginModule ControlFlag: LoginModuleControlFlag: required Options:name=sm.objectname, value=jboss.mq:service=StateManager name=unauthenticatedIdentity, value=guest --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
The result before the error is:
jbossmq LoginConfiguration
LoginModule Class: org.jboss.mq.sm.file.DynamicLoginModule
ControlFlag: LoginModuleControlFlag: required
Options:name=sm.objectname, value=jboss.mq:service=StateManager
name=unauthenticatedIdentity, value=guest
The result after the error is:
jbossmq LoginConfiguration
LoginModule Class: org.jboss.mq.sm.file.DynamicLoginModule
ControlFlag: LoginModuleControlFlag: required
Options:name=sm.objectname, value=jboss.mq:service=StateManager
name=unauthenticatedIdentity, value=guest
-Original Message-
From: Scott M Stark [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 22, 2003 7:26 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JbossMQ error: 'User: null is NOT
authenticated'
Go into the jmx-console when the error occurs and go to the
jboss.security:service=XMLLoginConfig mbean and invoke the
displayAppConfig operation passing in the jbossmq string.
The exception indicates that the jbossmq configuration has been removed.
This msg:
> 2003-10-02 13:00:26,125 TRACE
[org.jboss.mq.sm.file.DynamicLoginModule]
> logout
indicates that the authentication cache entry expired as the same time.
Does this always happen after 30 minutes?
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Panagiotis Korros wrote:
> I am using JBoss 3.2.2 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.java:
> 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.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.(Connection.java:238)
> at org.jboss.mq.Connection.(Connection.java:315)
> at org.jboss.mq.SpyConnection.(SpyConnection.java:60)
> At
> org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionF
> ac
> tory.java:78)
> at ...
>
> When I start my application it works ok but after a while the problem
> appears. When it appears a server restart is required for the jms
> topic to function correctly. This is happening when I use the default
> JVM Invoker.
>
> When I switched to use the OIL2 invoker instead of JVM Invoker then
> the problem doesn't appear at all.
>
>
>
> If I enable TRACE logging for the following categories I get:
>
> org.jboss.security
> org.jboss.mq.security
> org.jboss.mq.sm
>
>
>
>
>
>
>
>
>
>
> TRACE INFO
>
> 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,durpubl
> is
> 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,durpubl
> is
> 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 {sub
Re: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
Go into the jmx-console when the error occurs and go to
the jboss.security:service=XMLLoginConfig mbean and invoke
the displayAppConfig operation passing in the jbossmq string.
The exception indicates that the jbossmq configuration has
been removed. This msg:
> 2003-10-02 13:00:26,125 TRACE [org.jboss.mq.sm.file.DynamicLoginModule]
> logout
indicates that the authentication cache entry expired as the same
time. Does this always happen after 30 minutes?
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Panagiotis Korros wrote:
I am using JBoss 3.2.2 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.java:
215)
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.(Connection.java:238)
at org.jboss.mq.Connection.(Connection.java:315)
at org.jboss.mq.SpyConnection.(SpyConnection.java:60)
At
org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFac
tory.java:78)
at ...
When I start my application it works ok but after a while the problem
appears. When it appears a server restart is required for the jms topic
to function correctly. This is happening when I use the default JVM
Invoker.
When I switched to use the OIL2 invoker instead of JVM Invoker then the
problem doesn't appear at all.
If I enable TRACE logging for the following categories I get:
org.jboss.security
org.jboss.mq.security
org.jboss.mq.sm
TRACE INFO
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)
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
I have seen the problem to appear in jboss versions 3.2 and above. Now I
am using the 3.2.2RC4 release available at sourceforge.
In my runtime environment there is a message driven bean receiving the
messages configured to use the default message driven container.
There are 4-5 senders that each send 1-2 messages per minute at most.
If I configure the jbossmq login module to use an
ConfiguredIdentityLoginModule instead of the DynamicLoginModule will I
be able to solve my problem (temporarily)?
-Original Message-
From: Scott M Stark [mailto:[EMAIL PROTECTED]
Sent: Friday, October 03, 2003 2:45 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JbossMQ error: 'User: null is NOT
authenticated'
Its seems to be occuring after the authentication cache is timing out.
Is this the 3.2.2RC4 release available from SF or a cvs snapshot?
Can you describe the runtime env a bit more in terms of how many
senders/receivers there are and how many msgs are being exchanged?
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Panagiotis Korros wrote:
>>Yes, are there any messages in the log just before the above message
>
> about the jbossmq security policy configuration?
> No
>
>
>
> This is the exact trace for the last succesfull logins to the queue
> (Just as you told me I enabled tracing for org.jboss.security
> org.jboss.mq.security org.jboss.mq.sm).
>
> 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]
> 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
---
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
Re: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
Its seems to be occuring after the authentication cache is timing out. Is this
the 3.2.2RC4 release available from SF or a cvs snapshot?
Can you describe the runtime env a bit more in terms of how many
senders/receivers there are and how many msgs are being exchanged?
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Panagiotis Korros wrote:
Yes, are there any messages in the log just before the above message
about the jbossmq security policy configuration?
No
This is the exact trace for the last succesfull logins to the queue
(Just as you told me I enabled tracing for org.jboss.security
org.jboss.mq.security org.jboss.mq.sm).
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]
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
---
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
RE: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
> Yes, are there any messages in the log just before the above message
about the jbossmq security policy configuration?
No
This is the exact trace for the last succesfull logins to the queue
(Just as you told me I enabled tracing for org.jboss.security
org.jboss.mq.security org.jboss.mq.sm).
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]
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.(LoginContext.java:350)
at
javax.security.auth.login.LoginContext.(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.(Connection.java:238)
at org.jboss.mq.Connection.(Connection.java:315)
at org.jboss.mq.SpyConnection.(SpyConnection.java:60)
at
org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFac
tory.java:78)
>From what I see the first unsucessfull login misses this line
2003-10-02 12:56:58,796 TRACE
[org.jboss.security.plugins.JaasSecurityManager.jbossmq] validateCache,
[EMAIL PROTECTED]
Is it possible that the JaasSecurityManager logs out the guest identity
when it invalidates the cache?
-Original Message-
From: Adrian Brock [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2003 2:17 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JbossMQ error: 'User: null is NOT
authenticated'
On Thu, 2003-10-02 at 11:46, Panagiotis Korros wrote:
> 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.(LoginContext.java:350)
> at
> javax.security.auth.login.L
RE: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
On Thu, 2003-10-02 at 11:46, Panagiotis Korros wrote: > 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.(LoginContext.java:350) > at > javax.security.auth.login.LoginContext.(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) WTF? > I think that this trace is very usefull. > Yes, are there any messages in the log just before the above message about the jbossmq security policy configuration? Regards, Adrian > Regard, Panagiotis > -- > > Adrian Brock > Director of Support > Back Office > JBoss Group, LLC > --- 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
RE: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
) 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. > > > > > flag = "required"> > "unauthenticatedIdentity">guest > "sm.objectname">jboss.mq:service=StateManager > > > > > 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.(Connection.java:238) > > at org.jboss.mq.Connection.(Connection.java:315) > > at org.jboss.mq.SpyConnection.(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: > > > >> name="jboss.mq:service=ReactorInvocationLayer,type=JVM"> > > > optional-attribute-name="Invoker">jboss.mq:service=Invoker > > > name="ConnectionFactoryJNDIRef">TopicConnectionFactory > > > name="XAConnectionFactoryJNDIRef">XATopicConnectionFactory > > 0 > > > > > >> name="jboss.mq.destination:service=Topic,name=PolicyExecution"> > > > optional-attribute-name="DestinationManager">jboss.mq:service=Destinat > > io > > nManager > > > > optional-attribute-name="SecurityManager">jboss.mq:service=SecurityMan > ag > > er > > > > > > > > > > > > > > > > > > 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 -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- 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
RE: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
I enabled tracing and I will post the log file when the problem appears again. It takes sometime for the problem to appear but when it does a server restart is required. Regards, 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. > > > > > flag = "required"> > "unauthenticatedIdentity">guest > "sm.objectname">jboss.mq:service=StateManager > > > > > 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.(Connection.java:238) > > at org.jboss.mq.Connection.(Connection.java:315) > > at org.jboss.mq.SpyConnection.(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: > > > >> name="jboss.mq:service=ReactorInvocationLayer,type=JVM"> > > > optional-attribute-name="Invoker">jboss.mq:service=Invoker > > > name="ConnectionFactoryJNDIRef">TopicConnectionFactory > > > name="XAConnectionFactoryJNDIRef">XATopicConnectionFactory > > 0 > > > > > >> name="jboss.mq.destination:service=Topic,name=PolicyExecution"> > > > optional-attribute-name="DestinationManager">jboss.mq:service=Destinat > > io > > nManager > > > > optional-attribute-name="SecurityManager">jboss.mq:service=SecurityMan > ag > > er > > > > > > > > > > > > > > > > > > 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 -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- 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
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. > > > > > flag = "required"> > "unauthenticatedIdentity">guest > "sm.objectname">jboss.mq:service=StateManager > > > > > 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.jav > > a: > > 215) > > 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.(Connection.java:238) > > at org.jboss.mq.Connection.(Connection.java:315) > > at org.jboss.mq.SpyConnection.(SpyConnection.java:60) > > at > > > org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFac > > 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: > > > >> name="jboss.mq:service=ReactorInvocationLayer,type=JVM"> > > > optional-attribute-name="Invoker">jboss.mq:service=Invoker > > > name="ConnectionFactoryJNDIRef">TopicConnectionFactory > > > name="XAConnectionFactoryJNDIRef">XATopicConnectionFactory > > 0 > > > > > >> name="jboss.mq.destination:service=Topic,name=PolicyExecution"> > > > optional-attribute-name="DestinationManager">jboss.mq:service=Destinat > > io > > nManager > > > > optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManag > > er > > > > > > > > > > > > > > > > > > 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 -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- 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
RE: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
This is the section in conf/login-config.xml regarding jbossmq. I didn't change this file at all. guest jboss.mq:service=StateManager 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.jav > a: > 215) > 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.(Connection.java:238) > at org.jboss.mq.Connection.(Connection.java:315) > at org.jboss.mq.SpyConnection.(SpyConnection.java:60) > at > org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFac > 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: > > name="jboss.mq:service=ReactorInvocationLayer,type=JVM"> > optional-attribute-name="Invoker">jboss.mq:service=Invoker > name="ConnectionFactoryJNDIRef">TopicConnectionFactory > name="XAConnectionFactoryJNDIRef">XATopicConnectionFactory > 0 > > > name="jboss.mq.destination:service=Topic,name=PolicyExecution"> > optional-attribute-name="DestinationManager">jboss.mq:service=Destinat > io > nManager > optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManag > er > > > > > > > > > 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 -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- 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
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.java: > 215) > 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.(Connection.java:238) > at org.jboss.mq.Connection.(Connection.java:315) > at org.jboss.mq.SpyConnection.(SpyConnection.java:60) > at > org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFac > 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: > > name="jboss.mq:service=ReactorInvocationLayer,type=JVM"> > optional-attribute-name="Invoker">jboss.mq:service=Invoker > name="ConnectionFactoryJNDIRef">TopicConnectionFactory > name="XAConnectionFactoryJNDIRef">XATopicConnectionFactory > 0 > > > name="jboss.mq.destination:service=Topic,name=PolicyExecution"> > optional-attribute-name="DestinationManager">jboss.mq:service=Destinatio > nManager > optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManag > er > > > > > > > > > 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 -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- 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
RE: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
You haven't got that far. You are still trying to make a connection. Are there any more informative messages in log/server.log you might need to enable DEBUG or TRACE for org.jboss.mq The answer to this specific question is that it will add if you don't specify it. Regards, Adrian On Wed, 2003-09-10 at 15:30, Panagiotis Korros wrote: > Yes there is an "unathenticated identity" for jbossmq > in conf/login-config.xml. > > Should I also have: > optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManag > er > > > > > create="true"/> > > > > In my mbean definition? > > -Original Message- > From: Adrian Brock [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 10, 2003 2:39 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] JbossMQ error: 'User: null is NOT > authenticated' > > > Have you made any other changes to the config? > There should be an "unathenticated identity" for jbossmq > in conf/login-config.xml > The default is "guest" > > Regards, > Adrian > > On Wed, 2003-09-10 at 07:23, Panagiotis Korros wrote: > > > > I am using JBoss 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.java: > 215) > > 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.(Connection.java:238) > > at org.jboss.mq.Connection.(Connection.java:315) > > at org.jboss.mq.SpyConnection.(SpyConnection.java:60) > > at > > > org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFac > 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: > > > > > > > name="jboss.mq:service=ReactorInvocationLayer,type=JVM"> > > > optional-attribute-name="Invoker">jboss.mq:service=Invoker > > > name="ConnectionFactoryJNDIRef">TopicConnectionFactory > > > name="XAConnectionFactoryJNDIRef">XATopicConnectionFactory > > 0 > > > > > > > name="jboss.mq.destination:service=Topic,name=PolicyExecution"> > > > optional-attribute-name="DestinationManager">jboss.mq:service=Destinat > > ionManager > > > > > > > > > > Does anyone knows what is going on? -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- 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
RE: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
Yes there is an "unathenticated identity" for jbossmq in conf/login-config.xml. Should I also have: jboss.mq:service=SecurityManag er In my mbean definition? -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 10, 2003 2:39 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated' Have you made any other changes to the config? There should be an "unathenticated identity" for jbossmq in conf/login-config.xml The default is "guest" Regards, Adrian On Wed, 2003-09-10 at 07:23, Panagiotis Korros wrote: > > I am using JBoss 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.java: 215) > 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.(Connection.java:238) > at org.jboss.mq.Connection.(Connection.java:315) > at org.jboss.mq.SpyConnection.(SpyConnection.java:60) > at > org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFac 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: > > > name="jboss.mq:service=ReactorInvocationLayer,type=JVM"> > optional-attribute-name="Invoker">jboss.mq:service=Invoker > name="ConnectionFactoryJNDIRef">TopicConnectionFactory > name="XAConnectionFactoryJNDIRef">XATopicConnectionFactory > 0 > > > name="jboss.mq.destination:service=Topic,name=PolicyExecution"> > optional-attribute-name="DestinationManager">jboss.mq:service=Destinat > ionManager > > > > > Does anyone knows what is going on? -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- 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
Re: [JBoss-user] JbossMQ error: 'User: null is NOT authenticated'
Have you made any other changes to the config? There should be an "unathenticated identity" for jbossmq in conf/login-config.xml The default is "guest" Regards, Adrian On Wed, 2003-09-10 at 07:23, Panagiotis Korros wrote: > > I am using JBoss 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.java:215) > at > org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:51) > at > org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java: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.(Connection.java:238) > at org.jboss.mq.Connection.(Connection.java:315) > at org.jboss.mq.SpyConnection.(SpyConnection.java:60) > at > org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFactory.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: > > > name="jboss.mq:service=ReactorInvocationLayer,type=JVM"> > optional-attribute-name="Invoker">jboss.mq:service=Invoker > name="ConnectionFactoryJNDIRef">TopicConnectionFactory > name="XAConnectionFactoryJNDIRef">XATopicConnectionFactory > 0 > > > name="jboss.mq.destination:service=Topic,name=PolicyExecution"> > optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager > > > > > Does anyone knows what is going on? -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- 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
