Skip to main content
 
developerworks > Community >  Dashboard > WebSphere eXtreme Scale V6.1 User Guide > ... > ObjectGrid 6.1 cumulative fix 3 contents > startOgServer hangs in WebSphere
developerWorks
Log In   View a printable version of the current page.
Overview New to Forums Wikis
startOgServer hangs in WebSphere
Browse space Browse Space    
Added by Chris.D.Johnson, last edited by Chris.D.Johnson on Dec 19, 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 Systems Management
Software Version 6.1

Problem

The startOgServer.bat/sh command hangs when starting an ObjectGrid server process in a WebSphere environment.

When attempting to start a server or container in a WebSphere environment, where WebSphere Extended Deployment Data Grid v6.1 is installed on top of WebSphere Application Server, the startOgServer.bat or startOgServer.bat script may appear to hang after logging message:
CWOBJ2514I: Waiting for ObjectGrid server activation to complete.

After 3 minutes, the following message will be logged:
CWOBJ2509E: Timed out after waiting 180 seconds for the server to start.

Cause

ObjectGrid was inadvertently disabling all of message logging and tracing when no trace specification was provided.

Workaround

There are two workarounds for this problem:

  1. Enable trace using the -traceSpec argument with any valid or invalid component or group specification. For example: startOgServer.sh catalogServer -traceSpec *=all=disabled
  2. Use a standalone Data Grid installation (non-WebSphere installation).

Solution

Apply ObjectGrid cumulative intermediate fix 3.

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