W3C home > Mailing lists > Public > www-jigsaw@w3.org > May to June 1998

problems starting jigadmin

From: Krishna Padmasola <pkrishna@cybercash.co.in>
Date: Fri, 29 May 1998 10:00:37 -0600
Message-Id: <199805291600.KAA10222@cashmail>
To: www-jigsaw@w3.org
Hi,

I downloaded 2.0b1 version of Jigsaw, and installed it.  After
starting JigSaw, I tried starting jigadmin and got a core dump.  I am
able to access http://localhost:8001/ but when I try to access
http://localhost:8009/, the browser displays a message saying "method
GET not implemented".

Here's is the output when I try running jigadmin---any ideas?  BTW, I
am on an intel solaris 2.6 platform.

% java org.w3c.jigadm.Main -root /fsys1/krishna/src/Jigsaw/Jigsaw http://localhost:8009
SIGSEGV   11*  segmentation violation
    si_signo [11]: SIGSEGV   11*  segmentation violation
    si_errno [0]: Error 0
    si_code [1]: SEGV_ACCERR [addr: 0x14]
 
        stackbase=8047828, stackpointer=80467B8
 
Full thread dump:
    "AWT-Motif" (TID:0xde7122a0, sys_thread_t:0x81786d8, state:CW, thread_t: t@8, sp:0xde0622b8 threadID:0xde062dd0, stack_base:0xde062db0, stack_size:0x21000) prio=5
        java.lang.Thread.run(Compiled Code)
    "AWT-Input" (TID:0xde712280, sys_thread_t:0x8173c20, state:MW, thread_t: t@7, sp:0xde0834f0 threadID:0xde085dd0, stack_base:0xde085db0, stack_size:0x21000) prio=5
    "AWT-EventQueue-0" (TID:0xde712250, sys_thread_t:0x815ebf0, state:CW, thread_t: t@6, sp:0xde1ab2e8 threadID:0xde1abdd0, stack_base:0xde1abdb0, stack_size:0x21000) prio=5
        java.lang.Object.wait(Compiled Code)
        java.awt.EventQueue.getNextEvent(Compiled Code)
        java.awt.EventDispatchThread.run(Compiled Code)
    "SIGQUIT handler" (TID:0xde700190, sys_thread_t:0x807c470, state:R, thread_t: t@5, sp:0xde3dbc68 threadID:0xde3dbdd0, stack_base:0xde3dbdb0, stack_size:0x21000) prio=0
    "Finalizer thread" (TID:0xde7000d0, sys_thread_t:0x807c408, state:CW, thread_t: t@4, sp:0xde3fea48 threadID:0xde3fedd0, stack_base:0xde3fedb0, stack_size:0x21000) prio=1
    "main" (TID:0xde7000a8, sys_thread_t:0x8074c28, state:R, thread_t: t@1, sp:0x804768c threadID:0x8049a50, stack_base:0x8047828, stack_size:0x848000) prio=5 *current thread*
        sun.awt.motif.MFramePeer.<init>(Compiled Code)
        sun.awt.motif.MToolkit.createFrame(Compiled Code)
        java.awt.Frame.addNotify(Compiled Code)
        java.awt.Window.show(Compiled Code)
        org.w3c.jigadm.gui.ServerBrowser.popupDialog(Compiled Code)
        org.w3c.jigadm.gui.ServerBrowser.<init>(Compiled Code)
        org.w3c.jigadm.gui.ServerBrowser.main(Compiled Code)
        org.w3c.jigadm.Main.main(Compiled Code)
Monitor Cache Dump:
    java.awt.EventQueue@DE712200/DE7ED578: <unowned>
        Waiting to be notified:
            "AWT-EventQueue-0"
    sun.awt.motif.MToolkit@DE7121B0/DE7ED428: owner "main" (0x8074c28, 1 entry)
        Waiting to acquire:
            "AWT-Input"
        Waiting to be notified:
            "AWT-Motif"
Registered Monitor Dump:
    PCMap lock: <unowned>
    Thread queue lock: <unowned>
    Name and type hash table lock: <unowned>
    String intern lock: <unowned>
    JNI pinning lock: <unowned>
    JNI global reference lock: <unowned>
    BinClass lock: <unowned>
    Class loading lock: <unowned>
    Java stack lock: <unowned>
    Code rewrite lock: <unowned>
    Heap lock: <unowned>
    Has finalization queue lock: <unowned>
    Finalize me queue lock: <unowned>
        Waiting to be notified:
            "Finalizer thread"
    Monitor cache expansion lock: <unowned>
    Monitor registry: owner "main" (0x8074c28, 1 entry)
Abort (core dumped)
Exit 134


--
Krishna Padmasola
pkrishna@cybercash.co.in
Received on Friday, 29 May 1998 00:30:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:27 GMT