Hello ,

 I need some help  getting the jini kit working on Linux.
I am trying to get jini working on Linux before switching to other
platforms.
 I have the alternative of using Solarisx86 or NT,but  I  want to do
some research before I do that.

In short I tried it and doesn' t  work

here  is my configuration :

   1-  Suse 6.2  ie. glibc2.1
    2- jdk1.2-pre-v2 from blackdown
    3-  reading the bugs' list on blackdown web page I decided to use
THREADS_FLAG=green


 These are the  Results:

        1- with this settings  -green flags the example hangs ( no
output
               java -cp jini-examples.jar
com.sun.jini.example.service.StartService
        2 - with native threads this one works fine except when the GC
thread kicks in  I get

SIGSEGV   11*  segmentation violation
        stackpointer=0xbedff844

Full thread dump Classic VM (Linux_JDK_1.2_pre-release-v2, native
threads):
    "GC Daemon" (TID:0x4037b2a8, sys_thread_t:0x81f0248, state:R, native
ID:0x18
07) prio=2
        at java.lang.Runtime.gc(Native Method)
        at java.lang.System.gc(Compiled Code)
        at sun.misc.GC$Daemon.run(Compiled Code)
    "RMI Reaper" (TID:0x4037b390, sys_thread_t:0x8215418, state:CW,
native ID:0x
1406) prio=5
        at java.lang.Object.wait(Native Method)
        at java.lang.ref.ReferenceQueue.remove(Compiled Code)
        at java.lang.ref.ReferenceQueue.remove(Compiled Code)
        at sun.rmi.transport.ObjectTable$Reaper.run(Compiled Code)
        at java.lang.Thread.run(Compiled Code)
    "RMI TCP Accept-1" (TID:0x40377bd0, sys_thread_t:0x81b0930, state:R,
native
ID:0x1005) prio=5
        at java.net.SocketInputStream.socketRead(Native Method)
        at java.net.SocketInputStream.read(Compiled Code)
        at java.io.BufferedInputStream.fill(Compiled Code)
        at java.io.BufferedInputStream.read(Compiled Code)
        at sun.rmi.transport.proxy.HttpAwareServerSocket.accept(Compiled
Code)
        at sun.rmi.transport.tcp.TCPTransport.run(Compiled Code)
        at java.lang.Thread.run(Compiled Code)
    "Finalizer" (TID:0x4036f320, sys_thread_t:0x80cd088, state:CW,
native ID:0xc
04) prio=8
        at java.lang.Object.wait(Native Method)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:112)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
        at
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:174)
    "Reference Handler" (TID:0x4036f3b0, sys_thread_t:0x80c88d0,
state:CW, nativ
e ID:0x803) prio=10
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:424)
        at
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:114)
    "SIGQUIT handler" (TID:0x4036f3e0, sys_thread_t:0x80c1368, state:R,
native I
D:0x402) prio=5
    "main" (TID:0x4036f1e0, sys_thread_t:0x804ca70, state:MW, native
ID:0x400) p
rio=5
        at java.lang.ClassLoader.findNative(Compiled Code)

   [... etc]
  I suppose  this is the bug mentioned  on blackdown page.

 3- if running still with native threads   the jini client  (with green
this one also hangs)
        I am getting:

        java.lang.reflect.InvocationTargetException:
java.net.SocketException: error set
ting options
        at java.net.PlainDatagramSocketImpl.join(Native Method)
        at java.net.MulticastSocket.joinGroup(Compiled Code)
        at
net.jini.discovery.LookupDiscovery$AnnouncementListener.<init>(Compil
ed Code)
        at net.jini.discovery.LookupDiscovery$3.run(Compiled Code)
        at java.security.AccessController.doPrivileged(Native Method)
        at net.jini.discovery.LookupDiscovery.<init>(Compiled Code)
        at com.sun.jini.example.browser.Browser.<init>(Compiled Code)
        at java.lang.reflect.Constructor.newInstance(Native Method)
        at com.sun.jini.example.browser.Browser.main(Compiled Code)
        at com.sun.jini.example.browser.Browser.main(Compiled Code)


 Any help would be  appreciated,

Thanks
 Bogdan






----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to