Issue with jboss tibco integration after tibco EMS restart

[ravikanth reddy]

1. I have set up Tibco EMS Server
2. JBOSS4.2.3GA with jobs messaging
3. Two queues hosted in TIbco server firstQueue, secondQueue
4. I have consumer in JBOSS for firstTibcoQueue (FirstQueueBean.java)
5. I have session bean in jboss SecondQueueBean.java in the same server instance(same.ear) it post message on to secondTibcoQueue

Here the problem is, if Tibco server goes down in between, after that my MDB FirsQueueBean unable to consume message from the firstTibcoQueue.

But I am able to send messages on secondTibcoQueue.

I have monitored jboss logs after Tibco restart my server is able to reconnect successfully.


I am able to post the message but unable to consume the message.

Could you please let me know what is the problem here? Is I am missing any configuration. I have configured this instance as per JBOSS documentation.

tibco-ds.xml

<?xml version="1.0" encoding="UTF-8"?>
<connection-factories>

    
    <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
        name="jboss.messaging:service=JMSProviderLoader,name=TibcoJMSProvider">
        <attribute name="ProviderName">TibcoJMSProvider</attribute>
        <attribute name="ProviderAdapterClass">
            org.jboss.jms.jndi.JNDIProviderAdapter
        </attribute>
        <attribute name="FactoryRef">ConnectionFactory</attribute>
        <attribute name="QueueFactoryRef">
            XAQueueConnectionFactory
        </attribute>
        <attribute name="TopicFactoryRef">
            XAConnectionFactory
        </attribute>
        <attribute name="Properties">
            java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
            java.naming.factory.url.pkgs=com.tibco.tibjms.naming
            java.naming.provider.url=tibjmsnaming://dingo:7222
            java.naming.security.principal=tibadm
            java.naming.security.credentials=tibadm
        </attribute>
    </mbean>

    <!-- The server session pool for Message Driven Beans -->
    <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
        name="jboss.mq:service=ServerSessionPoolMBean,name=TibcoJMSPool">
        <depends optional-attribute-name="XidFactory">
            jboss:service=XidFactory
        </depends>
        <attribute name="PoolName">TibcoJMSPool</attribute>
        <attribute name="PoolFactoryClass">
            org.jboss.jms.asf.StdServerSessionPoolFactory
        </attribute>
    </mbean>

    <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
    <tx-connection-factory>
        <jndi-name>TibcoJmsXA</jndi-name>
          <use-java-context>false</use-java-context>
        <xa-transaction />
        <rar-name>jms-ra.rar</rar-name>
        <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
        <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
        <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/TibcoJMSProvider</config-property>
        <config-property name="UserName" type="java.lang.String">tibadm</config-property>
        <config-property name="Password" type="java.lang.String">tibadm</config-property>
        <max-pool-size>20</max-pool-size>        
    </tx-connection-factory>
      
</connection-factories>

Could you please let me know why my consumer is not able to reconnect to Tibco Server?

[Jaikiran Pai]

Is this EJB2.x MDB or a EJB3 MDB?

[ravikanth reddy]

Thanks for the reply.

It is ejb2.1 mdb.

[Jaikiran Pai]

From what I know, by default, the "ReconnectIntervalSec" is set to 10 seconds for the MDBs unless you have overridden it http://community.jboss.org/wiki/ConfigJBossMDB

[ravikanth reddy]

Hi Jaikiran,

I have overriden this value in jboss.xml

jboss.xml

<message-driven>
            <ejb-name>FirstQueueBean</ejb-name>
            <destination-jndi-name>firstQueue</destination-jndi-name>
            <mdb-user>tibuser</mdb-user>
            <mdb-passwd>tibpwd</mdb-passwd>
            <invoker-bindings>
                <invoker>
                    <invoker-proxy-binding-name>TibcoInvoker</invoker-proxy-binding-name>
                </invoker>
            </invoker-bindings>



----


<invoker-proxy-bindings>
    <invoker-proxy-binding>
            <name>TibcoInvoker</name>
            <invoker-mbean>TibcoInvokerjmx</invoker-mbean>
            <proxy-factory>
                org.jboss.ejb.plugins.jms.JMSContainerInvoker
            </proxy-factory>
            <proxy-factory-config>
                <JMSProviderAdapterJNDI>TibcoJMSProvider</JMSProviderAdapterJNDI>
                <ServerSessionPoolFactoryJNDI>TibcoJMSPool</ServerSessionPoolFactoryJNDI>
                <MinimumSize>1</MinimumSize>
                <MaximumSize>15</MaximumSize>
                <KeepAliveMillis>30000</KeepAliveMillis>
                <MDBConfig>
                    <ReconnectIntervalSec>10</ReconnectIntervalSec>
                </MDBConfig>
            </proxy-factory-config>
        </invoker-proxy-binding>
----

When tibco server is down I can see below error messgage in the logs
javax.jms.JMSException: Failed to connect to the server at tcp://dingo:7222

when tibco srver is up jboss server is able to reconnect successfully.