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.
Related
I have a problem starting glassfish on Mac Os X 10.14.6.
I installed it with
brew install glassfish
then I added
AS_JAVA="/Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home"
in asenv.conf in order to solve a java null pointer exception.
and now I receive the following error:
$ ./asadmin start-domain domain1
Waiting for domain1 to start .Error starting domain domain1.
The server exited prematurely with exit code 1.
Before it died, it produced the following output:
-Djava.endorsed.dirs=/usr/local/Cellar/glassfish/5.1.0/libexec/glassfish/modules/endorsed:/usr/local/Cellar/glassfish/5.1.0/libexec/glassfish/lib/endorsed is not supported. Endorsed standards and standalone APIs
in modular form will be supported via the concept of upgradeable modules.
Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Command start-domain failed.
Does anyone know how to solve this issue?
The endorsed directories have been removed since Java 9. So the error message suggests that you are running with at least Java 9.
You need to use Java 8 for this to work. If I remember correctly then Glassfish does not support Java 9 and higher.
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
My setup
MobileFrist Platform foundation 6.3.0.00-20141127-1357
WebSphere Application Server 8.5.5.0 (1.0.3.20130510-0831)
on Java HotSpot(TM) 64-Bit Server VM, version 1.7.0_75-b13 (en_US)
hosted on softlayer
Installed using this knowledge center guide for 6.3
after starting the server I can visit my appcenterconsole fine.
I have 2 issues now that I can't seem to understand:
Firstly, tried to build the Myproject.war file using MFP cli to deploy the server configuration tool. However Mfp build produced all the .wlapps but no war file. Can I build a .war file using mfp build?
Secondly, built the .war file using eclipse on my local machine tried to deploy it using the server config tool and I end up with no runtime found like in the post
So I checked my java version that was fine,
checked app center version seems fine,
and checked the entries in server.xml for duplicates of WL Admin services war, only one exists.
server.xml http://pastebin.com/gXqfVknb
logs too long and paste bin counts as en extra link limited to 2 will post link to logs as comment
Use mfp bd (build & deploy) instead of just build.
It will start a test server to generate the WAR file.
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.
How do i configure WebLogic 8.1 to use a specific JRE / JDK on my development machine. I realized that it is using hot spot and i would like to change it to run on JRockit.
You need to change the JAVA_VENDOR setting in the setDomainEnv.sh/.cmd file (depending whether you are running a Linux or Windows box).
Adding/changing the following lines to the start of your setDomainEnv file should work:
set JAVA_VENDOR=BEA
set BEA_JAVA_HOME=(path to your jrockit installation, e.g. c:\BEA\jrockit)
Now you should start the server. You can monitor, in the console (stdout), the indication about which Java version is being used:
starting weblogic with Java version:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
BEA JRockit(R) (build R27.6.0-50_o-100423-1.6.0_05-20080626-2105-windows-ia32, compiled mode)
It is also possible to do it during the configuration wizard, when you are adding a domain, under the Java SDK Selections tab.