JBoss 5.1.0GA“user null is not authenticated”issue

Question

我有一个运行服务器的jBoss 5.1.0-GA，它运行的是find。但是我将整个jboss复制到另一台服务器上（通过使用tar）。当我开始新的jBoss，它给一个“用户null未验证”，这里是堆栈跟踪

[ExceptionUtil] 
ConnectionFactoryEndpoint[jboss.messaging.connectionfactory:service=ConnectionFactory] 
createFailoverConnectionDelegate [nb-z2y983bh-1-4b8983bh-kwpr33-100j3] 
javax.jms.JMSSecurityException: User null is NOT authenticated 
at 
org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore.authenticate(JBossASSecurityMetadataStore.java:223) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:597) 
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93) 
at 
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27) 
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208) 
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) 
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) 
at javax.management.StandardMBean.invoke(StandardMBean.java:391) 
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) 
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) 
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) 
at $Proxy260.authenticate(Unknown Source) 
at 
org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:233) 
at 
org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171) 
at 
org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) 
at 
org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) 
at 
org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) 
at 
org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) 
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) 
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) 
at org.jboss.remoting.Client.invoke(Client.java:1724) 
at org.jboss.remoting.Client.invoke(Client.java:629) 
at 
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:171) 
at 
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeTarget(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) 
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) 
at 
org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:81) 
at 
org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_31070867.invoke(StateCreationAspect_z_handleCreateConnectionDelegate_31070867.java) 
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) 
at 
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) 
at 

org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) 
at 

org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101) 
at 

org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95) 
at 
org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137) 
at 
org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83) 
at 
org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48) 
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413) 
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351) 
at 
org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729) 
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205) 
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) 
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
at java.lang.Thread.run(Thread.java:662) 

12:01:34,859 ERROR [ExceptionUtil] 
ConnectionFactoryEndpoint[jboss.messaging.connectionfactory:service=ConnectionFactory] 
createFailoverConnectionDelegate [mb-z2y983bh-1-4b8983bh-kwpr33-100j3] 

有人可以帮忙吗？

Answer 1

解决了这个问题，那是我们要解决其他问题时发生的那个问题，那就是com.arjuna事务问题，在这个jboss中不断抛出消息不停，要解决这个问题，有的帖子建议删除'data '文件夹，当我们删除它时，数据文件夹内的超音速数据库脚本也被删除，因此用户Null问题出来了，所以我们做了恢复超音速数据库脚本，现在它工作正常。

Answer 2

另一种可能性是，在“messaging-jboss-beans.xml”中配置的DatabaseServerLoginModule bean中指定的数据源与您用于JMS的数据源不匹配。

如果在服务器的“deploy/messaging”目录中替换了“hsqldb-persistence-service.xml”文件，并将定制的持久性服务文件配置为您希望用于JMS（例如“postgresql-persistence-service.xml”）。

如果这样做，则需要确保DatabaseServerLoginModule bean的dsJndiName模块选项的值与新“-persistence-service.xml”文件中的数据存储的JNDI名称匹配。只需将java:/DefaultDS替换为您的数据源JNDI名称（例如java:/MysqlDB或其他）。

参考：http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg59720.html