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.
-Jim
> Was wondering if any other Linux/Java developers have run into problems
> when developing RMI Objects. I have a Runnable, Activatable Object,
> which has been subclassed from an Activatable RMI Server Object. When
> instantiated, the RMI Server Object starts a thread and suspends it
> until one of it's methods is called from a remote client, at which time
> the thread is resumed.
>
> 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
> setting my JAVA_COMPILER=NONE environment variable.
>
> RedHat Linux 6.0
> glib2.1 jck1.2 rel2
>
> This appears to be a Java-on-linux bug.
>
> Thanks,
>
> James
>
> ----------------------------------------------------------------------
> 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]
