Develop Reference

ibm java on rhel 7.4 is so slow

I am trying to install IBM Installation Manager(agent.installer.linux.gtk.x86_64_1.9.0.20190715_0328.zip) on Rhel 7.4 which is installed newly. I test the java because GUI is so slow and here are the result; as you can see oracle java dramaticly faster than IBM java!! why does this happen?
[root#adige bin]# uname -a
Linux adige 3.10.0-693.el7.x86_64 #1 SMP Thu Jul 6 19:56:57 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
[root#adige bin]# time /installations/unpacked/installationManagerX86_64_1.9/jre_8.0.5035.20190626_1229/jre/bin -version
java version "1.8.0_211"
Java(TM) SE Runtime Environment (build 8.0.5.35 - pxa6480sr5fp35-20190418_01(SR5 FP35))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190417_414854 (JIT enabled, AOT enabled)
OpenJ9 - 777635f
OMR - 16b77d7
IBM - 72459d3)
JCL - 20190409_01 based on Oracle jdk8u211-b25
real 0m20.185s <<<<<< Lasting 20 seconds.
user 0m0.169s
sys 0m0.034s
[root#adige bin]# time /tmp/java-8-oracle/jre/bin/java -version
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
real 0m0.098s
user 0m0.079s
sys 0m0.031s

That's very strange. real and user times would normally be very similar on a lightly loaded system. e.g.
$ time bin/java -version
java version "1.8.0_211"
Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled)
OpenJ9 - 46e57f9
OMR - 06a046a
IBM - 0b909bf)
JCL - 20190409_01 based on Oracle jdk8u211-b25
real 0m0.090s
user 0m0.093s
sys 0m0.012s
I've not heard of any similar issues with IBM Java on RHEL. Is there any possibility that the filesystem where /installations/unpacked/installationManagerX86_64_1.9 is mounted is having problems?

The problem caused by hostname is not in DNS records and /etc/hosts does not contain hostname. You can find the solution at this site. I did not link because ibm sunsetting community sites through developerworks.
https://www.ibm.com/developerworks/community/forums/html/topic?id=7becc2aa-6897-4d16-b696-dca2c9e767bf

Relationship between java memory allocation needs and available memory/swap

when starting a new java process we are getting an error which sounds like this:
"Could not reserve enough space for 16775168KB object heap"
Looking at the log file produced by JVM we see however the following:
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 32744 bytes for ChunkPool::allocate
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
At the same time at the bottom of the log file there is a statement:
Memory: 4k page, physical 67098420k(52119824k free), swap 86034256k(8132400k free)
vm_info: Java HotSpot(TM) 64-Bit Server VM (25.45-b02) for windows-amd64 JRE (1.8.0_45-b15), built on Apr 30 2015 12:40:44 by "java_re" with MS VC++ 10.0 (VS2010)
How can the java process fail to allocate 1GB of memory if at the same time there is a bigger amount of memory available for both the physical memory and the swap space?
Thanks a lot
Boris
Excerpt from the log file:
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 32744 bytes for ChunkPool::allocate
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (allocation.cpp:273), pid=17164, tid=21188
#
# JRE version: Java(TM) SE Runtime Environment (8.0_45-b15) (build 1.8.0_45-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.45-b02 mixed mode windows-amd64 compressed oops)
# Failed to write core dump.
#
...
VM Arguments:
java_command: com.uniper.rest.bridge.ExternalBridge -Xmx128m
java_class_path (initial): D:\Progs\ENDUR-~1\EN57BD~1\bin\otk\openjvs...
Launcher Type: SUN_STANDARD
Environment Variables:
JAVA_HOME=D:\Progs\Endur-64bit\Endur_V15_0_05052016EON_07072016_1104\bin\olf_dependencies\java\jdk1.8.0_45\
...
--------------- S Y S T E M ---------------
OS: Windows Server 2008 R2 , 64 bit Build 7601 (6.1.7601.23807)
CPU:total 8 (4 cores per cpu, 2 threads per core) family 6 model 26 stepping 5, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, ht, tsc, tscinvbit, tscinv
Memory: 4k page, physical 67098420k(52119824k free), swap 86034256k(8132400k free)
vm_info: Java HotSpot(TM) 64-Bit Server VM (25.45-b02) for windows-amd64 JRE (1.8.0_45-b15), built on Apr 30 2015 12:40:44 by "java_re" with MS VC++ 10.0 (VS2010)

Eclipse and Intellij keeps crashing with EXCEPTION_ACCESS_VIOLATION

