Jboss下JMS的Topic非持久性操作成功，为何持久性部署时总报错？？

Question

11:19:26,596 INFO  [MainDeployer] Starting deployment of package: file:/C:/jboss
/server/default/deploy/JMS_topic.jar
11:19:27,598 INFO  [EjbModule] Creating
11:19:27,628 INFO  [EjbModule] Deploying JMS_Topic
11:19:27,658 INFO  [MessageDrivenContainer] Creating
11:19:27,668 INFO  [MessageDrivenInstancePool] Creating
11:19:27,668 INFO  [MessageDrivenInstancePool] Created
11:19:27,678 INFO  [JMSContainerInvoker] Creating
11:19:27,678 INFO  [JMSContainerInvoker] Created
11:19:27,848 INFO  [MessageDrivenContainer] Created
11:19:27,848 INFO  [EjbModule] Created
11:19:27,858 INFO  [EjbModule] Starting
11:19:27,858 INFO  [MessageDrivenContainer] Starting
11:19:27,868 INFO  [JMSContainerInvoker] Starting
11:19:27,898 INFO  [DLQHandler] Creating
11:19:28,199 INFO  [DLQHandler] Created
11:19:28,619 INFO  [JMSContainerInvoker] Started
11:19:28,619 INFO  [MessageDrivenInstancePool] Starting
11:19:28,629 INFO  [MessageDrivenInstancePool] Started
11:19:28,629 INFO  [MessageDrivenContainer] Started
11:19:28,639 INFO  [EjbModule] Started
11:19:28,639 INFO  [EJBDeployer] Deployed: file:/C:/jboss/server/default/deploy/
JMS_topic.jar
11:19:28,679 WARN  [JMSContainerInvoker] JMS provider failure detected:
javax.jms.JMSSecurityException: Connection not authorized to do durable subscrip
tion on topic: MyDurableTopic
        at org.jboss.mq.security.ServerSecurityInterceptor.subscribe(ServerSecur
ityInterceptor.java:142)
        at org.jboss.mq.server.TracingInterceptor.subscribe(TracingInterceptor.j
ava:677)
        at org.jboss.mq.server.JMSServerInvoker.subscribe(JMSServerInvoker.java:
298)
        at org.jboss.mq.il.jvm.JVMServerIL.subscribe(JVMServerIL.java:315)
        at org.jboss.mq.Connection.addConsumer(Connection.java:1082)
        at org.jboss.mq.SpyConnectionConsumer.<init>(SpyConnectionConsumer.java:
73)
        at org.jboss.mq.SpyConnection.createDurableConnectionConsumer(SpyConnect
ion.java:102)
        at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContaine
rInvoker.java:509)
        at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContain
erInvoker.java:579)
        at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
92)
        at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContai
ner.java:220)
        at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
92)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:966)
        at $Proxy12.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:392)
        at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
        at $Proxy43.start(Unknown Source)
        at org.jboss.ejb.EjbModule.startService(EjbModule.java:329)
        at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
92)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:966)
        at $Proxy12.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:392)
        at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
        at $Proxy19.start(Unknown Source)
        at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:540)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
        at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
        at $Proxy7.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:302)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:458)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:200)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
loop(AbstractDeploymentScanner.java:211)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
run(AbstractDeploymentScanner.java:190)
11:19:29,040 INFO  [JMSContainerInvoker] Trying to reconnect to JMS provider
11:19:29,070 INFO  [MainDeployer] Deployed package: file:/C:/jboss/server/defaul
t/deploy/JMS_topic.jar

Answer 1

自己UP一下。
偶是用JB开发的，在非持久性部署操作成功后，直接把MDB属性中的非持久性改为持久性，编译没问题，但部署时就发生上述错误，大家再帮我看看！！

Answer 2

Connection not authorized to do durable subscrip
要做durable，得配置用户名密码，看看jbossmp-state.xml文件吧，缺省的用户名是john
密码needle
      Hashtable props = new Hashtable();
      props.put(Context.INITIAL_CONTEXT_FACTORY,
      "org.jnp.interfaces.NamingContextFactory");
      props.put(Context.PROVIDER_URL, "localhost:1099");      InitialContext iniCtx = new InitialContext(props);
      Object tmp = iniCtx.lookup("ConnectionFactory");
      TopicConnectionFactory tcf = (TopicConnectionFactory) tmp;
      TopicConnection conn = tcf.createTopicConnection("john", "needle");
      Topic topic = (Topic) iniCtx.lookup("topic/testTopic");
      TopicSession session = conn.createTopicSession(false,
         TopicSession.AUTO_ACKNOWLEDGE);
      TopicSubscriber recv = session.createDurableSubscriber(topic, "chap6-ex1dtps");
      conn.close();
      System.out.println("End DurableTopicSetup");

Answer 3

jboss还有用户与密码的要求！！weblogic中就没有。
持久性主题和非持久性主题在weblogic中是要进入控制台创建的，JBoss的就不清楚，帮不了你。

Answer 4

to:flowercat(小强)，你好！
感谢你的回答，我还想再问一下，我是用JB7开发的，在MDB的属性设置时，我填写的是topic/testTopic，其他属性没有设置用户名和密码的地方，你给出的这段代码我把它加到MDBean中，且默认用户和密码没改变。编译是通过的，但在部署时依旧是以上错误，我不知道是否代码加的地方不对，还是什么原因？请再详细指教。谢谢！！

Answer 5

现在我把以上代码写入cliten端程序中执行，持久性问题可以解决并正常运行，但如果放入MDB中，一部署就马上出现老问题，我知道还是JB在开发MDB中某些属性没配置好或是以上代码在Bean中的位置不对，大家再帮我一下？？谢谢了！！