chunk_id
string
chunk
string
0777e5e8be561e726031c3e100039abf_19
Enhancement for Dynamic Condition Connector [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=7832] Enhancement for Shallow History Connector [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=5916] Enhancement Deferred Event [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=12691]
b2da6f28d6d0d2c6d876309e0bc66471_0
IBM How to serve static files from both IBM HTTP Server and an application in WebSphere Application Server - United States TECHNOTE (FAQ) QUESTION How can I configure IBM HTTP Server (IHS), and the IBM web server Plug-in, and my web application running in WebSphere Application Server (WAS), to serve some of my static files (JPG, GIF, CSS, JS, etc) from the IHS web server, but serve other static files from my web app running in WAS? CAUSE The "fileServingEnabled" property in the ibm-web-ext.xmi file in the web application, is like an ON / OFF switch. A setting of fileServingEnabled="true" means that ALL static files will be served from the web application in WAS only. In this case, the plug-in config will use a wildcard with the application context-root like "/myapp/*". That way every URL starting with /myapp/* will be routed to the application in WAS.
b2da6f28d6d0d2c6d876309e0bc66471_1
On the other hand, fileServingEnabled="false" means NO static files will be served from the application in WAS. In this case, a wildcard will NOT be used in the plugin-cfg.xml file. Instead, there will be several URI entries matching the URL-Patterns from <servlet-mappings> in the web.xml, like "/myapp/servlet1" and "/myapp/index.jsp". Requests for dynamic content matching the URI entries in the Plug-in config, will be routed to the application in WAS. But everything else (static content) will be handled by the IHS web server itself.
b2da6f28d6d0d2c6d876309e0bc66471_2
ANSWER If you want to serve any static files (JPG, GIF, CSS, JS, etc) from your web application in WAS, you must use fileServingEnabled="true" in the ibm-web-ext.xmi file. That will cause the plug-in to use a wildcard entry for the context-root of your web application. For example, if the context-root is "myapp", then there will be a URI entry for "/myapp/*" in the plug-in config, and everything starting with "myapp" will be routed to the application in WAS. Now, if you also want to be able to serve some of the static files from the IHS web server itself, you will need to do a trick using RewriteRule in the IHS config. Here is how the trick works: 1) Create a subdirectory called "static" under the IHS DocumentRoot directory. And put the static files that you want IHS to serve into that directory. For example in the IHS document root directory (HTTPServer/htdocs/) create a subdirectory called "static". Something like this: /usr/IBM/HTTPServer/htdocs/static/
b2da6f28d6d0d2c6d876309e0bc66471_3
2) In your web application, you will reference those files using relative references like "static/picture.jpg", or "static/mystyles.css". Those relative references will be interpreted as URLs like this: /myapp/static/picture.jpg /myapp/static/mystyles.css Keep in mind that there really is NOT any "static" subdirectory in the application. But that is ok. 3) Now, in the IHS config, you must use RewriteCond and RewriteRule to watch for these references, and redirect to get them from IHS. For example, look at these directives... <ifModule mod_rewrite.c> RewriteEngine on RewriteRule ^/myapp/static/(.*) /static/$1 [PT] </ifModule> It means, if the URI begins with /myapp/static/* then IHS will rewrite it to just /static/* and "pass-through". Since /static/* does NOT match anything in the Plug-in config, the request will be handled by IHS, and the file will be served from the static directory under IHS DocumentRoot.
b2da6f28d6d0d2c6d876309e0bc66471_4
To the user looking at the URL in the browser they will see this: /hostname/myapp/static/picture.jpg But, the file will really be served by IHS from here: /hostname/static/picture.jpg Here is another example: If you just want to match and serve *.gif files from IHS, use: RewriteCond %{REQUEST_URI} \.(gif)$ [NC] RewriteRule ^/myapp/(.*) /static/$1 [PT] If you just want to match and serve *.gif, *.css and *.js files from IHS, use: RewriteCond %{REQUEST_URI} \.(gif|css|js)$ [NC] RewriteRule ^/myapp/(.*) /static/$1 [PT] Which assumes the files themselves are placed in [IHS_DOC_ROOT]/static/. 4) For the static files in the application, you will need to put them in some other directory that is NOT called "static", for example "images/sunset.jpg" would be a directory and file in the myapp application. This URL request, would be handled by the Plug-in and sent to the application in WAS: hostname/myapp/images/sunset.jpg
b2da6f28d6d0d2c6d876309e0bc66471_5
So, by using the trick described above, some static files will be served from IHS, like: /hostname/myapp/static/picture.jpg But other static files will be served from the web application running in WAS, like: /hostname/myapp/images/sunset.jpg
5bad65c8bb44c2a6f99258150fd4a447_0
IBM Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5 (CVE-2015-4000) - United States SECURITY BULLETIN SUMMARY The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5.
5bad65c8bb44c2a6f99258150fd4a447_1
VULNERABILITY DETAILS CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000] DESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as "Logjam". CVSS Base Score: 4.3 CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] 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 IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server version 2.5 REMEDIATION/FIXES None
5bad65c8bb44c2a6f99258150fd4a447_2
WORKAROUNDS AND MITIGATIONS Customers should follow the mitigation advice contained in the WebSphere Application Server security bulletin, located at http://www.ibm.com/support/docview.wss?uid=swg21957980 [http://www-01.ibm.com/support/docview.wss?uid=swg21957980] . 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 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 Reported to IBM by The WeakDH team at https://weakdh.org [https://weakdh.org] CHANGE HISTORY 08 June 2015: Original document published
5bad65c8bb44c2a6f99258150fd4a447_3
*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.
c355b4474bf3f762290b3fd07f669934_0
IBM Why does IBM Datacap 8.1 appear to hang, requiring a restart of all components? - United States hang; non responsive; timeout; Admin retry; Engine retry TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT) Why does IBM Datacap appear to hang, requiring a restart of all components? SYMPTOM The Datacap system appears to become non-responsive, requiring a restart of all components to get it working again. CAUSE The cause is due to a malformed SQL query string. From the client perspective, it was reported to occur during logon via TMWeb, and Thick Client. Another case was from a user that was doing a Thick Client query. TMServer has an feature where it will retry any command that results in error, based on the settings in the registry. The settings reflect the number of retries to do and the time interval to wait. The default settings have a duration of 16 minutes, which gives the appearance that the TMServer has hung.
c355b4474bf3f762290b3fd07f669934_1
DIAGNOSING THE PROBLEM Collect and examine the TMServer log. Look for multiple instances (6-12) of an ADO error, indicating a bad query was executed. This information can be used to identify the user that is causing the problem RESOLVING THE PROBLEM While bad queries should be avoided, the following will allow TMServer to respond faster, should a bad query happen: 1. Stop all Datacap applications, then stop the TMServer. 2. Change the following registry entries on the TMServer box:
c355b4474bf3f762290b3fd07f669934_2
* * * HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\TMS\InterThread (REG_SZ) Admin retries HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\TMS\InterThread (REG_SZ) ADO retries HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\TMS\InterThread (REG_SZ) Engine retries * * * * HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\TMS\InterThread (REG_SZ) Admin retries HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\TMS\InterThread (REG_SZ) ADO retries HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\TMS\InterThread (REG_SZ) Engine retries * * * * * * * * * * * * * * * * 3. Restart the TMServer, then start the Datacap applications in reverse order. Please Note: Since these are considered tuning parameters, you will need to test to see what settings work best for your system. Note: for Datacap 9.x, the registry entry name is singular, as in 'Admin retry' or 'Engine retry'.
6f09a8c5ef85188c55aca72e7935bef4_0
IBM Configure IBM Content Collector to use SSL to communicate with IBM FileNet P8. - United States TECHNOTE (FAQ) QUESTION How do I configure IBM Content Collector (ICC) to use SSL to communicate with IBM FileNet P8 for all components? CAUSE ICC communicates with P8 in several different components. Depending on the API used for the various components, P8 certificates need to be installed in multiple places. ANSWER Do the following steps to install P8 certificates. Depending on your business requirements, you may not use all of the components so some steps may not be necessary.
6f09a8c5ef85188c55aca72e7935bef4_1
* First obtain a P8 server certificate by accessing the P8 Content Engine ping page using this URL: https://<ce_server>:<ssl_port>/FileNet/Engine From the browser, view the certificate and copy it to a file. Use it for later steps. Do not use the MTOM page as it may not produce the same certificate that ICC requires. * Perform this step if you are going to run ICC Initial Configuration to create new document classes in P8 object store. * To import the certificate, issue the following command, whereICCInstallDiris the directory of your Content Collector installation andP8CertificatFileis the certificate for the FileNet P8 server: "ICCInstallDir\java\jre\bin\keytool.exe" -import -file P8CertificateFile -keystore "ICCInstallDir\java\jre\lib\security\cacerts" -alias afup8 * At the password prompt, enter the password for the JRE keystore. (The default password is changeit.) * Enterywhen asked whether to trust the certificate.
6f09a8c5ef85188c55aca72e7935bef4_2
* Run ICC Initial Configuration and you should then be able to validate the connection with P8 using SSL.
6f09a8c5ef85188c55aca72e7935bef4_3
* Perform this step if you are going to run task route archiving to P8: * Add the P8 certificate into the Windows Trusted Root Certificate Authorities via the Microsoft Management Console. * For more details instructions, refer to this document: http://www-01.ibm.com/support/docview.wss?uid=swg21610358 [http://www-01.ibm.com/support/docview.wss?uid=swg21610358]
6f09a8c5ef85188c55aca72e7935bef4_4
* Perform this step if you are going to retrieve, restore, or search for documents from P8: * Start ikeyman from ICC-install-directory\AFUWeb\ewasfor the ICC embedded web application server. * In the ikeyman utility, select Key Database File>Open, and select PKCS12as key database type. * In theLocationfield, specify theWAShome\profiles\profile name\config\cells\cell name\nodes\node name\trust.p12file. ReplaceWAShome,profile name,cell name, andnode namewith the proper values of your web application server installation. * Click OK. * When prompted for a password, enter the password. ClickOK. The default password is WebAS. * Under theSigner certificateslist, clickAddto add the P8 certificate. * Exit ikeyman utility and restart IBM Content Collector Web Application service.
6f09a8c5ef85188c55aca72e7935bef4_5
* For more details instructions, refer to this document: http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/installing/t_afu_establish_trust_relationship.dita?lang=en [http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/installing/t_afu_establish_trust_relationship.dita?lang=en]
ccc5de8e865deebd684e3cc5d7c41f59_0
IBM Using dblook and ij to work with the embedded Apache Derby in WebSphere Portal - United States TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT) IBM WebSphere Portal 6.1 uses an embedded version of Apache Derby out of the box. However, there is no longer a graphical tool such as CloudView (as with Cloudscape 5.x). In order to obtain the data and structure of the WebSphere Portal database, dblook and ij utilities can be used to accomplish such goals. RESOLVING THE PROBLEM Before proceeding with the following, it is strongly recommended that you back up your Derby database. Make a copy of <wp_profile>/PortalServer/derby/wpsdb to a backup directory. Since the version of Derby used in WebSphere Portal is embedded, you must stop the Portal server before you can access the database although you can always work on the backup copy. NOTE: For simplicity, we will omit the extension of the utilities. You should add ".sh" or ".bat' depending on the platform.
ccc5de8e865deebd684e3cc5d7c41f59_1
There are three primary utility tools that are installed with WebSphere 6.1, "dblook", "ij", and "sysinfo", under the <was_root>/AppServer/derby/bin/embedded directory. The sysinfo utility generates information about the operating system, the Java version and classpath, and the Derby driver files and version information. dblook utility The dblook utility is used to view the database structure (in DDL - Data Definition Language) for a specific database. The usage is dblook -d <databaseURL> [options], where databaseURL is in the "jdbc:derby:<database>" format. The <database> should be given as a full path, such as C:\IBM\WebSphere\wp_profile\derby\wpsdb. Commonly used options include:
ccc5de8e865deebd684e3cc5d7c41f59_2
* * * * * * * * * * * Examples: * * * dblook -d jdbc:derby:C:\IBM\WebSphere\wp_profile\PortalServer\wpsdb -o C:\temp\wpsdb_ddl.sql * * * * * dblook -d jdbc:derby:C:\IBM\WebSphere\wp_profile\PortalServer\wpsdb -z release -o C:\temp\wpsdb_ddl.sql * * * * * dblook -d jdbc:derby:C:\IBM\WebSphere\wp_profile\PortalServer\wpsdb -z release -t user_desc -verbose -o C:\temp\user_desc.sql * * ij utility The ij utility is a command line SQL processor. It can be used to run DDL for creating database, tables, indexes, and so on. In a WebSphere Portal environment, it would typically be used for exporting data or making simple changes (when advised by IBM Support). To start ij, simply open a command prompt or terminal window, change the directory and enter the command. You should then see the ij shell with prompt "ij>".
ccc5de8e865deebd684e3cc5d7c41f59_3
The following are some common commands that you may use when reviewing data in the Portal database. * * ij> connect 'jdbc:derby:C:\IBM\WebSphere\wp_profile\derby\wpsdb'; * * * * * ij> show connections; * * * CONNECTION0* - jdbc:derby:C:\ibm\websphere\wp_profile\portalserver\derby\wpsdb * = current connection ij> driver "org.apache.derby.jdbc.EmbeddedDriver'; * * * * ij> set schema=release; * * * * * ij> select * from user_desc where oid=1000; * * * * * ij> run 'myquery.sql'; * * * * * * * ij> CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE('RELEASE','USER_DESC','USER_DESC.SQL',';','|',NULL); * * * * * ij> * CALL SYSCS_UTIL.SYSCS_EXPORT_QUERY('SELECT * FROM RELEASE.USER_DESC','user_desc_query.sqlL',null,'|',NULL); * *
ccc5de8e865deebd684e3cc5d7c41f59_4
RELATED INFORMATION Derby utility from Apache [http://docs.oracle.com/javadb/10.3.3.0/getstart/cgsusingtoolsutils.html] Derby SQL references from Apache [http://db.apache.org/derby/docs/10.1/ref/crefsqlj23296.html] Cross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS 7.0, 6.1
df5f00ce30f61b8c466198e4178b7aa9_0
IBM How to set an appropriate number of Portal Datasource connections in WebSphere Portal - United States TECHNOTE (FAQ) QUESTION For a given maximum number of Portal WebContainer threads set, what should I set my maximum Portal datasource connections to? ANSWER When tuning WebSphere Portal at version 6.0 and beyond, one of the concerns that arises is how should one tune the maximum number of Portal datasources. Portal can and does make heavy internal use of datasources, so miscalculating this (maximum) value can have a significant impact on system behavior. Out of the box, the default maximum setting is 50. This may or may not be sufficient for any given system.
df5f00ce30f61b8c466198e4178b7aa9_1
Each Portal request may make any number of database (DB) requests ranging for none to several.. Further, customized portlets and PPR (Parallel Portlet Rendering) may cause several concurrent DB requests. By default, the maximum number of WebContainer threads is also set to 50. Therefore the ratio between the maximum number of Portal datasource connections to the maximum number of Portal WebContainer threads is 1:1. Support has found that this ratio is often too low for the best performance. In the past, there have been recommendations of this ratio as high as of 2:1 or even 2.5:1. However, these values caused concern in large deployments where the TOTAL number of maximum datasource connections might start to place a strain on backend resources. Recent analysis suggests that these ratio values may be safely reduced to 1.25: 1 for all Portal datasource, with the exception of the jcrDB when WCM is used extensively. In this case, we recommend a ratio of 1.5:1
df5f00ce30f61b8c466198e4178b7aa9_2
----------------------------------------------------------------------------------------------------------------- For example, if your system's Maximum number of WebContainer threads is 100 then you should set your Maximum number of Portal datasource connections to 125 for each Portal datasource. ----------------------------------------------------------------------------------------------------------------- If during Runtime, you should find that your running out of Portal Datasource connections, you may go ahead and increase the ratio up to 2:1. Please be aware of how this might impact your backend resources and be sure to scale your database accordingly. ------------------------------------------------------------------------------------------------------------------ To find the number of WebContainer threads that are running in any particular Portal server, use the WebSphere Application Server Admin Console and go to the following location:
df5f00ce30f61b8c466198e4178b7aa9_3
Servers ---> Application Servers --> WebSphere_Portal (your server) --> Thread Pools --> WebContainer To find the Data Source setting for your Portal datasources, use the WebSphere Application Server Admin Console to go to the following location: Resources ---> Data Sources ---> wpdbDB (for example) --> Connection pools --------------------------------------------------------------------------------------------------------------------
7dfc556a4dca638c98f0acdd267eebf7_0
IBM Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task - United States upgrade; TASK001X; import-nodes; 404 TECHNOTE (TROUBLESHOOTING) PROBLEM While attempting to upgrade Portal to CF14 the upgrade fails during the import-nodes sub-task. SYMPTOM The ConfigTrace.log shows the following... import-nodes: --- Exception Thrown --- C:\Portal8\PortalServer\jcr\wp.content.repository.install\config\include s\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task execution failed with response code 404 due to exception : Not Found . Please check the server log for more information. at com.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java: 840) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369)
7dfc556a4dca638c98f0acdd267eebf7_1
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleChe ckExecutor.java:37) ... Caused by: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task execution failed with response code 404 due to exception : Not Found . Please check the server log for more information. at com.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java: 825) ... 75 more CAUSE The customer had previously disabled the autostart on several applications to improve the Portal startup time ENVIRONMENT Portal 8.0.0.1 Windows DIAGNOSING THE PROBLEM from ConfigTrace.log... Wed Nov 19 16:49:42 CST 2014 Target started: import-nodes
7dfc556a4dca638c98f0acdd267eebf7_2
import-nodes: --- Exception Thrown --- C:\Portal8\PortalServer\jcr\wp.content.repository.install\config\include s\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task execution failed with response code 404 due to exception : Not Found . Please check the server log for more information. at com.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java: 840) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) ... Caused by: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task execution failed with response code 404 due to exception : Not Found . Please check the server log for more information. at com.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java: 825) ... 75 more From here I reviewed the SystemOut.log at the same timestamp and see the following...
7dfc556a4dca638c98f0acdd267eebf7_3
[11/19/14 16:49:43:804 CST] 00000042 filter E com.ibm.ws.webcontainer.filter.FilterInstanceWrapper doFilter SRVE8109W: Uncaught exception thrown by filter Extensible Filter: java.io.FileNotFoundException: SRVE0190E: File not found: /jcr/remotetask at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor._processEDR( DefaultExtensionProcessor.java:893) at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.processEDR(D efaultExtensionProcessor.java:874) Both of these messages seems to indicate a problem with the WCM startup. This code is contained in the following application....JavaContentRepository.ear. Looking at your last Portal startup I saw this below which occurs during the wcm application startup.... [11/19/14 15:57:54:566 CST] 00000009 ApplicationMg A WSVR0200I: Starting application: wcm ....
7dfc556a4dca638c98f0acdd267eebf7_4
[11/19/14 16:00:36:812 CST] 00000005 TimeoutManage I WTRN0006W: Transaction 00000149CA10760B000000012830B348BBD991CDC4031D0DFCED27CDD500F13F7FC95B79 00000149CA10760B000000012830B348BBD991CDC4031D0DFCED27CDD500F13F7FC95B79 00000001 has timed out after 120 seconds. [11/19/14 16:00:36:831 CST] 00000005 TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[server.startup : 0,5,main]. The stack trace of this thread when the timeout occurred was: java.lang.Thread.blockedOn(Thread.java:1076) sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce ssorImpl.java:37) java.lang.reflect.Method.invoke(Method.java:611) Knowing this I further reviewed the SystemOut.log to see where the JCR web module gets loaded during startup....it should begin like this... SRVE0169I: Loading Web Module: JCRContentRepository.
7dfc556a4dca638c98f0acdd267eebf7_5
Your startup does not have this. This prompted me to review the deployment.xml from the JavaContentRepository application directory at this location... Portal8/wp_profile/config/cells/C001389391Cell/applications/JavaContentR epository.ear/deployments/JavaContentRepository/deployment.xml The contents show the following... <targetMappings xmi:id="DeploymentTargetMapping_1335003370698" enable="false" target="ServerTarget_1335003370698"/> The enable=false means that you have this application set to not autostart. Because of this it is not starting during Portal startup and therefore is not available when the config task attempts to communicate with it during the upgrade...and therefore causes the problem.
7dfc556a4dca638c98f0acdd267eebf7_6
RESOLVING THE PROBLEM Please make the following change in the WAS Admin Console... Applications > WebSphere enterprise applications > JavaContentRepository > Target specific application status > Check the box for the WebSphere_Portal server > Click Enable Auto Start > Save changes > restart Portal After making this change please attempt the CF upgrade again.
05cc9e2991b6bd8296cf7a8534b5b432_0
IBM Tivoli Integrated Portal hangs because of Argus java.lang.OutOfMemory. - United States cacheTime; config.xml; Argus; TIP cache; TIPL2CONF; TIPL2PERF TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT) Argus stores it's role authorizations in memory cache, and is not cleaned out unless the TIP is restarted. The "cacheTime" variable controls this, which is set to -1 by default. If the number of TIP roles is high, it can cause Java OOM errors. SYMPTOM TIP hangs. SystemOut.log file shows Java.lang.OutOfMemoryError: [10/2/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[/secure/isclite/tiles/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method)
05cc9e2991b6bd8296cf7a8534b5b432_1
CAUSE By default, the ARGUS cache will not get cleaned up unless the TIP server is restarted. This normally will give the system good runtime performance. However, in cases where a large number of user/role mappings are defined, the system may run into Java memory issues causing Java OutOfMemory outages. The cacheTime we are talking about here is Argus cache. The is used for the way the role authorizations are stored in memory by Argus and nothing related to LDAP or SSO. The Argus cache time by default we ship with in TIP is -1 which means the cache will not get cleaned up till we re-start the server. Error from the <TIP_HOME>/profiles/TIPProfile/logs/server1/SystemOut.log [10/2/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[/secure/isclite/tiles/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method) ENVIRONMENT all environments
05cc9e2991b6bd8296cf7a8534b5b432_2
DIAGNOSING THE PROBLEM Java heapdump files will be created in the <TIP_HOME>/profiles/TIPProfile directory. heapdump.20131022.144244.20034001.phd The Systemout.log will have have errors similar to this: [10/2/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[/secure/isclite/tiles/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method) Using the memory heap dump analysis shows that Argus is the problem, specifically the instance shown inside the red line in the output of the Java memory analyzer below: [/support/docview.wss?uid=swg21657452&aid=1] [/support/docview.wss?uid=swg21657452&aid=1] You can also check the cacheTime variable in the <TIP_HOME>/profiles/TIPProfile/config/cells/TIPCell/commonauthz/config.xml file to confirm if it's set to "-1", which means the Argus cache will not get cleaned up unless the TIP server is restarted.
05cc9e2991b6bd8296cf7a8534b5b432_3
RESOLVING THE PROBLEM The cacheTime value in config.xml is in milliseconds. TIP is shipped with the initial value of -1, which means the Argus cache will not be cleared out unless TIP restart. To resolve this issue you need to configure 'cacheTime' to non -1 value. Initially we suggest setting the value to 1200000, which is 20 minutes. After the change you will have to restart the TIP server, normally server1. NOTE: The cacheTime variable was added in TIP version 2.2.0.0.
4cc08246e988abe9a55038175f24a9fb_0
IBM Security Bulletin: IBM MQ and IBM MQ Appliance Shared memory leak caused by MQ applications using dynamic queues. (CVE-2017-1283) - United States SECURITY BULLETIN SUMMARY Shared memory leak caused by MQ applications using dynamic queues. VULNERABILITY DETAILS CVEID: CVE-2017-1283 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1283] DESCRIPTION: IBM WebSphere MQ could allow an authenticated user to cause a shared memory leak by MQ applications using dynamic queues, which can lead to lack of resources for other MQ applications. CVSS Base Score: 3.1 CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125144 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125144] 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)
4cc08246e988abe9a55038175f24a9fb_1
AFFECTED PRODUCTS AND VERSIONS IBM MQ V8 IBM MQ 8.0.0.0 - 8.0.0.6 maintenance levels IBM MQ Appliance V8 IBM MQ Appliance 8.0.0.0 - 8.0.0.6 maintenance levels IBM MQ V9 IBM MQ 9.0.0.0 - 9.0.0.1 maintenance levels IBM MQ V9 CD IBM MQ 9.0.1 - 9.0.3 releases IBM MQ Appliance V9 CD IBM MQ Appliance 9.0.1 - 9.0.3 REMEDIATION/FIXES IBM MQ V8 Apply Fix Pack 8.0.0.7 [https://www-01.ibm.com/support/docview.wss?uid=swg22005832] IBM MQ Appliance V8 Apply Fix Pack 8.0.0.7 for MQ Appliance [https://www-01.ibm.com/support/docview.wss?uid=swg22005832] IBM MQ V9 Apply Fix Pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038] IBM MQ V9 CD Upgrade to IBM MQ 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348] IBM MQ Appliance V9 CD Upgrade to IBM MQ Appliance 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348] WORKAROUNDS AND MITIGATIONS None.
4cc08246e988abe9a55038175f24a9fb_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. 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 14 Nov 2017: Initial Version *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.
4cc08246e988abe9a55038175f24a9fb_3
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.
b5ae55df31857b05cbca8e53da1494c0_0
IBM Multiple logins using the same user ID - United States ConcurrentModificationException; log in; login; multiple; userid; multiple login TECHNOTE (FAQ) QUESTION "ConcurrentModificationException" and other errors may occur if the same user id is logged in to IBM WebSphere Portal multiple times. ANSWER WebSphere Portal has no built-in mechanism or configuration setting to limit the number of times a user id may log in. Unexpected behavior may occur if the same id is logged in more than once and this is not supported. "ConcurrentModificationException" and other errors may be logged. Most of the related issues were resolved in WebSphere Portal 5.1. However, you may still encounter exceptions or side-effects if you access the Portal in multiple browser windows using the same user id, whether or not the authentication requests take place on separate physical hosts.
b5ae55df31857b05cbca8e53da1494c0_1
It may be possible to prevent multiple logins by writing custom "tracking code." Contact IBM Services for assistance to undertake such a project. WebSphere Portal Development does not have any sample code. If you wish to write your own code, some of the issues to be aware of are (this is not an inclusive list): -- Multiple logins may take place on different nodes in a cluster. This means some cluster-wide mechanism would have to be in place to keep track of the logged-in users. Look at the WebSphere Application Server DistributedMap interface. -- There should be a fail-safe way to track user logout (explicit logout and session timeout). Using a session listener might be a possibility. -- If a user closes the browser without logging out, that user must wait for a session timeout before logging in again. Otherwise, there should be a "force simultaneous login" option in the login user interface. For load testing, use unique user ids or virtual users.
b5ae55df31857b05cbca8e53da1494c0_2
RELATED INFORMATION Portal 6.1/7.0: Authentication Filters [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?topic=/com.ibm.wp.ent.doc_v615/admin/adauthflt.html] Portal 6.1: Custom Login Portlet [https://www.ibm.com/support/docview.wss?uid=swg21358508] Restricting Multiple Sessions [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Restricting_Multiple_Sessions_in_WebSphere_Portal] Cross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products General AIX, HP-UX, Linux, Solaris, Windows 7.0, 6.1.5, 6.1, 6.0, 5.1
484794b4c3c27e484fb5bf2874bb908d_0
IBM WebSphere Portal startup fails with EJCBC0002E: The service [<serviceName>] could not be located. - United States EJCBC0002E; EJPFD0016E; extensionregistry; CORFriendlySelectionServiceHome TECHNOTE (TROUBLESHOOTING) PROBLEM When starting the WebSphere_Portal server, startup throws an exception: EJCBC0002E: The service could not be located.
484794b4c3c27e484fb5bf2874bb908d_1
SYMPTOM In the SystemOut.log, the following exception can be seen at the time the wps.ear application is started: =========================== [1/13/11 11:00:56:875 EST] 00000015 Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed. com.ibm.portal.resolver.exceptions.LocalizedIOException: EJCBC0002E: The service [com.ibm.wps.resolver.friendly.CORFriendlySelectionServiceHome] could not be located. at com.ibm.portal.resolver.helper.eclipse.Platform.createInstance(Platform.java:201) at com.ibm.portal.resolver.helper.eclipse.Platform.createInstance(Platform.java:128) at com.ibm.wps.resolver.friendly.service.PortalFriendlySelectionBootstrapService.init(PortalFriendlySelectionBootstrapService.java:197) at com.ibm.wps.services.Service.init(Service.java:107) at com.ibm.wps.services.Service.init(Service.java:83) at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:363) ===========================
484794b4c3c27e484fb5bf2874bb908d_2
The service name in this case is "com.ibm.wps.resolver.friendly.CORFriendlySelectionServiceHome", but the name could vary. You may also see warnings for various applications like this:
484794b4c3c27e484fb5bf2874bb908d_3
=========================== [1/13/11 11:00:54:250 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.model.skinlistprovider) not available for Extension: com.ibm.wps.engine.standardSkinListProvider [1/13/11 11:00:54:252 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.model.themelistprovider) not available for Extension: com.ibm.wps.engine.standardThemeListProvider [1/13/11 11:00:54:269 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.resolver.model.ContentNodeLinkGenerator) not available for Extension: com.ibm.wps.ai.rest.AIContentNodeLinkGenerator [1/13/11 11:00:54:278 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.resolver.model.NavigationNodeLinkGenerator) not available for Extension: com.ibm.wps.ai.rest.AINavigationNodeLinkGenerator ===========================
484794b4c3c27e484fb5bf2874bb908d_4
CAUSE These messages indicate that the the temporary directory for extension points has become corrupted. This can happen after a server is upgraded. RESOLVING THE PROBLEM To resolve this problem, you can do the following: 1. Stop the WebSphere_Portal server 2. Delete the contents of the following directory: <wp_profile root>/temp/<node name>/WebSphere_Portal/_extensionregistry 3. Start the WebSphere_Portal server.
c973a17bd5901015e60f91f00ede0934_0
IBM Seed value used during the instance creation is lost : Recovery procedure - United States seed lost; idsgendirksf; Encryption Seed Value; key stash file TECHNOTE (TROUBLESHOOTING) THIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S): English PROBLEM(ABSTRACT) Generating key stash file if the seed value which was used at the time of instance creation has been lost then there is no way to recover this seed value. RESOLVING THE PROBLEM There is NO way to recover the seed value used during the instance creation if it has been lost. The only workaround is to create a new instance with a new encryption seed value and then use the db2ldif and ldif2db utilities to export and import data respectively. These utilities can be supplied with the new encryption seed and the salt value of the new instance. Thus the data would be preserved(alongwith the passwords) on this new instance. Here are the steps to follow: 1. Set up a new instance says "newinst".
c973a17bd5901015e60f91f00ede0934_1
$> idsicrt -I newinst -e thisismyencryptionseed -l (/home/newinst) -n $> idscfgdb -I newinst -w ldap -a newinst -t newinst -l (/home/newinst) -n $> idscfgsuf -s "o=ibm,c=us" -I newinst -n $> idsdnpw -u cn=root -p root -I newinst -n 2. Note the encryption seed - "thisismyencryptionseed". Let us call this new_encryptionseed 3. Once this new instance is setup note down the salt value generated by the new server instance by searching for "cn=crypto,cn=localhost". $> ldapsearch -D <administrator DN> -w <administrator password> -b "cn=crypto,cn=localhost" -s base objectclass=* ibm-slapdCryptoSalt Let us call this value: new_saltvalue 4. Lets assume that the instance name with the forgotten encryption seed is "oldinst" 5. Use the db2ldif utility on the instance with the forgotten encryptionseed, oldinst with the following options - $> db2ldif -o outputfile -I oldinst -k new_encryptionseed -t new_saltvalue
c973a17bd5901015e60f91f00ede0934_2
6. Once this step is successfully completed the entire data from "oldinst" would be dumped in outputfile. 7. Use the utilities like ldif2db to re-load all the data into the new server instance. HISTORICAL NUMBER
11a385c2cd40e3536bfa50b9a55cdd49_0
IBM Procedure to change the username and/or password for the FileNet Content Engine Directory Service Account, including the bootstrap user - United States change; user; password; fem; directory service; bootstrapconfig; bootstrap user TECHNOTE (FAQ) QUESTION How do you change the user and/or password for Directory Service Account used by the Content Engine? ANSWER The Directory Service user account and password are normally used in two product components: FileNet Enterprise Manager (FEM), and the application server. A coordinated update procedure should be followed when there is a need to change the user account and/or password. This procedure applies to FileNet Content Engine 4.x and above. * * Note: * *
11a385c2cd40e3536bfa50b9a55cdd49_1
If the same user account is also used as the CE Bootstrap user, the corresponding user in the BootstrapConfig.properties needs to change as well. For changing the GCD admin user/password in BootstrapConfig.properties specifically, refer to this documentation: http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=/com.ibm.p8.doc/admin/security/sec_how_change_bootstrap_pwd.htm [http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=/com.ibm.p8.doc/admin/security/sec_how_change_bootstrap_pwd.htm] 1. Launch FEM and the application server's administrative console. a. Login to FEM using the Directory Service account. b. Login to the application server administrative console with an administrator account. Important: Do not close above two applications until you have completed step 5 below.
11a385c2cd40e3536bfa50b9a55cdd49_2
2. Make LDAP account changes: a. Change the password for an existing account on the LDAP server - Using LDAP interface, change the password for the CE Directory Service account. OR b. Create a new user account on the LDAP server for the CE Directory Service account. 3. Add new user (if applicable), to FEM If the bind user is also the CE admin user, then the bind user will need to be added to all the existing objects in the P8 domain. Please read Update object store with new users and groups [http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=/com.ibm.p8.doc/admin/security/sec_how_update_os.htm] for instructions
11a385c2cd40e3536bfa50b9a55cdd49_3
4. Change Directory Configuration bind user in FEM Using FEM (step 1a above), go to Domain properties > Directory Configuration > Select Directory Configuration > click on the Modify button > General Tab: a. Modify the Directory Service User with new user's full distinguish name (DN) b. Click on Change password check box > change to a new password > click OK. At this point you will be presented a dialog box with following message: “These changes require the application server to be restarted. Please restart the application server to incorporate these changes” click OK > click OK Important: Do not restart the application server until you have completed step 5 below. 5. Change the user in the application server's directory configuration - For Websphere, in the WebSphere Administrative Console, go to Global Security > click on Configure under User Account Repository > Modify Bind Distinguished Name (DN) > Modify Bind Password > click OK and Save changes
11a385c2cd40e3536bfa50b9a55cdd49_4
- For WebLogic go to Security Realms > myrealm > Providers > ldap provider and click on "Provider Specific" tab in WebLogic Admin Console. Change "Principal" and "Credential". - For JBoss go to <JBoss Home>\server\<CE Server>\conf directory and edit "login-config.xml". Find "FileNet" application-policy and in login module change bindDN/bindCredential. 6. Changing the CE Bootstrap user For CE 4.5.x and above: a. In the Configure Bootstrap Properties task, set the Bootstrap Operation property to Modify Existing. b. Confirm that the Bootstrapped EAR file property contains the path to the bootstrap file you need to edit. c. Change the Bootstrap user password. Use Configuration Manager's features to save and run the task. d. Run Configuration Manager's Deploy Application. For CE 4.0: Note: This step is needed only if the GCD user name is the same as the Directory Service account. Note that the example below is for a Windows environment.
11a385c2cd40e3536bfa50b9a55cdd49_5
- For WebSphere a. Open command prompt window, go to folder where EAR file reside (it differs depending on CE version). For example, in CE 4.5.1, go to "<CE Home> \ tools \ configure \ profiles \ <profile> \ ear" b. Backup Engine-ws.ear c. Execute the command below: java –jar “c:\program files\FileNet\ContentEngine\lib\BootStrapConfig.jar” –e Engine-ws.ear --username <username> --password <password> d. Since the Engine-ws.ear file has been deployed in the WebSphere's installedApps path, the Bootstrap file need to be copied to the path manually. Extract the props.jar file from the ear file by utility such as Winzip, copy the props.jar file to theinstalledApps location - “<WebSphere Home>\ AppServer\ profiles \ <profile name> \ InstalledApps \<serverNodecell> \ FileNetEngine.ear \ APP-INF \ lib \" Note that an alternative to copying the props.jar file is to uninstall and re-install the updated ear file in WebSphere.
11a385c2cd40e3536bfa50b9a55cdd49_6
- For WebLogic a. Open command prompt window, go to folder - "<WebLogic home> \ user_projects \ domains \ <domain> \ servers " b. Backup FileNetEngine.ear c. Execute the command below: java –jar “c:\program files\FileNet\ContentEngine\lib\BootStrapConfig.jar” –e Engine-wl.ear --username <username> --password <password> - For JBoss a. Open command prompt window, go to folder - "<JBoss Home> \ server \ <server> \ deploy \" b. Backup FileNetEngine.ear c. Execute the command below: java –jar “c:\program files\FileNet\ContentEngine\lib\BootStrapConfig.jar” –e Engine-jb.ear --username <username> --password <password>
11a385c2cd40e3536bfa50b9a55cdd49_7
7. Remove cached files in the application server - Close FileNet Enterprise Manager (Step 1a) - Close Administrative Console (Step 1b) - Stop the application server - Remove the cached FileNetEngine directory in the application server. For example, the default windows path on Websphere 6.0 is "C:\program files\Websphere\AppServer\profiles\<profile name>\temp\<server node>\ <server>\FileNetEngine" 8. Restart the application server, and login to FEM using the new user and password. 9. Troubleshooting If CE fails to start due to mistakes in the above procedures, you may not be able to redo the change through these procedures because FEM will fail to run. In this case, you can do the following:
11a385c2cd40e3536bfa50b9a55cdd49_8
- Back out the change made to the GCD database in step 3 by deleting the latest row in the FNGCD table. - Back out the change made to the application server in step 4 by redoing the procedure with the previous user. - Back out the change made to the BootstrapConfig.properties file's GCD user by using the backup EAR file - Restart the application server, and login to FEM using the previous user.
46639f066ce4771d7738214435d92c75_0
IBM Security Bulletin: Multiple vulnerabilities affect Java Server Faces (JSF) used by WebSphere Application Server shipped with Jazz for Service Management (CVE-2017-1583, CVE-2011-4343) - United States SECURITY BULLETIN SUMMARY There are two potential information disclosure vulnerabilities that affects the Java Server Faces (JSF) component used by WebSphere Application Server. VULNERABILITY DETAILS CVEID: CVE-2017-1583 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1583] DESCRIPTION: IBM WebSphere Application Server could allow a remote attacker to obtain sensitive information caused by improper error handling by MyFaces in JSF. CVSS Base Score: 5.3 CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132342 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132342] for the current score CVSS Environmental Score*: Undefined CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)
46639f066ce4771d7738214435d92c75_1
CVEID: CVE-2011-4343 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4343] DESCRIPTION: Apache MyFaces could allow a remote attacker to obtain sensitive information. An attacker could exploit this vulnerability using specially crafted parameters to inject EL expressions into input fields mapped as view parameters and obtain sensitive information. CVSS Base Score: 5 CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132287 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132287] for the current score CVSS Environmental Score*: Undefined CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N) AFFECTED PRODUCTS AND VERSIONS Jazz for Service Management version 1.1.0 - 1.1.3 REMEDIATION/FIXES
46639f066ce4771d7738214435d92c75_2
Principal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin Jazz for Service Management version 1.1.0 - 1.1.3 Websphere Application Server Full Profile 8.5.5 Security Bulletin: Multiple vulnerabilities affect Java Server Faces (JSF) used by WebSphere Application Server (CVE-2017-1583, CVE-2011-4343) [http://www-01.ibm.com/support/docview.wss?uid=swg22008707] WORKAROUNDS AND MITIGATIONS Please refer to WAS iFix 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]
46639f066ce4771d7738214435d92c75_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] CHANGE HISTORY 27-November-2017: 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.
46639f066ce4771d7738214435d92c75_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.
af39eb4d1cff61c40213c68f4998ef43_0
IBM Content Navigator known issue: In a SPNEGO/Kerberos Single sign-on environment, IBM Content Navigator the Log Out option is enabled - United States PRODUCT DOCUMENTATION ABSTRACT In a SPNEGO/Kerberos single sign-on (SSO) environment, your IBM Content Navigator session shows the Log Out option as enabled when you select the drop-down menu on the user name. However, the option should be disabled. CONTENT IBM Content Navigator disables the Log Out option under SSO environments. However, under some SSO environments or desktop load scenarios, such as SPNEGO/Kerberos on a WebLogic Application Server, IBM Content Navigator enables the Log Out option. If the Log Out option is enabled but does not work correctly in your SSO environment, you can remove the Log Out option by customizing the banner user session context menu that is used by your desktop configuration. To remove the Log Out option:
af39eb4d1cff61c40213c68f4998ef43_1
1. In the administration tool, select Menus. 2. Enter "User" in the Name contains filter field. 3. Select the Default banner user session context menu and click Copy. 4. Enter a name for the new menu such as "Banner user session context menu - no Log Out option". 5. Remove the Log Out from the Selected list. 6. Save the new menu. 7. Open the Desktops configuration, then open your desktop configuration. 8. Select the Menus tab and scroll to the Feature Context Menus section. 9. Select the new menu that you created for the Banner user session context menu menu type. 10. Save your desktop. The change to the menus takes effect when the modified desktop is reloaded. Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management Case Manager AIX, Linux, Linux on System z, Windows 5.2.1.0
48589d6149fd013356b97dea9ce24d22_0
IBM PI69518:group search fails with a classcast exception after upgrade to 8.5.5.10 - United States PI69518; PI69518; PI69518 DOWNLOADABLE FILES ABSTRACT group search fails with a classcast exception after upgrade to 8.5.5.10 DOWNLOAD DESCRIPTION PI69518 resolves the following problem: ERROR DESCRIPTION: After upgrade to 8.5.5.10, there are cases when group search fails from "Users and Groups" -> "Administrative Groups" panel. When it happens in GUI, the same issue happens with AdminTask listRegistryGroups command. Seeing the following in systemout.log: [9/20/16 15:37:21:077 EDT] 00000076 GroupDetailAc W listRegistryGroups: Command not successful: java.lang.ClassCastException: javax.management.ObjectName incompatible with javax.management.AttributeList ************************************************** In traces we see stack:
48589d6149fd013356b97dea9ce24d22_1
[9/20/16 15:36:05:658 EDT] 00000076 SecurityRealm 3 exception caught java.lang.ClassCastException: javax.management.ObjectName incompatible with javax.management.AttributeList at com.ibm.ws.security.admintask.securityDomain.SecurityRealmProvid er.getLD APProps(SecurityRealmProvider.java:1420) at com.ibm.ws.security.admintask.securityDomain.SecurityRealmProvid er.getLD APList(SecurityRealmProvider.java:1363) at com.ibm.ws.security.admintask.securityDomain.SecurityRealmProvid er.listR egistryGroups(SecurityRealmProvider.java:402) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.jav a:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod Accessor Impl.java:56) at java.lang.reflect.Method.invoke(Method.java:620) at com.ibm.websphere.management.cmdframework.provider.SimpleCommand Provider .executeReal(SimpleCommandProvider.java:156) at
48589d6149fd013356b97dea9ce24d22_2
com.ibm.websphere.management.cmdframework.provider.SimpleCommand Provider .execute(SimpleCommandProvider.java:142) at com.ibm.websphere.management.cmdframework.provider.SimpleAdminCo mmand.ex ecute(SimpleAdminCommand.java:57)
48589d6149fd013356b97dea9ce24d22_3
LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: All users of IBM WebSphere Application Server PROBLEM DESCRIPTION: java.lang.ClassCastException when group search is performed. RECOMMENDATION: None There was a bug in the code that uses a registry object that may not contain necessary attributes for the group search and causes ClassCastException. PROBLEM CONCLUSION: The bug was fixed in the code to correct the exception. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.11. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980] PREREQUISITES None INSTALLATION INSTRUCTIONS Please review the readme.txt for detailed installation instructions. URL LANGUAGE SIZE(Bytes) V85 Readme [ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixes/PI69518/8.5.5.10/readme.txt] US English 6584 DOWNLOAD PACKAGE
48589d6149fd013356b97dea9ce24d22_4
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 8.5.5.10-WS-WAS-IFPI69518 09-28-2016 US English 276737 HTTP [http://www-933.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?fixes=8.5.5.10-WS-WAS-IFPI69518&productid=WebSphere%20Application%20Server&brandid=5] TECHNICAL SUPPORT Contact IBM Support using SR (http://www.ibm.com/software/support/probsub.html [http://www.ibm.com/software/support/probsub.html]), visit the WebSphere Application Server support web site (http://www.ibm.com/software/webservers/appserv/was/support/ [http://www.ibm.com/software/webservers/appserv/was/support/]), or contact 1-800-IBM-SERV (U.S. only). [/support/docview.wss?uid=swg24042833&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24042833&aid=2]Problems (APARS) fixed PI69518
2b9664521f8d895f07380262c8704a7d_0
IBM Unable to start Ping Probe by non-root user on AIX - United States Ping probe; non root; start; permissions TECHNOTE (TROUBLESHOOTING) THIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S): English PROBLEM(ABSTRACT) Ping probe fails to start when the probe is installed and started by non-root user. SYMPTOM The following error is seen in the probe's log: Error: E-P_P-002-038: Could not change euid: Operation not permitted Error: E-P_P-002-017: IPv4 socket failed: specified action does not have access permission of the file Error: E-P_P-002-037: This program can only be run by root, or it must be setuid root. CAUSE Ping probe needs permissions which allow it to run as root and the LIBPATH setting should be changed. ENVIRONMENT AIX
2b9664521f8d895f07380262c8704a7d_1
RESOLVING THE PROBLEM To enable non-root user to start the probe, you need to change the owner to root and permissions to setuid. And AIX ignores the LIBPATH setting when program runs as setuid root, so you also need to put either a copy of the required libraries, or a symbolic link to the required libraries in one of the trusted paths like /lib or /usr/lib. 1. Change the owner to root and permissions to setuid. e.g # cd $OMNIHOME/probes/aix5/ # chown root:root nco_p_ping # chmod +s nco_p_poing 2. Put a symbolic link to the required libraries. e.g # cd /usr/lib
2b9664521f8d895f07380262c8704a7d_2
# ln -s /opt/IBM/netcool/platform/aix5/lib/libgsk* # ln -s /opt/IBM/netcool/platform/aix5/lib/libPa_r.so # ln -s /opt/IBM/netcool/platform/aix5/lib/libnetcool_r.so # ln -s /opt/IBM/netcool/platform/aix5/lib/libslclient_r.so # ln -s /opt/IBM/netcool/platform/aix5/lib/libOpl_r.so # ln -s /opt/IBM/netcool/platform/aix5/lib/libsybct_r.so # ln -s /opt/IBM/netcool/platform/aix5/lib/libsybcs_r.so # ln -s /opt/IBM/netcool/platform/aix5/lib/libsybtcl_r.so # ln -s /opt/IBM/netcool/platform/aix5/lib/libsybcomn_r.so # ln -s /opt/IBM/netcool/platform/aix5/lib/libtre.a # ln -s /opt/IBM/netcool/platform/aix5/lib/libsybintl_r.so # ln -s /opt/IBM/netcool/platform/aix5/lib/libicuuc40.a # ln -s /opt/IBM/netcool/platform/aix5/lib/libicui18n40.a # ln -s /opt/IBM/netcool/platform/aix5/lib/libicudata40.a Note: The required libraries can be seen by the following command: # dump -H $NCHOME/omnibus/platform/aix5/nco_p_ping
2b9664521f8d895f07380262c8704a7d_3
Note: If there are newer modules of the required libraries, it's better to create a symbolic link to the newer module. e.g Run # ln -s /opt/IBM/netcool/platform/aix5/lib/libicui18n40.1.a rather than, # ln -s /opt/IBM/netcool/platform/aix5/lib/libicui18n40.a But, please note that it would be better to create the symbolic links again whenever after you apply Fix pack for OMNibus core. Cross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Netcool/OMNIbus Ping AIX All Versions
41862f7c54a0fddb543dbf7be76c9a60_0
IBM SqlException with message "Caught java.io.CharConversionException." and ERRORCODE=-4220 - United States TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT) When an application uses the IBM Data Server Driver for JDBC and SQLJ (also known as the JCC driver) and is connected to a database with code set UTF-8 (code page 1208), it throws an SqlException with message including "Caught java.io.CharConversionException" and ERRORCODE=-4220 if the data in a character column that it queries contains a sequence of bytes that is not a valid UTF-8 string. SYMPTOM An exception is thrown similar to this: com.ibm.db2.jcc.am.SqlException: [jcc][t4][1065][12306][XXX.XXX.XXX] Caught java.io.CharConversionException. See attached Throwable for details. ERRORCODE=-4220, SQLSTATE=null [...] Caused by: java.nio.charset.MalformedInputException: Input length = XXX [...] Caused by: sun.io.MalformedInputException at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:XXX) [...]
41862f7c54a0fddb543dbf7be76c9a60_1
CAUSE The JCC driver throws the exception when data in a character column that it queries is not a valid string in the database code page. The invalid data could have been input to the database in the following ways: * By running an SQL statement which writes byte values to the database. For example: INSERT INTO tab1 VALUES (X'C3') * By running the IMPORT or LOAD commands for files which contain character data that is not in the code page of the client machine, so the appropriate code page conversion was not done. To make sure that the the appropriate code page conversion is done when running IMPORT or LOAD, specify the code page of the input file by including the "codepage=x" file type modifier (specifying the code page in place of x). DIAGNOSING THE PROBLEM You can use the HEX function to find out what are the byte values in a character column. For example, to find out the byte values in column COL1 in table TAB1, run: SELECT HEX(col1) FROM tab1
41862f7c54a0fddb543dbf7be76c9a60_2
RESOLVING THE PROBLEM Update the invalid data with a valid UTF-8 character string. Alternatively, for JCC driver versions that support it you can set the JCC configuration property db2.jcc.charsetDecoderEncoder=3 so that instead of throwing an exception the JCC driver returns the Unicode REPLACEMENT CHARACTER (U+FFFD) in place of a sequence of bytes that is not a valid UTF-8 string. The JCC configuration property db2.jcc.charsetDecoderEncoder is supported in versions of the JCC driver that come with DB2 LUW 9.5 Fix Pack 8 and later (APAR IC74896), DB2 LUW 9.7 Fix Pack 5 and later (APAR IC74895), and all DB2 LUW releases from DB2 10.1 onwards.
41862f7c54a0fddb543dbf7be76c9a60_3
For example, suppose you have a Java program MyApp.java that executes an SQL query of a database column that contains a sequence of bytes that is not a valid string. When you run: java MyApp it throws an exception. But when you run: java -Ddb2.jcc.charsetDecoderEncoder=3 MyApp it returns the string with any invalid sequence of bytes replaced by the Unicode REPLACEMENT CHARACTER. The Unicode REPLACEMENT CHARACTER often appears like this (a diamond with a question mark inside it) : [/support/docview.wss?uid=swg21684365&amp;aid=1]
41862f7c54a0fddb543dbf7be76c9a60_4
RELATED INFORMATION APAR IC78495 [https://www-01.ibm.com/support/entdocview.wss?uid=swg1IC74895] APAR IC74896 [https://www-01.ibm.com/support/entdocview.wss?uid=swg1IC74896] Making the setting for IBM Data Studio [http://www.ibm.com/support/docview.wss?uid=swg21612346] Making the setting for IBM Content Collector [http://www-01.ibm.com/support/knowledgecenter/SSAE9L_4.0.0/com.ibm.content.collector.doc_kc/troubleshooting/ts_afu_java_throws_exception.dita] UDF to identify invalid data in a UTF-8 character colum [http://www.ibm.com/support/docview.wss?uid=swg21608985] How invalid data can get into a UTF-8 character column [http://www.ibm.com/support/docview.wss?uid=swg21412846] LOAD command [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0008305.html] IMPORT command [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0008304.html]
41862f7c54a0fddb543dbf7be76c9a60_5
HEX function [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.sql.ref.doc/doc/r0000811.html]
31d648dff0b4842142616488256a4100_0
IBM Missing Icon pulldown options in DASH main menu after 3.1.2.1 Install - United States DASHL2; Console Settings; missing.; icons; WAS 8.5.5.9; DASH 3.1.2.1; Cumulative patch 5; CP5 TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT) After fresh install of WAS 8.5.5.9 with JazzSM 1.1.2.1/DASH 3.1.2.1, the "Console Settings" is missing entries and other expected icons are missing from the DASH main page. SYMPTOM After successful installation of JazzSM 1.1.2.1/DASH 3.1.2.1 with WebSphere 8.5.5.9, some of the icons in the main DASH window are missing on the left. CAUSE It was recently discovered that some .jar files were not included in WebSphere 8.5.5.9, that were available in previous WebSphere releases, and are required for several functions in DASH. ENVIRONMENT JazzSM 1.1.2.1 / DASH 3.1.2.1 WAS 8.5.5.9 DIAGNOSING THE PROBLEM After you login to DASH and select "Console Settings", the displayed window, which should have several lines, is blank:
31d648dff0b4842142616488256a4100_1
[/support/docview.wss?uid=swg21981870&amp;aid=1] Also, in this case there wasn't any icons in the upper left portion of the main DASH window. RESOLVING THE PROBLEM The missing jar files are included in DASH 3.1.2.1 Cumulative Patch 5, which you can download from this site: http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli∏uct=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=all [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=all] [/support/docview.wss?uid=swg21981870&aid=2] [/support/docview.wss?uid=swg21981870&aid=2] If you have any questions as to whether DASH 3.1.2.1 Cumulative Patch 5 has been installed, please run this command: <JazzSM_HOME>/ui/bin/consolecli Version if patch 5 has been installed, it will have output showing the patch number shown in the red square in the screen shot:
31d648dff0b4842142616488256a4100_2
[/support/docview.wss?uid=swg21981870&aid=3] [/support/docview.wss?uid=swg21981870&aid=3] If installing on a UNIX server, you will see several of these messages, they indicate that the jar files are not currently on the server, but the Patch install will finish successfully. cp: /opt/IBM/JazzSM/ui/../profile/installedApps/JazzSMNode01Cell//isc.ear/TI PChangePasswd.war/js/ibm/tivoli/tip/changepasswd/nls/iw/messages.js: No such file or directory . . Patch 201603301212 successfully installed.
aa44f0e81b37ca7d206eb97838ec461a_0
IBM Leap Second bug in older Linux kernels may affect IBM MQ and WebSphere MQ - United States FLASH (ALERT) ABSTRACT Leap seconds are a periodic one-second adjustment of Coordinated Universal Time (UTC) required to keep a system's time of day close to the mean solar time. A leap second is scheduled for 31 December 2016 at 23h 59m 60s UTC. In the past, the addition of leap seconds caused some systems running older Linux kernels to fail. IBM MQ and WebSphere MQ queue managers running on these systems generated repeated FDC files showing Probe Id XY348010 or XC272003 from xcsCreateThread, with error code xecP_E_NO_RESOURCE. Other FDCs are also possible.
aa44f0e81b37ca7d206eb97838ec461a_1
CONTENT On 31 December 2016, the Network Time Protocol (NTP) daemon will schedule a leap second [http://en.wikipedia.org/wiki/Leap_second] to occur at midnight, making the final minute of the day 61 seconds long. Prior leap second insertions, including the 30 June 2016 leap second, caused some Linux systems to exhibit unexplained high CPU usage. IBM MQ and WebSphere MQ use the Native POSIX Thread Library (NPTL) which relies on futuxes ("fast userspace mutexes") for synchronization between threads. Futexes can exhibit high CPU spins after leap seconds on Linux kernel versions 2.6.22 through 3.5-rc7, inclusive, although some Linux distributions shipped patches for kernels in this range: * * Leap Second to be added on December 31st 2016 * * * * General information on Leap Second 2016 * * Fixes and workarounds to avoid issues caused by Leap Second 2015 * * * * Addition of leap second causes spuriously high CPU usage and futex lockups
aa44f0e81b37ca7d206eb97838ec461a_2
Contact your Linux vendor to check the status of other distributions, or check the Linux kernel version using "uname -r" and confirm that your system is older than 2.6.22 or running 3.5 or later. If you encounter this problem, the following workaround may resolve the high CPU usage. As root, run: * date -s "$(LC_ALL=C date)" PRODUCT ALIAS/SYNONYM IBM MQ WMQ WebSphere MQ MQSeries
4c5774389a7413aca3c48842e5f326d8_0
IBM DB2 UDB Version 8, v10.5 compliance with FIPS 140-2 standard - United States TECHNOTE (FAQ) QUESTION Is DB2 v8, v10.5 compliant to FIPS 140-2 ?. ANSWER Is DB2 v10.5 compliant with FIPS 140-2? Q: Is DB2 vulnerable to the problem described below? V-58165 DBMS main in the middle attack [https://www.stigviewer.com/stig/database_security_requirements_guide/2015-06-23/finding/V-58165] "One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known. The preferred technique for thwarting guesses at Session IDs is the generation of unique session identifiers using a FIPS 140-2 approved random number generator. However, it is recognized that available DBMS products do not all implement the preferred technique yet may have other protections against session hijacking. Therefore, other techniques are acceptable, provided they are demonstrated to be effective. "
4c5774389a7413aca3c48842e5f326d8_1
A: No because DB2 does not use session ids for authentication and thus not vulnerable to the attack described above. DB2 uses encryption modules which are FIPS 140-2 certified. DB2 v8.x compliancy to FIPS 140-2 DB2 v8.x went out of support in April 2009. What is ICC? ICC (IBM Crypto for C) is a set of libraries from Tivoli® for performing encryption. As of DB2® Universal Database™ (DB2 UDB) Version 8 fixpak 7 (equivalent to DB2 UDB Version 8.2), DB2 is using ICC on most platforms. Customers who need to operate in an environment that is compliant with FIPS 140-2 federal standard should take into account the releases of ICC that are shipped by DB2 on different platforms and the compliance status of those releases with FIPS 140.2. Following is a list of platforms on which DB2 is using ICC for encryption of data flowing between clients and servers:
4c5774389a7413aca3c48842e5f326d8_2
DB2 V8 Fixpak 7 through DB2 Fixpak 11: ICC Version 1.2.2 on platforms: AIX 32 bit HP-UX PA-RISC 32 bit ICC Version 1.2.1 on platforms: AIX 64 bit HP-UX PA-RISC 64 bit HP-UX IA64 Linux x86, Linux x86-64, Linux IA64 Linux for zSeries Linux for POWER Windows x86 and IA64 Solaris SPARC 64 bit ICC Version 1.3.9 on platforms: Solaris x86-64 (DB2 V8.2 GA) DB2 V8 Fixpak 12 and later: ICC Version 1.4.1 on platforms AIX HP-UX PA-RISC Linux x86 and x86-64 Linux for zSeries Linux for POWER Windows x86 and x86-64 Solaris SPARC ICC Version 1.3.9 on platforms HP-UX IA64 Linux IA64 Windows IA64 Summary of known problems encountered in ICC 1.2.1/1.2.2: There are a number of issues with DB2 and the ICC encryption libraries at levels prior to 1.3.9. The known problems are:
4c5774389a7413aca3c48842e5f326d8_3
1. Severe performance problems where processes seem to hang, or take several minutes to run. 2. A bug in ICC code causes it to communicate with the OpenSSL EGD (Entropy Gathering Daemon) which under certain circumstances could hang 3. ICC symbols have not been namespaced and DB2 can end up with symbol collisions with OpenSSL code. This can also happen when multiple versions of ICC are used within the same process. DB2 Version 8 Fixpak 12 and later incorporates IBM Crypto for C (ICC) version 1.3.9 or 1.4.1 cryptographic module which fixes these problems. Note: The latest status of ICC conformance with FIPS 140-2 standard can be obtained by referring to http://www.ibm.com/security/standards/st_evaluations.shtml [http://www.ibm.com/security/standards/st_evaluations.shtml] RELATED INFORMATION FIPS PUB 140-2 [http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf]
26b405692546ec7b1444f54cb4e27c65_0
IBM JRules or ODM module fails to access database with StaleConnectionException - United States TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT) JRules and ODM modules such as Rule Execution Server (RES) and Rule Team Server (RTS) / Decision Center (DC) may fail to access their data source with the following type of exception present in the log: com.ibm.websphere.ce.cm.StaleConnectionException: Io exception: Connection timed out SYMPTOM The problem may occur when a JRules or ODM module accesses its data source after a period of database access inactivity. For example:
26b405692546ec7b1444f54cb4e27c65_1
* The first user accessing a RTS / DC server that remained idle overnight experiences a failure upon logging and the server log shows an com.ibm.websphere.ce.cm.StaleConnectionException occurred at that time. * After a RES server has been processing execution requests normally for some time, an attempt to deploy a ruleset update fails and the server log shows an com.ibm.websphere.ce.cm.StaleConnectionException occurred upon an attempt to invalidate a ruleset or to retrieve its definition.
26b405692546ec7b1444f54cb4e27c65_2
CAUSE The underlying network connection for a data source is no longer valid although the data source itself remains considered active from the WebSphere Application Server data source connection pool management perspective. An attempt by a JRules module to try and access its data base through one such data source connection provided by the Application Server may then fail. The network connection of a data source may become invalid for a number of reasons, one typical example is that a firewall between the Application Server and the Database has a policy to discard network connections that remain idle for some time. ENVIRONMENT The exception com.ibm.websphere.ce.cm.StaleConnectionException is specific to WebSphere Application Server environments. But a similar issue can be experienced with Weblogic, see: Rule Execution Server on WebLogic unable to load ruleset after period of inactivity [http://www-01.ibm.com/support/docview.wss?uid=swg21615801]
26b405692546ec7b1444f54cb4e27c65_3
RESOLVING THE PROBLEM Configure the WebSphere Application Server data source connection pool [http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/udat_conpoolset.html] so as to eliminate occurrences of StaleConnectionException : * Set the Minimum connections to 0 to avoid situations where a connection is kept in the pool to meet the minimum requirement, even though it may have been idle for longer than Unused timeout * Set the values for Unused timeout and Reap timeout so that the sum does not exceed any network level idle connection timeout