Products | Versions |
---|---|
TIBCO Enterprise Message Service | - |
Not Applicable | - |
Description:
TIBCO Enterprise Message Service 4.4.1 Hotfix2 has been released
* You can download this 4.4.1 Hotfix2 from the TIBCO Product Support FTP server using your eSupport username and password, at
ftp://support-ftp.tibco.com
* This server hotfix is cumulative. It includes all previously generated TIBCO Enterprise Message Service 4.4.1 server hotfixes.
======================================================================
Affected Files for 4.4.1-hotfix02
The following files are installed by this hotfix. Note that some files may be platform-specific and are installed only on that platform.
All Platforms:
tibemsd
tibemsd64
======================================================================
Closed Issues in 4.4.1-hotfix02 (this release):
Defect ID: 1-838PFR
A change in Release 4.4.0 resulted in a performance issue with
the data store for valid messages. This has been fixed.
Defect ID: 1-7W1MX1
The error "Error: Global or routed queue cannot specify
prefetch=none" was returned when using "addprop" to set any
property. This has been fixed so that properties (except for
prefetch=none) can now be set on global or routed queues.
Defect ID: 1-837ZMF
If an application that uses a client ID disconnects or terminates
before a commit() succeeds, immediately reconnecting was not
always successful. This has been fixed.
Defect ID: 1-81ZZCH
Fixed a defect that could cause the server to not recover valid
messages if, prior to the restart, the server ran out of memory
at a very specific point in time while creating an internal
record that is later persisted on disk. This memory failure may
not be repored if the user is not using reserve_memory. Of
course, users should always ensure that the EMS Server has
appropriate resources. You can limit the memory usage by setting
the max_msg_memory parameter according to the system's memory
availability.
======================================================================
Closed Issues in 4.4.1-hotfix01:
Defect ID: 1-82HYZW
In EMS 4.4.0, messages in the $sys.undelivered queue that are
consumed are not removed from the "Pending Message" count.
This has been fixed.
Defect ID: 1-820SBH
Fixed a defect that could cause the EMS Server to crash when it
would try to discard NON_PERSISTENT or RELIABLE messages that
have reached their maximum delivery count based on the queue's
maxRedelivery property. Messages with the
TIBCO_PRESERVE_UNDELIVERED boolean property would be unaffected
and are correctly moved to the $sys.undelivered queue.
Defect ID: 1-81UJTJ
Under an operational mode that disables batched synchronous
writes, the server may return the debug message "DEBUG:
Insufficient buffer - SEVERE ERROR: Failed writing message".
This has been fixed.
======================================================================
Installation
Stop the applications and EMS server.
Replace the EMS server binary with the new version supplied.
Start the EMS server and its applications.