JBoss 4.0.5 GA and Tibco EMS 6.0 - Acknowledgement Mode
kthegeek Jun 24, 2013 6:14 PMHi ,
We are using jboss version 4.0.5 and have deployed a EJB project to test an integeration with Tibco EMS
I have mentioned in the ejb-jar.xml to set up the message driven bean as Auto-acknowledge.But still the consumer acknowledge mode in TIBCO is Client Acknowledge.
Please let me know if i need to make changes to any other configuration files to have the consumer/bean registered for Auto-acknowledge
here are my configuration files
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd"> <ejb-jar> <enterprise-beans> <message-driven> <description>TestMessageDrivenBean</description> <ejb-name>TestMessageDrivenBean</ejb-name> <ejb-class>org.test.TestMessageDrivenBean</ejb-class> <transaction-type>Bean</transaction-type> <message-selector></message-selector> <acknowledge-mode>Auto-acknowledge</acknowledge-mode> <message-driven-destination> <destination-type>javax.jms.Queue</destination-type> <subscription-durability>NonDurable</subscription-durability> </message-driven-destination> </message-driven> </enterprise-beans> </ejb-jar>
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://host1:6222,tcp://host2:6224</attribute> </mbean> </server>
jboss.xml
<?xml version="1.0" encoding="UTF-8"?> <jboss> <invoker-proxy-bindings> <invoker-proxy-binding> <name>cpas-TestMessageDrivenBean-invoker</name> <invoker-mbean>cpas-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>5</MaximumSize> <MaxMessages>1</MaxMessages> <MDBConfig> <ReconnectIntervalSec>10</ReconnectIntervalSec> </MDBConfig> </proxy-factory-config> </invoker-proxy-binding> </invoker-proxy-bindings> <enterprise-beans> <message-driven> <ejb-name>TestMessageDrivenBean</ejb-name> <configuration-name>Standard Message Driven Bean</configuration-name> <destination-jndi-name>testQueue</destination-jndi-name> <invoker-bindings> <invoker> <invoker-proxy-binding-name>cpas-TestMessageDrivenBean-invoker</invoker-proxy-binding-name> </invoker> </invoker-bindings> <xa-connection>false</xa-connection> </message-driven> </enterprise-beans> </jboss>
Thanks,
-KR