Skip to main content
 
developerworks > Community >  Dashboard > WebSphere eXtreme Scale V6.1 User Guide > ... > ObjectGrid 6.1 cumulative fix 3 contents > UnknownRequestException occurs when starting clustered catalog services
developerWorks
Log In   View a printable version of the current page.
Overview New to Forums Wikis
UnknownRequestException occurs when starting clustered catalog services
Added by Chris.D.Johnson, last edited by Chris.D.Johnson on Dec 18, 2007  (view change)
Labels: 
(None)

Getting Started Examples Reference API documentation
See the WebSphere eXtreme Scale Wiki for links to up-to-date eXtreme Scale Version 7.x documentation.

If you log in with your developerWorks ID, you can leave comments and feedback for the development team.

Component Catalog Services and Dynamic Environment
Software Version 6.1

Problem

A com.ibm.ws.objectgrid.UnknownRequestException exception occurs when a clustered catalog service is started.

When attempting to start a cluster of catalog server processes, the following exception might be displayed in the ObjectGrid system logs:

[8/31/07 7:57:45:409 PDT]  1420142 Launcher      d launchServerRuntimeFrameWork failure: 
com.ibm.websphere.objectgrid.em.PersistenceException: Unable to activate the EMFactoryImpl.  See the cause for details.
      at com.ibm.ws.objectgrid.em.EMFactoryImpl.activate(EMFactoryImpl.java:710)
      at com.ibm.ws.objectgrid.runtime.ServerRuntimeFrameWorkImpl.activate(ServerRuntimeFrameWorkImpl.java:1432)
      at com.ibm.ws.objectgrid.Launcher.launchServerRuntimeFrameWork(Launcher.java:410)
      at com.ibm.ws.objectgrid.InitializationService.startService(InitializationService.java:771)
      at com.ibm.ws.objectgrid.InitializationService.main(InitializationService.java:1132)
Caused by: com.ibm.websphere.projector.MetadataException: 
  CWOBJ3009E: An exception occurred while communicating with the entity metadata repository: com.ibm.ws.objectgrid.UnknownRequestException
      at com.ibm.ws.objectgrid.em.EMFactoryImpl.storeEntityMetadata(EMFactoryImpl.java:2017)
      at com.ibm.ws.objectgrid.em.EMFactoryImpl.activate(EMFactoryImpl.java:690)
      ... 4 more.
Caused by: com.ibm.websphere.objectgrid.ClientServerLoaderException:com.ibm.ws.objectgrid.UnknownRequestException
      at com.ibm.ws.objectgrid.client.RemoteTransactionCallbackImpl.processGetResponse(RemoteTransactionCallbackImpl.java:1758)
      at com.ibm.ws.objectgrid.client.RemoteTransactionCallbackImpl.getGetResponseWithAuthenticationRetry(RemoteTransactionCallbackImpl.java:2535)
      at com.ibm.ws.objectgrid.client.RemoteTransactionCallbackImpl.processGetRequestAndResponse(RemoteTransactionCallbackImpl.java:2000)
      at com.ibm.ws.objectgrid.client.RemoteTransactionCallbackImpl.sendGetRequest(RemoteTransactionCallbackImpl.java:2483)
      at com.ibm.ws.objectgrid.client.RemoteCacheLoader.get(RemoteCacheLoader.java:265)
      at com.ibm.ws.objectgrid.map.BaseMap.getRaw(BaseMap.java:2607)
      at com.ibm.ws.objectgrid.DiffMap.lookForKey(DiffMap.java:640))
      at com.ibm.ws.objectgrid.DiffMap.get(DiffMap.java:566)
      at com.ibm.ws.objectgrid.ObjectMapImpl.get(ObjectMapImpl.java:329)
      at com.ibm.ws.objectgrid.em.ObjMapWrapper.get(ObjMapWrapper.java:65)
      at com.ibm.ws.objectgrid.em.EMFactoryImpl.storeEntityMetadata(EMFactoryImpl.java:1874)
      ... 5 more.
Caused by: com.ibm.ws.objectgrid.UnknownRequestException

Cause

Catalog services can be clustered using the -catalogServiceEndpoints parameter with the startOgServer.bat or startOgServer.sh script. See Starting a catalog service for details. If the host and ports are not in the same order in each of the catalog service startup scripts, then the above exception results and the catalog service does not start.

Workaround

Verify that the -catalogServiceEndpoints parameters are ordered properly in each of the commands that are used to start the catalog services.

Solution

Apply ObjectGrid cumulative intermediate fix 3.

Wiki Disclaimer and License
© Copyright IBM Corporation 2007,2010. All Rights Reserved.