aspose file tools*
The moose likes Distributed Java and the fly likes Marshal Exception: Best way to find cause Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Distributed Java
Bookmark "Marshal Exception: Best way to find cause" Watch "Marshal Exception: Best way to find cause" New topic
Author

Marshal Exception: Best way to find cause

Alton Hernandez
Ranch Hand

Joined: May 30, 2003
Posts: 443
Hi,

Our middleware projects runs on BEA Weblogic. From time to time we would get CORBA Marshal Exception. The problem is when we get this error there is almost nothing in the error message that would give us a hint on what's causing it.

So what is the best way of debugging this kind of error? Are there any debugging tools out there that can at least identify what part of the object that we are passing is causing the error?

tks.
Edward Harned
Ranch Hand

Joined: Sep 19, 2005
Posts: 291

You have my condolances. You're working through many interfaces. Each can raise exceptions and when they propagate up the chain details are often lost.

If you have a minor code then you can get some help by looking up that code. This is all I have used. Then it's a matter of guess work.


Ed's latest article: A Java Parallel Calamity http://coopsoft.com/ar/Calamity2Article.html
Jignesh Patel
Ranch Hand

Joined: Nov 03, 2001
Posts: 626

Use open source framework like log4j. Put debug statement and see where it goes.
Alton Hernandez
Ranch Hand

Joined: May 30, 2003
Posts: 443
Originally posted by Jignesh Patel:
Use open source framework like log4j. Put debug statement and see where it goes.


Loggers(like log4j) or debuggers doesn't help much in this case as the error happens when the client calls the remote object, unless there is a way to actually debug the call.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Marshal Exception: Best way to find cause
 
Similar Threads
IJ Debugging issue
Becoming a Hardman
NX: Exception handling implementing the DBAccess
Servlet code causes webserver to crash - sometimes
java heap size out of memory error