I've got a problem during migration to v4.0.4 (There were a lot of problems, but i solved most. But this trouble....)
I built project and deployed it. Immediately, i got the folowing stacktrace: | 18:49:58,232 WARN [JMSContainerInvoker] JMS provider failure detected for SchedulerListenerBean | org.jboss.deployment.DeploymentException: Error during topic setup; - nested throwable: (javax.jms.InvalidDestinationException: Pr | evious topic does not exist: TOPIC.com/mysystem/mq/JobInvocationTopic) | at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:720) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:839) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) File topic-config-service.xml contains the following: <mbean code="org.jboss.mq.server.jmx.Topic" | name="jboss.mq.destination:service=Topic,name=job-invocation-topic"> | <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends> | <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends> | <attribute name="JNDIName">topic/com/mysystem/mq/JobInvocationTopic</attribute> | </mbean> | ejb-jar contains: | <message-driven> | <ejb-name>SchedulerListenerBean</ejb-name> | <resource-adapter-name>jms-ra.rar</resource-adapter-name> | <configuration-name>Standard Message Driven Bean</configuration-name> | <destination-jndi-name>topic/com/mysystem/mq/JobInvocationTopic</destination-jndi-name> | <mdb-subscription-id>SchedulerListenerBeanSubscribtion</mdb-subscription-id> | <mdb-client-id>SchedulerListenerBean</mdb-client-id> | </message-driven> For lookup() we use constant "topic/com/mysystem/mq/JobInvocationTopic" But... There are several topics and all of them are unavailable by JNDI in this way. topic-config are the same in 4.0.2 and 4.0.4 Somebody told me, that it could be new version of JMS provider, but can somebody tell me what's exactly with topic names and how i can solve it... ? Thanks in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955400#3955400 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955400 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
