IBM
Platform Symphony 6.1.1 Fix Patch #230310
Readme
File
Abstract
When a Symphony service instance had an infinite loop or other event listeners in the callback function onSessionEnter, after user tried to abort the session, the slot occupied by the instance was wasted.
Description
If the callback function onSessionEnter cannot return for a long time
when the session is aborted, the slot occupied by the SI will be wasted;
SI and corresponding SIM will hang forever; other applications cannot
get the wasted slots.
This fix patch applies only to the following platform:
· Linux 64-bit
Readme file for: IBM® Platform Symphony
Product/Component Release: 6.1.1
Update Name: Fix pack
Fix ID: sym-6.1.1-build230310-ms
Publication date: 26th Feb, 2014
Last modified date: 26th Feb, 2014
Contents
1.
List of fixes
2.
Download location
3.
Products or components affected
4.
System requirements
5.
Installation and configuration
6.
List of files
7. Copyright and trademark
information
1.
List of fixes
SUP_BY_SYM#229582
2.
Download location
Download
Fix #230310 from the following location:
http://www.ibm.com/eserver/support/fixes/
3.
Products or
components affected
Product/Component Name, Platform,
Fix ID:
Platform Symphony/ssm, Linux 64-bit, sym-6.1.1-build230310-ms
4.
System
requirements
N/A
5. Installation and configuration
5.1 Before installation
1.
Disable all applications
Log on
to the master host as the cluster administrator and run:
> source cshrc.platform
> soamcontrol app disable all
2. Back up file
Log on to each
management host and back up the following binary that will be replaced by this
patch:
> $SOAM_HOME/6.1.1/linux2.6-glibc2.3-x86_64/etc/ssm
5.2 Installation steps
Apply
the fix patch
Log on to each management host and replace
the old binary “ssm” with the downloaded one in the following directory:
> $SOAM_HOME/6.1.1/linux2.6-glibc2.3-x86_64/etc/ssm
5.3 After installation
1.
Verify the installation
>$SOAM_HOME/6.1.1/linux2.6-glibc2.3-x86_64/etc/ssm -V
Platform
Symphony 6.1.1.230310, Feb 26 2014
Copyright
(C) 2001-2011 Platform Computing Corporation.
2. Configure the
parameter of “SOAM_CANCEL_BIND_SESSION_END” in the application profile. For
example:
<SSM ……> <osTypes> <osType name="X86_64" …… <env name="SOAM_CANCEL_BIND_SESSION_END ">true</env>
</osType> </osTypes> </SSM> |
Set the value of env parameter
SOAM_CANCEL_BIND_SESSION_END to true to enable the feature; for other values,
the feature is disabled, which is the default.
3.
Enable all applications
Log on
to the master host as the cluster administrator and run:
>
source cshrc.platform
>
soamcontrol app enable <appName>
5.4 Uninstalling
1.
Disable all applications
Log on
to the master host as the cluster administrator and run:
> source cshrc.platform
> soamcontrol app disable all
2. Restore the backup file
Log on
to each management host and restore the backup file for the following binary:
>
$SOAM_HOME/6.1.1/linux2.6-glibc2.3-x86_64/etc/ssm
6.
List of files
ssm
7. Copyright and trademark information
© Copyright IBM Corporation 2014
U.S. Government Users Restricted
Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
IBM®, the IBM logo and ibm.com® are trademarks of
International Business Machines Corp., registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.