Skip to main content
 
developerworks > Community >  Dashboard > WebSphere eXtreme Scale V6.1 User Guide > ... > ObjectGrid 6.1 cumulative fix 3 contents > Server side exception is not shown in the client-side exception stack
developerWorks
Log In   View a printable version of the current page.
Overview New to Forums Wikis
Server side exception is not shown in the client-side exception stack
Added by Jian.Tang, 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

The original server-side exception is propagated to the client-side exception stack.

In dynamic deployment environment (using a catalog server), if a ObjectGrid client request causes an exception to occur in an ObjectGrid server, the client receives an exception. However, the server-side exception is not shown in the client exception stack. A common error that results on the client follows:
org.omg.CORBA.INTERNAL: An internal error happened processing the request

Cause

The object request broker (ORB) that is used to communicate between the client and server processes does not automatically put the original server-side exception into the client-side exception.

Solution

The ObjectGrid server needs to explicitly send the original exception to the client. The client runtime then must chain the server-side exception into the client-side exception.

Apply ObjectGrid cumulative intermediate fix 3.

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