Product Readmes
Abstract
IBM WebSphere eXtreme Scale provides periodic fixes for release V8.6.1. The complete listing of fixes for V8.6.1 is as follows, starting with the most recent fix.
Content
Back to Recommended Fixes for WebSphere eXtreme Scale |
Release Date
|
Total number of APARs
|
Total number of Security APARs
|
||
Fix Pack 8.6.1.6 | 25 September 2023 | 9 | 5 | |
Fix Pack 8.6.1.5 | 21 May 2021 | 14 | 1 | |
Fix Pack 8.6.1.4 | 11 March 2020 | 18 | 5 | |
Fix Pack 8.6.1.3 | 21 December 2018 | 36 | 7 | |
Fix Pack 8.6.1.2 | 24 March 2017 | 10 | 0 | |
Fix Pack 8.6.1.1 | 18 November 2016 | 18 | 1 | |
Refresh Pack 8.6.1.0 | 16 June 2016 | 111 | 3 |
Fix Pack 8.6.1.6
|
|
Fix release date: 25 Sep 2023 Last modified: 25 Sep 2023 Status: Recommended Download Fix Pack 8.6.1.6 |
Component | Security APAR | APAR | Description |
All | ✓ | PH55403 | There are multiple vulnerabilities in IBM Runtime Environment Java Version 8 used by WebSphere eXtreme Scale. |
✓ | PH53340 | Multiple vulnerabilities in Dojo toolkit and jQuery version shipped with IBM WebSphere eXtreme Scale Liberty Deployment | |
✓ | PH51696 | There are multiple vulnerabilities in IBM® Runtime Environment Java™ Version 8 used by WebSphere eXtreme Scale. | |
✓ | PH44474 | There are multiple vulnerabilities in IBM® Runtime Environment Java™ Version 8 used by WebSphere eXtreme Scale. | |
✓ | PH44065 | Apache Log4j is used by IBM WebSphere eXtreme Scale as part of remote logging functionality (CVE-2022-23307). The fix includes Apache Log4j v2.17.1. | |
PH47326 | Deadlock may occur when new near-cache clients are being subscribed while the slow near-cache clients are being unsubscribed. | ||
PH46846 | A large number of Grids in the XSLD environment can lead to a few Grids not starting because of MessageTimeOutException. | ||
PH46847 | XSLD GRID APPLICATION FAIL TO START BECAUSE PLUG-IN CLASSES CANNOT BE FOUND. | ||
PH48913 | checkStatus.sh returns “XS-Nanny-Watch-Dog service” after stopXSLD.sh.This fix will show the correct status for the XS-Nanny-Watch-Dog service |
Fix Pack 8.6.1.5
|
|
Fix release date: 21 May 2021 Last modified: 21 May 2021 Status: Recommended Download Fix Pack 8.6.1.5 |
Component | Security APAR | APAR | Description |
---|---|---|---|
All | PH34493 | OOM is caused by prober storing probe records for all slow clients. | |
✓ | PH34473 |
Multiple vulnerabilities in IBM SDK, Java technology edition affect the websphere extreme scale.
|
|
PH31055 | HTTP Session could be lost with idreuse=false when failover happens. | ||
PH32142 | Session Attributes may be orphaned when shareSessionsAcrossWebApps is enabled. | ||
PH27548 | Using both webprofile-8.0 and elasticcacheclient-1.0 features causes conflicts. | ||
PH27393 | Custom grid template not honoured while creating grids from rest API. | ||
PH27416 |
SETUPDERBYREPLICATIONTASKCOMMAND fails in non-english locale env.
|
||
PH26976 | With XM enabled, customers may see elevated CPU usage when subscribing/resubscribing is called after a disconnection. | ||
PH26656 | Failure of derby failover when we use XSLD_MEMBER_HOST_ADDRESS. | ||
PH26331 | Orphan thread evictor is not working with eXtremeMemory. | ||
PH26090 | Rest API is not working correctly for updating the statistics time interval | ||
PH25418 | Improvements to automatic derby replication and auto-recovery script. | ||
PH24830 | In XSLD orphaned attributes are not removed due to NoClassDefFoundError | ||
PH24235 | After upgrading to XSLD 8.6.1.4 objectgrid TTL button is disabled in XSLD UI Console. |
Fix Pack 8.6.1.4
|
|
Fix release date: 11 March 2020 Last modified: 11 March 2020 Status: Recommended Download Fix Pack 8.6.1.4 |
Component | Security APAR | APAR | Description |
---|---|---|---|
All | ✓ | PH21775 | Multiple Vulnerabilities in IBM SDK, Java Technology Edition affect WebSphere eXtreme Scale |
PH20616 |
Post upgrade from 8.6.1002.* to 8.6.1003.* the information of Datacachemembers on UI console is not correct.
|
||
PH19398 | XS on Docker - doesn't pick up the main IP address. | ||
PH19249 | Java heap OOM is caused by a security cache when LDAP is slow to respond or in a hung state. | ||
PH19097 | TTL values from custom grid templates are not honoured while creating grids. | ||
PH19040 | XIO timeout from server.xml is not honoured. | ||
PH18792 |
ArrayIndexOutOfBoundsException for objectgrids with missing domainName.
|
||
PH18500 | Automatically replicate Derby in a cache member group (AutoDB replication feature). | ||
✓ | PH17611 | Multiple vulnerabilities in IBM SDK, Java Technology Edition affect WebSphere eXtreme Scale. | |
✓ | PH16881 | Multiple vulnerabilities in IBM WebSphere eXtreme Scale Liberty Deployment could expose sensitive information(CVE-2019-4106, CVE-2019-4109, CVE-2019-4112, CVE-2019-4115). | |
✓ | PH16598 | XSLD remediate QID 11827. | |
PH15549 | XSLD Console query fails to run on _services WebSphere Commerce cache maps. | ||
PH13541 | OOM in catalog server because of Liberty SSL leak. | ||
PH12258 | Client ObjectGrid instances can leak when they are not destroyed. | ||
PH11649 | XSLD will fail to enable eXtreme Memory on PPC8. | ||
✓ | PH11543 | Multiple vulnerabilities in IBM SDK, Java Technology Edition affect WebSphere eXtreme Scale. | |
PH08066 | Warning message CWOBJ0061W occurring frequently in the logs. | ||
PH08443 | Join member caused NPE when the member name was too long (more than 41 characters). |
Fix Pack 8.6.1.3
|
|
Fix release date: 21 December 2018 Last modified: 31 December 2018 Status: Superseded Download Fix Pack 8.6.1.3 |
Component | Security APAR | APAR | Description |
---|---|---|---|
All | IT22807 | Session orphaned attributes were not cleaned properly and were left behind in the session grid | |
PH06272 | XSLD REST Data Server out of memory error | ||
✓ | PH05857 | Multiple vulnerabilities in IBM SDK, Java Technology Edition affect WebSphere eXtreme Scale | |
PH00604 | ClassNotFoundException for class com.ibm.ws.xs.sessionmanager.httpsessionfilter in Liberty | ||
✓ | PH00404 | A vulnerability in IBM SDK, Java Technology Edition affects WebSphere eXtreme Scale | |
PI99759 | Specifying a variable as the HTTP port value results in a NumberFormatException when using xscmd -c showmapsizes | ||
PI98505 | The subscription timer should not start until the publisher is ready | ||
PI98420 | Share HTTP sessions between multiple J2EE applications | ||
PI97935 | KeyNotFoundException in CSOBJ1524I message when replica shard is registering with primary | ||
✓ | PI96369 | Multiple Vulnerabilities in IBM SDK, Java Technology Edition affect WebSphere eXtreme Scale | |
PI93165 | The JVM setting was out of sync with the console as well as changed the JVM security setting unexpectedly | ||
PI93137 | The CWOBJ1537E message for exceeding the maximum number of reregisters can occur erroneously | ||
PI93135 | DuplicateKeyException seen in CSOBJ1524I message when replica shared is registering with primary | ||
PI92350 | Write-Behind loader fails with NullPointerException when XDF is configured | ||
PI91380 | UpdateContainerAndJVMSizeTaskCommand for XSLD throws IndexOutOfBoundsException when in a collective | ||
PI91106 | XSLD user interface does not return the expected error when a faulty custom template is used | ||
PI89813 | XSLD fails if restricting restAdminServer | ||
PI89706 | NullPointerExceptions while stopping catalog jvm via WAS admin console and xscmd teardown command | ||
PI89685 | XSLD created grid set authorization flag incorrectly | ||
PI88403 | ArrayIndexOutOfBoundsException can occur when using eXtreme Scale Dynacache provider | ||
PI88192 | Map entries do not expire at the right time after an update operation | ||
PI87836 | Incorrect transaction timeout setting in catalog server transactions causes LockTimeoutExceptions | ||
PI86927 | An ArrayIndexOutOfBoundsException exception can occur when using a global index | ||
PI86607 | WXS 8.6.1 install can fail with a bad JAVA version for WAS 8.5.5 starting at 8.5.5.11 even if the JAVA version is supported | ||
PI84936 | OutOfMemoryError exception can occur when using eXtremeIO (XIO) transport | ||
PI84448 | Entries in a map configured with time to live eviction do not evict at the right time during failover | ||
✓ | PI83531 | Multiple vulnerabilities in IBM SDK, Java Technology Edition affect WebSphere eXtreme Scale | |
PI82969 | Entries not evicted if time to live eviction transactions fail | ||
PI82096 | In WXS 861 setting a TTL programmatically of more than 6442450 seconds causes an IllegalArgumentException | ||
PI80152 | Manual steps are required when upgrading to eXtreme Scale Liberty Deployment after 8.6.1.2 as a non-root user | ||
PI79994 | ObjectQuery throwing NullPointerException | ||
PI79938 | NullPointerException occurred in the client when SSL transport is TCP/IP but no SSL configuration exists in server.xml in Liberty | ||
PI79409: | eXtreme Scale Liberty Deployment cache members'' statuses will be set to offline if using the ipv6 address | ||
✓ | PI78584 | Multiple vulnerabilities in IBM SDK, Java Technology Edition affect WebSphere eXtreme Scale | |
✓ | PI78572 | Multiple vulnerabilities in IBM SDK, Java Technology Edition affect WebSphere eXtreme Scale | |
✓ | PI78567 | Multiple vulnerabilities in IBM SDK, Java Technology Edition affect WebSphere eXtreme Scale |
Fix Pack 8.6.1.2
|
|
Fix release date: 21 September 2018 Last modified: 21 September 2018 Status: Superseded Download Fix Pack 8.6.1.2 |
Component | Security APAR | APAR | Description |
---|---|---|---|
All | PI69125 | WXS ContinuousQueryListener in the client does not get an update from the server after the server restart. | |
PI72417 | Enable XSLD non-root user install functionality. | ||
PI72831 | Enabling Derby replication on zLinux using REST API may fail occasionally because of socket permission errors. | ||
PI72832 | After SSL mutual authentication is enabled, some administrative operations fail. | ||
PI73012 | Unable to enable Websphere Extreme Scale SSL connection on Liberty Profile when using Java 8. | ||
PI73187 | The eXtreme Scale Liberty Deployment UI dashboard displays incorrect cache member data after a failed member joins. | ||
PI73554 | Derby replication task command may fail on some systems. | ||
PI74091 | NPE is thrown when the WXS client is retrieving the latest routing table from catalog during container failover. | ||
PI74503 | Unable to retrieve total duration time using Websphere Extreme Scale AgentManagerMBean. | ||
PM94029 | Websphere eXtreme scale 8.6 installs sMash product smash0101.Sys2 file. |
Fix Pack 8.6.1.1
|
|
Fix release date: 29 June 2018 Last modified: 29 June 2018 Status: Superseded Download Fix Pack 8.6.1.1 |
Component | Security APAR | APAR | Description |
---|---|---|---|
All | ✓ | PI70239 | Multiple vulnerabilities in IBM SDK, Java Technology Edition affect WebSphere eXtreme Scale. |
PI53891 | Transactions fail with ExpiredCredentialException when using extremeIO transport. | ||
PI64273 | Error message with prefix CWOBJ0012E is seen when using near cache invalidation. | ||
PI65179 | Performing an update for WebSphere eXtreme Scale Liberty Deployment from the installation manager fails on Windows. | ||
PI65346 | WebSphere eXtreme Scale Console does not show initialization messages on startup. | ||
PI65755 | WebSphere eXtreme Scale server side (container) dynacache statistics reflect higher than expected values | ||
PI66609 | On Microsoft Windows Operating Systems, getLogs.bat command fails to launch when the installed location contains space. | ||
PI66651 | eXtremeMemory Is Incorrect In New Server Created Using REST API | ||
PI66966 | On AIX systems the datastore is not started after installation if no public network interface is configured. | ||
PI67063 | The nanny process from the datastore replica member is hung. | ||
PI67936 | xscmd failed in WebSphere eXtreme Scale V8.6.1 with WebSphere Application Server V9 | ||
PI68271 | Webcontainer threads are hung in SessionsLRUOffloader even after PI05917 | ||
PI68534 | Add support for and default to NO_COPY near cache CopyMode for the eXtreme Scale Dynacache provider | ||
PI68561 | NullPointerException happens during routetable recovery | ||
PI68771: | The data store is not started on default Windows Docker toolbox VMs. | ||
PI69267 | xscmd does not exit with the proper return code | ||
PI70751 | A large amount of threads are spawned when attempting to restart the eXtreme Scale server in case of a network partition | ||
PI70955 | WebSphere eXtreme Scale JPA plugin does not tolerate network issue |
Refresh Pack 8.6.1.0
|
|
Fix release date: 21 December 2018 Last modified: 31 December 2018 Status: Superseded Download Refresh Pack 8.6.1.0 |
Component | Security APAR | APAR | Description |
---|---|---|---|
All | IT11003 | XC10 Web console Message Center no longer displays messages. | |
IT11057 | With ORB transport disconnecting an appliance from a two-member collective keeps the other box from. | ||
IT11116 | Memory cleanup is not done when a grid is deleted. | ||
IT12299 | The appliance web console message Center no longer displays messages. It shows empty messages. | ||
IT13029 | After the network brownout resolves, XC10 does not complete restart and xsServer00 does not recycle. | ||
IT13437 | The start-progress command stays at 4%, xsServer00 repeatedly logs "XSServerStartHandler waitForWorkItems". | ||
IT13440 | After recovering from a network disconnect, the appliance does not complete the restart. | ||
IT13578 | MessageTimeOutException exceptions may occur in fail-over scenarios with large amounts of data. | ||
IT15714 | XDF deserialization errors after failover. | ||
IT15860 | XDF EnumSerializer logging errors. | ||
PI23994 | Externalize the ObjectGrid.getDomainName() API. | ||
PI38515 | The ability to disable replication status to avoid garbage collection pauses from the memory consumption is needed. | ||
PI42180 | When you create a remote session grid in WebSphere Application Server V8.5.5.5, the browse function does not return grids. | ||
PI42444 | The server fails to start with the transport catalog attribute when using Spring Framework. | ||
PI42537 | The trace was insufficient for debug analysis. | ||
PI42795 | ObjectQuery fails when using a field of an embedded type as part of the query statement. | ||
PI42955 | A NumberFormatException occurs during container reconnect or restart scenarios. | ||
PI43279 | An ObjectGridXIOException occurs indicating that a protocol message was too large when very large requests are sent. | ||
PI43426 | Catalog servers fail after a network outage when failure recovery is suspended. | ||
PI43439 | A WebSphere eXtreme Scale client in the same JVM as the catalog server fails to connect to a remote domain. | ||
PI43649 | The eXtreme Scale monitoring console is blank after logging in. | ||
PI43836 | eXtremeMemory usage is greater than expected. | ||
PI43972 | Java EE 6 features that WebSphere eXtreme Scale uses conflict with Java EE 7 features in the Liberty profile V8.5.5.6. | ||
✓ | PI44031 | An unspecified vulnerability in WebSphere eXtreme Scale 8.6 can cause a denial of service. | |
PI44104 | The autocomplete parameter in the form tag for the eXtreme Scale console page needs to be turned off. | ||
PI44121 | A long timeout can occur when connections to all catalog server endpoints time out on a client connection. | ||
PI44458 | Simultaneous writes for the same key can result in a LockTimeoutException when using the write-behind function. | ||
PI44986 | You cannot define more than one WebSphere eXtreme Scale session data grid and dynamic cache data grid in Liberty. | ||
PI45073 | When restarting individual container servers without placement constraints, extra primary shards can occur. | ||
PI45242 | Catalog servers can fail to start when clients are left running and all servers are stopped. | ||
PI45246 | AcessControlException exception can occur when starting a server and using a security manager. | ||
PI45445 | With two or more synchronous replicas placed, uncommitted transactions are possible after failover. | ||
PI45744 | Incorrect routing can occur when using PartitionKey annotation on one or more fields in the key class. | ||
PI45880 | After an unexpected timeout, old primary shards do not stop. | ||
PI45881 | XIO handshake failures can result in a build-up of XIOConnectionController objects, which can cause OOM errors. | ||
PI46020 | After several MessageTimeOutExceptions during promotion, extra primary shards or lost data can occur. | ||
PI46042 | The monitoring console fails to load the detail reports and query data grid contents panels. | ||
PI46410 | WebSphere eXtremeScale servers running in Liberty 8554+ may encounter "java.io.IOException: unknown protocol: bundleresource". | ||
PI46496 | You cannot upload a new keystore or update the administrative password using the WebSphere eXtreme Scale. | ||
PI46833 | LockTimeoutException exception can occur when using the write-behind function. | ||
PI47492 | A domain of 3 or more catalog servers fails initial start-up. | ||
PI47586 | Out-of-memory errors can occur when using objects with HashMap or Hashtable fields. | ||
PI47962 | ClassCastException exception can occur in HashIndex when trying to roll back a transaction. | ||
PI48326 | Missing messages from the monitoring console message center. | ||
PI49170 | TransactionCallbackImpl.begin() method is called while processing replica shards. This should only occur on primary shards. | ||
PI49299 | getObjectGridState API does not return a consistently correct result when the grid is in transition. | ||
PI49452 | Client requests fail when using null values and the client and server are co-located in the same Java process. | ||
PI49518 | Inactive and empty maps appear in xscmd command showMapSizes. | ||
PI50024 | WebSphere eXtreme Scale REST gateway used near-side cache by default. | ||
PI50254 | Exceptions resolving old primary shard causes the next primary's hard promotion to fail. | ||
PI50255 | Missing agent permission causes java.security.accesscontrolexception. | ||
PI50551 | Repeated network failures cause primary shard demotions and Targ etNotAvailableExceptions. | ||
PI50624 | The WXS restgateway does not allow a catalog service domain beyond the default catalog service in WAS to be used. | ||
PI50772 | WebSphere eXtreme Scale Client for .NET authenticode certificate has expired. | ||
PI50921 | Primary or replica shard fails to transition from a StateManager setObjectGridState request causing AvailabilityExceptions. | ||
PI51087 | Brief network losses during primary shard promotion can cause data loss. | ||
PI51551 | ClassNotFoundException for com.ibm.wsspi.runtime.config.ConfigService with WXS on Liberty. | ||
PI51742 | IBM WebSphere eXtremeScale allows some sensitive data to linger in memory instead of being overwritten. | ||
PI52221 | Extreme Scale transaction identifiers can be duplicates causing transaction errors. | ||
PI52401 | NullPointerException when serializing a value from the grid via REST gateway. | ||
✓ | PI52487 | An Apache Commons Collections vulnerability for handling Java object deserialization. | |
PI52606 | LastUsedBytes is not correctly updated. | ||
PI52838 | OptimisticCollisionException fails to deserialize when using EntityManager. | ||
PI52945 | Deserialization using eXtreme Data Format (XDF) fails with MissingSerializationInfoException in readObject(). | ||
PI53272 | wxs-visibility attributes in manifest.mf requires double quotes. | ||
PI53604 | Excessive CWOBJ1550 and CWOBJ1551 messages for the same exception. | ||
PI53771 | JMXConnectorPort property in server.properties is not processed correctly. | ||
PI54398 | Support eXtremeMemory function on PowerPC big-endian platforms for both AIX and Linux. | ||
PI54509 | While doing placement under heavy load or network contention, the primary shard can be promoted too early. | ||
PI54796 | OutOfMemoryError error can occur when a removed replica attempts to replicate. | ||
PI55408 | ArrayIndexOutOfBoundsException exception can occur when using XsDataOutputStream.writeVarInt(long) with a negative number. | ||
PI56083 | NullPointerException from ReplicatedPartition TrackingTempReplica. | ||
PI56154 | After a network bronwn out recovers, the routetable contains unreachable entries. | ||
PI56295 | BufferUnderflowException and general protection faults(GPF) can occur. | ||
✓ | PI56341 | Multiple vulnerabilites in IBM WebSphere SDK Java Technology edition affect WebSphere eXtreme Scale(includes SLOTH fix). | |
PI56572 | Time to live eviction can stop running due to an exception occurring. | ||
PI56574 | Server stop hangs when there are in-doubt transactions. | ||
PI56769 | WKSP0009E with FileNotFoundException may happen when several application servers are started concurrently. | ||
PI57058 | WXS Spring provider DuplicateKeyException. | ||
PI57071 | Multiple login prompts appear on xscmd mixing localhost and local IP address. | ||
PI57109 | Network brownout recovery for embedded catalog servers stops incorrectly. | ||
PI57536 | Improved dynacache trace. | ||
PI57551 | WXS overwrites failure detection properties on heartbeat. | ||
PI57838 | Update the sample server and client properties files' SSL properties. | ||
PI57949 | StopConsoleServer.sh script fails with an error finding the script. | ||
PI58417 | Authorization fails for users with passwords and usernames that match. | ||
PI58491 | No error message for incorrect number of tokens in the URI. | ||
PI58512 | Asynchronous replication fails to replicate remove operations when using eXtremeMemory (XM) and not using a KeyDataSerializer. | ||
PI58620 | WebSphere eXtreme Scale mapstats and ogstats incorrect when multiple mapsets are defined in a single grid. | ||
PI58859 | A java.lang.NullPointerException may occur in the WebSphere eXtreme Scale exception path when the XIO transport is enabled. | ||
PI59054 | Agent invocations time out when an exception class is returned that is not found on the client. | ||
PI59667 | IllegalArgumentException encountered while setting fields during readObject() in XDF. | ||
PI59904 | eXtreme Scale Spring cache plug-in to support Spring Framework 4.2.x. | ||
PI60897 | WebSphere eXtreme Scale is subject to HTTP response splitting attacks. | ||
PI60904 | WebSphere eXtreme Scale encryption for Dynacache entries was using MD5, which is insecure. | ||
PI60922 | The container server fails to start during the concurrent catalog and the container server starts. | ||
PI61047 | LogElement.getKey() or SerializedKey.getObject() can return null when using the write-behind function. | ||
PI61076 | WebSphere eXtreme Scale .NET client trace enhancements. | ||
PI61198 | The eXtreme Scale plug-in for InfoSphere Data Replication (IDR) fails to initialize when using Java 7 or 8. | ||
PI61249 | Placement failures after full catalog restart (catalog recycle). | ||
PI61281 | Statistics only work with all enabled. | ||
PI61441 | EntityManager operations fail when using eXtremeIO (XIO). | ||
PI61641 | NullPointerException logged for MBeanService. | ||
PI61704 | WXS session removing orphaned attributes will only remove attributes for a single context root. | ||
PI61794 | Running xscmd command to show placement with default settings will not show a container which only hosts reserved shards. | ||
PI62238 | Container servers recycle when the primary catalog server is lost. | ||
PI62261 | Improve ByteBuffer usage and provide statistics information. | ||
PI62469 | com.ibm.websphere.objectgrid.ConnectException: "Connection closed from remote client" errors with XIO with SSL. | ||
PI62853 | InfoSphere Data Replication plug-in fails with ReadOnlyException. | ||
PI63661 | Installed eXtreme Scale libraries cause versionInfo to report the WebSphere install as 32-bit. | ||
PI65519 | WXS Http session stat affinityBreakCount doesn't increment when reuseSessionId=false. |
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.1.4;8.6.1.3;8.6.1.2;8.6.1.1;8.6.1.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
25 September 2023
UID
ibm10793321