the Sybase user community (or better yet, their support department) would
> be very handy to have in on the discusion - they may very well say that
> they don't have any, and that all IPC is handled by tcp sockets and high
> level protocols... in which case the question to them is &
ocols... in which case the question to them is "then why does
getConnection() fail under only java_g??" (I'm assuming it works under
normal java) Note that when I started trying to help I understood the
problem to be with in RMI when trying to use Runtime.trace*() . . . my
code does that
I'm sorry, but I'm obviously missing something. What *.so and *_g.so. As
far as I know the only libraries that I'm using are the ones included
with the JDK and Debug JDK Versions. I'm using class files for the Sybase
stuff. And my java files are not being compiled into a library. Maybe
I'm mi
On Sun, 17 Oct 1999, Chris Abbey wrote:
> At 23:21 10/16/99 -0600, Brandon Anderson wrote:
> >
> >OK, here is the thread dump, but like I already wrote in the previous
> >post I only get this while running java_g so I don't know if its really
> >relevant.
&g
At 23:21 10/16/99 -0600, Brandon Anderson wrote:
>
>OK, here is the thread dump, but like I already wrote in the previous
>post I only get this while running java_g so I don't know if its really
>relevant.
>
>*** panic: "../../../../src/share/javavm/runtime/classresolv
ning, no one can answer that 'cept you.
>javac_g/java_g? And how do I get Runtime.trace*() to work. I just simply
use java_g
>want to know if those function work under the Linux JVM. They are not
they work in 117v1a on RH5.2, and 117v3 on RH6.0
>required to be implemented accord
OK, here is the thread dump, but like I already wrote in the previous
post I only get this while running java_g so I don't know if its really
relevant.
*** panic: "../../../../src/share/javavm/runtime/classresolver.c", line
1285: assertion failure
SIGABRT 6* abort (gener
If that's the case than why does my program run correctly when I compile
it and run it with javac/java but not when I compile it with
javac_g/java_g? And how do I get Runtime.trace*() to work. I just simply
want to know if those function work under the Linux JVM. They are not
required
Overkill my friend... overkill. the _g versions don't change how they interact
with the outside world, only how they work internally. Class files generated
from javac and javac_g are the same. Unless you're debugging a failure of
rmiregistry there is no need for rmiregistry_g. Please send the stac
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 ir
At 19:47 10/16/99 -0400, 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
>
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 poin
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
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?
Thanx again (in advance
14 matches
Mail list logo