Update: The same problem seems to occur in Intellij as well.
My eclipse installation keeps crashing without warning. The window will just suddenly close at random points.
An error log is sometime produced. An example of this is below (the message varies)
I had a few issues with crashes during the eclipse installation. I've reinstalled java (8) and eclipse, even gone to a fresh windows install (this just changed the error messages)
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000003bd0248, pid=3780, tid=0x0000000000000718
#
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# J 8164 C1 org.eclipse.emf.ecore.util.EcoreUtil$Copier.copy(Lorg/eclipse/emf/ecore/EObject;)Lorg/eclipse/emf/ecore/EObject; (139 bytes) # 0x0000000003bd0248 [0x0000000003bcf3c0+0xe88]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
--------------- T H R E A D ---------------
Current thread (0x00000000025d0800): JavaThread "main" [_thread_in_Java, id=1816, stack(0x0000000000050000,0x0000000000150000)]
siginfo: ExceptionCode=0xc0000005, reading address 0x00000000000003c1
Registers:
RAX=0x0000000000000000, RBX=0x000000001dd15fb8, RCX=0x000000000000047d, RDX=0x00000001003ae698
RSP=0x000000000014df30, RBP=0x000000001f727c40, RSI=0x00000000c1668a48, RDI=0x0000000000000001
R8 =0x000000001f727c40, R9 =0x0000000000000320, R10=0x0000000000000000, R11=0x0000000000000000
R12=0x0000000000000000, R13=0x000000010038d100, R14=0x000000000014de18, R15=0x00000000025d0800
RIP=0x0000000003bd0248, EFLAGS=0x0000000000010212
And another:
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006ce0c220, pid=7156, tid=0x00000000000015a0
#
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [MSVCR100.dll+0x3c220]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
--------------- T H R E A D ---------------
Current thread (0x0000000017f4b000): JavaThread "C1 CompilerThread1" daemon [_thread_in_vm, id=5536, stack(0x00000000189d0000,0x0000000018ad0000)]
siginfo: ExceptionCode=0xc0000005, reading address 0x000000002234fff8
Registers:
RAX=0x0000000000000027, RBX=0x0000000018acf968, RCX=0x000000002eca5910, RDX=0xfffffffff36aa6f0
RSP=0x0000000018aced48, RBP=0x00000000005aff00, RSI=0x000000001cd1fdc0, RDI=0x0000000021e25640
R8 =0x000000000052af00, R9 =0x0000000021fe9c00, R10=0x0000000000002000, R11=0x000000002e77b050
R12=0x00000000005aff00, R13=0x00000000000000b8, R14=0x000000001cd1fb70, R15=0x0000000000000000
RIP=0x000000006ce0c220, EFLAGS=0x0000000000010206
The system info contains
--------------- S Y S T E M ---------------
OS: Windows 10.0 , 64 bit Build 15063 (10.0.15063.0)
CPU:total 3 (3 cores per cpu, 1 threads per core) family 16 model 5 stepping 3, cmov, cx8, fxsr, mmx, sse, sse2, sse3, popcnt, mmxext, 3dnowpref, lzcnt, sse4a, tsc, tscinvbit, tscinv
Memory: 4k page, physical 8386740k(6510284k free), swap 10352820k(8395928k free)
vm_info: Java HotSpot(TM) 64-Bit Server VM (25.121-b13) for windows-amd64 JRE (1.8.0_121-b13), built on Dec 12 2016 18:21:36 by "java_re" with MS VC++ 10.0 (VS2010)
And a third
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ILLEGAL_INSTRUCTION (0xc000001d) at pc=0x000000000276703f, pid=11876, tid=0x0000000000002e68
#
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# J 32 C1 sun.misc.FDBigInteger.trimLeadingZeros()V (57 bytes) # 0x000000000276703f [0x0000000002766f00+0x13f]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
--------------- T H R E A D ---------------
The workspace log contains repeated:
!ENTRY org.eclipse.egit.ui 2 0 2017-04-11 18:19:39.359
!MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git
user global configuration and to define the default location to store repositories: 'C:\Users\gardi'. If this is
not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and
EGit might behave differently since they see different configuration options.
This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
!SESSION 2017-04-11 18:40:15.939 -----------------------------------------------
eclipse.buildId=4.6.3.M20170301-0400
java.version=1.8.0_121
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Framework arguments: -product org.eclipse.epp.package.java.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product
!ENTRY org.eclipse.egit.ui 2 0 2017-04-11 18:40:39.941
!MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git
user global configuration and to define the default location to store repositories: 'C:\Users\gardi'. If this is
not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and
EGit might behave differently since they see different configuration options.
This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
Contents of eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.3.201.v20161025-1711.jar
--launcher.library
C:\Users\gardi\.p2\pool\plugins\org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.401.v20161122-1740
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.8
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
-Declipse.p2.max.threads=10
-Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest
-Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/
Update:
Tried solution from Eclipse EXCEPTION_ACCESS_VIOLATION crash with no luck.

