Re: JSwat and CORBA servers

Somehow the classpath is different when running the app in jswat. It
could be the app is launched using the Java Extensions Mechanism
(-Djava.ext.dirs=....) or -Xbootclasspath, and this is not being
reproduced in jswat. It is not likely to be worth the trouble, so...

What I recommend in cases like this is to launch the server separately,
with the necessary debug flags, then connect jswat to it remotely.
JSwat's help has a page about remote debugging, including the debug
flags you will need. You could even start up the server suspended until
you connect jswat to it. Although I've heard that is rather slow with
large applications like app servers.

n


On Tue, 2002-11-12 at 11:40, Nascif Abousalh-Neto wrote:
> Hi,
> 	I'm trying to use JSwat (locally, running under JSwat as opposed to
> remotely by using attach) to debug a CORBA (Sun's ORB, JDK 1.4.1, Solaris)
> application server. When I try to register the CORBA servant with the naming
> server (tnameserv from Sun) I got a CORBA.OBJECT_NOT_EXIST exception. The
> exact same code works fine outside of JSwat. I checked the JVM properties
> that control the ORB configuration and they are the same.
> 	Any suggestion on what could be going on?
> 
> 	TIA,
> 		Nascif