A fatal error has been detected by the Java Runtime Environment: SIGBUS while installing ZAP proxy in parrot home OS - jvm

I was trying to install the ZAP proxy in my parrot home OS, but I'm unable to install it and the error that I'm receiving in the terminal is as follows:
(A fatal error has been detected by the Java Runtime Environment:
SIGBUS (0x7) at pc=0x00007f904544b12f, pid=6446, tid=6447JRE version: OpenJDK Runtime
Environment (11.0.5+10) (build 11.0.5+10-post-Debian-2)
Java VM: OpenJDK 64-Bit Server VM (11.0.5+10-post-Debian-2, mixed mode, sharing, tiered,
compressed oops, g1 gc, linux-amd64)
Problematic frame:
V [libjvm.so+0xcce12f]
No core dump will be written. 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:
(https://bugs.debian.org/openjdk-11)
Aborted

This error message...
(A fatal error has been detected by the Java Runtime Environment:
SIGBUS (0x7) at pc=0x00007f904544b12f, pid=6446, tid=6447JRE version: OpenJDK Runtime
Environment (11.0.5+10) (build 11.0.5+10-post-Debian-2)
Java VM: OpenJDK 64-Bit Server VM (11.0.5+10-post-Debian-2, mixed mode, sharing, tiered,
compressed oops, g1 gc, linux-amd64)
Problematic frame:
V [libjvm.so+0xcce12f]
...implies that the V frame was the Problematic frame which crashed which resulted in libjvm.so file.
The crash you observed is possibly not a zap or java issue but a debian issue.
Deep Dive
However as per the documentation in What versions of Java are supported? page, ZAP should be able to run with all/newer Java versions, but might require a minimum for certain ZAP versions:
ZAP 2.7.0 and later requires a minimum of Java 1.8
ZAP 2.0.0 and later requires a minimum of Java 1.7
Previous versions of ZAP also support Java 1.6, the last of those being 1.4.1
Additionally, as per the documentation in Download ZAP page:
The Windows and Linux versions require Java 8 or higher to run.
The macOS version includes Java 8 - you can use the Linux or Cross Platform versions if you do not want to download this.
Finally, as per the documentation in Release 2.9.0 page:
This is a bug fix and enhancement release, which requires a minimum of Java 8. Note that a minimum of Java 11 is recommended, especially for high DPI displays.
References
You can find a couple of relevant discussions in:
Jvm crash :fatal error has been detected by the Java Runtime Environment
“A fatal error has been detected by the Java Runtime Environment” when running java project on another computer
A fatal error has been detected by the Java Runtime Environment (SIGBUS (0x7))
JVM crashes with problematic frame [libjvm.so+0x7f582e] PerfLongVariant::sample()+0x1e

Related

How to change log4j version in Mule Runtime

I want to change log4j version from 2.8.2 to 2.17.2 for fix vulnerable. I have changed the jars underneath of mule-enterprise-standalone-3.9.4\lib\boot but i am getting below error.
Please advise what else need to to changed.
I have added below jars though i'm getting below error.
log4j-slf4j-impl-2.17.2 ,
log4j-jul-2.17.2 ,
log4j-jcl-2.17.2 ,
log4j-api-2.17.2 ,
log4j-1.2-api-2.17.2
I have referenced the question : log4j2 for MULE 3 CE patch update
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=1024m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: Using the ParNew young collector with the Serial old collector is deprecated and will likely be removed in a future release
Exception in thread "main" java.lang.NoSuchMethodError: com.lmax.disruptor.dsl.Disruptor.<init>(Lcom/lmax/disruptor/EventFactory;ILjava/util/concurrent/ThreadFactory;Lcom/lmax/disruptor/dsl/ProducerType;Lcom/lmax/disruptor/WaitStrategy;)V
at org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor.start(AsyncLoggerConfigDisruptor.java:212)
at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:303)
at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:137)
at org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:55)
at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:47)
at org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:33)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
at org.mule.module.boot.LicenseKeyHandler.<clinit>(LicenseKeyHandler.java:23)
at org.mule.module.reboot.MuleContainerBootstrap.handleLicenseKey(MuleContainerBootstrap.java:221)
at org.mule.module.reboot.MuleContainerBootstrap.main(MuleContainerBootstrap.java:69)
JVM exited while loading the application.
Mule versions are developed with a specific log4j2 target version. Changing the version directly can lead to unpredictably errors like you are experiencing. To avoid the vulnerabilities in log4j2 without having compatibility issues you need to follow the instructions in MuleSoft Help Center that are available to Enterprise Edition customers. Note that the version that you are using is an Enterprise Edition release, not a Community Edition release. Alternatively downloading the last released build for your version may already incorporate the patches to fix the vulnerabilities. Although I would recommend to use Mule 3.9.5 since it is the final release of Mule 3.x and has additional bug fixes compared to 3.9.4.