Check /.metadata/.log and post logged messages
Navigate to a hidden directory in your Eclipse Workspace named .metadata, delete it, and start eclipse. Files in the .metadata directory seem to cause recurrent problems once Eclipse begins to crash.
If this does not help, update the question with your eclipse.ini file containts

Multithreaded Java Application uses only one core and gets stuck

We are running a multithreaded java application in a Linux environment (vm). We have 30 cores. Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Linux version 2.6.32-279.5.1.el6.x86_64 (mockbuild#x86-004.build.bos.redhat.com) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Tue Jul 24
13:57:35 EDT 2012
We are running our application inside Tomcat (7.0.42)
What we see is that sometimes only one of the processors gets used around 100% and in those situations the application becomes non responsive and needs to be restarted, the rest of the cores appear to be completely idle, while one of them seems to be intensively used.
We got a few thread dumps (we had to get them using kill -3 as jstack was getting connection errors), although they don’t show any obvious deadlock or issue.
When the application becomes non responsive we can’t attach to it using visual vm or jconsole.
We checked this article in java-monitor.com http://java-monitor.com/forum/showthread.php?t=317
In a couple of cases, we observed this behaviour within minutes of restart.
Following some of the instructions provided below, we identified the thread that was using the CPU, it was the "VM thread".
We updated the jvm to the lastest available version:
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)
Since then we haven't been able to see the issue, again, although in some cases it previously took weeks to appear.
A couple of times during the last months we also got the below message after a few minutes of restarting our application
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fbe71501d19, pid=18022, tid=139946328471296
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 )
# Problematic frame:
# J java.lang.management.ThreadInfo.<init>(Ljava/lang/Thread;ILjava/lang/Object;Ljava/lang/Thread;JJJJ[Ljava/lang/StackTraceElement;[Ljava/lang/Object;[I[Ljava/lang/Object;)V
#
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#
on a different case:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f1c2f0debec, pid=16493, tid=139756998551296
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 )
# Problematic frame:
# V [libjvm.so+0x756bec] PhaseIdealLoop::build_loop_late_post(Node*)+0x13c
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#
I would appreciate any idea or suggestion.
Thanks in advance.

Matlab:fatal error on Java Runtime Environment

I just download the matlab 2013b and once I start it,
it will automatically close once the main interface have been loaded.
In the workspace of Matlab, i find a log file and is posted below with only the infomation i believe is important.
I have tried to search for some information ,updated my java to the latest version, and re-install the whole matlab, even uninstall the older version
but all seem do nothing on the error, what would be the possible solution?
Thank in advances.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000770f004f, pid=9108, tid=5584
#
# JRE version: 7.0_11-b21
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C 0x00000000770f004f
[error occurred during error reporting (printing problematic frame), id 0xc0000005]
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--------------- T H R E A D ---------------
Current thread (0x0000000064006800): JavaThread "FileDecorationCache request queue" daemon [_thread_in_native, id=5584, stack(0x0000000100000000,0x0000000104000000)]
siginfo: ExceptionCode=0xc0000005, reading address 0x0000000003ffd5d0
> --------------- S Y S T E M ---------------
>
> OS: Windows 7 , 64 bit Build 7601 Service Pack 1
>
> CPU:total 4 (2 cores per cpu, 2 threads per core) family 6 model 42
> stepping 7, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1,
> sse4.2, popcnt, avx, ht, tsc, tscinvbit
>
> Memory: 4k page, physical 6127920k(3409508k free), swap
> 12253980k(9240140k free)
>
> vm_info: Java HotSpot(TM) 64-Bit Server VM (23.6-b04) for
> windows-amd64 JRE (1.7.0_11-b21), built on Jan 12 2013 02:38:42 by
> "java_re" with unknown MS VC++:1600
>
> time: Wed Apr 23 18:14:36 2014 elapsed time: 83 seconds

Found A solution from another site.
The problem can be solved by disable your anti-virus software.
In my case, I am using avast, and once your disable it, there will be no more error

I had the same problem. I confirm the origin of the problem.
I work with Matlab2010a, Windows 10 (64 bits) and Kapersky.
I disabled the antivirus and it works.
Cheers