From root@smadev.internal.net  Mon Aug 30 11:42:07 2004
Return-Path: <root@smadev.internal.net>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BF66116A4D0
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 30 Aug 2004 11:42:07 +0000 (GMT)
Received: from smadev.internal.net (host3.dynacom.ondsl.gr [62.103.35.211])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7BF9143D54
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 30 Aug 2004 11:42:06 +0000 (GMT)
	(envelope-from root@smadev.internal.net)
Received: from smadev.internal.net (localhost [127.0.0.1])
	by smadev.internal.net (8.13.1/8.13.1) with ESMTP id i7UBg4FL001422
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 30 Aug 2004 14:42:04 +0300 (EEST)
	(envelope-from root@smadev.internal.net)
Received: (from root@localhost)
	by smadev.internal.net (8.13.1/8.13.1/Submit) id i7UBg4iE001421;
	Mon, 30 Aug 2004 14:42:04 +0300 (EEST)
	(envelope-from root)
Message-Id: <200408301142.i7UBg4iE001421@smadev.internal.net>
Date: Mon, 30 Aug 2004 14:42:04 +0300 (EEST)
From: achill@matrix.gatewaynet.com
Reply-To: achill@matrix.gatewaynet.com
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: jdk 1.4.2-p6 jboss,eclipse problems
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         71146
>Category:       java
>Synopsis:       jdk 1.4.2-p6 jboss,eclipse problems
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-java
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug 30 11:50:22 GMT 2004
>Closed-Date:    Tue Dec 21 13:59:00 GMT 2004
>Last-Modified:  Sun Mar 17 04:55:19 UTC 2013
>Originator:     Achilleus Mantzios
>Release:        FreeBSD 5.3-BETA2 i386
>Organization:
Dynacom Tankers Mgmt.
>Environment:
System: FreeBSD smadev.internal.net 5.3-BETA2 FreeBSD 5.3-BETA2 #3: Sun Aug 29 12:26:27 EEST 2004 root@smadev.internal.net:/usr/obj/usr/src/sys/SMADEV2 i386


	
>Description:
	ktrace on jboss3.0.3 shows:
<lines skipped>
1259 java     RET   break 0
1259 java     PSIG  SIGBUS caught handler=0x2808f330 mask=0x4 code=0xc
1259 java     CALL  sigprocmask(0x1,0,0x805811c)
1259 java     RET   sigprocmask 0

and program stalls, with system showing 100% CPU usage.

ktrace on eclipse2 shows:
<lines skipped>
1294 eclipse  CALL  stat(0x804f000,0xbfbfebd0)
1294 eclipse  NAMI  "/usr/local/jdk1.4.2/bin/java"
1294 eclipse  RET   stat 0
1294 eclipse  CALL  break(0x8051000)
1294 eclipse  RET   break 0
1294 eclipse  CALL  fork
1294 eclipse  RET   fork 1295/0x50f
1294 eclipse  CALL  wait4(0xffffffff,0xbfbfec3c,0,0)

eclipse also stalls, and system showing 100% CPU usage.

>How-To-Repeat:
	Install the latest 1.4.2-p6 port in a 5.3-BETA2 system (RELENG_5),
	and try to run jboss or eclipse.
>Fix:

	no fix.

>Release-Note:
>Audit-Trail:

From: Charlie & <achill@matrix.gatewaynet.com>
To: freebsd-gnats-submit@FreeBSD.org, achill@matrix.gatewaynet.com
Cc:  
Subject: Re: java/71146: jdk 1.4.2-p6 jboss,eclipse problems
Date: Tue, 31 Aug 2004 12:57:25 +0300

 The problem with jboss3.0.3 seems to be of more
 general nature.
 Simply java -server dont seem to work.

From: Achilleus Mantzios <achill@matrix.gatewaynet.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc: freebsd-java@freebsd.org
Subject: Re: java/71146: jdk 1.4.2-p6 jboss,eclipse problems
Date: Tue, 31 Aug 2004 12:17:27 +0300 (EEST)

 It seems that the jboss issue is more general.
 -server does not work. (stalls consuming CPU cycles)
 Running jboss without -server seems to go ok.
 -- 
 -Achilleus
 

From: Achilleus Mantzios <achill@matrix.gatewaynet.com>
To: freebsd-gnats-submit@FreeBSD.org, <achill@matrix.gatewaynet.com>
Cc:  
Subject: java/71146
Date: Mon, 22 Nov 2004 11:51:03 +0200 (EET)

 It seems the bug is away in 5.3-STABLE.
 
 Should we close the bug?
 
 -- 
 -Achilleus
 
State-Changed-From-To: open->closed 
State-Changed-By: peadar 
State-Changed-When: Tue Dec 21 13:53:24 GMT 2004 
State-Changed-Why:  
Problem analysed, patch committed. Originator reports problem fixed. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=71146 
>Unformatted:

There were some problems related to interactions between gcc 3.4
and assumptions about enums in the JVM that caused some pretty major
problems with the 1.4 Server VM. These were addressed originally
in the port with patches, and have since been rolled into patchset
7.

This description of the problem is from Greg Lewis's commit of the
original patch from the port.

  The HotSpot code (ab)uses named enums as ints in a number of places.
  The problem with this is that according the the C++ spec, the compiler
  (essentially) only needs to use an integral type wide enough to hold
  the values defined in the enum.  Earlier versions of gcc appear to have
  just used an int whether they could have got away with a narrower type
  or not, hence the code worked as expected.  gcc 3.4 now appears to
  implement this part of the spec, so using an enum blindly as an int
  causes various problems due to overflow.