Is worklight working on windows 10 enterprise

Is worklight working on windows 10 enterprise for any one?
When I try to start Mobile first development server, I get this error:
Error occurred during initialization of VM
agent library failed to init: jdwp
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options.
Java 1.8 is not supported in MobileFirst Platform Foundation 6.3.
Downgrade to Java 1.6 or 1.7 and try again.

Red5: Error: Could not find or load main class org.red5.server.Bootstrap

I am doing a red5 eclipse integration using the following directions:
https://docs.google.com/document/d/1GncMDOEeUSyWxm6OM1Cedtl6BeJ2ppU-J-TIIKODreo/edit#heading=h.crcr7jpvtmhj
Versions: java8
Red5: 1.0.2-RC4
When I am starting the red5-server as java application debug, it is working fine
But on starting the server in the last step I am getting the following error
Running on Linux
Starting Red5
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option UseStringCache; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: Using the ParNew young collector with the Serial old collector is deprecated and will likely be removed in a future release
Listening for transport dt_socket at address: 8787
Error: Could not find or load main class org.red5.server.Bootstrap
Build and / or use the tarball or zip file; extract the jars and you'll have a server jar and another jar containing the bootstrap class. For version 1.0.2 I believe it will be named red5-bootstrap.jar; the sh and bat files will contain the correct jar file paths.

Titanium appcelerator close automatically

2 days ago I had installed Titanium Appcelerator 3.1 and today I installed android sdk 2.2 and 4.2, But now after starting my Titanium, it gets automatically closes after few minutes and showing some java related error.
My system configurations :
Ubuntu 12.04
64 bit java 1.6.0_27
Titanium 3.1
Android sdk 2.2 and 4.2
4 GB RAM
Please find the error log below
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007f29fb86f757, pid=2889, tid=139818259298048
JRE version: 6.0_27-b27
Java VM: OpenJDK 64-Bit Server VM (20.0-b12 mixed mode linux-amd64 compressed oops)
Derivative: IcedTea6 1.12.3
Distribution: Ubuntu 12.04 LTS, package 6b27-1.12.3-0ubuntu1~12.04.1
Problematic frame:
V [libjvm.so+0x588757] klassVtable::oop_follow_contents()+0xd7
You have the wrong JDK. You need to use the OracleJDK as specified here.

No unprofiled JVM found

I have WebSphere 7 Aplication Server. There is Java VM 1.6 installed. Linux.
Java version "1.6.0"
Java(TM) SE Runtime Environment (build pxa6460sr10fp1-20120321_01(SR10 FP1))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr10fp1-20120202_101568 (JIT enabled, AOT enabled)
J9VM - 20120202_101568
JIT - r9_20111107_21307ifx1
GC - 20120202_AA)
JCL - 20120320_01
I try to use jProfiler, using trial lisence. But don't want to change something on the server this time.
So I download jprofiler for linux to my server.
Then I run bin/jpenable and it says that:
No unprofiled JVM found
Now I don't know what to do, googling doesn't give any useful result. Can You tell me in what way I must search a problem? May be incorrect path or something else. I hope You'll understand my english (it is not so good).
Have a look at this help pdf, in specifically check out Attach to local JVM session.
Also, have a look at this answer and this question.
hope it will help..