[Karate][Standalone] Error - JavaFX Error [duplicate] - karate

This question already has answers here:
Test Framework quit unexpectedly - karate test
(4 answers)
Closed 1 year ago.
I have just started playing with Karate for API testing for one of my project written in golang. I have downloaded the standalone jar as mentioned in the docs. I am getting jfx error one after the other.
java --version
openjdk version "11.0.6" 2020-01-14
OpenJDK Runtime Environment (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1)
OpenJDK 64-Bit Server VM (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1, mixed mode, sharing)
On first run I get below error
java.lang.RuntimeException: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found
I checked on the internet and found error is related to openjfx and hence installed the same. And now I am getting below error
java.lang.ClassNotFoundException: com.sun.prism.es2.X11GLFactory
I am not sure If there is something missing on the platform or I am making some mistake.

Can you use the very latest version of Karate, we removed the JavaFX dependency in version 0.9.5 onwards.

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.

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

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

Boot layer initialization error when running RinSim examples on IntelliJ Idea

I'm trying to get some RinSim examples running on IntelliJ Idea Ultimate 2018.1.4. I've tried following the instructions on http://rinsim.rinde.nl/installation/intellij/, but I run into the following error when performing step 11 in the guide:
Error occurred during initialization of boot layer
java.lang.module.FindException: Unable to derive module descriptor for /home/svka/.m2/repository/org/jppf/jppf-client/4.1.3/jppf-client-4.1.3.jar
Caused by: java.lang.module.InvalidModuleDescriptorException: Provider class org.jppf.server.scheduler.bundle.providers.RLBundlerProvider not in module
The JDK I'm using is:
openjdk 10.0.1 2018-04-17
OpenJDK Runtime Environment (build 10.0.1+10-Ubuntu-3ubuntu1)
OpenJDK 64-Bit Server VM (build 10.0.1+10-Ubuntu-3ubuntu1, mixed mode)
JRE: 1.8.0_152-release-1136-b39 amd64
Furthermore, I'm on Kubuntu 18.04.
The example runs on Eclipse, so I suppose there is something wrong with some settings in IntelliJ or something similar, but I have no clue on what to look for and can't find any similar posts by googling. Any help or pointers would be greatly appreciated.

Failed to create Library in intelliji when configuring groovy sdk [duplicate]

This question already has answers here:
IntelliJ IDEA won't load Groovy found on my disk
(4 answers)
Closed 5 years ago.
Intelliji Version: 2017.1
Groovy version : 2.4.10 (zip file from official website)
Got following error in intelliji when configuring groovy library.
switched to 2.4.8 solved my problem, seems like intelliji doesn't support the latest version of groovy

"Unsupported major.minor version 51.0" in Netbeans

I know that the title is almost identical to other questions, but, I've not been able to resolve my problem with those answers.
This is the problem:
I have 2 almost identical projects (one has been cloned from the other with mercurial) and some changes have been made.
After the last pull from the original project, the following error appears when I try to run the project. I know that means that the project is being compiled with java7 and run with java6.
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/[...]/Start : Unsupported major.minor version 51.0
The original project keeps running normally.
It runs if I change the Java Platform in the project properties to java7, but I need the project to run on java6, so that's not an option.
Product Version: NetBeans IDE 7.2 (Build 201207171143)
Java: 1.6.0_35; Java HotSpot(TM) 64-Bit Server VM 20.10-b01
System: Linux version 3.2.0-32-generic running on amd64; UTF-8; en_US (nb)
Thanks for your help!
You can add more than 1 jdk to your environment and you can decide which one to use. try to add the jdk 6 and compile it based on that.