1 2 3 Previous Next 31 Replies Latest reply: Aug 13, 2007 4:10 PM by Mauricio Gomez RSS

    connectionFactoryJndiName config property

    Tobin Juday Newbie

      Does JBoss support the ActivationConfigProperty connectionFactoryJndiName?

      @MessageDriven(
       mappedName = "jms/NewMessage",
       activationConfig = {
       @ActivationConfigProperty(propertyName = "connectionFactoryJndiName", propertyValue = "activemq/QueueConnectionFactory"),
       @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
       @ActivationConfigProperty(propertyName = "destination", propertyValue = "activemq/queue/capacity3")
       }
      )
      public class NewMessage implements MessageListener {
      ...


      I haven't been able to get it to work. I've tried not using it, but I get ClassCastExceptions without this property, and it seems like JBoss would need to know which ConnectionFactory to use with this queue. Am I missing something here?

      I can provide more details if there's not an easy answer.

      Here's the exception I get when deploying:
      14:51:30,703 INFO [EJBContainer] STARTED EJB: ejb.NewMessage ejbName: NewMessage
      14:51:30,765 WARN [ServiceController] Problem starting service jboss.j2ee:ear=NewsApp.ear,jar=NewsApp-ejb.jar,name=NewMessage,service=EJB3
      org.jboss.deployment.DeploymentException: Error for ActivationSpec class org.jboss.resource.adapter.jms.inflow.JmsActivationSpec as JavaBean; - nested throwable: (java.beans.IntrospectionException: No property found for: ConnectionFactoryJndiName on JavaBean: org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1589559(ra=null destination=activemq/queue/capacity3 isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0))
      at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
      at org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:135)
      at org.jboss.resource.deployment.RARDeployment.createActivationSpec(RARDeployment.java:254)
      at org.jboss.resource.deployment.RARDeployment.internalInvoke(RARDeployment.java:218)
      at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:156)
      at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44)
      at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:285)
      at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.start(JBossMessageEndpointFactory.java:189)
      at org.jboss.ejb3.mdb.MessagingContainer.startProxies(MessagingContainer.java:185)
      at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:151)
      at org.jboss.ejb3.mdb.MDB.start(MDB.java:126)
      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:585)
      at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
      at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:417)
      at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
      at $Proxy67.start(Unknown Source)
      at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:96)
      at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:281)
      at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:328)
      at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
      at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:417)
      at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
      at $Proxy36.start(Unknown Source)
      at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:449)
      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:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
      at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
      at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
      at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
      at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
      at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
      at $Proxy37.start(Unknown Source)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
      at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
      at $Proxy6.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
      Caused by: java.beans.IntrospectionException: No property found for: ConnectionFactoryJndiName on JavaBean: org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1589559(ra=null destination=activemq/queue/capacity3 isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0)
      at org.jboss.util.propertyeditor.PropertyEditors.mapJavaBeanProperties(PropertyEditors.java:350)
      at org.jboss.util.propertyeditor.PropertyEditors.mapJavaBeanProperties(PropertyEditors.java:281)
      at org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:129)
      ... 108 more
      14:51:31,687 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=NewsApp.ear,jar=NewsApp-ejb.jar,name=NewsEntityFacade,service=EJB3 with dependencies:
      14:51:31,687 INFO [JmxKernelAbstraction] persistence.units:ear=NewsApp.ear,jar=NewsApp-ejb.jar,unitName=NewsApp-ejbPU
      14:51:31,718 INFO [EJBContainer] STARTED EJB: ejb.NewsEntityFacade ejbName: NewsEntityFacade
      14:51:31,781 INFO [EJB3Deployer] Deployed: file:/C:/Program Files/JBoss-4.0.5/server/default/tmp/deploy/tmp3661NewsApp.ear-contents/NewsApp-ejb.jar
      14:51:31,796 INFO [TomcatDeployer] deploy, ctxPath=/NewsApp-war, warUrl=.../tmp/deploy/tmp3661NewsApp.ear-contents/NewsApp-war-exp.war/
      14:51:32,328 INFO [EARDeployer] Started J2EE application: file:/C:/Program Files/JBoss-4.0.5/server/default/deploy/NewsApp.ear

      14:51:32,328 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.j2ee:ear=NewsApp.ear,jar=NewsApp-ejb.jar,name=NewMessage,service=EJB3
      State: FAILED
      Reason: org.jboss.deployment.DeploymentException: Error for ActivationSpec class org.jboss.resource.adapter.jms.inflow.JmsActivationSpec as JavaBean; - nested throwable: (java.beans.IntrospectionException: No property found for: ConnectionFactoryJndiName on JavaBean: org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1589559(ra=null destination=activemq/queue/capacity3 isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0))
      I Depend On:
      persistence.units:ear=NewsApp.ear,jar=NewsApp-ejb.jar,unitName=NewsApp-ejbPU

      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.j2ee:ear=NewsApp.ear,jar=NewsApp-ejb.jar,name=NewMessage,service=EJB3
      State: FAILED
      Reason: org.jboss.deployment.DeploymentException: Error for ActivationSpec class org.jboss.resource.adapter.jms.inflow.JmsActivationSpec as JavaBean; - nested throwable: (java.beans.IntrospectionException: No property found for: ConnectionFactoryJndiName on JavaBean: org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1589559(ra=null destination=activemq/queue/capacity3 isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0))
      I Depend On:
      persistence.units:ear=NewsApp.ear,jar=NewsApp-ejb.jar,unitName=NewsApp-ejbPU


      (sorry for the long stack trace, but i think it's appropriate to include. my apologies if it is not.)

      Tobin

        • 1. Re: connectionFactoryJndiName config property
          Weston M. Price Master

          You want to use the ProviderAdapterJNDI property. This groups the queue and topic connection factories together:

          so

           @ActivationConfigProperty(propertyName = "providerAdapterJNDI", propertyValue = "YourJNDIProvider"),
          


          Of course you will have to deploy the Provider part as well. Take a look at jms-ds.xml for an example.



          • 2. Re: connectionFactoryJndiName config property
            Tobin Juday Newbie

            Thanks for the quick reply.

            I have already tried that, and it was giving me troubles, but maybe I did something wrong.

            I had added this to the jms-ds.xml

            <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.mq:service=JMSProviderLoader,name=RemoteJMSProvider,server=queuehost">
             <attribute name="ProviderName">QueuehostJMSProvider</attribute>
             <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
             <attribute name="QueueFactoryRef">UIL2XAConnectionFactory</attribute>
             <attribute name="TopicFactoryRef">UIL2XAConnectionFactory</attribute>
             <attribute name="Properties">
             java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
             java.naming.factory.url.pkgs=org.jnp.interfaces
             java.naming.provider.url=queuehost:1199
             </attribute>
            </mbean>


            and my bean looked like:

            @MessageDriven(
             mappedName = "jms/NewMessage",
             activationConfig = {
             @ActivationConfigProperty(propertyName="providerAdapterJNDI", propertyValue="java:/QueuehostJMSProvider"),
             @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
             @ActivationConfigProperty(propertyName = "destination", propertyValue = "activemq/queue/capacity3")
             }
            )
            public class NewMessage implements MessageListener {


            However, when I tried that (and I just tried it again), JBoss appears to hang when trying to deploy.

            17:41:29,546 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
            17:41:29,593 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=NewsApp.ear,jar=NewsApp-ejb.jar,name=NewMessage,service=EJB3 with dependencies:
            17:41:29,593 INFO [JmxKernelAbstraction] persistence.units:ear=NewsApp.ear,jar=NewsApp-ejb.jar,unitName=NewsApp-ejbPU
            17:41:29,640 INFO [EJBContainer] STARTED EJB: ejb.NewMessage ejbName: NewMessage


            It never gets any farther than that, and the application is not deployed.

            Tobin

            • 3. Re: connectionFactoryJndiName config property
              Weston M. Price Master

              I am assuming queuehost is up and running on the specified port and that you can actually seem the JNDIProviderAdapter bound into JNDI (JNDIView).
              Also, the Destination you want to access is deployed and bound into JNDI on the foreign host.

              Out of curiousity, are you attempting to access a non JBoss JMS provider? If this is the case you will want to make sure you use the foreign providers ConnectionFactory, not JBoss.




              • 4. Re: connectionFactoryJndiName config property
                Tobin Juday Newbie

                Ok, I'm new to all this, so some of your questions went over my head.

                I mapped queuehost to 127.0.0.1 in my hosts file, so the host is certainly up.

                I'm using ActiveMQ as my JMS provider, and it is up and running (on port 61616, jmx on port 1199).

                I'm not sure what you mean by JNDIView. How do I use that?

                ActiveMQ creates queues on the fly when requested (like JBoss MQ), so I did not actually create a queue in ActiveMQ.

                Here's the thing, I've tried two different "kinds" of tutorials now, and neither one has worked.
                (1) http://wiki.jboss.org/wiki/Wiki.jsp?page=HowDoIConfigureAnEJB3MDBToTalkToARemoteQueue
                and
                (2) http://devzone.logicblaze.com/site/integrating-apache-activemq-with-jboss.html

                Each take a slightly different approach.

                The first uses a customized JMSProvider, the second uses JCA.

                I followed the instructions given; for the first, it didn't tell me to use a specific ConnectionFactory, and for the second, I'm trying to use a specific ConnectionFactory and it's not working. Is there some step these tutorials have wrong? And are they 2 completely separate ways of configuring a remote queue, or are they related somehow (because I can't see the relationship if they are).

                Sorry if I sound frustrated, I've just spent a lot of time working on this, and have gotten absolutely nowhere.

                Tobin

                • 5. Re: connectionFactoryJndiName config property
                  Weston M. Price Master

                  Let's start with the simple stuff. What type of configuration do you want to support?

                  I am assuming that what you want to do is deploy an MDB into JBoss that is listening on an ActiveMQ destination (queue || topic) . Is this correct?

                  Small steps ;-)

                  Don't get too frustrated, it's just a simple matter of putting the right pieces of the puzzle in place.

                  • 6. Re: connectionFactoryJndiName config property
                    Tobin Juday Newbie

                    Whew, thank you. :)

                    Yes, you are correct.

                    Right now, I have a simple MDB that is called when a message hits a queue. It is working using the queues built in to JBoss, but now that my bean is working, I would like to migrate to ActiveMQ as my queue provider.

                    • 7. Re: connectionFactoryJndiName config property
                      Weston M. Price Master

                      Ok, excellent ;-)

                      So, first off go here:

                      http://www.activemq.org/site/jboss-integration.html

                      Again, let's take it one step at a time. First, deploy the ActiveMQ RAR file. Rather than bother with setting up an embedded broker which requires modifying the RAR file, let's just deploy it as is. This will set up the broker on port 61616 on localhost.

                      So, that's step one. I would recommend using the ActiveMQ 4.0.2 RAR. So, grab that guy from ActiveMQ and dump it in your JBoss deploy directory. To make things easier, why don't we start with a 'fresh' copy of JBoss as well just so we are not dealing with files that have been deployed before that you might not want.


                      • 8. Re: connectionFactoryJndiName config property
                        Tobin Juday Newbie

                        Ok, done (sorry it took a little while).

                        The only thing that concerns me a little with this fresh install are the following log messages

                        20:08:01,109 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
                        20:08:01,343 INFO [[/web-console]] MonitorsFolder: Failed to init plugin, null
                        20:08:01,343 INFO [[/web-console]] UCLs: Failed to init plugin, null
                        20:08:01,359 INFO [[/web-console]] JMS Message: Failed to init plugin, null
                        20:08:01,359 INFO [[/web-console]] JSR77 WebModule: Failed to init plugin, null
                        20:08:01,375 INFO [[/web-console]] J2EEFolder: Failed to init plugin, null
                        20:08:01,375 INFO [[/web-console]] AOPFolder: Failed to init plugin, null
                        20:08:01,375 INFO [[/web-console]] SystemFolder: Failed to init plugin, null
                        20:08:01,734 INFO [[/web-console]] MBeans: Failed to init plugin, null
                        20:08:01,750 INFO [[/web-console]] JSR77 Domains and Servers: Failed to init plugin, null
                        20:08:01,750 INFO [[/web-console]] JSR77 EJBModules and EJBs: Failed to init plugin, null

                        20:08:01,750 INFO [[/web-console]] JSR77 J2EE Apps: Failed to init plugin, null


                        In the web console now, there are no menu items in the Java applet menu on the left. In my previous JBoss installation, that worked.

                        But other than that, it looks ok.

                        • 9. Re: connectionFactoryJndiName config property
                          Weston M. Price Master

                          Can you go to

                          http://hostname:8080/jmx-console

                          I want to make sure the RAR is deploying.

                          You should see it listed under jboss.jca:


                          name='activemq-ra-4.0.2.rar',service=RARDeployment


                          • 10. Re: connectionFactoryJndiName config property
                            Tobin Juday Newbie

                            Yep, it's there.

                            • 11. Re: connectionFactoryJndiName config property
                              Tobin Juday Newbie

                              Yep, it's there.

                              • 12. Re: connectionFactoryJndiName config property
                                Weston M. Price Master

                                Ok, now it's time to put the *-ds.xml file in place. The panacya-ds.xml from the link I sent is a good starting point.

                                Also, because we are using the non-embedded server, you should have ActiveMQ installed and up and running. Do you have this?

                                • 14. Re: connectionFactoryJndiName config property
                                  Weston M. Price Master

                                  Ok, so let's deploy the *-ds.xml file. Drop it in your deploy directory. Note, the *-ds.xml file has an entry for the RAR you should use. This should be set to the RAR name that you previously deployed.

                                  So

                                   <tx-connection-factory>
                                   <jndi-name>activemq/QueueConnectionFactory</jndi-name>
                                   <xa-transaction/>
                                   <track-connection-by-tx/> <!-- Thanks to Adrian Brock for pointing this one out! -->
                                   <!-- Your RAR name here -->
                                   <rar-name>activemq-ra-1.4.rar</rar-name>
                                   <connection-definition>javax.jms.QueueConnectionFactory</connection-definition>
                                   <security-domain-and-application>JmsXARealm</security-domain-and-application>
                                   </tx-connection-factory>
                                  
                                  


                                  1 2 3 Previous Next