Download WebSphere eXtreme Scale Version 8.6 Fix Pack 1 server upgrade
You can download the IBM WebSphere eXtreme Scale Version 8.6 Fix Pack 1, also known as 184.108.40.206.
IBM WebSphere eXtreme Scale is an elastic, scalable in-memory data grid that provides a key-addressable store of values or graphs. This product supports a processing unit state store for applications written in Java. You can replicate the data stored in the grid depending on availability requirements, and you can achieve out-of-the-box database integration.
WebSphere eXtreme Scale can be integrated with existing WebSphere Application Server and WebSphere Application Server, Network Deployment installations, or you can install the stand-alone product.
To access a wide variety of technical resources for this product, see the IBM WebSphere eXtreme Scale Version 8.6 Information Center.
The following APARs are included in this fix pack:
|PM82429||Errors occur with the WebSphere eXtreme Scale Client when credential authentication is set to required.|
|PM77861||After application server failover, HTTP session binding listeners might not be called back properly.|
|PM77948||The TargetNotAvailableException exception occurs when you set the RequestRetryTimeout value to 0 and use COPY_TO_BYTES.|
|PM78407||The HTTP session creation time in WebSphere eXtreme Scale is incorrect after application server failover.|
|PM78385||When entries of object properties are removed with the ClientSecurityConfigurationFactory.getClientSecurityConfiguration, errors occur.|
|PM77540||Session creation within a data grid agent causes an exception and a client timeout when data grid security is enabled.|
|PM79085||Startup failures might occur when you use large topologies.|
|PM77477||The xscmd command might not connect if one of the catalogs is unavailable, even with multiple catalog endpoints defined.|
|PM80587||The xscmd command, -c showMapSizes, does not retrieve all addresses.|
|PM80450||Query data grid console shows the first 50 characters of a key and truncates the rest.|
|PM77272||The command, xscmd -c suspendBalancing, which is used to suspend balancing is not working correctly.|
|PM77266||A workspace conflict causes containers to not start.|
|PM77856||Reduce synchronization for HTTP sessions that have been retrieved from the remote data grid to eliminate deadlocks.|
|PM77443||The management concentrator does not remove listeners on closed or failed JMX connections.|
|PM77893||Orphan threads are not cleaned up after stopping the server with the ServerFactory.stopServer() method.|
|PM78395||An OptionalDataException is seen while running a query against a Liberty profile server.|
|PM78397||Unnecessary synchronization limits XC10 appliance performance.|
|PM78414||.NET Client non-English messages are not displayed in a non-English environment.|
|PM78470||The ClassnotfoundException exception occurs on the channel framework when running a client with a third-party JDK.|
|PM78492||SpecialKeys are displayed for data grids enabled for dynamic cache when using XIO.|
|PM78825||ObjectMap output format is ignored by HashIndex find methods when XDF is enabled.|
|PM78827||When an unsigned 64-bit integer is used within a class in a C# application, an FFDC record is generated.|
|PM78841||The monitoring console is slow to retrieve statistics.|
|PM78867||Embedded catalogs and remote stand-alone eXtreme Scale containers using XIO receive catalog service endpoints with a port of 0 defined.|
|PM78869||Running the xscmd -c showNotificationHistory command against a list of catalog servers might result in inconsistent message results.|
|PM78875||When using COPY_TO_BYTES copy mode and eXtremeIO, both serialization plug-ins are available on the backing map.|
|PM78876||When the ObjectMap.clear() API or agent calls are in a client located in the same JVM as the container server, timeouts might occur.|
|PM78878||The command, xscmd -c showReplicationState, stops returning data when a container is dropped.|
|PM78936||Running XIO with COPY_TO_BYTES map fails with an assertion error when using map collections with the -ea JVM argument.|
|PM78938||Users are required to provide more security parameters than necessary.|
|PM78945||Applications might get stale data from the MapGlobalIndex API because the global index update process is set to asynchronous, which is the default.|
|PM78950||An eXtreme Scale catalog server throws java.Io.IOException in a remote JMX listener during startup, while continuing to process requests.|
|PM79151||When using XIO and COPY_TO_BYTES, the readobject method is not invoked.|
|PM79165||An access denied exception occurs when running XIO and security is enabled on WebSphere eXtreme Scale for WebSphere Application Server clients.|
|PM79166||The catalog server does not start on V8.6 after rolling upgrade from V220.127.116.11 to V18.104.22.168.|
|PM79168||XC10 upgraded mixed collective fails to initialize.|
|PM79169||The command, xscmd -c showmapsizes, is not working with XIO in the Liberty profile.|
|PM79276||The import and export functions conflict between traditional WebSphere Application Server packages provided by WebSphere eXtreme Scale and packages provided by the Liberty profile.|
|PM79317||xscmd -c showReplicationState command not returning data after inserting for over 20 minutes when security is enabled.|
|PM79338||The files, channel-outbound.Xml or channel.Xs.Xsd, were not loaded correctly.|
|PM79445||Time-to-live eviction fails when you change the time-to-live value from no timeout to having a timeout.|
|PM80420||Using AdminTasks scripting to configure catalog service domains might cause catalog servers to not be displayed as started.|
|PM81026||The ClassNotFoundException hides the original exception when using XIO transport.|
|PM81046||In the write-behind loader in MMR domains, the LoaderException can occur with the KeyNotFoundException.|
|PM81177||Agent calls or use of the clear API hangs when AvailabilityException is expected for XIO transport.|
|PM81179||With initial state set to preload, the data grid spends a short time in online state.|
|PM81708||StateManager.getObjectGridState() fails with TargetNotAvailableException repeatedly.|
|PM81901||Session runtime does not insert data into WebSphere eXtreme Scale grid for WebSphere Application Server V6.1.0.X embedded catalogs and containers.|
|PM82120||The command, xscmd -c showmapsizes, does not display data after session data is entered into the data grid with security enabled.|
|PM82123||Running the xscmd commands in the Liberty profile results in an error for every command.|
|PM82129||The monitoring console connects to catalogs but fails to display statistics when ORB ports are used.|
|PM82133||The data grid state manager fails when called before data grid has started.|
|PM82135||When starting a catalog server with ObjectGrid trace, a NullPointerException stops the catalog from starting correctly.|
|PM82149||When starting catalog server cluster, it results in a ClassNotFoundException and the second server hangs.|
|PM82148||Tracing in WebSphere eXtreme Scale and Liberty using the xscmd tool does not work.|
|PM82147||When running an application in same JVM as a container or catalog server, if a failure occurs, a reconnection might not happen.|
- Approximately 1.1 GB of disk space to store the required downloadable parts
- Approximately 1.1 GB of disk space to unpack the parts
- Approximately 400 MB of disk space to install the product
- Approximately 100 MB of space in the tmp directory to run the installation program
For more detailed information, see the WebSphere eXtreme Scale system requirements document.
WebSphere Application Server requirements
- WebSphere Application Server Version 22.214.171.124 or later
- WebSphere Application Server Version 126.96.36.199 or later
- WebSphere Application Server Version 188.8.131.52 or later
|Detailed system requirements||English||6215|
Complete the following instructions to download the server images.
- Download and extract one or more of the following WebSphere eXtreme Scale offerings from this page:
Description File name WebSphere eXtreme Scale in a stand-alone environment 8.6.0-WS-WXS--FP0000001.zip WebSphere eXtreme Scale for WebSphere Application Server Version 7 8.6.0-WS-WXS-WAS7-FP0000001.zip WebSphere eXtreme Scale for WebSphere Application Server Version 8 8.6.0-WS-WXS-WAS8-FP0000001.zip
- Install IBM Installation Manager. Use Installation Manager to install the product from the local product repositories that you downloaded from step 1.
- Add the fix pack repository location in IBM Installation Manager:
- Start IBM Installation Manager.
- In Installation Manager, click File > Preferences > Repositories.
- Click Add Repository.
- Browse to or enter the file path to the repository.config file. The repository.config file is located in the directory where you extracted the compressed files.
- Use Installation Manager to install or upgrade the product from the local product repositories that you downloaded in step 2. For more information about installing the fix pack, see Installing Fix Packs using Installation Manager in the information center.
|Quick Start Guide||English||184320|
Passport Advantage Online support at http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html
WebSphere Portal Server support at http://www.ibm.com/software/genservers/portal/support
This fix pack is no longer available for download. It is recommended that you apply fix pack 8. If you are using a z/OS install, you should apply fix pack 6. If you need access to fix pack 1, please contact IBM Support.
More support for:
WebSphere eXtreme Scale
Software version: 8.5, 184.108.40.206, 8.6, 220.127.116.11
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 4034293
Modified date: 26 June 2013