APAR status
Closed as program error.
Error description
The following exception is when WebSphere eXtreme Scale Client tries accessing the data grid randomly. In this scenario, a connection was attempted to the data grid; however, that connection was closed each time. WebSphere eXtreme Scale [WXS 8.6.0.6 cf61449.04150359] Platform 7.0.0.35 [ND 7.0.0.35 cf351436.02][ARIESJPA 1.0.0.9 cf091248.03] Operating System: Linux, version 2.6.32-431.29.2.el6.x86_64 Java version = JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr16-20140626_204542 (JIT enabled, AOT enabled) J9VM - 20140626_204542 JIT - r9_20130920_46510ifx7 GC - GA24_Java6_SR16_20140626_1848_B204542_CMPRSS, Java Compiler = j9jit24, Java VM name = IBM J9 VM ---- ---- [2/24/15 14:41:41:785 GMT] 00000035 WebServiceExc E org.apache.axis2.jaxws.WebServiceExceptionLogger log A com.ibm.websphere.objectgrid.ObjectGridRuntimeException throwable was caught. The detail message is: at com.ibm.ws.objectgrid.naming.LocationServiceFactory.getRemoteLoc ationSer vice(LocationServiceFactory.java:824) .... .... com.ibm.websphere.objectgrid.ObjectGridRuntimeException: The Location Service for domain DefaultDomain has not yet been resolved. 809 at com.ibm.ws.objectgrid.naming.LocationServiceFactory.getRemoteLoc ationSer vice(LocationServiceFactory.java:824) 810 at com.ibm.ws.objectgrid.ObjectGridManagerImpl.getObjectGrid(Object GridMana gerImpl.java) 811 at com.ibm.ws.objectgrid.ObjectGridManagerImpl.getObjectGrid(Object GridMana gerImpl.java:858)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere eXtreme Scale users with a * * remote topology. * **************************************************************** * PROBLEM DESCRIPTION: ObjectGridRuntimeException occur * * when concurrent threads connect and * * disconnect to the same data grid. * **************************************************************** * RECOMMENDATION: For performance reasons, a single client * * connection should be used per data grid * * and shared between any threads. * **************************************************************** A timing window exists where a ObjectGridRuntimeException might occur when concurrent threads in the same client JVM invoke ObjectGridManager.connect() and ObjectGridManager.disconnect() methods against the same remote data grid.
Problem conclusion
A code fix was made to eliminate the timing window.
Temporary fix
Comments
APAR Information
APAR number
PI38996
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
860
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-04-13
Closed date
2015-04-24
Last modified date
2016-08-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WS EXTREME SCAL
Fixed component ID
5724X6702
Applicable component levels
R860 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
30 August 2016