Marshal Exception: Best way to find cause

[Alton Hernandez]

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]

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.

[Jignesh Patel]

Use open source framework like log4j. Put debug statement and see where it goes.

[Alton Hernandez]

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.