OK, so I found out that not all the code is compiled with javac_g. Is
there any way to get around having to compile all the code with javac_g.
I'm connecting to a database via some jdbc drivers and they are not
compiled with javac_g and I don't/can't have the source to them.
Any ideas?
On Sat, 16 Oct 1999, Brandon Anderson wrote:
> I did recompile everything using javac_g, but that is when I get the nasty RMI
> thread dump. I would assume that the other code connecting through RMI doesn't
> have to be recompiled using the java_g. But that is pretty much irrelevant
> since I can't even get this program get to the point where it would accept RMI
> connections.
>
> I'm running the rmiregistry_g and all the code that is currently being used has
> been compiled with javac_g, so I just don't get what's wrong.
>
> On Sat, 16 Oct 1999, Michael Sinz wrote:
>
> > On Sat, 16 Oct 1999 15:47:02 -0600 (MDT), Brandon Anderson wrote:
> >
> > >Well, I tried to run my project with java_g as suggested. Unfortunately now I
> > >get a horrible RMI related thread dump. I was just wondering what exactly is
> > >the debug version of the jdk. Is it a development version or should it
> > >actually run correctly?
> >
> > The debug version of the JDK is specifically to help debug programs.
> > This also means that you need to have any RMI code built for debugging.
> >
> > --
> > Michael Sinz ---- Technology and Engineering Director/Consultant
> > "Starting Startups" mailto:[EMAIL PROTECTED]
> > My place on the web ---> http://www.users.fast.net/~michael_sinz
> >
> >
>
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
