WebSphere eXtreme Scale
Forum: WebSphere eXtreme Scale
Topic: WebSphere eXtreme Scale Version 8.5 Fix Pack 3 available for download!
Latest Post -
WebSphere eXtreme Scale Version 8.5 Fix Pack 3 available for download!
This question has been answered.
This question has not been answered yet.
WebSphere® eXtreme Scale Version 8.5 Fix Pack 3 includes fixes for internal defects and usability improvements.
WebSphere eXtreme Scale Version 8.5 Fix Pack 3 is available for you to download
Download WebSphere eXtreme Scale V220.127.116.11 server and client upgrades
Recommended fixes for WebSphere eXtreme Scale
Websphere eXtreme Scale Development
Log in to reply.
Re: WebSphere eXtreme Scale Version 8.5 Fix Pack 3 available for download!
This is the accepted answer.
This is the accepted answer.
Here is a list of the APARs included in the 18.104.22.168 Fix Pack. Please be advised some of the documents are still being published so some of the links may not work.
Timeouts are seen when you replicate shards.
The WebSphere eXtreme Scale locking function does not release locks.
CSIv2 inbound message authentication with basic authentication causes callback operations to fail on eXtreme Scale.
Entries in some asynchronous replica shards are not removed when you run the clear operation.
The exception, ConcurrentModificationException, occurs during session failover.
java.lang.NullPointerException encountered while Updating OSGi services for eXtreme Scale plug-ins with xscmd script.
The Help text for xscmd -h revisions command is incorrect.
The LRU evictor can fall into an infinite loop under certain conditions.
Authorization checking is not done on placement service operations.
The exception, LockTimeoutException, prevents shard failure recovery.
XSCMD ROUTETABLE COMMAND DOES NOT SORT PARTITIONS IN OUTPUT.
Entity queries using compound keys might return incorrect results.
Serialization errors when using the COPY_TO_BYTES copy mode after restarting the data grid and not restarting the client.
The xscmd command, -c showQuorumStatus, reports incorrectly after you migrate a server from V22.214.171.124 to V8.6.0.
Errors occur when you deploy large-scale environments.
A workspace conflict causes containers to not start.
The command, xscmd -c suspendBalancing, which is used to suspend balancing is not working correctly.
The xscmd command might not connect if one of the catalogs is unavailable, even with multiple catalog endpoints defined.
Session creation within a data grid agent causes an exception and a client timeout when data grid security is enabled.
After application server failover, HTTP session binding listeners might not be called back properly.
The Bundle-Version attribute for the objectgrid.jar and ogclient.jar bundles are not changed even after fixes are applied.
Orphan threads are not cleaned up after stopping the server with the ServerFactory.stopServer() method.
The TargetNotAvailableException exception occurs when you set the RequestRetryTimeout value to 0 and use COPY_TO_BYTES.
When entries of object properties are removed with the ClientSecurityConfigurationFactory.getClientSecurityConfiguration.
The HTTP session creation time WebSphere eXtreme Scale is incorrect after application server failover.
Duplicate PMI module registration error when multiple Websphere eXtreme Scale libraries are loaded.
Users are required to provide more security parameters than should be required.
Startup failures may be seen when using very large topologies.
Suspended placement issues seen when starting and stopping grids.
Catalog server will not start up on 8600 cf1 after rolling upgrade from 8503 to 8600 cf1.
Fail to load keystore and truststore when path has a directory that starts with the letter ''u'' when running on windows.
The TTLEvictor.updateTTL does not work properly.
LockTimeoutExceptions on the catalog servers cause trouble when starting entire catalog service domain.
Starting catalog service endpoints in different domains causing "catalogServiceEndPoints " property must be consistent message.
Optimization of WXS placement code.
Honor the value of suspendbalancing at container stop (or loss) when the grid has not been initially placed.
java.lang.Illegalaccesserror error is seen when using a secured grid and objectgridsecurity tracing is enabled on Solaris.
Allow a configured cap on the number of replica shards past the total ideal shard count.
After the install of WXS and during augmentation, receive an INSTCONFFAILED message during addOCOrbInitializers().
In environments with co-existing WXS JVMs, upon termination of one of these JVMs, the clusterstore may stop retrieving routes.
Containers should retry possible failed connections to catalog servers to be eligible for placement.
Catalog server does not retry timed out placement service work.
Reduce the ORB thread hold times by off loading the payload to processing thread.
Query data grid console shows the first 50 characters of a key and truncates the rest.
AccessControlException exception is seen when starting multiple catalog and container servers with java 2 security enabled.
Users see a java.lang.LinkageError in com.ibm.ws.objectgrid.security.MapPermissionCheckAction.
Improve xscmd -c showMapSizes to stop retrieving all addresses.
Log in to reply.
items per page
Feed for this topic