Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Sep 2005 15:38:31 -0600
From:      Greg Lewis <glewis@eyesbeyond.com>
To:        "Georg-W. Koltermann" <gwk@rahn-koltermann.de>
Cc:        freebsd-java@freebsd.org
Subject:   Re: cant get javaws to start up with jdk1.5p2, also plugin problems
Message-ID:  <20050923213831.GA14819@misty.eyesbeyond.com>
In-Reply-To: <1127504815.1265.28.camel@localhost.eu.mscsoftware.com>
References:  <1127504815.1265.28.camel@localhost.eu.mscsoftware.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 23, 2005 at 09:46:55PM +0200, Georg-W. Koltermann wrote:
> from a freshly installed jdk1.5p2 as of today on FreeBSD 5.4 I get:
> 
>         hunter[12]$ echo $JAVA_HOME
>         /usr/local/jdk1.5.0
>         hunter[13]$ $JAVA_HOME/jre/bin/javaws
>         Java Web Start splash screen process exiting ...
>         Bad installation. No JRE found in configuration file: Illegal byte sequence
>         hunter[14]$
> 
> Any idea on how to proceed?

So here is the problem with Java Web Start.  Basically I don't know how
to use it, so it gets next to no testing unless someone else tests it.
I'd greatly appreciate it if someone could point me at some documentation
or, even better, give me some examples I could test it with.  All I did
for it was forward port the patches from 1.4.2 and made it compile.  I
assumed that made it work since as I mentioned above I don't know how to
test it.

> Also when I symlink the new libjavaplugin_oji.so
> into /usr/X11R6/lib/browser_plugins and navigate to my favorite applet
> (an internal host), I get a java core dump:
> 
>         #
>         # An unexpected error has been detected by HotSpot Virtual Machine:
>         #
>         #  SIGSEGV (0xb) at pc=0x35bbb4c8, pid=63950, tid=0x8504800
>         #
>         # Java VM: Java HotSpot(TM) Client VM (1.5.0-p2-gwk_23_sep_2005_14_20 mixed mode)
>         # Problematic frame:
>         # C  [libmawt.so+0xd84c8]  processTree+0x284
>         #
>         
>         ---------------  T H R E A D  ---------------
>         
>         Current thread (0x08504600):  JavaThread "AWT-Motif" daemon [_thread_in_native,
>         id=139479040]
>         
>         siginfo:si_signo=11, si_errno=0, si_code=12, si_addr=0x00000800
>         
>         Registers:
>         EAX=0x084ea400, EBX=0x35d20b88, ECX=0x00000000, EDX=0x00000800
>         ESP=0xbf8a4428, EBP=0xbf8a4470, ESI=0x086ce860, EDI=0x00000000
>         EIP=0x35bbb4c8, EFLAGS=0x00010206
>         
>         Top of Stack: (sp=0xbf8a4428)
>         0xbf8a4428:   00000001 285b4414 08504600 35ba8f6b
>         0xbf8a4438:   00000001 28073c00 00000000 00000800
>         0xbf8a4448:   086ce860 00000000 00000000 00000000
>         0xbf8a4458:   00000004 085046bc 00504600 35d20b88
>         0xbf8a4468:   285a7820 08504600 bf8a4700 35baa991
>         0xbf8a4478:   084f8400 00000000 00000000 35baa3ff
>         0xbf8a4488:   00000003 084b8f40 bf8a44c0 00000001
>         0xbf8a4498:   086ce210 086cd600 bf8a44c0 35c5b49f
>         
>         Instructions: (pc=0x35bbb4c8)
>         0x35bbb4b8:   8b 45 d0 8d 0c 85 00 00 00 00 8b 55 d4 8b 04 37
>         0x35bbb4c8:   3b 04 11 75 13 8b 45 e8 48 3b 45 d0 75 05 e9 b9
>         
>         Stack: [0xbf865000,0xbf8a5000),  sp=0xbf8a4428,  free space=253k
>         Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
>         C  [libmawt.so+0xd84c8]  processTree+0x284
>         C  [libmawt.so+0xc7991]  shellEH+0x5a1
>         C  [libmawt.so+0xc57fe]  awt_util_processEventForEmbeddedFrame+0x9a
>         C  [libmawt.so+0xa8f51]  isFocusableWindow+0x1d5
>         C  [libmawt.so+0xa7f8b]  set_toolkit_busy+0x317
>         C  [libmawt.so+0xaa7bc]  Java_sun_awt_motif_MToolkit_run+0x44
>         j  sun.awt.motif.MToolkit.run()V+0
>         j  java.lang.Thread.run()V+11
>         ...

Rainer Alves posted the same stack trace a few days ago.  His occurred
with Firefox.  Out of interest, are you using Firefox or Mozilla?  Does
the behaviour change if you switch browsers?  The plugin works for me
with Firefox (or did last time I tried it) and I've had reports of others
using it successfully too, so I'm not sure what the problem is at the
moment.

-- 
Greg Lewis                          Email   : glewis@eyesbeyond.com
Eyes Beyond                         Web     : http://www.eyesbeyond.com
Information Technology              FreeBSD : glewis@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050923213831.GA14819>