1 Reply Latest reply on Aug 15, 2006 7:49 AM by Christopher Fagiani

    tibco ems and jboss 4.0.4

    Christopher Fagiani Newbie

      I am using MDBs on JBoss 4.0.4 running on Redhat linux and using Tibco's EMS as a JMS provider (on a different physical server than the app server). I followed the instructions in this wiki post:

      http://wiki.jboss.org/wiki/Wiki.jsp?page=IntegrationWithTibcoEMS

      My MDB cannot connect to the queue, though because Jboss is trying to connect on the default port (7222) instead of the one set in the properties file (8222). Is there any setting I can make to have the server point to the correct queue?

      I verified that the EMS integration works (I pointed to another EMS server that is running on 7222 and everything works fine), but I need to get this working on the server running on 8222.



      The error in the logs is:

       Failed to connect to the server at tcp://xxx:7222
      


      Anonomized sections of my config files are below:

      jms-ds.xml:

      <server>
      
       <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name=":service=JMSProviderLoader,name=TibjmsProvider">
       <attribute name="ProviderName">TIBCOJMSProvider</attribute>
       <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
       <attribute name="QueueFactoryRef">QueueConnectionFactory</attribute>
       <attribute name="TopicFactoryRef">TopicConnectionFactory</attribute>
       <attribute name="Properties">
       java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
       java.naming.provider.url=tcp://XXX.mydomain.com:8222
       </attribute>
       </mbean>
      
       <mbean code="org.jboss.naming.NamingAlias"
       name="DefaultDomain:service=NamingAlias,fromName=QueueConnectionFactory">
       <attribute name="ToName">tibjmsnaming://XXX.mydomain.com:8222/QueueConnectionFactory</attribute>
       <attribute name="FromName">QueueConnectionFactory</attribute>
       </mbean>
      
      </server>
      



      jndi.properties

      java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:com.tibco.tibjms.naming


      standardjboss.xml

       <DestinationQueue>tibjmsnaming://xxx.mydomain.com:8222/queue/DLQ</DestinationQueue>
      



      jboss.xml deployment descriptor
      <jboss>
      
       <invoker-proxy-bindings>
       <invoker-proxy-binding>
       <name>ivas-mdb-invoker</name>
       <invoker-mbean>xxx-mdb-invoker</invoker-mbean>
       <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
       <proxy-factory-config>
       <JMSProviderAdapterJNDI>TIBCOJMSProvider</JMSProviderAdapterJNDI>
       <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
       <MinimumSize>1</MinimumSize>
       <KeepAliveMillis>30000</KeepAliveMillis>
       <MaximumSize>15</MaximumSize>
       <MaxMessages>1</MaxMessages>
       <MDBConfig>
       <ReconnectIntervalSec>10</ReconnectIntervalSec>
      
       </MDBConfig>
       </proxy-factory-config>
       </invoker-proxy-binding>
       </invoker-proxy-bindings>
      
       <enterprise-beans>
       <message-driven>
       <ejb-name>PollMessageBean</ejb-name>
       <destination-jndi-name>ivasVoteQueue</destination-jndi-name>
       <invoker-bindings>
       <invoker>
       <invoker-proxy-binding-name>xxx-mdb-invoker</invoker-proxy-binding-name>
       </invoker>
       </invoker-bindings>
       </message-driven>
      
      
       </enterprise-beans>
      
       <resource-ref>
       <res-ref-name>jms/QCF</res-ref-name>
       <jndi-name>QueueConnectionFactory</jndi-name>
       </resource-ref>
      
      </jboss>