Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 380441 - jconsole (JRE 6.0_22-b22) crashes (SIGSEGV) in IcedTea6 1.10.3
Summary: jconsole (JRE 6.0_22-b22) crashes (SIGSEGV) in IcedTea6 1.10.3
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Java (show other bugs)
Hardware: x86 Linux
: Normal major (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: icedtea-tracker
  Show dependency tree
 
Reported: 2011-08-24 07:18 UTC by dio
Modified: 2015-08-21 07:23 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Error log (hs_err_pid17621.log,34.65 KB, text/plain)
2011-08-24 07:18 UTC, dio
Details
emerge --info (emerge.info,4.94 KB, text/plain)
2011-08-24 18:19 UTC, dio
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dio 2011-08-24 07:18:02 UTC
Created attachment 284439 [details]
Error log

$ jconsole localhost:8161
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xb773c3cf, pid=17621, tid=2079648624
#
# JRE version: 6.0_22-b22
# Java VM: OpenJDK Server VM (20.0-b11 mixed mode linux-x86 )
# Derivative: IcedTea6 1.10.3
# Distribution: Built on Gentoo Base System release 2.0.2 (Fri Jul 22 15:18:18 CEST 2011)
# Problematic frame:
# C  [libz.so.1+0xc3cf]  inflate+0x2003
#
# An error report file with more information is saved as:
# /opt/apache-activemq-5.5.0/hs_err_pid17621.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
#   http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted
Comment 1 Alistair Bush (RETIRED) gentoo-dev 2011-08-24 08:29:46 UTC
Are there any more details that you can provide.

I was unable to reproduce this using tomcat-6 with a non-ssl unauth'd jconsole connection on 8081.

$ java -version
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.3) (Gentoo build 1.6.0_22-b22)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
Comment 2 dio 2011-08-24 18:19:23 UTC
Created attachment 284511 [details]
emerge --info
Comment 3 dio 2011-08-24 18:19:43 UTC
(In reply to comment #1)
> Are there any more details that you can provide.
> 
> I was unable to reproduce this using tomcat-6 with a non-ssl unauth'd jconsole
> connection on 8081.

> $ java -version
> java version "1.6.0_22"
> OpenJDK Runtime Environment (IcedTea6 1.10.3) (Gentoo build 1.6.0_22-b22)
> OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)

• Sorry, my fault: this is a 32-bit linux.  I have changed this bug report to x86 platform.
• Java version is the same here (except for the 64-Bit [of course]):
  $ java -version
  java version "1.6.0_22"
  OpenJDK Runtime Environment (IcedTea6 1.10.3) (Gentoo build 1.6.0_22-b22)
  OpenJDK Server VM (build 20.0-b11, mixed mode)
• I'm trying to connect to a running Apache ActiveMQ server.  While port 8161 is the HTTP port and certainly ill-suited, all other ports the ActiveMQ offers (61616 and 54231) crash with the same SIGSEGV.
• I also tried connecting via PID:
  $ jconsole 17133
  This hangs forever (at least for the 15 minutes I gave it).
• I also tried invoking the jconsole w/o arguments and then connect to the process in the offered connection list.  This hangs forever, too.  Probably connects via PID, as well.

• Furthermore, I tried to connect to a java proxy server running in a JMX enabled JVM (java -Dcom.sun.management.jmxremote \
 -Dcom.sun.management.jmxremote.port=12345 \
 -Dcom.sun.management.jmxremote.authenticate=false \
 -Dcom.sun.management.jmxremote.ssl=false \
 -jar ~/projects/eclipse/workspace/AuthProxy/auth-proxy.jar
• I get the same result (Segmentation Violation when connecting through localhost:12345, and infinite hangup when connecting via PID).

• i have successfully updated my system (“emerge -uND world; emerge --depclean; revdep-rebuild; python-updater”) just a day or two ago.  Attached you will find my “emerge --info” now.
Comment 4 James Le Cuirot gentoo-dev 2015-07-19 10:32:29 UTC
I'd be very surprised if this is still an issue. Please reopen with fresh details if so.
Comment 5 Patrice Clement gentoo-dev 2015-08-21 07:23:29 UTC
Marking this bug as FIXED.