Re: RMI Activatable Object (solved)

1999-07-05 Thread Cees de Groot
[EMAIL PROTECTED] said: > Appreciate the help. I was able to get things working, for the most > part, by setting the following environment variables: > THREADS_FLAG=GREEN JAVA_COMPILER=NONE Yeah, that seems to be the most stable configuration for a lot of tasks. > I am, in fact, using native t

Re: RMI Activatable Object (solved)

1999-07-05 Thread James Caple
Appreciate the help. I was able to get things working, for the most part, by setting the following environment variables: THREADS_FLAG=GREEN JAVA_COMPILER=NONE I am, in fact, using native threads under Solaris. Thanks, James Cees de Groot wrote: > [EMAIL PROTECTED] wrote: > >Under Solaris 7

Re: RMI Activatable Object

1999-07-03 Thread Cees de Groot
[EMAIL PROTECTED] wrote: >Under Solaris 7, my code works fine. Under Linux, however, the RMI >Server Object's method is never gotten into; It's as if the suspended >thread blocks the object from all outside methods call. > >I've started both client and server using -green and turned off the JIT >

Re: RMI Activatable Object

1999-07-02 Thread Jim Hazen
I don't know what your code looks like, but you may need to carefully check your thread calls. As such fun calls as thread.suspend(), thread.stop(), etc are depricated in 1.2, and are almost guaranteed to break your app. Try looking at thread.wait() and thread.join() if you haven't already. -Ji