chunk_id string | chunk string |
|---|---|
0a817ba4be5983fa2a09beda72f6dfce_0 | IBM Security Bulletin: IBM MQ termination of a client application causes denial of service (CVE-2017-1235) - United States SECURITY BULLETIN
SUMMARY
Termination during an MQGET call of a client application running on a channel with SHARECNV=1, could cause a SIGSEGV and termination of the channel agent process.
VULNERABILITY DETAILS
CVEID: CVE-2017-1235 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1235]
DESCRIPTION: IBM MQ could allow an authenticated user to cause a premature termination of a client application thread, which could potentially cause denial of service.
CVSS Base Score: 3.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/123914 [https://exchange.xforce.ibmcloud.com/vulnerabilities/123914] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L)
AFFECTED PRODUCTS AND VERSIONS
IBM MQ V8.0
IBM MQ V8.0.0.6 and earlier maintenance levels. |
0a817ba4be5983fa2a09beda72f6dfce_1 | IBM MQ V9.0 Long Term Support Release
IBM MQ V9.0.0.1 and earlier maintenance levels.
IBM MQ V9.0 Continuous Delivery Release
IBM MQ Continuous delivery update 9.0.3 and earlier maintenance levels.
REMEDIATION/FIXES
IBM MQ V8.0
Apply 8.0.0.7 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.7&platform=All&function=all&useReleaseAsTarget=true] maintenance level.
IBM MQ V9.0 Long Term Support Release
Apply 9.0.0.2 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=9.0.0.2&platform=All&function=all&useReleaseAsTarget=true] maintenance level.
IBM MQ V9.0 Continuous Delivery Release
Apply continuous delivery update 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348] or later |
0a817ba4be5983fa2a09beda72f6dfce_2 | GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.
IMPORTANT NOTE
IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.
REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] |
0a817ba4be5983fa2a09beda72f6dfce_3 | RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. |
fead7be351c2c89d3239797643852c95_0 | IBM Solving IBM MQ Java code version mismatches using the mqjavalist.sh script - United States WebSphere MQ WMQ TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
When Java™ SE applications and Java EE application servers such as WebSphere Application Server do not use a consistent set of MQ Java archives, applications can fail in unpredictable ways. If WebSphere Application Server notices a mismatch, it issues this message: "MQJCA1008 The WebSphere MQ classes for JMS were found in the class path but were not the correct version. This error can occur if the application server finds an earlier version of the WebSphere MQ classes for JMS in the class path. The error can also occur if you do not configure WebSphere Application Server to use the correct version of the WebSphere MQ classes for JMS." |
fead7be351c2c89d3239797643852c95_1 | ENVIRONMENT
The mqjavalist.sh script runs on Linux and UNIX systems and can identify Java archives and classes from MQ V5.3 and later versions. Although the mqjavalist.sh script does not run on Windows systems, it is possible to zip up a directory structure on Windows in order to examine it with mqjavalist.sh on a different system. To use the mqjavalist.sh script, download it from the bottom of this page, copy it to the target system, and make the script executable. Make sure that either the unzip command or the Java jar command is available in your PATH before running mqjavalist.sh. For example:
1. Preparing to run mqjavalist.sh
2.
3. sh> chmod +x mqjavalist.sh
sh> PATH=$PATH:/opt/java7/bin |
fead7be351c2c89d3239797643852c95_2 | DIAGNOSING THE PROBLEM
IBM MQ ships a number of Java archives (jar files) that applications use to connect to MQ and work with messages. For Java EE environments, MQ provides a Resource Adapter called wmq.jmsra.rar which contains the jar files required by JMS applications. Java SE and Java EE applications must use a consistent set of MQ jar files at the same maintenance level, or else they might experience a wide variety of problems including intermittent errors, performance problems, and other failures.
It is common to find multiple versions of the MQ jar files in the Java CLASSPATH, or invalidly bundled in Java applications (.ear, .war, and .jar files). Finding and eliminating duplicate copies of the MQ jar files can be a difficult task, but the mqjavalist.sh script simplifies that task on Linux and UNIX systems.
* Syntax
* Examples
* WebSphere Application Server
* Sample output
* Resolving problems
* Download
SYNTAX |
fead7be351c2c89d3239797643852c95_3 | 1. mqjavalist.sh -? | -h
2.
3. mqjavalist.sh [-v] [-r] [-f File] -d Directory ...
4.
5.
6.
7. -?:
8.
9.
10. -h:
11.
12.
13. -v:
14.
15.
16. -r:
17.
18.
19. -f File:
20.
21.
22. -d Directory:
23.
24.
25.
26.
27.
28. The mqjavalist.sh script can take several minutes to complete, depending on the number of Java archives to search and whether you perform a recursive examination of archive files. While running, the script regularly prints its status and the percentage of work completed.
Back to top
EXAMPLES |
fead7be351c2c89d3239797643852c95_4 | 1. Search for MQ files under /usr/IBM/WebSphere and save the results to the file mqlist.txt:
mqjavalist.sh -f mqlist.txt -d /usr/IBM/WebSphere
2.
3.
4. Perform a recursive search of archives under /opt/IBM:
mqjavalist.sh -r -d /opt/IBM
5.
6.
7. Recursively search archive files under the /opt/IBM/IIB and /opt/mqm directories and enable verbose output to ~/output.txt:
mqjavalist.sh -vrf ~/output.txt -d /opt/IBM/IIB -d /opt/mqm
8.
Back to top
WEBSPHERE APPLICATION SERVER
WebSphere Application Server and other IBM products built on WebSphere Application Server normally show the MQ jar files in more than one location. Except as noted below, the copies of the MQ jar files should match the versions listed on this page [https://www.ibm.com/support/docview.wss?uid=swg21248089]. Any copies of the MQ jar files other than those listed below might represent a problem:
1. WebSphere Application Server V8.5.5, V8.5 and V8.0
2.
3. |
fead7be351c2c89d3239797643852c95_5 | 1. WebSphere Application Server V7.0
2.
3.
4.
5.
6. If you created a WebSphere Application Server V7.0 profile before applying fix pack 7.0.0.1 or later, you must update the profile to use the correct MQ Resource Adapter path [https://www.ibm.com/support/knowledgecenter/SSAW57_7.0.0/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tmj_wmqra_restoredefault.html]. Otherwise, the application servers in that profile will use the old MQ Resource Adapter jars under the profile installedConnectors/wmq.jmsra.rar directory rather than the MQ jars in the main installedConnectors/wmq.jmsra.rar directory, which are kept up to date by WebSphere Application Server fix packs.
1. WebSphere Application Server V6.1
2.
3.
Back to top
SAMPLE OUTPUT |
fead7be351c2c89d3239797643852c95_6 | 1. sh>
2. ./mqjavalist.sh -r -f mqlist.txt -d /opt/IBM/WebSphere/AppServer
3.
4. Running mqjavalist.sh V1.4 on SUSE Linux Enterprise Server 10 (ppc) with arguments: -r -f mqlist.txt -d /opt/IBM/WebSphere/AppServer
mqjavalist.sh: Searching directory /opt/IBM/WebSphere/AppServer
mqjavalist.sh: 2180 possible Java archives found
1. Found 80 MQ classes in classes.jar in WMQHTTP.war in /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear:
root root 145600 2014-07-16 13:56 /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear
2. Found 80 MQ classes in /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/aemtux1Cell01/WMQHTTP_war.ear/WMQHTTP.war/WEB-INF/lib/classes.jar: |
fead7be351c2c89d3239797643852c95_7 | root root 156845 2013-09-25 18:02 /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/aemtux1Cell01/WMQHTTP_war.ear/WMQHTTP.war/WEB-INF/lib/classes.jar
3. Found 80 MQ classes in classes.jar in WMQHTTP.war in /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear:
root root 145600 2014-07-16 13:57 /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear
4. Found com.ibm.mq.commonservices.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar
Implementation-Title: WebSphere MQ Common Service
Implementation-Version: ${version.number} - ${build.level}
Implementation-Vendor: IBM Corporation
5. Found com.ibm.mq.connector.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar |
fead7be351c2c89d3239797643852c95_8 | Implementation-Title: WebSphere MQ J2EE Connector Architecture
Implementation-Version: 7.1.0.0-k000-L111005.1
Implementation-Vendor: IBM Corporation
6. Found com.ibm.mq.headers.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 /wmq.jmsra.rar
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
7. Found com.ibm.mq.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
8. Found com.ibm.mq.jmqi.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar |
fead7be351c2c89d3239797643852c95_9 | Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
9. Found com.ibm.mq.jmqi.local.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
10. Found com.ibm.mq.jmqi.remote.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
11. Found com.ibm.mq.jmqi.system.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar |
fead7be351c2c89d3239797643852c95_10 | Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
12. Found com.ibm.mq.jms.admin.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar
Implementation-Title: JMS Common Client API/SPI
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
13. Found com.ibm.mq.pcf.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
14. Found com.ibm.mqjms.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar
Implementation-Title: JMS Client Common Facade |
fead7be351c2c89d3239797643852c95_11 | Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
15. Found dhbcore.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:
root root 7885592 2012-10-15 12:56 wmq.jmsra.rar
Implementation-Version: "DH610-GOLD"
Implementation-Title: "Webscale Distribution Hub Core"
Implementation-Vendor: "IBM Corporation"
16. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.jar:
root root 1115668 2012-10-15 12:56 com.ibm.mq.jmqi.jar
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
17. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.commonservices.jar:
root root 728387 2012-10-15 12:56 com.ibm.mq.commonservices.jar
Implementation-Title: WebSphere MQ Common Service |
fead7be351c2c89d3239797643852c95_12 | Implementation-Version: ${version.number} - ${build.level}
Implementation-Vendor: IBM Corporation
18. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.remote.jar:
root root 546407 2012-10-15 12:56 com.ibm.mq.jmqi.remote.jar
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
19. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jar:
root root 448745 2012-10-15 12:56 com.ibm.mq.jar
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
20. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jms.admin.jar:
root root 358016 2012-10-15 12:56 com.ibm.mq.jms.admin.jar
Implementation-Title: JMS Common Client API/SPI |
fead7be351c2c89d3239797643852c95_13 | Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
21. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mqjms.jar:
root root 352254 Aug 01 11:49 com.ibm.mqjms.jar
Implementation-Title: JMS Common Client facade
Implementation-Version: 7.0.1.5 - k701-105-110419
Implementation-Vendor: IBM Corporation
22. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.connector.jar:
root root 339396 2012-10-15 12:56 com.ibm.mq.connector.jar
Implementation-Title: WebSphere MQ J2EE Connector Architecture
Implementation-Version: 7.1.0.0-k000-L111005.1
Implementation-Vendor: IBM Corporation
23. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.headers.jar:
root root 338572 2012-10-15 12:56 com.ibm.mq.headers.jar
Implementation-Title: WebSphere MQ classes for Java |
fead7be351c2c89d3239797643852c95_14 | Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
24. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.local.jar:
root root 224747 2012-10-15 12:56 com.ibm.mq.jmqi.local.jar
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
25. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.system.jar:
root root 209738 2012-10-15 12:56 com.ibm.mq.jmqi.system.jar
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
26. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.pcf.jar:
root root 125200 2012-10-15 12:56 com.ibm.mq.pcf.jar
Implementation-Title: WebSphere MQ classes for Java |
fead7be351c2c89d3239797643852c95_15 | Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
27. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/dhbcore.jar:
root root 2011835 2012-10-15 12:56 dhbcore.jar
Implementation-Version: "DH610-GOLD"
Implementation-Title: "Webscale Distribution Hub Core"
Implementation-Vendor: "IBM Corporation"
mqjavalist.sh: 27 jar files with MQ code found in /opt/IBM/WebSphere/AppServer
mqjavalist.sh: 27 total jar files with MQ code found
mqjavalist.sh: Results saved to mqlist.txt
5.
6. Back to top |
fead7be351c2c89d3239797643852c95_16 | RESOLVING THE PROBLEM
Review the output from mqjavalist.sh to determine where copies of the MQ jar files have been found. Not all duplicates represent a problem, unless they are being loaded by your Java SE application or Java EE application server at runtime. If the com.ibm.mq.commonservices.jar file shows an implementation version of ${version.number} - ${build.level} just ignore it.
In the sample output above, entries #16 through #27 represent the jar files for the installed MQ Resource Adapter. They all show an implementation version of 7.1.0.0 - k000-L111005.1 except for #21, com.ibm.mqjms.jar, which shows an implementation version of 7.0.1.5 - k701-105-110419. Because the jar file versions are not in sync, MQ JMS will not function as expected. |
fead7be351c2c89d3239797643852c95_17 | In cases like this, the wmq.jmsra.rar file should contain a copy of the MQ jar at the right level for the application server. Entry #14 in the mqjavalist.sh output shows the com.ibm.mqjms.jar file with an implementation version of 7.1.0.0 - k000-L111005.1, which is what we need. Use the jar program to extract the com.ibm.mqjms.jar file from the wmq.jmsra.rar archive, then copy it over the back-level version of the jar. Use chown and chmod to ensure the permissions on the file are correct.
In other cases, you might find that the classpath for the application server, or for your Java SE application, is picking up extra copies of the MQ jar files. Eliminating unnecessary classpath entries can resolve the problem.
If your Java EE application (.ear or .war) bundles a copy of any MQ jar files, you should remove them and rely on the ones from the installed MQ Resource Adapter instead.
Back to top |
fead7be351c2c89d3239797643852c95_18 | Additional Keywords:
troubleshoot troubleshooting trouble shoot classloader classpath configuration scripts
DOWNLOAD
1.
2. mqjavalist.sh [/support/docview.wss?uid=swg21681142&aid=2]mqjavalist.sh
DISCLAIMER: All source code and/or binaries attached to this document are referred to here as "the Program". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an "AS IS" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Back to top |
93fac663822cf59702ccc32de2195af8_0 | IBM Demystifying the WebSphere StaleConnectionException - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
What is the StaleConnectionException, why is it issued by WebSphere Application Server, and what should be done about it?
RESOLVING THE PROBLEM
In WebSphere Application Server, the StaleConnectionException is issued when the database vendor issues an exception indicating that a connection currently in the connection pool is no longer valid. This can happen for many reasons, including: |
93fac663822cf59702ccc32de2195af8_1 | * The application tries to get a connection and fails, as when the database is not started.
* A connection is no longer usable due to a database failure. When an application tries to use a connection it has previously obtained, the connection is no longer valid. In this case, all connections currently in use by an application can get this error when they try to use the connection.
* The application using the connection has already called close() and then tries to use the connection again.
* The application tries to use a JDBC™ resource, such as a statement, obtained on a now-stale connection.
When the StaleConnectionException is issued, the behavior is determined by the Purge Policy setting for the connection pool. If the Purge Policy is set to EntirePool, the entire pool is flushed. But if the Purge Policy is set to FailingConnectionOnly, only the connection that caused the StaleConnectionException is purged from the pool. |
93fac663822cf59702ccc32de2195af8_2 | An application can recover from bad connections by explicitly catching the StaleConnectionException and getting a new connection from the pool. Numerous exceptions issued by DB2, Oracle, DataDirect (for connecting to SQLServer), Sybase, and Informix are currently mapped to the StaleConnectionException, which makes recovery easier for the application programmer. The following pseudocode provides an example of how to recover from a StaleConnectionException: |
93fac663822cf59702ccc32de2195af8_3 | //get a userTransaction
javax.transaction.UserTransaction tran = getSessionContext().getUserTransaction();
//retry indicates whether to retry or not
//numOfRetries states how many retries have
// been attempted
boolean retry = false;
int numOfRetries = 0;
java.sql.Connection conn = null;
java.sql.Statement stmt = null;
do {
try {
//begin a transaction
tran.begin();
//Assumes that a datasource has already been obtained
//from JNDI
conn = ds.getConnection();
conn.setAutoCommit(false);
stmt = conn.createStatement();
stmt.execute("INSERT INTO EMPLOYEES VALUES
(0101, 'Bill', 'R', 'Smith')");
tran.commit();
retry = false;
} catch(java.sql.SQLException sqlX)
{
// If the error indicates the connection is stale, then
// rollback and retry the action
if (com.ibm.websphere.rsadapter.WSCallHelper
.getDataStoreHelper(ds)
.isConnectionError(sqlX))
{
try {
tran.rollback();
} catch (java.lang.Exception e) {
//deal with exception
//in most cases, this can be ignored
}
if (numOfRetries < 2) { |
93fac663822cf59702ccc32de2195af8_4 | retry = true;
numOfRetries++;
} else {
retry = false;
}
}
else
{
//deal with other database exception
retry = false
}
} finally {
//always cleanup JDBC resources
try {
if(stmt != null) stmt.close();
} catch (java.sql.SQLException sqle) {
//usually can ignore
}
try {
if(conn != null) conn.close();
} catch (java.sql.SQLException sqle) {
//usually can ignore
}
}
} while (retry) ; |
93fac663822cf59702ccc32de2195af8_5 | Further details about WebSphere Connection Pooling are located in the WebSphere Application Server Knowledge Center article Connection pooling [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/cdat_conpool.html]
Knowledge Center article Exceptions pertaining to data access [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/cdat_daexcp.html] contains details on the StaleConnectionException error
Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK |
8b21bc37a60c97eaf63920df14a5783b_0 | IBM Security Bulletin: IBM PureApplication System is affected by a security vulnerability. (CVE-2015-1890) - United States SECURITY BULLETIN
SUMMARY
A security vulnerability have been identified in the General Parallel File System gpfs.snap service tool that affects IBM PureApplication System.
VULNERABILITY DETAILS
CVEID: CVE-2015-1890 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1890]
DESCRIPTION: IBM General Parallel File System could allow someone who has access to a snap file generated by the gpfs.snap tool (/usr/lpp/mmfs/bin/gpfs.snap) to read the private keys of certificates used by GPFS for daemon communications via the TLS protocol.
CVSS Base Score: 3.5
CVSS Temporal Score: See [https://exchange.xforce.ibmcloud.com/]https://exchange.xforce.ibmcloud.com/vulnerabilities/101382 [https://exchange.xforce.ibmcloud.com/vulnerabilities/101382] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:S/C:P/I:N/A:N) |
8b21bc37a60c97eaf63920df14a5783b_1 | AFFECTED PRODUCTS AND VERSIONS
This vulnerability affects IBM PureApplication Server and the GPFS pattern type included in:
*
*
*
REMEDIATION/FIXES
The solution is to upgrade the IBM PureApplication System to the following fix levels and update deployments that implement the GPFS pattern type using the GPFS Pattern Interim Fix:
IBM PureApplication System V2.1
*
* GPFS Pattern Interim Fix is located at: http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.1.0&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.1.0&includeSupersedes=0] |
8b21bc37a60c97eaf63920df14a5783b_2 | IBM PureApplication System V2.0 *
* GPFS Pattern Interim Fix is located at: http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.0.0_1.2.0.1_and_1.2.0.2&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.0.0_1.2.0.1_and_1.2.0.2&includeSupersedes=0]
WORKAROUNDS AND MITIGATIONS
None
GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. |
8b21bc37a60c97eaf63920df14a5783b_3 | REFERENCES
Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]
On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]
RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT
None
CHANGE HISTORY
10 August 2015: Original Version Published
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. |
8b21bc37a60c97eaf63920df14a5783b_4 | DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. |
9ae09b01b600501c6bac409ca1603944_0 | IBM Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect - United States SECURITY BULLETIN
SUMMARY
There are multiple vulnerabilities in IBM® Runtime Environment Java™ used by IBM API Connect.
These issues were disclosed as part of the IBM Java SDK updates in January 2017 and April 2017.
VULNERABILITY DETAILS
CVEID: CVE-2016-5546 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5546]
DESCRIPTION: An unspecified vulnerability related to the Libraries component has no confidentiality impact, high integrity impact, and no availability impact.
CVSS Base Score: 7.5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120869 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120869] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) |
9ae09b01b600501c6bac409ca1603944_1 | CVEID: CVE-2016-5548 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5548]
DESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.
CVSS Base Score: 6.5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120864 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120864] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) |
9ae09b01b600501c6bac409ca1603944_2 | CVEID: CVE-2016-5549 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5549]
DESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.
CVSS Base Score: 6.5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120863 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120863] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) |
9ae09b01b600501c6bac409ca1603944_3 | CVEID: CVE-2016-5547 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5547]
DESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.
CVSS Base Score: 5.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120871 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120871] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) |
9ae09b01b600501c6bac409ca1603944_4 | CVEID: CVE-2016-2183 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2183]
DESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the DES/3DES cipher, used as a part of the SSL/TLS protocol. By capturing large amounts of encrypted traffic between the SSL/TLS server and the client, a remote attacker able to conduct a man-in-the-middle attack could exploit this vulnerability to recover the plaintext data and obtain sensitive information. This vulnerability is known as the SWEET32 Birthday attack.
CVSS Base Score: 3.7
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116337 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116337] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) |
9ae09b01b600501c6bac409ca1603944_5 | CVEID: CVE-2017-3511 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3511]
DESCRIPTION: An unspecified vulnerability related to the Java SE JCE component could allow an unauthenticated attacker to take control of the system.
CVSS Base Score: 7.7
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/124890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124890] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)
AFFECTED PRODUCTS AND VERSIONS
IBM API Connect V5.0.0.0 - V5.0.7.2
REMEDIATION/FIXES
Affected Product Addressed in VRMF APAR Remediation/First Fix IBM API Connect
V5.0.0.0 - 5.0.6.2 5.0.6.3 LI79749 Addressed in IBM API Connect V5.0.6.3.
Follow this link and find the "APIConnect_Management" and "apiconnect-collective-controller" packages: |
9ae09b01b600501c6bac409ca1603944_6 | https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] IBM API Connect
V5.0.7.0 - 5.0.7.2 5.0.8.0 LI79749 Addressed in IBM API Connect V5.0.8.0.
Follow this link and find the "APIConnect_Management" and "apiconnect-collective-controller" packages: |
9ae09b01b600501c6bac409ca1603944_7 | https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. |
9ae09b01b600501c6bac409ca1603944_8 | REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]
IBM Java SDK January 2017 Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg21997194]
IBM Java SDK April 2017 Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg22002169]
RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]
CHANGE HISTORY
11 September 2017: original document published
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. |
9ae09b01b600501c6bac409ca1603944_9 | DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. |
a58a7a6f9d0faacb2043f47481fd0d42_0 | IBM Unable to log on to FileNet WorkplaceXT receive an AE SecurityCheckFilter error - United States AE SecurityCheckFilter; JSSE; unlimited strength TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Unable to log on to FileNet WorkplaceXT - AE SecurityCheckFilter error
SYMPTOM
When attempting to log on to FileNet WorkplaceXT deployed on an IBM WebSphere Application Server, the following error is displayed :
Exception Message: [Filter AE SecurityCheckFilter]: filter is unavailable.
Filter AE SecurityCheckFilter: filter is unavailable.
DIAGNOSING THE PROBLEM
SystemOut.log may contain the following exception : |
a58a7a6f9d0faacb2043f47481fd0d42_1 | Problem initializing encryption/decryption with keyId abcd1234, size 256 bits. java.home=<<WAS_home>>\AppServer\java\jre. Cause: java.security.InvalidKeyException: Illegal key size or default parameters
com.filenet.wcm.api.EncryptionException: Problem initializing encryption/decryption with keyId abcd1234, size 256 bits. java.home=<<WAS_home>>\AppServer\java\jre. Cause: java.security.InvalidKeyException: Illegal key size or default parameters
at com.filenet.wcm.api.impl.CryptoHelper.getCipher(CryptoHelper.java:93)
at com.filenet.wcm.api.impl.CryptoHelper.doEncryptOrDecrypt(CryptoHelper.java:104)
at com.filenet.wcm.api.impl.SessionImpl.getTokenSymmetric(SessionImpl.java:771)
at com.filenet.wcm.api.impl.SessionImpl.getToken(SessionImpl.java:741)
at com.filenet.ae.toolkit.server.util.credentials.UserTokenUtil.getUserToken(UserTokenUtil.java:131)
at com.filenet.ae.toolkit.server.servlet.filter.SecurityCheckFilter.doFilter(SecurityCheckFilter.java:51)
.... |
a58a7a6f9d0faacb2043f47481fd0d42_2 | RESOLVING THE PROBLEM
This behavior occurs if Workplace XT is configured to use Maximum strength keys (>128bit) during installation. In this case, the JRE used by the J2EE Application server, for example <<WAS_home>>\AppServer\java\jre should contain unlimited strength policy files, otherwise it will be unable to encrypt / decrypt user tokens.
* One option is to install the JSSE unlimited strength jar files for the JRE used by the J2EE Application Server. For IBM JREs, more info can be found at
https://www.ibm.com/developerworks/java/jdk/security/ [https://www.ibm.com/developerworks/java/jdk/security/]
* Another option is to regenerate the encryption keys using 128bit encryption which doesn't require the unlimited strength policy .jar files. Please refer to the P8 Infocenter for usage information on the com.filenet.wcm.api.util.MakeCryptoKeys utility. |
8c04f859e8331f06d482b0b7a940450c_0 | IBM Security Bulletin: Vulnerability in SSLv3 affects IBM Integration Designer and WebSphere Integration Developer (CVE-2014-3566) - United States SECURITY BULLETIN
SUMMARY
SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. SSLv3 is enabled in IBM Integration Designer and WebSphere Integration Developer.
VULNERABILITY DETAILS
CVE-ID: CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566]
DESCRIPTION: IBM Integration Designer and WebSphere Integration Developer could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections. |
8c04f859e8331f06d482b0b7a940450c_1 | CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97013 [https://exchange.xforce.ibmcloud.com/vulnerabilities/97013] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)
AFFECTED PRODUCTS AND VERSIONS
This vulnerability affects some versions and releases of IBM Integration Designer and WebSphere Integration Developer.
REMEDIATION/FIXES
IBM recommends that you review your entire environment to identify areas that enable the SSLv3 protocol and take appropriate mitigation and remediation actions. The most immediate mitigation action that can be taken is disabling SSLv3. You should verify disabling SSLv3 does not cause any compatibility issues.
Note that other related products are also affected by this vulnerability. In the context of applying fixes, you will also want to update Installation Manager to version 1.8 or later. |
8c04f859e8331f06d482b0b7a940450c_2 | To fully mitigate the POODLE vulnerability for server side components, an additional fix for IBM Integration Designer and WebSphere Integration Developer is required (JR51720):
* WebSphere Integration Developer V7.5.1.2 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Integration+Designer&release=7.5.1.2&platform=All&function=aparId&apars=JR51720]
* IBM Integration Designer V8.0.1.3 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Integration+Designer&release=8.0.1.3&platform=All&function=aparId&apars=JR51720]
* IBM Integration Designer V8.5.5.0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Integration+Designer&release=8.5.5&platform=All&function=aparId&apars=JR51720] |
8c04f859e8331f06d482b0b7a940450c_3 | WORKAROUNDS AND MITIGATIONS
Customers who cannot or do not want to install the fix recommended in the "Remediation/Fixes" section of this security bulletin can disable the use of SSLv3 using manual configuration as described in "Workarounds and Mitigations" under the "Client configuration files" section in the following bulletin: Security Bulletin: Vulnerability in SSLv3 affects IBM WebSphere Application Server (CVE-2014-3566) [http://www.ibm.com/support/docview.wss?uid=swg21687173]
GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. |
8c04f859e8331f06d482b0b7a940450c_4 | REFERENCES
Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]
On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]
Security Bulletin: Vulnerability in SSLv3 affects IBM WebSphere Application Server (CVE-2014-3566) [http://www.ibm.com/support/docview.wss?uid=swg21687173]
RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]
CHANGE HISTORY
2014-11-14- Original Version Published
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. |
8c04f859e8331f06d482b0b7a940450c_5 | DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Integration Developer Security Linux, Windows 7.0.0.5, 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0.0.1, 7.0, 6.2.0.3, 6.2.0.2, 6.2.0.1, 6.2, 6.1.2 |
9850d0282449f241845a4b327b2d6a36_0 | IBM Raise the feature level of a single VOB without increasing the feature level for other VOBs on the server - United States feature level; chflevel; unreplicated; non-replicated; base; clearcase; 1150579; feature levels; replicated VOB TECHNOTE (FAQ)
QUESTION
How can you increase the feature level of a single non-replicated IBM Rational ClearCase VOB without increasing the feature level for the other VOBs on the server?
ANSWER
Execute the following two commands:
1. cleartool chflevel -replica <new feature level> replica:<replica name>@\<vob tag>
2. cleartool chflevel -family <new feature level> vob:\<vob tag> |
9850d0282449f241845a4b327b2d6a36_1 | Notes: * These commands are used for replicated VOB as well; however, there are special considerations that need to be taken when changing the feature level of a VOB that is replicated. Review the MultiSite Administrator's Guide under the topic of Feature levels [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/index.jsp?topic=/com.ibm.rational.clearcase.cc_ms_admin.doc/c_feature_levels.htm]for more details.
* If a VOB is used in a UCM environment, the PVOB and all Component VOBs must be at the same feature level in order to utilize the features of that level.
Example: |
9850d0282449f241845a4b327b2d6a36_2 | 1. Open a command prompt and set into a view
2. Mount and change directory into the VOB tag
3. Describe the VOB to show current feature level
> cleartool describe -long vob:.
versioned object base "/vobstore/test_vob"
created 23-Mar-01.09:36:29 by John Doe (jdoe.group1@host1)
VOB family feature level: 2
VOB storage host:pathname "host1:/vobstore/test_vob.vbs"
VOB storage global pathname "/net/host1/vobstore/test_vob.vbs"
database schema version: 53
VOB ownership:
owner ibm.com/jdoe
group ibm.com/group1
Additional groups:
group ibm.com/other
VOB holds objects from the following views:
Attributes:
FeatureLevel = 2
4. Determine the replica name (by default is original)
> cleartool lsreplica
For VOB replica "/vobstore/test_vob":
23-Mar.09:36 jdoe replica "original"
5. Change the feature level. * Step 1: |
9850d0282449f241845a4b327b2d6a36_3 | > cleartool chflevel -replica 3 replica:original@/vobstore/test_vob
Replica feature level raised to 3.
* Step 2:
> cleartool chflevel -family 3 vob:/vobstore/test_vob
cleartool: Warning: Raising the VOB family feature level may make it impossible to move this VOB to servers running an earlier revision of ClearCase and to create MultiSite replicas of this VOB on such servers.
Raise VOB family feature level? [no] y
VOB family feature level raised to 3.
6. Describe the VOB to show new feature level:
> cleartool describe -long vob:.
versioned object base "/vobstore/test_vob"
created 23-Mar-01.09:36:29 by John Doe (jdoe.group1@host1)
VOB family feature level: 3
VOB storage host:pathname "host1:/vobstore/test_vob.vbs"
VOB storage global pathname "/net/host1/vobstore/test_vob.vbs"
database schema version: 53
VOB ownership:
owner ibm.com/jdoe |
9850d0282449f241845a4b327b2d6a36_4 | group ibm.com/user
Additional groups:
group ibm.com/other
VOB holds object from the following views:
Attributes:
FeatureLevel = 3 |
9850d0282449f241845a4b327b2d6a36_5 | Review the ClearCase Command Reference Guide on the topic of chflevel (cleartool man chflevel) for more information.
RELATED INFORMATION
#About Feature Levels and ClearCase [http://www.ibm.com/support/docview.wss?uid=swg21119269] |
5a21b0ab376d0b7b53bd91c01a907585_0 | IBM Security Bulletin: IBM MQ Clients can send a specially crafted message that could cause a channel to SIGSEGV. (CVE-2017-1747) - United States SECURITY BULLETIN
SUMMARY
A specially crafted message could cause a denial of service in an IBM MQ application consuming messages that the application needs to perform data conversion on.
VULNERABILITY DETAILS
CVEID: CVE-2017-1747 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1747]
DESCRIPTION: A specially crafted message could cause a denial of service in an IBM MQ application consuming messages that the application needs to perform data conversion on.
CVSS Base Score: 5.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/135520 [https://exchange.xforce.ibmcloud.com/vulnerabilities/135520] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H)
AFFECTED PRODUCTS AND VERSIONS
IBM MQ V9 LTS
Maintenance levels 9.0.0.0 - 9.0.0.2 |
5a21b0ab376d0b7b53bd91c01a907585_1 | IBM MQ V9 CD
Maintenance levels 9.0.0 - 9.0.4
REMEDIATION/FIXES
IBM MQ V9 LTS
Apply FixPack 9.0.0.3 [http://www-01.ibm.com/support/docview.wss?uid=swg24044508]
IBM MQ V9 CD
Upgrade to IBM MQ version 9.0.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24043463]
GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.
REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]
RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]
CHANGE HISTORY
28 March 2018: Original Version published
29 March 2018: Correction to bulletin to remove HPE Nonstop as affected platform. |
5a21b0ab376d0b7b53bd91c01a907585_2 | *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
Cross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ Business Integration IBM MQ Advanced Business Integration IBM MQ Advanced for Developers |
f8805bcf461e26962c72453d5ca1b2c3_0 | IBM Increasing Java Heap Memory in IBM Tivoli Common Reporting 2.1/2.1.1 - United States TCR - Tivoli Common Reporting TECHNOTE (FAQ)
QUESTION
How to increase Java heap memory size in IBM Tivoli Common Reporting (TCR) 2.1/2.1.1 versions?
CAUSE
Running a large scale report with Default java heap settings might result in OutOfMemory error
ANSWER
TCR 2.1/2.1.1 server provides a default setting for heap size, a minimum size (xms) of 512MB and a maximum size (xmx) of 1024MB.
In order to change the heap memory size, execute the following command:
<INST>/tipv2/bin/wsadmin.sh[.bat] -user <USERNAME> -password <PASSWORD> -f <INST>/tipv2/profiles/TIPProfile/bin/changeMem.py --xms <MINVALUE> --xmx <MAXVALUE>
where <INST> is the TCR Installation folder like /opt/IBM/tivoli
<MINVALUE> can be 1024 and <MAXVALUE> can be 1843 (1GB and 1.8GB respectively) |
f8805bcf461e26962c72453d5ca1b2c3_1 | NOTE: In order to avoid OutOfMemory error, it is recommended to be within the 2GB limit (for 32 bit architectures - maximum memory can be 2^32)
For 64-bit JVM, the maximum heap value can be upto 50% of the available physical memory. Reason being maximum memory will be 2^64 which is 16 exabytes which is a very huge number!
1 exabyte = 1024*1024*1024 Gigabyte!
Please refer to the links provided in the 'Related Infomation' section to learn more on the Java sizing and heap information. |
f8805bcf461e26962c72453d5ca1b2c3_2 | To test the JVM's maximum heap memory support, please follow the below test:
a) Open command line / shell script and navigate to <INST>/tipv2/java/jre/bin folder
b) Execute this command: java -Xmx1843m hello
- if java accepts this 1.8GB setting, then it will throw the "class not found" error for hello
- if java does not accept this value, then it gives the "Initialization error" and "Failed to instantiate heap" message!
- You can try to increase the value of Xmx and see where it breaks
- For 32-bit JVM, it is not advised to set this value beyond 1843m but for 64-bit JVM, value can be upto 50% of the available physical memory.
After setting the new values, restart the TCR server for the changes to take effect. |
f8805bcf461e26962c72453d5ca1b2c3_3 | RELATED INFORMATION
Sizing the Java Heap [http://publib.boulder.ibm.com/infocenter/javasdk/tools/index.jsp?topic=%2Fcom.ibm.java.doc.igaa%2F_1vg000139b8b453-11951f1e7ff-8000_1001.html]
Java code to Java Heap [http://www.ibm.com/developerworks/java/library/j-codetoheap/index.html] |
21a53c505a48e3e9be099f579d05f1a9_0 | IBM Trouble installing ITM on Windows OS - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Getting the below error when you try to install ITM on Window OS
"D:\Program Files\IBM\ITM" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces.
SYMPTOM
When you try to install ITM on " C:\Program Files\IBM\ITM" it woks fine but when we try to install it on "D:\Program Files\IBM\ITM" we get the below error:
"D:\Program Files\IBM\ITM" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces.
If you take out the spaces and use D:\ProgramFiles\IBM\ITM, the install will continue.
RESOLVING THE PROBLEM
Couple of ways to fix this...
1. Remove the space in the directory path and install the ITM on a directory without spaces.
Example : D:\IBM\ITM |
21a53c505a48e3e9be099f579d05f1a9_1 | 2. Check the NTFS 8.3 name creation and enable the 8.3 naming creation to install the ITM on a directory path with spaces.
check the value on the below registry location
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation
In case NtfsDisable8dot3NameCreation is set to (2), this means the following: NTFS sets the 8.3 naming convention creation on a per volume basis.
You can check the 8.3 name creation using this command for the volumes that are impacted.
For example, if the %TEMP% folder is located on c:\, but you are installing on d:\, then you should run these commands:
fsutil 8dot3name query c:
fsutil 8dot3name query d:
You will get an output like this:
The volume state is: 0 (8dot3 name creation is enabled).
The registry state is: 2 (Per volume setting - the default).
Value and Meaning |
21a53c505a48e3e9be099f579d05f1a9_2 | 0 NTFS creates short file names. This setting enables applications that cannot process long file names and computers that use different code pages to find the files.
1 NTFS does not create short file names. Although this setting increases file performance, applications that cannot process long file names, and computers that use different code pages, might not be able to find the files.
2 NTFS sets the 8.3 naming convention creation on a per volume basis.
3 NTFS disables 8dot3 name creation on all volumes except the system volume.
more detail...
https://technet.microsoft.com/en-us/library/cc959352.aspx [https://technet.microsoft.com/en-us/library/cc959352.aspx] |
73ebea160dfb4da729a773dcc79de5a5_0 | IBM WebSphere Application Server 7.0 Test Environment Extension 7.0.0.41 - United States ifix; interim fix; i-fix; fix; patch; update; fixes; upgrade DOWNLOADABLE FILES
ABSTRACT
IBM WebSphere Application Server 7 Fix Pack 41 (7.0.0.41) is available as an installed test environment extension
DOWNLOAD DESCRIPTION
This download includes the following update to the WebSphere Application Server v7.0 Test Environment extension included with Rational Software Delivery Platform products: |
73ebea160dfb4da729a773dcc79de5a5_1 | * IBM WebSphere Application Server Version 7 Fix Pack 41 also known as version 7.0.0.41. For more information, see the WebSphere Application Server readme [http://www-01.ibm.com/support/docview.wss?uid=swg27004980#ver70].
* WebSphere Application Server Feature Pack for Web 2.0 1.0.1.1
* WebSphere Application Server Feature Pack for Mobile 1.1.0.1 (Note: This feature pack is available only when installing with version 8.0 or newer.)
* WebSphere Application Server Feature Pack for Communications Enabled Applications 1.0.0.13
* WebSphere Application Server Feature Pack for Service Component Architecture 1.0.1.17
* WebSphere Application Server Feature Pack for XML 1.0.0.15
* WebSphere Application Server Feature Pack for OSGi Applications and Java Persistence API (JPA) 2.0 v1.0.0.9 (Note: This feature pack is available only when installing with version 8.0 or newer.) |
73ebea160dfb4da729a773dcc79de5a5_2 | * WebSphere Application Server Feature Pack for Modern Batch 1.0.0.5 (Note: This feature pack is available only when installing with version 8.0 or newer.) |
73ebea160dfb4da729a773dcc79de5a5_3 | For more information on feature packs for WebSphere Application Server, see http://www.ibm.com/support/docview.wss?uid=swg27008534&wv=1#was70 [http://www.ibm.com/support/docview.wss?uid=swg27008534&wv=1#was70]. PREREQUISITES
You must have the WebSphere Application Server 7.0 Test Environment extension installed.
You need up to 5.18 GB of disk space to install the fix pack. To download and extract the compressed installation files, you need an additional 6 GB of disk space.
INSTALLATION INSTRUCTIONS
Important: By default, you do not need to download the compressed files that contain the update; the update is downloaded and installed by IBM Installation Manager directly from the IBM update repository.
For instructions on installing this update using Installation Manager, see the topic Updating Installed Product Packages in the information center for your product and version: |
73ebea160dfb4da729a773dcc79de5a5_4 | * Rational Application Developer for WebSphere Software, version 8.5.x [http://www.ibm.com/support/knowledgecenter/SSRTLW_8.5.5/com.ibm.rad.install.doc/topics/t_update.html]
* Rational Application Developer for WebSphere Software, version 9.0.x [http://www.ibm.com/support/knowledgecenter/SSRTLW_9.0.0/com.ibm.rad.install.doc/topics/t_update.html]
* Rational Application Developer for WebSphere Software, version 9.1.x [http://www.ibm.com/support/knowledgecenter/SSRTLW_9.1.0/com.ibm.rad.install.doc/topics/t_update.html] |
73ebea160dfb4da729a773dcc79de5a5_5 | To download and install the update from the compressed files, complete the following steps:
1. Download the update files from Fix Central by following the link listed in the download table below
2. Extract the compressed files in an appropriate directory. For example, choose to extract to C:\temp\update
3. Add the update's repository location in IBM Installation Manager: 1. Start IBM Installation Manager.
2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.
3. On the Repositories page, click Add Repository.
4. In the Add repository window, browse to or enter the file path to the diskTag.inf file, which is located in the disk1 sub-directory in the directory where you extracted the compressed files and then click OK. For example, enter C:\temp\updates\disk1\diskTag.inf.
5. Click OK to close the Preference page. |
73ebea160dfb4da729a773dcc79de5a5_6 | 4. Install the update as described in the the topic "Updating Installed Product Packages" in the information center for your product and version |
73ebea160dfb4da729a773dcc79de5a5_7 | DOWNLOAD PACKAGE
You can download the fix pack from Fix Central using either Download Director, HTTP or FTP.
1. Click the link in the table that follows to access Fix Central.
2. On the Select Fixes page, select Fix pack : 9.1.1.2-Rational-RAD-groupfixpack (IBM Rational Application Developer for WebSphere Software Version 9.5.0.2)
3. Expand section Show contained fixes.
4. From the list of contained fixed, select one of the following options:
* (For 64-bit) 7.0.0.41-Rational-WAS70_64-fixzippack (WebSphere Application Server 70 64bit Extension version 7.0.0.41 update pack)
* (For 32-bit) 7.0.0.41-Rational-WAS70-fixzippack (WebSphere Application Server 70 Extension version 7.0.0.41 update pack
1. Click Continue and follow the prompts to download the update. |
73ebea160dfb4da729a773dcc79de5a5_8 | Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 7.0.0.41-Rational-WAS70-fixzippack 6 May 2016 English 1 FC [https://ibm.biz/Bd48Av] [ ]
TECHNICAL SUPPORT
TAB NAVIGATION
* General Support Information- selected tab,
* Support Resources [http://www.ibm.com/support/docview.wss?uid=swg27020747]- selected tab,
IBM Rational Software Support Communities |
73ebea160dfb4da729a773dcc79de5a5_9 | * Visit the IBM Support Portal [http://www.ibm.com/support/entry/portal/Overview/Software/Rational/product] to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.
* Visit developerWorks [http://www.ibm.com/developerworks/rational/] to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community [http://www.ibm.com/developerworks/rfe/].
* Visit the Jazz Community [http://jazz.net/] if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track developement progress. |
73ebea160dfb4da729a773dcc79de5a5_10 | HELPFUL HINTS FOR OBTAINING TECHNICAL ASSISTANCE:
Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
* What software versions were you running when the problem occurred?
* Do you have logs, traces, or messages that are related to the problem?
* Can you reproduce the problem? If so, what steps do you take to reproduce it?
* Is there a workaround for the problem? If so, be prepared to describe the workaround. |
73ebea160dfb4da729a773dcc79de5a5_11 | If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support [http://www.ibm.com/software/support/exchangeinfo.html].
Follow IBM Rational Client Support on Twitter [http://twitter.com/rationalsupport] | Facebook [http://facebook.com/rationalsupport] | YouTube [http://www.youtube.com/ibmrationalsupport] | devWorks Blog [https://www.ibm.com/developerworks/mydeveloperworks/blogs/nfrsblog/?lang=en]
Back to top |
0777e5e8be561e726031c3e100039abf_0 | IBM Differences between Rational Rhapsody 8.0 Statecharts and UML 2.4.1 Behavior State Machine - United States Restriction; Restrictions; Limitation; Limitations; drawing; graphical; graph; difference; diferences; gap; deffer; feature; features; concept; concepts; error; errors WHITE PAPER
ABSTRACT
This is a white paper that explains the differences between IBM Rational Rhapsody 8.0.x Statecharts and UML 2.4.1 Behavior State Machine.
CONTENT
Authors: Shinji Kanai, Moria Abadi |
0777e5e8be561e726031c3e100039abf_1 | OMG UML and IBM Rational Rhapsody have been evolving in parallel, and some differences were created and expanded over time. Not all graphical notations that are defined in UML specification are supported by Rhapsody. There are certain patterns of transitions you cannot draw due to restrictions imposed deliberately, but not necessarily limited by UML specification. Some of UML features such as deferred event and do-activity are not natively supported today. This document covers such gaps that are found between UML specification and Rhapsody implementation, aiming to help you design statechart more effectively and enable easier interchange of statecharts among UML-based modeling tools. |
0777e5e8be561e726031c3e100039abf_2 | Disclaimer This documentation is created based on differences that are found between Rhapsody 8.0.x Statechart and OMG UML 2.4.1 Superstructure Specification (UML spec). The content is believed to be accurate at the time of publication. Use this documentation at your own risk as it might contain some incompleteness and imprecision.
Table: Graphical Notations and Naming comparison |
0777e5e8be561e726031c3e100039abf_3 | UML2.4.1 Concept: Behavior state machine element or capability as it is named in OMG UML 2.4.1 Superstructure Spec. Section in spec: The section describing the element in UML spec. In Rhapsody: The corresponding name and graphical notation of UML concept that is used in Rhapsody. Note: Additional comments to help understand the specific concept better.
[/support/docview.wss?uid=swg27040251&aid=1] UML2.4.1 Concept Section in spec In Rhapsody Note 1. Entry Point
[/support/docview.wss?uid=swg27040251&aid=2] 15.3.1 EnterExitPoint
[/support/docview.wss?uid=swg27040251&aid=3] (*) Visualization using a rectangular symbol is not supported
(*) Not supported for composite states (See NO. 36). 2. Exit Point
[/support/docview.wss?uid=swg27040251&aid=4] 15.3.1 EnterExitPoint
[/support/docview.wss?uid=swg27040251&aid=5] (*) Visualization using a rectangular symbol is not supported
(*) Not supported for composite states, only for submachine states 3. Final State |
0777e5e8be561e726031c3e100039abf_4 | [/support/docview.wss?uid=swg27040251&aid=6] 15.3.2 Termination State
[/support/docview.wss?uid=swg27040251&aid=7] [/support/docview.wss?uid=swg27040251&aid=1] 4. Initial Pseudostate
[/support/docview.wss?uid=swg27040251&aid=8] 15.3.8 Default Connector
[/support/docview.wss?uid=swg27040251&aid=9] [/support/docview.wss?uid=swg27040251&aid=1] 5. Deep History Pseudostate
[/support/docview.wss?uid=swg27040251&aid=10] 15.3.8 History Connector |
0777e5e8be561e726031c3e100039abf_5 | [/support/docview.wss?uid=swg27040251&aid=11] [/support/docview.wss?uid=swg27040251&aid=1] 6. Shallow History Pseudostate
[/support/docview.wss?uid=swg27040251&aid=12] 15.3.8 Shallow History Connector
[/support/docview.wss?uid=swg27040251&aid=13] (*) Code Generation is supported in v8.0.6. See technote 1668548 [http://www.ibm.com/support/docview.wss?uid=swg21668548] for more information. 7. Join Pseudostate
[/support/docview.wss?uid=swg27040251&aid=14] 15.3.8 Join Sync Bar
[/support/docview.wss?uid=swg27040251&aid=15] [/support/docview.wss?uid=swg27040251&aid=1] 8. Fork Pseudostate
[/support/docview.wss?uid=swg27040251&aid=16] 15.3.8 Fork Sync Bar
[/support/docview.wss?uid=swg27040251&aid=17] [/support/docview.wss?uid=swg27040251&aid=1] 9. Junction Pseudostate
[/support/docview.wss?uid=swg27040251&aid=18] 15.3.8 Junction Connector |
0777e5e8be561e726031c3e100039abf_6 | [/support/docview.wss?uid=swg27040251&aid=19] (*) Used only for merge. Only one outgoing transition is permitted 10. Static Conditional Branch
[/support/docview.wss?uid=swg27040251&aid=20] 15.3.8 Condition Connector
[/support/docview.wss?uid=swg27040251&aid=21] (*) Only one incoming transition is allowed.
(*) Realized by way of the condition connector. 11. Terminate Pseudostate
[/support/docview.wss?uid=swg27040251&aid=22] 15.3.8 termination Connector
[/support/docview.wss?uid=swg27040251&aid=23] [/support/docview.wss?uid=swg27040251&aid=1] 12. State List
[/support/docview.wss?uid=swg27040251&aid=24] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=25] (*) This is an additional representation for transition from the junction having a history as target. the regular representation can be used instead. 13. Region
[/support/docview.wss?uid=swg27040251&aid=26] 15.3.10 Region |
0777e5e8be561e726031c3e100039abf_7 | [/support/docview.wss?uid=swg27040251&aid=27] [/support/docview.wss?uid=swg27040251&aid=1] 14. Simple State
[/support/docview.wss?uid=swg27040251&aid=28] 15.3.11 Simple State
[/support/docview.wss?uid=swg27040251&aid=29] [/support/docview.wss?uid=swg27040251&aid=1] 15. Composite State
[/support/docview.wss?uid=swg27040251&aid=30] 15.3.11 Composite State
[/support/docview.wss?uid=swg27040251&aid=31] [/support/docview.wss?uid=swg27040251&aid=1] 16. Submachine State
[/support/docview.wss?uid=swg27040251&aid=32] 15.3.11 Sub-statechart
[/support/docview.wss?uid=swg27040251&aid=33] [/support/docview.wss?uid=swg27040251&aid=1] 17. Entry Behavior
[/support/docview.wss?uid=swg27040251&aid=34] 15.3.11 Action on Entry
[/support/docview.wss?uid=swg27040251&aid=35] [/support/docview.wss?uid=swg27040251&aid=1] 18. Exit behavior
[/support/docview.wss?uid=swg27040251&aid=36] 15.3.11 Action on Exit |
0777e5e8be561e726031c3e100039abf_8 | [/support/docview.wss?uid=swg27040251&aid=37] [/support/docview.wss?uid=swg27040251&aid=1] 19. Behavior in state (do-activity)
[/support/docview.wss?uid=swg27040251&aid=38] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=39] (*) Can be implemented using entry and exit actions. See appendix (*2) for additional information. 20. Deferred events
[/support/docview.wss?uid=swg27040251&aid=40] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=41] (*) Can be modeled by customizing the framework. See appendix (*3) for additional information. 21. State Redefinition 15.3.11 State Redefinition (*) Class inheritance causes inheritance of statecharts. the inherited statechart can redefine its inherited states. 22. State Machine extension 15.3.12 State machine extension (*) through class inheritance 23. Time event
[/support/docview.wss?uid=swg27040251&aid=42] 15.3.13 Time event |
0777e5e8be561e726031c3e100039abf_9 | [/support/docview.wss?uid=swg27040251&aid=43] (*) First option tm(<expression>), where<expression> is the number of time units. Second option Accept time event. 24. Transition 15.3.14 Transition (*) A transition cannot be associated with more than one trigger. Separate transitions for each trigger need to be used.
(*) See appendix (*4) for the list of known transaction patterns that are forbidden by Rhapsody. 25. Internal transition
[/support/docview.wss?uid=swg27040251&aid=44] 15.3.14 Reaction in state |
0777e5e8be561e726031c3e100039abf_10 | [/support/docview.wss?uid=swg27040251&aid=45] [/support/docview.wss?uid=swg27040251&aid=1] 26. Completion transition 15.3.14 Null transition [/support/docview.wss?uid=swg27040251&aid=1] 27. Completion event 15.3.14 Null event [/support/docview.wss?uid=swg27040251&aid=1] 28. Transition redefinition 15.3.14 Transition redefinition (*) Class inheritance causes inheritance of statecharts. the inherited statechart can redefine its transitions, except the source state and the trigger. 29. Signal receipt
[/support/docview.wss?uid=swg27040251&aid=46] 15.3.14 Accept Event Action
[/support/docview.wss?uid=swg27040251&aid=47] [/support/docview.wss?uid=swg27040251&aid=1] 30. Signal sending
[/support/docview.wss?uid=swg27040251&aid=48] 15.3.14 Send Action
[/support/docview.wss?uid=swg27040251&aid=49] [/support/docview.wss?uid=swg27040251&aid=1] 31. Action sequence notation |
0777e5e8be561e726031c3e100039abf_11 | [/support/docview.wss?uid=swg27040251&aid=50] 15.3.14 [/support/docview.wss?uid=swg27040251&aid=51] [/support/docview.wss?uid=swg27040251&aid=1] 32. Local transition
[/support/docview.wss?uid=swg27040251&aid=52] 15.3.15 [/support/docview.wss?uid=swg27040251&aid=53] [/support/docview.wss?uid=swg27040251&aid=1] 33. Choice Pseudostate/Dynamic Conditional Branch
[/support/docview.wss?uid=swg27040251&aid=54] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=55] (*) Can be simulated for example by using an additional state with guarded outgoing null transitions. See attachment (*1) in appendix. 34. Final Notation
[/support/docview.wss?uid=swg27040251&aid=56] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=57] (*) {final} means that the state cannot be redefined (such as, extended). 35. Entry/Exit Point as part of submachine state graph |
0777e5e8be561e726031c3e100039abf_12 | [/support/docview.wss?uid=swg27040251&aid=58] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=59] [/support/docview.wss?uid=swg27040251&aid=1] 36. Entry/Exit Point on composite state
[/support/docview.wss?uid=swg27040251&aid=60] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=61] [/support/docview.wss?uid=swg27040251&aid=1] 37. "Bracket" Entry/Exit Point notation
[/support/docview.wss?uid=swg27040251&aid=62] 15.3.1 [/support/docview.wss?uid=swg27040251&aid=63] [/support/docview.wss?uid=swg27040251&aid=1] 38. Referenced/Reused submachine state
[/support/docview.wss?uid=swg27040251&aid=64] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=65] (*) Creation of submachine is supported, but cannot be reused/referenced elsewhere. 39. Multiple triggers for a transition
[/support/docview.wss?uid=swg27040251&aid=66] 15.3.14 [/support/docview.wss?uid=swg27040251&aid=67] [/support/docview.wss?uid=swg27040251&aid=1] 40. Extended Notation |
0777e5e8be561e726031c3e100039abf_13 | [/support/docview.wss?uid=swg27040251&aid=68] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=69] (*) Similar effect is achievable but need to extend a whole class containing a state machine using generalization. |
0777e5e8be561e726031c3e100039abf_14 | Appendix:
Disclaimer All source code or binaries attached to this document are referred to here as "the Program". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an "AS IS" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
#tbc
#tbc
(*1) Dynamic Conditional Branch
DynamicBranch74orHigher.zip [/support/docview.wss?uid=swg27040251&aid=71]DynamicBranch74orHigher.zip [/support/docview.wss?uid=swg27040251&aid=70] |
0777e5e8be561e726031c3e100039abf_15 | #tbc
(*2)
there is a risk that is involved to support an execution of an action that is being performed while the owning object is in a certain state. For example, there is a state "WaitForInput" with Do Action reading an input from the console in the background. Now an event comes to trigger a transition - a need arose to interrupt the operation of reading the input - but there is no generic way to do such things for all operations unless the action is being performed in a different thread and kill this thread. this solution seems risky for embedded systems and considered inefficient.
#tbc
(*3)
Rhapsody does not support deferred events, but there is an easy way to catch an event, which is not consumed, and process it according to your need. OMReactive class contains handleNotConsumed() virtual function, which can be overridden in your reactive class. This function is always called when event is not consumed. |
0777e5e8be561e726031c3e100039abf_16 | (*4)Transactional Restrictions - List of known transaction patterns that are forbidden by Rhapsody |
0777e5e8be561e726031c3e100039abf_17 | Multiple outgoing transitions from Exit Point [/support/docview.wss?uid=swg27040251&aid=72] Transition to Condition Connector from Entry/Exit Point having multiple incoming transitions [/support/docview.wss?uid=swg27040251&aid=73] [/support/docview.wss?uid=swg27040251&aid=73] |
0777e5e8be561e726031c3e100039abf_18 | [/support/docview.wss?uid=swg27040251&aid=74] [/support/docview.wss?uid=swg27040251&aid=74] Direct transition from Junction to Condition Connector [/support/docview.wss?uid=swg27040251&aid=75] Indirect transition from Junction to Condition Connector by way of Entry/Exit Point [/support/docview.wss?uid=swg27040251&aid=76] Direct transition from Join Bar to Junction [/support/docview.wss?uid=swg27040251&aid=77] Direct transition from Junction to Fork Bar [/support/docview.wss?uid=swg27040251&aid=78] Multiple incoming transition to Condition Connector [/support/docview.wss?uid=swg27040251&aid=79] Set a trigger on a transition that is originated from Exit Point [/support/docview.wss?uid=swg27040251&aid=80]
RELATED INFORMATION
UML 2.4.1 Superstructure [http://www.omg.org/spec/UML/2.4.1/Superstructure/PDF/]
Enhancement for Do Activity [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=8817] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.