chunk_id
stringlengths 34
35
| chunk
stringlengths 1
1k
|
|---|---|
0e96f41edaee104d36883d6f133b9af3_9 | CAUSE
Installation Manager is an Eclipse Rich Client Program application based on the open source project found at http://www.eclipse.org [http://www.eclipse.org]. Eclipse changed the window system requirement from motif to gtk on UNIX operating systems. For AIX, this Eclipse window system change requires the gtk libraries to be installed to support the GUI. For Installation Manager, the GUI is the wizard mode of operation.
You can use Installation Manager without the gtk libraries. For information on console mode, command-line mode, or silent mode; see the Installation Manager Information Center [http://pic.dhe.ibm.com/infocenter/install/v1r6/topic/com.ibm.cic.agent.ui.doc/topics/c_modes.html]. Silent mode uses a response file and command-line mode is supported by all packages. For console mode, check your product documentation to verify that the product supports console mode.
RESOLVING THE PROBLEM
To use the GUI, the gtk+ RPM and dependencies must be available on AIX. |
0e96f41edaee104d36883d6f133b9af3_10 | Install this set of RPMs on AIX:
atk-1.12.3-2.aix5.2.ppc.rpm
cairo-1.8.8-1.aix5.2.ppc.rpm
expat-2.0.1-1.aix5.2.ppc.rpm
fontconfig-2.4.2-1.aix5.2.ppc.rpm
freetype2-2.3.9-1.aix5.2.ppc.rpm
gettext-0.10.40-6.aix5.1.ppc.rpm
glib2-2.12.4-2.aix5.2.ppc.rpm
gtk2-2.10.6-4.aix5.2.ppc.rpm
libjpeg-6b-6.aix5.1.ppc.rpm
libpng-1.2.32-2.aix5.2.ppc.rpm
libtiff-3.8.2-1.aix5.2.ppc.rpm
pango-1.14.5-4.aix5.2.ppc.rpm
pixman-0.12.0-3.aix5.2.ppc.rpm
xcursor-1.1.7-3.aix5.2.ppc.rpm
xft-2.1.6-5.aix5.1.ppc.rpm
xrender-0.9.1-3.aix5.2.ppc.rpm
zlib-1.2.3-3.aix5.1.ppc.rpm
The installed RPMs must be of the minimum versions listed above.
To install the RPM versions specified above take the following steps: |
0e96f41edaee104d36883d6f133b9af3_11 | 1. Download the gtk2_bundle_v2.tar package [ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/ezinstall/ppc/] (version 'v2') containing all the RPMs and the install script to a new directory.
2. Decompress the tar file.
You can use the command tar -xvf gtk2_bundle_<version>.tar to decompress the file.
3. Open the decompressed directory gtk2_bundle_<version> and run the install.sh script.
The script will check if the required RPMs are installed at the compatible level. If they are not, the script will prompt to install the compatible versions.
4. Verify the environment variable LIBPATH contains a path to the installed libraries.
For example LIBPATH=/opt/freeware/lib/
Note that if you download and install RPMs individually, we have found that the following libraries are incompatible: * glib2-2.14.6-2 and gtk2-2.10.6-5 |
0e96f41edaee104d36883d6f133b9af3_12 | RELATED INFORMATION
#Unreadable characters in the GUI when using X11 [http://www.ibm.com/support/docview.wss?uid=swg21661861] |
840a2353899fb3b903deca1347ec4a60_0 | IBM Security Bulletin: Multiple vulnerabilities in IBM® Java SDK affect WebSphere Application Server that ships with WebSphere Enterprise Service Bus (CVE-2015-2613, CVE-2015-2601, CVE-2015-4749, CVE-2015-2625, CVE-2015-1931) - United States SECURITY BULLETIN
SUMMARY
There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Application Server that ships with WebSphere Enterprise Service Bus.
VULNERABILITY DETAILS
CVEID:CVE-2015-2613 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2613]
DESCRIPTION:An unspecified vulnerability and Java SE Embedded related to the JCE component could allow a remote attacker to obtain sensitive information.
CVSS Base Score: 5
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104734 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104734]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N) |
840a2353899fb3b903deca1347ec4a60_1 | CVEID:CVE-2015-2601 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2601]
DESCRIPTION:An unspecified vulnerability related to the JCE component could allow a remote attacker to obtain sensitive information.
CVSS Base Score: 5
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104733 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104733]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)
CVEID:CVE-2015-4749 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4749]
DESCRIPTION:An unspecified vulnerability related to the JNDI component could allow a remote attacker to cause a denial of service.
CVSS Base Score: 4.3
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104740 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104740]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:N/I:N/A:P) |
840a2353899fb3b903deca1347ec4a60_2 | CVEID:CVE-2015-2625 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2625]
DESCRIPTION:An unspecified vulnerability related to the JSSE component could allow a remote attacker to obtain sensitive information.
CVSS Base Score: 2.6
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104743 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104743]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:H/Au:N/C:P/I:N/A:N)
CVEID:CVE-2015-1931 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1931]
DESCRIPTION:IBM Java Security Components store plain text data in memory dumps, which could allow a local attacker to obtain information to aid in further attacks against the system.
CVSS Base Score: 2.1
CVSS Temporal Score: Seehttp://xforce.iss.net/xforce/xfdb/102967 [http://xforce.iss.net/xforce/xfdb/102967]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N) |
840a2353899fb3b903deca1347ec4a60_3 | AFFECTED PRODUCTS AND VERSIONS
WebSphere Enterprise Service Bus 6.2
WebSphere Enterprise Service Bus 7.0
WebSphere Enterprise Service Bus 7.5
REMEDIATION/FIXES
Please consult the security bulletin Multiple vulnerabilities in IBM® Java SDK affect WebSphere Application Server July 2015 CPU [http://www-01.ibm.com/support/docview.wss?uid=swg21962931] for vulnerability details and information about fixes.
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] CHANGE HISTORY
4th September 2015: Original version published |
840a2353899fb3b903deca1347ec4a60_4 | *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. |
ad9506ea2130d9444cfcbd4494490546_0 | IBM Getting java.io.NotSerializableException when SessionObjectSize counter is enabled - United States java.io.NotSerializableException SessionObjectSize counter PMI enabled disable serializable TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
When PMI (Performance Monitoring Infrastructure) is enabled with SessionObjectSize counter enabled, getting NotSerializableException. The SystemOut.log shows something similar to: |
ad9506ea2130d9444cfcbd4494490546_1 | [4/10/07 5:25:42:618 EDT] 00000091 SessionContex E Exception is: java.io.NotSerializableException: com.com1.dept.nls.model.someModel
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java(Compiled Code))
...
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java(CompiledCode))
at com.ibm.ws.webcontainer.httpsession.SessionContextMBeanAdapter.getSessionsInfo(SessionContextMBeanAdapter.java(Compiled Code))
at com.ibm.ws.webcontainer.httpsession.SessionTrackingPMIApplicationData$1.getRuntimeInfo(SessionTrackingPMIApplicationData.java(Inlined Compiled Code)) ...
at com.ibm.ws.pmi.server.modules.ServletSessionsModule$SessionObjSize.updateStatistic(ServletSessionsModule.java(Compiled Code))
at com.ibm.ws.pmi.server.data.SpdStatExternal.updateExternal(SpdStatExternal.java(Compiled Code))
at com.ibm.websphere.pmi.server.PmiAbstractModule.update(PmiAbstractModule.java(Compiled Code))
... |
ad9506ea2130d9444cfcbd4494490546_2 | The error does not affect application functionality. Disabling SessionObjectSize counter makes the error stop occurring.
CAUSE
WebSphere® Application Server Session Manager throws NotSerializableException when it tries to serialize non-serializable SessionData from the application before sending it to PMI.
RESOLVING THE PROBLEM
The application needs to ensure there is no session object that is not serializable. The object needs to implement java™.io.Serializable interface.
HISTORICAL NUMBER
53925
L6Q
000 |
e64cbc81dad5b2dcf921f2feb9b57644_0 | IBM Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by Open Source Tomcat vulnerability (CVE-2016-3092) - United States WMB IIB SECURITY BULLETIN
SUMMARY
WebSphere Message Broker and IBM Integration Bus are affected by Open Source Apache Tomcat vulnerability.
VULNERABILITY DETAILS
CVEID: CVE-2016-3092 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]
DESCRIPTION: Apache Tomcat is vulnerable to a denial of service, caused by an error in the Apache Commons FileUpload component. By sending file upload requests, an attacker could exploit this vulnerability to cause the server to become unresponsive.
CVSS Base Score: 5.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/114336 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114336] 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) |
e64cbc81dad5b2dcf921f2feb9b57644_1 | AFFECTED PRODUCTS AND VERSIONS
IBM Integration Bus V10.0 & V9.0
WebSphere Message Broker V8.0
REMEDIATION/FIXES
Product VRMF APAR Remediation/Fix IBM Integration Bus V10
IT15719 An interim fix is available from IBM Fix Central for all platforms.
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719] |
e64cbc81dad5b2dcf921f2feb9b57644_2 | The APAR is targeted to be available in fix pack 10.0.0.7 IBM Integration Bus V9
IT15719 An interim fix is available from IBM Fix Central for all platforms.
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719] |
e64cbc81dad5b2dcf921f2feb9b57644_3 | The APAR is targeted to be available in fix pack 9.0.0.7 WebSphere Message Broker
V8
IT15719 An interim fix is available from IBM Fix Central for all platforms.
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibms~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibms~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15719]
The APAR is targeted to be available in fix pack 8.0.0.8
For unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product.
The planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :
http://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]
WORKAROUNDS AND MITIGATIONS
None known |
e64cbc81dad5b2dcf921f2feb9b57644_4 | 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. |
e64cbc81dad5b2dcf921f2feb9b57644_5 | 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] ACKNOWLEDGEMENT
None
CHANGE HISTORY
27 Oct 2016 - 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. |
e64cbc81dad5b2dcf921f2feb9b57644_6 | 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 Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0
PRODUCT ALIAS/SYNONYM
WMB IIB |
eda478021689dcb57b0061bcce259a33_0 | IBM Too Many Open Files error message - United States wasrun; wasjdk; open; files; too; ProblemDeterminationDocument; JCC was appserver app server TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
This technote explains how to debug the "Too many open files" error message on Microsoft Windows, AIX, Linux and Solaris operating systems.
SYMPTOM
The following messages could be displayed when the process has exhausted the file handle limit:
java.io.IOException: Too many open files
[3/14/15 9:26:53:589 EDT] 14142136 prefs W Could not lock User prefs. Unix error code 24.
New sockets/file descriptors can not be opened after the limit has been reached.
CAUSE
System configuration limitation. |
eda478021689dcb57b0061bcce259a33_1 | When the "Too Many Open Files" error message is written to the logs, it indicates that all available file handles for the process have been used (this includes sockets as well). In a majority of cases, this is the result of file handles being leaked by some part of the application. This technote explains how to collect output that identifies what file handles are in use at the time of the error condition.
RESOLVING THE PROBLEM
Determine Ulimits
On UNIX and Linux operating systems, the ulimit for the number of file handles can be configured, and it is usually set too low by default. Increasing this ulimit to 8000 is usually sufficient for normal runtime, but this depends on your applications and your file/socket usage. Additionally, file descriptor leaks can still occur even with a high value.
Display the current soft limit:
ulimit -Sn
Display the current hard limit:
ulimit -Hn
Or capture a Javacore, the limit will be listed in that file under the name NOFILE:
kill -3 PID |
eda478021689dcb57b0061bcce259a33_2 | Please see the following document if you would like more information on where you can edit ulimits:
Guidelines for setting ulimits (WebSphere Application Server)
http://www.IBM.com/support/docview.wss?rs=180&uid=swg21469413 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21469413]
Operating Systems
Windows By default, Windows does not ship with a tool to debug this type of problem. Instead Microsoft provides a tool that you can download called Process Explorer [http://technet.microsoft.com/en-us/sysinternals/bb896653]. This tool identifies the open handles/files associated with the Java™ process (but usually not sockets opened by the Winsock component) and determines which handles are still opened. These handles result in the "Too many open files" error message. |
eda478021689dcb57b0061bcce259a33_3 | To display the handles, click on the Gear Icon [/support/docview.wss?uid=swg21067352&aid=1] in the toolbar (or press CTRL+ H to toggle the handles view). The icon will change to the icon for DLL files (so you can toggle it back to the DLL view).
It is important that you change the Refresh Rate. Select View > Update Speed, and change it to 5 seconds.
[/support/docview.wss?uid=swg21067352&aid=2] [/support/docview.wss?uid=swg21067352&aid=2]
There is also another Microsoft utility called Handle that you can download from the following URL:
https://technet.microsoft.com/en-us/sysinternals/bb896655.aspx [https://technet.microsoft.com/en-us/sysinternals/bb896655.aspx]
This tool is a command line version of Process Explorer. The URL above contains the usage instructions.
AIX
The commands lsof and procfiles are usually the best commands to determine what files and sockets are opened.. |
eda478021689dcb57b0061bcce259a33_4 | lsof
To determine if the number of open files is growing over a period of time, issue lsof to report the open files against a PID on a periodic basis. For example:
lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out
This output does not give the actual file names to which the handles are open. It provides only the name of the file system (directory) in which they are contained. The lsof command indicates if the open file is associated with an open socket or a file. When it references a file, it identifies the file system and the inode, not the file name.
It is best to capture lsof several times to see the rate of growth in the file descriptors.
procfiles
The procfiles command does provide similar information, and also displays the full filenames loaded. It may not show sockets in use.
procfiles -n [PID] > procfiles.out
Other commands (to display filenames that are opened) |
eda478021689dcb57b0061bcce259a33_5 | INODES and DF
df -kP filesystem_from_lsof | awk '{print $6}' | tail -1
>> Note the filesystem name
find filesystem_name -inum inode_from_lsof -print > filelist.out
>> Shows the actual file name
svmon
svmon -P PID -m | grep pers (for JFS)
svmon -P PID -m | grep clnt (for JFS2, NFS)
(this opens files in the format: filesystem_device:inode)
Use the same procedure as above for finding the actual file name.
Linux To determine if the number of open files is growing over a period of time, issue lsof to report the open files against a PID on a periodic basis. For example:
lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out
The output will provide you with all of the open files for the specified PID. You will be able to determine which files are opened and which files are growing over time.
It is best to capture lsof several times to see the rate of growth in the file descriptors. |
eda478021689dcb57b0061bcce259a33_6 | Alternately you can list the contents of the file descriptors as a list of symbolic links in the following directory, where you replace PID with the process ID. This is especially useful if you don't have access to the lsof command:
ls -al /proc/PID/fd
Solaris Run the following commands to monitor open file (socket) descriptors on Solaris:
pfiles
/usr/proc/bin/pfiles [ PID ] > pfiles.out
lsof
lsof -p [ PID ] > lsof.ou t
This will get one round of lsof output. If you want to determine if the number of open files is growing over time, you can issue the command with the -r option to capture multiple intervals:
lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out
It is best to capture lsof several times to see the rate of growth in the file descriptors.
HP-UX
lsof
lsof -p [ PID ] > lsof.out |
eda478021689dcb57b0061bcce259a33_7 | This will get one round of lsof output. If you want to determine if the number of open files is growing over time, you can issue the command with the -r option to capture multiple intervals:
lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out
It is best to capture lsof several times to see the rate of growth in the file descriptors.
Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK |
081e575f4942e2d7f840acc432eef531_0 | IBM Important Information about the WebSphere MQ Configuration Agent, Withdrawn from IBM OMEGAMON for Messaging on z/OS V7.5 - United States PRODUCT DOCUMENTATION
ABSTRACT
Starting with V7.5, IBM OMEGAMON for Messaging on z/OS no longer delivers the component called WebSphere MQ Configuration Agent, referred to as MQ Configuration in the rest of this document, because there are other recommended ways to configure IBM MQ. It is stabilized in the previous V7.3 release, but MQ Configuration will be supported as long as V7.3 is in support. The components in V7.5 are the IBM MQ Monitoring Agent and the IBM Integration Bus Monitoring Agent, both of which have enhancements in V7.5 that address monitoring requirements you may have. You can upgrade your OMEGAMON for Messaging monitoring components to V7.5 while using the previous release of MQ Configuration. |
081e575f4942e2d7f840acc432eef531_1 | Whether or not you want to continue using MQ Configuration when you install and configure OMEGAMON for Messaging V7.5, there may be steps you need to take, so please review this document prior to installing and configuring V7.5.
CONTENT
First, please determine whether you have previously installed and configured the MQ Configuration component. If you have not done so previously, there is no need for you to consider the rest of this document. For this determination, please examine the following: |
081e575f4942e2d7f840acc432eef531_2 | · SMP/E: Are the FMIDs for MQ Configuration installed? The FMIDs are HKMC730 and HKCF730, or HKMC710 and HKCF710 if you are using the V7.1 level.
· PARMGEN: In your PARMGEN configuration for each runtime environment, does the “Include Products in this PARMGEN RTE panel (KCIP@PGI)” (under step “1 KCIJPCFG Set-up/Refresh PARMGEN work environment” navigation from the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU), have the line for “KMC OMEGAMON for Messaging – WebSphere MQ Configuration” selected for configuration in the environment?
If the answers are “yes” to both of the above questions, then you do need to continue with the following general steps, which are documented in detail below: |
081e575f4942e2d7f840acc432eef531_3 | 1) Determine whether there are any users of MQ Configuration in your environment. There are many cases in which the MQ Configuration component is installed and configured in PARMGEN, but no one is actually using it. It is important to determine this in order to decide which step to take next.
2) If you do not have users of MQ Configuration, or you want to remove it anyway, there may be steps required when you are installing and configuring OMEGAMON for Messaging V7.5 especially if you previously configured a shared agent address space for MQ monitoring (KMQ) and MQ configuration (KMC) agents.
3) If you do have users of MQ Configuration and want to continue supporting that usage, you need to follow recommendations when you are installing and configuring OMEGAMON for Messaging V7.5 upgraded products.
Here are the details:
1) Suggested ways to determine whether there are any users of MQ Configuration: |
081e575f4942e2d7f840acc432eef531_4 | a. In the Tivoli Enterprise Portal (TEP), using an administrator user ID, click Edit->Administer Users to check whether any users or groups have access to the Configuration navigator view. For users and/or groups that have been configured for TEP, check the Navigator Views tab to see if any of them have “Configuration” in their Assigned Views. If no one is allowed access to the Configuration navigator, then they are not using MQ Configuration feature.
b. Another item to check in Administer Users is whether any user or group has the Permissions tab showing that View or Modify permission has been authorized for WebSphere MQ Configuration Authorities “Configure” authority. Some user or group should have permission to use this feature if it is used by anyone. |
081e575f4942e2d7f840acc432eef531_5 | c. Check whether there are configured names that reflect queue managers in your environment. Click on the Configuration navigator in the view drop-down list in the Navigator pane, then click on Defined View on the left. In the middle Defined Tree pane on the workspace, expand the various “+” items, and with the help of someone who knows MQ queue managers in your environment, see if any of the expanded items reflect queue managers actually in your environment. There will be default and example items shipped with the product, but you are looking for names reflecting MQ at your site. If there are no names that reflect queue managers in your environment, then no one is using MQ Configuration. |
081e575f4942e2d7f840acc432eef531_6 | d. If it appears that there is usage of MQ Configuration, it would still be good to check with MQ users at your site to see if they actually require it. Perhaps they have experimented with it but do not actually use it regularly. If the OMEGAMON feature for MQ Configuration is not absolutely required in your environment, the recommendation would be to review all the ways that the IBM MQ product offers to configure and administer MQ, some of which are new in recent releases. Also, remember that the OMEGAMON MQ Monitoring agent offers the Take Action facility to issue any MQSC configuration command if the user is authorized.
2) If there are no users of MQ Configuration, or you want to remove it anyway: |
081e575f4942e2d7f840acc432eef531_7 | a. If you use a Serverpac that contains the upgraded OMEGAMON for Messaging V7.5 components to install, the MQ Configuration FMIDs (HKMC730 and HKCF730) are not installed because they are not included in the Serverpac. However, depending on your previous configuration, the missing MQ Configuration component could cause unexpected results in your LPAR runtime environment (RTE), so check and act on the following items prior to installation and configuration of OMEGAMON for Messaging V7.5:
1. If your Hub TEMS is configured on the z/OS platform and there are RKCF* DDNAME statements in your existing Hub TEMS started task JCL, update the TEMS started task JCL to remove those RKCF* DDNAME statements. |
081e575f4942e2d7f840acc432eef531_8 | 2. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, make sure that the owner of that address space is the MQ Monitoring agent. For the MQ Monitoring agent to be the owner, the related PARMGEN LPAR RTE profile parameters for OMEGAMON for Messaging components may need adjusting, as depicted in the following example before and after settings:
Before (MQ Configuration owns the Agent address space called OMEGMQ):
ISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%)
Command ===>
KMC_AGT_STC OMEGMQ
KMC_AGT_STC_OWNER “”
KMQ_AGT_STC “”
KMQ_AGT_STC_OWNER OMEGMQ
After (MQ Monitoring owns the Agent address space called OMEGMQ):
ISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%)
Command ===>
KMQ_AGT_STC OMEGMQ
KMQ_AGT_STC_OWNER “” |
081e575f4942e2d7f840acc432eef531_9 | Tip: Please review the SMPE06 upgrade scenario [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe06_parmgenref.htm?pos=2] in the OMEGAMON Shared Knowledge Center as part of deploying these changes. You can use the refreshed OMEGMQ OMEGAMON for Messaging – KMQ Agent-only address space in the RTE’s W/RKANSAMU dataset for refreshing the original shared address space in your system procedure library. The only delta would be the RKMCAPLA DDNAME, which can be staged for removal.
b. If you install OMEGAMON for Messaging V7.5 as a CBPDO into an existing SMP/E CSI, the MQ Configuration FMIDs will remain installed, but since you are not using MQ Configuration, it is recommended you follow these steps:
1. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, make sure that the owner of that address space is the MQ Monitoring agent. See item a.2 above for more details. |
081e575f4942e2d7f840acc432eef531_10 | 2. In the “Include Products in this PARMGEN RTE panel (KCIP@PGI)” (under step “1 KCIJPCFG Set-up/Refresh PARMGEN work environment” navigation from the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU), deselect the line with “KMC OMEGAMON for Messaging – WebSphere MQ Configuration” so that it will be removed from the runtime environment (RTE) during reconfiguration/upgrade of the RTE. Follow one of the SMPEnn upgrade scenarios [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe04_parmgenref.htm?pos=2] documented in the OMEGAMON Shared Knowledge Center. |
081e575f4942e2d7f840acc432eef531_11 | Tip: Prior to upgrading the RTE, you also have the option to SMP/E delete the HKMC730 and HKCF730 FMIDs from the existing CSI. When you start the PARMGEN configuration phase of the upgrade, the inexistence of these deleted FMIDs is PARMGEN’s trigger to delete the product from the RTE upon reconfiguration following any of the SMPEnn upgrade scenarios (SMPE04 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe04_parmgenref.htm?pos=2], SMPE05 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe05_parmgenref.htm?pos=2] or SMPE06 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe06_parmgenref.htm?pos=2]).
3) If there are users of MQ Configuration, and you want to continue supporting that usage: |
081e575f4942e2d7f840acc432eef531_12 | a. It is highly recommended that you install OMEGAMON for Messaging V7.5 as a CBPDO into the existing SMP/E CSI so that MQ Configuration remains available. If you do this, there are no other steps required, however, the following step is also highly recommended:
1. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, separate them into their own address spaces, since they will be running at different product levels. For this, the related PARMGEN LPAR RTE profile parameters for OMEGAMON for Messaging components may need adjusting to be like the following example in which MQ Configuration is running in an address space called OMEGMC and MQ Monitoring is running in an address space called OMEGMQ:
ISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%)
Command ===>
KMC_AGT_STC OMEGMC
KMC_AGT_STC_OWNER “”
KMQ_AGT_STC OMEGMQ
KMQ_AGT_STC_OWNER “” |
081e575f4942e2d7f840acc432eef531_13 | b. If you were to install OMEGAMON for Messaging V7.5 in a Serverpac, you would need to retain your old SMP/E CSI and maintain a separate PARMGEN runtime environment in order to use MQ Configuration separately. This may be acceptable to you if you already separate MQ Configuration from the rest of your monitoring infrastructure, with its own Hub TEMS, etc. In this case, for the configuration that will contain OMEGAMON for Messaging V7.5, please see item 2 above, steps a.1 and a.2 in case they would apply to that particular configuration. |
081e575f4942e2d7f840acc432eef531_14 | c. OMEGAMON for Messaging V7.5 application support does not include application support for the MQ Configuration component. If you need to re-install application support for MQ Configuration for any reason, you should use the latest V7.3 level of application support. For z/OS customers, that is available with DVD LCD7-3513-08 at the following link: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]
For more information about OMEGAMON for Messaging V7.5, please see this link to the product documentation:
https://www.ibm.com/support/knowledgecenter/SSRLD6_7.5.0/welcome_omxe_msg750.html [https://www.ibm.com/support/knowledgecenter/SSRLD6_7.5.0/welcome_omxe_msg750.html] |
081e575f4942e2d7f840acc432eef531_15 | For more information about OMEGAMON installation and configuration with PARMGEN, please see this link to the shared documentation:
https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/shared_welcome/welcome.htm?pos=2 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/shared_welcome/welcome.htm?pos=2] |
081e575f4942e2d7f840acc432eef531_16 | For more information about recommended ways to configure IBM MQ, please see the following links:
Administering IBM MQ [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.adm.doc/q019950_.htm]
Configuring queue managers on z/OS [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q019070_.htm]
Using IBM z/OSMF to automate IBM MQ [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q019925_.htm]
Support continuous configuration deployments for IBM MQ with UrbanCode [https://www.ibm.com/developerworks/library/d-continuous-configuration-deployments-urbancode-mq-trs/index.html]
ORIGINAL PUBLICATION DATE
2017/10/26 |
261225347d9d5fabe42722ea81ecfa37_0 | IBM Security Bulletin: IBM WebSphere MQ MQXR insecure passwords (CVE-2015-2012) - United States SECURITY BULLETIN
SUMMARY
The Telemetry (MQXR) service can be configured to use SSL/TLS connections - the passphrase used to access the keystore is written to the file system in clear text in a properties file that is world readable.
VULNERABILITY DETAILS
CVEID: CVE-2015-2012 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2012]
DESCRIPTION: IBM WebSphere MQ stores the MQXR keystore password in clear text in a world readable file.
CVSS Base Score: 2.1
CVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/103923 [http://xforce.iss.net/xforce/xfdb/103923] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N)
AFFECTED PRODUCTS AND VERSIONS
IBM WebSphere MQ 8.0
* 8.0.0.3 and earlier maintenance levels
IBM WebSphere MQ 7.5 * 7.5.0.5 and earlier maintenance levels |
261225347d9d5fabe42722ea81ecfa37_1 | IBM WebSphere MQ 7.1 * 7.1.0.6 and earlier maintenance levels
REMEDIATION/FIXES
IBM WebSphere MQ 8.0
Install fixpack 8.0.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg21969244]
IBM WebSphere MQ 7.5 * Apply Interim fix IT09866 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.5.0.5&platform=All&function=aparId&apars=IT09866]
IBM WebSphere MQ 7.1 * Install fixpack 7.1.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg21965293]
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. |
261225347d9d5fabe42722ea81ecfa37_2 | 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
01 February 2016: Original Copy 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. |
261225347d9d5fabe42722ea81ecfa37_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.
RELATED INFORMATION
A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21977183] |
d21abd3a949c6ad77a40e84f43893c8a_0 | IBM HTTP Session time-out settings and overwrite precedence rules - United States WebSphere http session management time-out wasrun precedence overwrite TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
It is possible to set the HTTP Session time-out in various places on the IBM® WebSphere® Application Server Administrative Console. It is also possible to set HTTP Session time-out for the application packaging process.
Since Session time-out can be set in multiple places, it is necessary to understand how the ultimate Session time-out for an application is determined.
CAUSE
Application needs HTTP session time-out set.
RESOLVING THE PROBLEM
The HTTP Session time-out can be set in the following places:
* From the Administrative Console at the server, Enterprise application, and Web application levels
* At the time when the application is packaged
* In the application code |
d21abd3a949c6ad77a40e84f43893c8a_1 | Setting the HTTP Session time-out from the Administrative Console
1. To set the HTTP Session time-out at the server level, navigate to Servers > Application Servers > Your Server > Web Container > Session Management.
In the Session time-out section of this window, you can select No time-out or Set time-out by clicking the appropriate radio button. If you choose to set the time-out, type the desired value in minutes in the box.
2. To set the HTTP Session time-out at the Enterprise Application level, navigate to Applications > Enterprise Applications > Your Application > Session Management.
Check Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the application session to overwrite those values set at the parent, which in this case is the Server level. |
d21abd3a949c6ad77a40e84f43893c8a_2 | 3. To set the HTTP Session time-out at the Web Application level, navigate to Applications > Enterprise Applications > Your Application > Web Module > Your Web App.war > Session Management.
Check Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the Application Session to overwrite those values set at the parent levels, which in this case is the Server or Enterprise Application level.
After modifying these settings, save the master configuration.
Setting HTTP Session time-out when application is packaged
The application developer can also select to set the HTTP Session time-out parameter when the application is packaged. This value is stored in the web.xml file for the Web application. |
d21abd3a949c6ad77a40e84f43893c8a_3 | This setting overrides any session time-outs defined from the Administrative Console. Alter this setting by repackaging the application with a new value, or by modifying the web.xml file. The entry in the web.xml will be as follows:
<session-config>
* <session-timeout>60</session-timeout>
*
* </session-config>
Where the "session-timeout" is an integer value for the desired session time-out in minutes.
Setting HTTP Session time-out from the application code
Finally, the HTTP Session time-out can be set in the application code. The programmer can invoke the setMaxInactiveInterval() method on HttpSession object to set the time-out value as desired. This setting overrides any time-out defined in the application package or made from the Administrative Console.
HTTP Session time-out Override Precedence Summary
The list below shows the precedence from which the final HTTP Session time-out is derived. |
d21abd3a949c6ad77a40e84f43893c8a_4 | 1. Server Level [/support/docview.wss?uid=swg21163875&aid=1] Lowest level 2. Enterprise Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server Level if Override is selected 3. Web Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server and Enterprise Application settings if Override is selected 4. Application Level (web.xml) [/support/docview.wss?uid=swg21163875&aid=1] Overrides Server, Enterprise Application, and Web Application settings 5. Application Code [/support/docview.wss?uid=swg21163875&aid=1] Overrides all other settings RELATED INFORMATION
A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21659740]
Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK |
f267c0f24ce97b839d4bf0584852a259_0 | IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) - United States SECURITY BULLETIN
SUMMARY
The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects IBM WebSphere MQ Internet Pass-thru (MQIPT). |
f267c0f24ce97b839d4bf0584852a259_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) |
f267c0f24ce97b839d4bf0584852a259_2 | AFFECTED PRODUCTS AND VERSIONS
The affected ciphersuite is available in all versions of IBM WebSphere MQ Internet Pass-thru (MQIPT) prior to 2.1.0.2
REMEDIATION/FIXES
SupportPac MS81: IBM WebSphere MQ Internet Pass-Thru
Users of IBM WebSphere MQ Internet Pass-Thru 2.1.0.1, 2.0 and older releases should first upgrade to IBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386].
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. |
f267c0f24ce97b839d4bf0584852a259_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
Reported to IBM by the WeakDH team at https://weakdh.org [https://weakdh.org]
CHANGE HISTORY
11th June 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. |
f267c0f24ce97b839d4bf0584852a259_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.
RELATED INFORMATION
A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21962347] |
8bea2655494f9f635e443d64d82d40b4_0 | IBM How to find details of Corrupted Object from the entries in db2diag.log? - United States TECHNOTE (FAQ)
QUESTION
How to find details of Corrupted Object from the entries in db2diag.log?
ANSWER
When we have corruption in the database we may received following kind of entries in db2diag.log
These also notify object where we t where we have detected corruption in the Database.
Sample db2diag.log entry for Corruption.
2016-05-04-03.13.05.261082-360 I3442A358 LEVEL: Error
PID : 393470 TID : 1 PROC : db2pfchr 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbReadAndReleaseBuffers,probe:13
RETCODE : ZRC=0x86020001=-2046689279=SQLB_BADP "page is bad"
DIA8400C A bad page was encountered. |
8bea2655494f9f635e443d64d82d40b4_1 | 2016-05-04-03.13.05.264301-360 I3801A437 LEVEL: Error
PID : 393470 TID : 1 PROC : db2pfchr 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbReadAndReleaseBuffers,
probe:13
DATA #1 : String, 158 bytes
Obj={pool:3;obj:21;type:0} State=x27 Parent={3;21}, EM=1120, PP0=1152
Page=51235 Cont=17 Offset=2848 BlkSize=15
sqlbReadAndReleaseBuffers error: num-pages=16
Based on this information dumped in db2diag.log entry we can Identify {pool:3;obj:21;type:0} is the Object is corrupted.
e.g. Obj={pool:3;obj:21;type:0}
Pool = Tablespace ID
Obj = Object ID
Type = Type of the Object
If Type is 0 its Table Object ,If its 1 then its Index.
We can find the Name of the Object using following query, to further backup the Definition for future reference.
db2 "select char(tabname,20), char(tabschema,20) from syscat.tables where tableid=<ObjectID> and tbspaceid=<Tablepace id>" |
8bea2655494f9f635e443d64d82d40b4_2 | Obj={pool:3;obj:21;type:0}
db2 "select char(tabname,20), char(tabschema,20) from syscat.tables where tableid=21 and tbspaceid=3"
RELATED INFORMATION
SYSCAT.TABLES catalog view [http://www.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.sql.ref.doc/doc/r0001063.html?lang=en] |
b475dabfa94007c6b88660f9a28eeb6c_0 | IBM JMSExceptions CWSIT0006E and CWSIA0241E on bus connect - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Your application throws JMS exceptions CWSIT0006E and CWSIA0241E when trying to connect to a WebSphere Application Server (WAS) Service Integration Bus (SIBus).
SYMPTOM
Application throws the following JMS exceptions in the stack trace while trying to connect to the SIBus:
JMSException caught
javax.jms.JMSException: CWSIA0241E: An exception was received during the call to the method
JmsManagedConnectionFactoryImpl.createConnection:
com.ibm.websphere.sib.exception.SIResourceException: CWSIT0006E: It is not possible to contact
a messaging engine in bus YOURBUS..
at
com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:225)
at
com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:148) |
b475dabfa94007c6b88660f9a28eeb6c_1 | CAUSE
This can be caused by a stopped messaging engine, a wrong or misspelled bus name (case-sensitive) in the connection factory settings or, the HA manager is not able to find the running messaging engine.
RESOLVING THE PROBLEM
The error messages CWSIA0241E and CWSIT0006E indicate that when the connection was attempted, there were no running messaging engines available on the specified bus. To see why the messaging engines were not available, check the SystemOut.log for applicable messages. Examine the SystemOut.log file starting at the time period when the application experienced the problem and search backward.
Check for the CWSID0016I which indicates status of the Messaging Engine activity. You may see messages like this:
SibMessage I [:] CWSID0016I: Messaging engine [mename]is in state Stopping.
SibMessage I [:] CWSID0016I: Messaging engine [mename]is in state Stopped.
The solution for this problem is to start the messaging engine. |
b475dabfa94007c6b88660f9a28eeb6c_2 | If the messaging engine is running and you still see these errors at the application side, other possible reasons for this problem are:
1) Check provider end points. The value for the provider endpoints should be in the format of host_name:port_number:BootstrapBasicMessaging.
In the JMS connection factory, you can define a list of provider endpoints that govern which servers the application will attempt to connect to. If you have defined these endpoints, ensure that the messaging engines for these servers have all started and that the port and transport chains defined in the endpoint list are correct. Also, ensure that the values for the Connection proximity (bus, cluster, host or server) and the Target groups and Target significance settings are appropriate. For example, if the Target significance value is Required and no suitable messaging engine could be located, then this would cause a connection failure. Please refer to the following links for how to set provider endpoints: |
b475dabfa94007c6b88660f9a28eeb6c_3 | Default messaging provider queue connection factory [Settings] : [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/SIBJMSQueueConnectionFactory_DetailForm.html]
Default messaging provider topic connection factory [Settings]: [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/SIBJMSTopicConnectionFactory_DetailForm.html]
Restart the server after making the change.
2) If your environment is heavily loaded, the HA manager might not be able to locate the running messaging engine within three seconds. In this case, check if there are any hung threads in the SystemOut.log, and resolve them if possible. Next, consider increasing the value of sib.trm.linger from three to give the HA manager more time to locate a messaging engine. |
b475dabfa94007c6b88660f9a28eeb6c_4 | Tune the sib.trm.linger property value in the sib.properties file to set the messaging engine lookup delay so that the Work Load Manager (WLM) waits for a longer period of time before returning an error. Please refer to information below on how to set this property in the sib.properties.
1)<WAS_HOME>/properties : The properties declared under this location would be applicable to all the profiles in that installation.
2)<PROFILE_ROOT>/properties : The properties declared here are applicable for all the servers on this profile
If a property is defined at both <PROFILE_ROOT>/properties and <WAS_HOME>/properties, then the property defined at <PROFILE_ROOT>/properties would take precedence.
After resetting the property you must restart the server. |
b475dabfa94007c6b88660f9a28eeb6c_5 | Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ Not Applicable Business Integration WebSphere Process Server Business Integration WebSphere Service Registry and Repository Business Integration IBM Business Process Manager Standard Business Integration WebSphere Enterprise Service Bus Business Integration WebSphere Partner Gateway Advanced Edition Configuration Business Integration WebSphere MQ Configuration
PRODUCT ALIAS/SYNONYM
WebSphere Application Server WAS SIB SIBUS SI BUS |
db3761666c74ce644f1ad4fcc7fa4b05_0 | IBM Security Bulletin: IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms ( CVE-2016-0394 ) - United States WMB IIB SECURITY BULLETIN
SUMMARY
IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms, which exposes it to an unintended actor.
VULNERABILITY DETAILS
CVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]
DESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files.
CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) |
db3761666c74ce644f1ad4fcc7fa4b05_1 | AFFECTED PRODUCTS AND VERSIONS
IBM Integration Bus V9
WebSphere Message Broker V8
REMEDIATION/FIXES
Product VRMF APAR Remediation/Fix IBM Integration Bus V9 IT14845 The APAR is available in Fix Pack 9.0.0.6 https://www-304.ibm.com/support/docview.wss?uid=swg24042598 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598]
WebSphere Message Broker V8 IT14845 The APAR is available in Fix Pack 8.0.0.8
https://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925]
For unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product.
The planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :
http://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308] |
db3761666c74ce644f1ad4fcc7fa4b05_2 | WORKAROUNDS AND MITIGATIONS
To mitigate the problem with a current V8 or V9 fix pack installation on Unix platforms, you can run the following commands:
find <IIB install dir>/isadc -type d -exec chmod 755 {} \;
find <IIB install dir>/isadc -type f -exec chmod 644 {} \;
find <IIB install dir>/isadc -type f -name *.sh -print -exec chmod 755
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. |
db3761666c74ce644f1ad4fcc7fa4b05_3 | 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]
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] |
db3761666c74ce644f1ad4fcc7fa4b05_4 | CHANGE HISTORY
28-Nov-2016 - Original version Published
04-Apr-2017 - Removed v10 (distributed) from affected list, text change to explicitly mention 'on unix platforms'
*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. |
db3761666c74ce644f1ad4fcc7fa4b05_5 | RELATED INFORMATION
A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21995532]
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0
PRODUCT ALIAS/SYNONYM
WMB IIB |
d0dc915879763669af604c305bbab83d_0 | IBM Portal upgrades fail during ejbdeploy with 'Error is Platform not running' message - United States 7001eGA TECHNOTE (TROUBLESHOOTING)
PROBLEM
Portal upgrades fails during ejbdeploy with 'Error is Platform not running' message. This could happen for any v6.1.0.x , v7.0.0.x, or v8.0.0.x upgrade |
d0dc915879763669af604c305bbab83d_1 | SYMPTOM
In the ConfigTrace.log, the following exception can be seen:
==========================
[wsadmin] ADMA5016I: Installation of wps started.
[wsadmin] ADMA5058I: Application and module versions are validated with versions of deployment targets.
[wsadmin] ADMA5018I: The EJBDeploy program is running on file /var/tmp/app5791171104868981175.ear.
[wsadmin] Starting workbench.
[wsadmin] EJB Deploy configuration directory: /opt/IBM/WebSphere/AppServer/profiles/dmgrProfile/ejbdeploy/configuration/
[wsadmin] framework search path: /opt/IBM/WebSphere/AppServer/deploytool/itp/plugins
[wsadmin] build: RAD753-I20090617_1116
[wsadmin] An unexpected exception was thrown. Halting execution.
[wsadmin] Shutting down workbench.
[wsadmin] Error executing deployment: java.lang.IllegalStateException. Error is Platform not running.
[wsadmin] java.lang.IllegalStateException: Platform not running
[wsadmin] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:374) |
d0dc915879763669af604c305bbab83d_2 | [wsadmin] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wsadmin] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wsadmin] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wsadmin] at java.lang.reflect.Method.invoke(Method.java:597)
[wsadmin] at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:487)
[wsadmin] at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:106)
[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:106)
[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.deploy(EJBDeploy.java:349)
[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:311)
[wsadmin] EJBDeploy level: @build@
[wsadmin] ADMA5008E: The EJBDeploy program failed on file /var/tmp/app5791171104868981175.ear. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy |
d0dc915879763669af604c305bbab83d_3 | [wsadmin] ADMA0063E: An error occurred during Enterprise JavaBeans (EJB) deployment. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy
[wsadmin] ADMA5011I: The cleanup of the temp directory for application wps is complete.
[wsadmin] ADMA5069E: The installation of application wps failed. This application was in the middle of a full update and therefore is uninstalled from the configuration session. Discard your current configuration session immediately to recover the application. Do not save changes to the WebSphere Application Server configuration repository. The application is not uninstalled from this repository. Until the current configuration session is discarded you do not see this application in the current session. |
d0dc915879763669af604c305bbab83d_4 | [wsadmin] WASX7017E: Exception received while running file "/opt/IBM/WebSphere/AppServer/profiles/wp_profile/ConfigEngine/config/work/was/curJaclScript.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for wps failed: see previous messages for details. |
d0dc915879763669af604c305bbab83d_5 | [wsadmin] WASX7341W: No "save" was performed before the interactive scripting session exited; configuration changes will not be saved.
/opt/IBM/WebSphere/AppServer/profiles/wp_profile/ConfigEngine/config/includes/apply_PTF.xml:59: Java returned: 105
==========================
CAUSE
This exception can happen during ejbdeploy after the WebSphere Application Server has been upgraded, and old OSGI cache remains for the ejbdeploy tool. The OSGI class of the ejbdeploy tool contains class information within the deploytool folder and can become stale if the content inside deploytool has changed.
RESOLVING THE PROBLEM
To resolve the problem, complete the following steps:
1. Delete/Remove the contents of the following directory EXCEPT for the 'config.ini' file, if it exists (the paths are different depending on your backend WAS version):
WebSphere Application Server v6.1.x:
<profile root>/deploytools/configuration |
d0dc915879763669af604c305bbab83d_6 | WebSphere Application Server v7.0.x:
<profile root>/ejbdeploy/configuration
<AppServer root>/deploytool/itp/configuration
WebSphere Application Server v8.0.x:
<profile root>/ejbdeploy/configuration
<AppServer root>/deploytool/itp/configuration
Cluster Environments: Do this for both the DMGR profile and the node profile.
Note: The deploytools and ejbdeploy directories may not exist on all nodes. They are created when ejbdeploy is executed successfully for the first time. If it has never been executed successfully in your environment, then the directories will not be there.
2. Re-attempt the WebSphere Portal upgrade.
*
* |
d48c95334fb4b437296791796ef09f7e_0 | IBM The affect of the auto-update feature for Oracle JDK 7 on IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation - United States NEWS
ABSTRACT
The IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation products support Oracle JDK 7, but do not support Oracle JDK 8.
CONTENT
On Windows operating systems, because the upgrade to Oracle JDK 8 is enabled by default, you might not be aware that the upgrade has occurred. This Oracle JDK 8 issue applies to the Mac OS as well.
SYMPTOM
You might see one of the following messages in the log file on Windows and Mac OS machines that originate from the WebSphere Application Server Liberty Profile:
* TRAS0033E: Runtime injection of detailed method trace failed for class <class name> with exception <exception name>
* CWWKC0044W: An exception occurred while scanning class and annotation data. |
d48c95334fb4b437296791796ef09f7e_1 | RESOLUTION
As stated on the Java SE at a Glance [http://www.oracle.com/technetwork/java/javase/overview/index.html] page, Oracle is automatically migrating users with the auto-update feature enabled from Oracle JDK 7 to Oracle JDK 8. However, a number of IBM and third-party dependencies for IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation do not support Oracle JDK 8. |
d48c95334fb4b437296791796ef09f7e_2 | * Windows operating systems
If you have already migrated to Oracle JDK 8, you need to revert to Oracle JDK 7 using the following steps: 1. Uninstall Oracle JDK 8.
2. Download the latest version of Oracle JDK 7 from the Java SE Downloads [http://www.oracle.com/technetwork/java/javase/downloads/index.html] tab of the Oracle web site.
3. Reinstall Oracle JDK 7.
To disable the JDK auto-update feature on Windows operating systems, see the Change Automatic Update Settings [http://java.com/en/download/help/java_update.xml#adv] section of the Oracle Java Auto Update documentation.
* Mac OS
If you have already migrated to Oracle JDK 8, you need to revert to Oracle JDK 7 using the following steps: 1. Uninstall Oracle JDK 8. For more information, see the How do I uninstall Java 7 and later versions on my Mac? [https://www.java.com/en/download/help/mac_uninstall_java.xml] information on the Oracle web site. |
d48c95334fb4b437296791796ef09f7e_3 | 2. Download the latest version of Oracle JDK 7 from the Java SE Downloads [http://www.oracle.com/technetwork/java/javase/downloads/index.html] tab of the Oracle web site. For more information, see JDK 7 Installation for Mac OS X [http://docs.oracle.com/javase/7/docs/webnotes/install/mac/mac-jdk.html].
3. Reinstall Oracle JDK 7.
On the Mac OS operating system, you are explicitly asked if you want to update your Java version. Do not update the Java version to Java 8. To verify your Java version, see How do I update Java for my Mac? [https://www.java.com/en/download/help/mac_java_update.xml] |
d48c95334fb4b437296791796ef09f7e_4 | Cross reference information Segment Product Component Platform Version Edition Mobile- Speech and Enterprise Access IBM Worklight Security Mac OS X, Windows 6.2, 6.1, 6.0, 5.0.6, 5.0.5 Consumer, Enterprise Mobile- Speech and Enterprise Access IBM Mobile Foundation Security Mac OS X, Windows 6.0, 5.0.6, 5.0.5 Consumer, Enterprise |
f5a2f48ee0da974b4296df440496bf33_0 | IBM WebSphere DataPower M/T 9235 appliance might incorrectly report failure of both power supplies - United States TECHNOTE (FAQ)
QUESTION
The IBM WebSphere DataPower M/T 9235 appliance might incorrectly report the failure of both power supplies. This message is not reported on all appliances and can occur rarely in the field.
ANSWER
The following message would be present in the DataPower logs:
System power supply #2 has failed.
or logging event code:
0x80400022 System power supply #2
The problem can be confirmed by issuing the following commands on the appliance CLI:
co
test hardware
exit
The following output from the test hardware command confirms this problem:
[failure] Power supply '1' has no AC input power, or is not present.
[failure] Power supply '2' has no AC input power, or is not present.
Other results in the test hardware command might also show incorrect values. |
f5a2f48ee0da974b4296df440496bf33_1 | This problem does not affect the operation of the appliance other than the continuous reporting power supply failure message.
To confirm the power supplies are working normally you may check the LED status on the power supplies. If the LED's are green the power supplies are working normally.
To recover from the false errors perform a reboot of the appliance:
From the WebGUI:
Control Panel → System Control → In the “Shutdown” section choose “Reboot System” then click “Shutdown”
From the CLI:
top
shutdown reboot
y
This problem is caused by a highly intermittent error that may allow the sensor reading mechanism to get into a bad state. This bad state then generates the false error messages. In most cases, a reboot of the appliance will reset the sensors and no additional errors are logged. The highly intermittent error rarely occurs again on the same appliance |
f5a2f48ee0da974b4296df440496bf33_2 | If the issue reoccurs on the same appliance contact IBM DataPower support [http://www.ibm.com/support/docview.wss?uid=swg21236322] with the following information:
1) How many times have you seen the issue on the same appliance?
2) Gather the outputs for the following CLI commands:
show clock
show version
show ipmi
show sensors-other
config
service show
test hardware |
fca3c13963151c64905236d48a1a534b_0 | IBM Diagnosing a java.lang.StackOverflowError - United States StackOverflow; overflowing; recursion; recursively; jit; JustInTime; Hot; Spot; WebSphere; Just-In-Time TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Stack Overflow exceptions can occur when a thread stack continues to grow in size until reaching the maximum limit.
SYMPTOM
A stack overflow can result from:
* A deeply nested application
* An infinite loop within an application
* A problem in just-in-time (JIT) compiled code
* Applications requiring a larger stack size, especially ones relying on XML, GUI, or java2D classes.
* Native method calls |
fca3c13963151c64905236d48a1a534b_1 | Stack overflow issues are frequently masked by Out of Memory exceptions. By resolving the memory constraints, the stack overflow can be resolved.
CAUSE
When a stack overflow occurs, the amount of stack space required by the program exceeds what is configured for the stack in the Java™ Virtual Machine (JVM) process, or the native stack size configured by the operating system.
Some applications require stacks that are larger than the default size; for example, a graphics-intensive Java program can require a larger stack, which may require an increase in the stack size to avoid StackOverflow.
DIAGNOSING THE PROBLEM
Look for either Out of Memory messages or java.lang.StackOverflow in the server logs. The process may continue to run after either of these messages are seen.
If a crash did occur, a javacore should have generated on IBM SDK. You will either see the signal as SIGSEGV, SIGILL, SIGABRT, or SIGBUS. Usually the current thread will indicate the following |
fca3c13963151c64905236d48a1a534b_2 | pending=java.lang.StackOverflowError
RESOLVING THE PROBLEM
[/support/docview.wss?uid=swg21162896&aid=1]Explanations and Solutions
[/support/docview.wss?uid=swg21162896&aid=2]Detailed Configuration Options
Explanations and Solutions
Infinite Recursion
If an application is performing recursion, the maximum stack size can easily be reached and a Stack Overflow exception is thrown. The thread stack has a limited size and eventually its space will run out as the thread stack grows without bounds.
Some traits of recursion:
- Large thread stacks that appear to repeat
- An infinite loop that continuously spawns off threads
- Very large XML documents loaded into the Document Object Model (DOM)
- JSP or servlets calling itself (usually by executing forward or include to itself)
- Repeated calls in native functions |
fca3c13963151c64905236d48a1a534b_3 | Increasing the thread stack size allows for larger thread stacks. However if the recursion continues to trigger a stack overflow, the next step is to identify what code is causing the recursion from javacores, thread dumps, or even system core files.
A thread stack that indicates it's too large to display can be an indicator of stack overflow. This is especially true if the stack appears to repeat (such as recursive method calls).
JIT/HotSpot Compiled Code |
fca3c13963151c64905236d48a1a534b_4 | The JIT/HotSpot compiler (JIT) is designed to speed up the JVM execution times by compiling method calls. This can speed up execution time, but as more aggressive optimizations are used, this can inadvertently cause recursion, resulting in stack overflow or crash. The documents linked below explain how to debug JIT and HotSpot compiler issues: * JIT Problem Determination for IBM SDK 5.0 and 6.0 using -Xjit [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21294023]
* Debugging HotSpot failures on the Solaris and HP-UX operating environment [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21081179]
Depleted Native Stack
It is almost guaranteed that a crash will occur if the native stack runs out of space. System cores can be used to identify long and possibly recursively looping native thread stacks. |
fca3c13963151c64905236d48a1a534b_5 | To resolve, increase the native stack size (usually by adjusting the operating system limit for stack size) to accommodate the recursive native calls; however, identifying the recursive native calls will help determine the root cause of the stack overflow.
[/support/docview.wss?uid=swg21162896&aid=3] Back to top
[http://www.ibm.com/i/v14/rules/dotted_blue_rule_443.gif]
Detailed Configuration Options
Adjusting the Stack Sizes (Xss and Xmso) options
If this does not work, you can adjust the stack sizes. Doubling the stack size is suggested as a first step; however, every thread that the JVM creates will consume memory. Be careful to not exhaust your physical and heap memory resources. |
fca3c13963151c64905236d48a1a534b_6 | For every Java thread, there are two stacks that are utilized. One is for Java code for method calls, and the other is for native C code (on Solaris and HP-UX, only the native stack is utilized). These are adjustable and can be raised to provide more room on the stacks to prevent an overflow.
* Maximum Thread Stack Size (-Xss)
*
*
*
*
* -Xss<size>
*
* <size>
*
* nn[k|m|g|K|M|G]
*
*
*
*
*
*
* there is no distinction between native and thread stack sizes
*
* only
*
* HP-UX
*
*
*
* -XX:MainThreadStackSize=<size>
*
*
*
*
*
*
*
* Initial Thread Stack Size (-Xiss)
*
* This is only for distributed platforms (AIX, Linux, Windows)
*
*
*
*
*
* -Xiss<size>
*
* <size>
*
* nn[k|m|g|K|M|G]
*
*
*
*
* Initial Native Stack Size (-Xmso)
*
* This is only for distributed platforms (AIX, Linux, Windows)
*
*
*
*
*
*
* -Xmso<size>
*
* <size>
*
* nn[k|m|g|K|M|G]
*
*
*
* |
fca3c13963151c64905236d48a1a534b_7 | Default Values
This is a chart of default sizes for the various stack size arguments. This is subject to change due to upgrades of the SDK. |
fca3c13963151c64905236d48a1a534b_8 | [/support/docview.wss?uid=swg21162896&aid=4]
Value [/support/docview.wss?uid=swg21162896&aid=4]
AIX [/support/docview.wss?uid=swg21162896&aid=4]
Linux [/support/docview.wss?uid=swg21162896&aid=4]
Windows [/support/docview.wss?uid=swg21162896&aid=4]
Solaris [/support/docview.wss?uid=swg21162896&aid=4]
HP-UX [/support/docview.wss?uid=swg21162896&aid=4]
Initial Thread Stack Size [/support/docview.wss?uid=swg21162896&aid=4]
2KB [/support/docview.wss?uid=swg21162896&aid=4]
2KB [/support/docview.wss?uid=swg21162896&aid=4]
2KB [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Maximum Thread Stack Size [/support/docview.wss?uid=swg21162896&aid=4]
256KB (32-bit)
512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
256KB (32-bit)
512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
256KB (32-bit) |
fca3c13963151c64905236d48a1a534b_9 | 512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Native Stack Size [/support/docview.wss?uid=swg21162896&aid=4]
256KB [/support/docview.wss?uid=swg21162896&aid=4]
256KB [/support/docview.wss?uid=swg21162896&aid=4]
32KB (32-bit)
256KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
512KB (32-bit)
1024KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
64KB (PA-RISC)
1024KB (Itanium) [/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=5] Back to top |
fca3c13963151c64905236d48a1a534b_10 | Examples of Stack Overflow |
fca3c13963151c64905236d48a1a534b_11 | Server Logs
These logs may contain references to StackOverflow, alongside other messages. Thread stacks may accompany these messages, indicating if there is a recursive call.
* SystemOut.log example
* [3/14/15 3:14:15:926 CST] 31415926 BaseMap W CWOBJ0006W: An exception occurred:
*
* com.ibm.websphere.objectgrid.ObjectGridRuntimeException: java.lang.StackOverflowError
*
* <<Thread stack may follow this message>>
*
*
*
*
* SystemErr.log example
* [3/14/15 3:14:15:926 PST] 31415926 SystemErr R Caused by: java.lang.StackOverflowError
*
* at java.util.Hashtable.get(Hashtable.java:461)
*
* at com.ibm.ws.webcontainer.srt.SRTServletRequest.getParameter(SRTServletRequest.java:1257)
*
* at psdi.webclient.system.session.WebClientSession.applySkin(WebClientSession.java:295)
*
* at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1177)
*
* at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1213)
* |