Resolution:
TIBCO Enterprise Message Service 4.4.3 Hotfix1 has been released

* You can download this 4.4.3 Hotfix1 from the TIBCO Product Support FTP server using your eSupport username and password, at

            ftp://support-ftp.tibco.com

* This hotfix is available on all platforms.

The following file is installed by this hotfix:

   tibrvjms.jar

* Closed Issues in 4.4.3-hotfix01 (this release):

Defect ID: 1-8X8G0U
======
     Fixed an error that prevented temporary topics from being
     deleted. The tibrvjms.jar could cause the EMS server to leak
     temporary topics in two ways:
      - If the application used the sendRequest method, it created a
        temporary topic for the reply which was not later deleted.
      - If the application called the createInbox method, the
        corresponding temporary topic was immediately leaked.
     This has been fixed.

Symptoms:
========

If you run "show topics" tibemsadmin commands and notice a lot of temporary topics with "0" value on "Subs" "Msgs" columns, You may run into this defect.

If you suspect that you run into this defect, you can select one of those topics and do a "show topic &lttemporary topic name>".
If this temporary topic was created by an EMS 4.4+ client, there should be a connection id greater than 0 in the output. Then, using "show connections version", you can find this connection in the list, and based on the username/hostname you should be able to verify that this temporary topic has been created by which application.


Impact:
=======

The accumulation of a very high number of temporary topics will cause an EMS Server memory usage increase, potentially leading to degraded performance and/or the process running out of memory.

Workaround:
========

If the connections are destroyed, the orphan Temporary topics will be deleted automatically. You can create a utility with tibems Admin API to remove the orphan temporary topics periodically.

If none of the above workarounds is suitable for you, please contact Tibco Support, there may be additional workarounds for you depending on which product you are running. E.g. If you are Hawk Display,  exit the Display, the temporary topics will be removed.

If you need any assistant, please contact Tibco Support at support@tibco.com.


Cause:
========

In EMS 4.4.0 we fixed defects:

--------------------------------------
Upgraded the clients and server so that temporary destinations are
fully JMS compliant.
--------------------------------------

Pre EMS 4.4.0, the EMS Server deletes temporary destinations at regular interval when those temporary destinations do not have any message and consumer."
To comply with JMS spec, after EMS 4.4.0, client who calls "session.createTemporaryTopic();", should delete the temporary topic
explicitly, EMS only delete the temporary topic automatically when connections is closed.

Unfortunately the TibrvJMSTransport class in the tibrvjms.jar does not explicitly destroy the temporary destination and so they
accumulate until the transport is destroyed..


======================================================================
Installation

    Stop all applications that use the tibrvjms.jar file (this
    includes all applications that use Rendezvous transports).

    Replace the tibrvjms.jar file.

    Start the applications.

======================================================================