PI31852: StateManager.getObjectGridState() fails when using eXtremeIO with security enabled.

APAR status

• Closed as program error.

Error description

• The StateManager.getObjectGridState() function fails with the
  following exception:
  
  com.ibm.ws.xsspi.xio.exception.TransportException$CommFailure [o
  at com.ibm.ws.xsspi.xio.dispatch.MessageDispatcher.tell(
  at com.ibm.ws.xsspi.xio.dispatch.MessageDispatcher.ask(M
  at com.ibm.ws.xsspi.xio.dispatch.MessageDispatcher.ask(M
  at com.ibm.ws.xs.xio.actor.impl.ActorRefImpl.ask(ActorRe
  at com.ibm.ws.objectgrid.partition.xio.XIORemoteShardImp
  at com.ibm.ws.objectgrid.StateManagerImpl.getObjectGridS
  Caused by: com.ibm.websphere.objectgrid.security.ObjectGridSecur
  at com.ibm.ws.xsspi.xio.dispatch.MessageDispatcher.XIOAu
  at com.ibm.ws.xsspi.xio.dispatch.MessageDispatcher.tell(
  ... 41 more
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users running data grid clients in the same *
  *                  JVM process as the WebSphere eXtreme        *
  *                  Scale container server.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Client Security Context is null, but    *
  *                      CredentialAuthentication is set to be   *
  *                      Required.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When WebSphere eXtreme Scale security is enabled and you are
  running a grid client in the same JVM process as the
  container server, it is possible to run into a problem during
  container process startup where you see the following
  message in the logs:
  Client Security Context is null, but CredentialAuthentication
  is set to be Required.
  There is a code issue where the client credentials are not
  always passed to the catalog server and the request fails
  with the message.
  

Problem conclusion

• Code has been fix to make sure user credentials are used for
  client requests sent from the container process.
  

Temporary fix

Comments

APAR Information

• 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