Tibco Gems Code From Can

Its a freeware which was developed distributed by the Tibco community and is very helpful for debuggingtesting purposes.GEMS can be found and downloaded from tibcommunity.com.

To find out more, including how to control cookies, see here.

It can be used by JMS developers as a general purpose test debugging tool and by administrative support staff as a management and monitorig tool.

Request and reply messages can be correlated to provide service response times.

A destination can be created statically in the server configuration files, or dy.

The log file location depends on whether you are accessing an administration domain.

All other names mentioned herein may be trademarks of their respective owners.

The use of any Trademark or Copyrighted material is not intended to infringe Copyright.

This blog is intended to be used under a policy of personal and non commercial use.

How to test your implementation for automatic reconnectionrecovery from JMS connection issues Option1 If you dont have access to a TIBCO EMS server that you can bounce or kill anytime then here is one possible way to test it.

This tool uses JavaScript and much of it will not work correctly without it enabled.

A special thanks to Marjono Reksopuro, Susanta Mondal and Michael McKernan for their help with Tibco Administration, integration and testing for this configuration.

TibcoEMS Configuration The steps in this section outline the steps required to create a test queue on TibcoEMS as well as the DLQ.

Please note this EMS configuration assumes the following: - Authorization enabled - UsernamePassword are set to: adminadmin - A single instance running locally: localhost with port of 7222.

Queues and Connection Factories Step2 Create two queues (queuemyTestQueue and queueDLQ) and two XA connection factories (TIBXAQueueConnectionFactory and TIBXATopicConnectionFactory), by entering the following commands in tibemsadmin: connect create queue queuemyTestQueue create queue queueDLQ create factory TIBXAQueueConnectionFactory xaqueue urltcp:localhost:7222 create factory TIBXATopicConnectionFactory xatopic url tcp:localhost:7222 Tibco pairs for Failover: create factory TIBXAQueueConnectionFactory xaqueue urltcp:localhost:7222, tcp:localhost:7222 create factory TIBXATopicConnectionFactory xatopic url tcp:localhost:7222, tcp:localhost:7222 JBoss Configuration The steps in this section outline the steps required to configure JBoss to connect withTibcoEMS.

Step1 Add TIBCO EMS and the TIBCO EMS adapter class for JBoss to the CLASSPATH of the JBoss server.

There are two options to accomplish this: Option1 Add the following lines under the element in the file JBOSSHOMEjboss-asservermyinstanceconfjboss-service.xml: Option2 Copy tibjms.jar file to: JBOSSHOMEjboss-asservermyinstancelib Step2 Create a new datasource file called tibco-jms-ds.xml or whatever name you prefer, and place it in: JBOSSHOMEjboss-asservermyinstancedeploy And add the following contents to the file mentioned above: noformat.

Therefore, modify the file JBOSSHOMEjboss-asservermyinstanceconfjndi.properties as follows: Change: java.naming.factory.url.pkgsorg.jboss.naming:org.jnp.interfaces To java.naming.factory.url.pkgsorg.jboss.naming:org.jnp.interfaces:com.tibco.tibjms.naming When Using a Client Step1 When the client program invokes JNDI, it should use the TIBCO Enterprise Message Service JNDI server.

Modify JBOSSCLIENTjndi.properties to use TIBCO Enterprise Message Service JNDI by setting the following property: java.naming.factory.initialcom.tibco.tibjms.naming.TibjmsInitialContextFactory Step2 Add EMSHOMElibtibjms.jar to the CLASSPATH of the client program.

Tibco Gems Code From Can

MDB configuration The sample mdb code from can be used: IntegrationWithTibcoEMS Update your jboss.xml file to look as follows.

The problem here is that the number of times to attempt to reconnect to the JMS provider needs a new property reconnectAttempts and by default it is 5.

Prior to this version, reconnection attempts were infinite by default.

In the above format it is not possible to define the reconnectAttempts.

I have tested this with JBoss 5.1.0GA.

Update your jboss.xml file to look as follows - replace the invoker-proxy-binding block with following.

You need to catch the JMSException when sending the reply, and first close the session and connection (look at the ejbRemove), and then reconnect again (look at setup) before retrying to send the reply message.

Attached is a modified TIBCO tibjmsMsgAsyncConsumer example that demonstrates use of automatic reconnection with plain Java.

The tibjmsMsgProducer demonstrates a simple request-reply client with automatic reconnection.

If you need access to multithreaded TIBCO examples they can be found in the EMS samples directory (any EMS installation).

Or here. TIBCO EMS documentation is available at docs.tibco.com.

And you can download an evaluation version of EMS here.

I experimented also with the TibjmsConnectionFactory.setReconnAttemptCountDelayTimeout settings.

Changing those defaults helps only to reconnect during a fairly short period depending on other settings like client to server heartbeat parameters andor your TCP settings in your operating system.

It seems that if EMS has purged the client connection due to a network issue ( about 15 mins for my EMSLinux server when client heartbeat is not activated, less with heartbeat on ), setting the ReconnAttemptCount to a big number does not help any more, and EMS logs repeatedly that reconnect failed.

So my advice is to register an exception listener and loop until a new connection is created.

Perhaps delays between connect attempts need to be carefully considered not to create too big log files during connection issues.

After all this trial and error I honestly think that its perhaps easier to not to use EJBMDB at all but to use plain Java for TIBCO JMS (or any JMS provider).

Or use TIBCO Businessworks for your JMS projects, because it makes life easy.

Install Tibco Gems