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.
Related
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
I'm installing a v7.0.0 MobileFirst Server with Liberty 8.5.5.4 with Java 1.7.0 on RedHat in Nonadminstrator mode. Steps I have followed:
Successfully install Liberty, create a server and verify it starts with no errors in messages.log.
Install MFP Server.
Use the MFP Server Configuration Tool to create an MFP configuration using the Liberty server.
Bounce the Liberty server and verify it starts with no errors.
Create an MFP Runtime using the Server Configuration Tool.
Bounce the server and observe SSL errors in the log.
The SSL errors seem to be related to Liberty trying to talk to the JMX REST client - at least that is my assumption since I haven't even invoked an adapter yet.
The WAR file I am using for the Runtime comes from a project that builds and runs fine in the MFP Studio Liberty development server.
The full log can be found at https://www.dropbox.com/s/o1frf7pjszm46n6/messages.log?dl=0, but here's the relevant error:
[8/4/15 18:23:09:400 CDT] 00000050 com.ibm.ws.channel.ssl.internal.SSLHandshakeErrorTracker E CWWKO0801E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLException: Received fatal alert: certificate_unknown
at com.ibm.jsse2.o.a(o.java:6)
at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:409)
at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:469)
at com.ibm.jsse2.SSLEngineImpl.j(SSLEngineImpl.java:181)
at com.ibm.jsse2.SSLEngineImpl.b(SSLEngineImpl.java:176)
at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:495)
at com.ibm.jsse2.SSLEngineImpl.unwrap(SSLEngineImpl.java:66)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:23)
at com.ibm.ws.channel.ssl.internal.SSLUtils.handleHandshake(SSLUtils.java:870)
at com.ibm.ws.channel.ssl.internal.SSLConnectionLink.readyInbound(SSLConnectionLink.java:531)
at com.ibm.ws.channel.ssl.internal.SSLConnectionLink.ready(SSLConnectionLink.java:304)
at com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:174)
at com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:83)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.requestComplete(WorkQueueManager.java:504)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.attemptIO(WorkQueueManager.java:574)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager.workerRun(WorkQueueManager.java:929)
at com.ibm.ws.tcpchannel.internal.WorkQueueManager$Worker.run(WorkQueueManager.java:1018)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
at java.lang.Thread.run(Thread.java:796)
Solved it. I went back to a system I knew worked and started looking for differences. The configuration was all the same, but I noticed the working system used
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr7fp1-20140708_01(SR7 FP1))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20140627_204598 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR7_20140627_0924_B204598
JIT - r11.b06_20140409_61252.04
GC - R26_Java726_SR7_20140627_0924_B204598_CMPRSS
J9CL - 20140627_204598)
JCL - 20140707_01 based on Oracle **7u65-b16**
The system that was throwing the SSL errors was running
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr6fp1ifix-20140220_01(SR6 FP1+IX90136+IX90137))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20140106_181350 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR6_20140106_1601_B181350
JIT - r11.b05_20131003_47443.02
GC - R26_Java726_SR6_20140106_1601_B181350_CMPRSS
J9CL - 20140106_181350)
JCL - 20140103_01 based on Oracle **7u51-b11**
I installed 7u65-b16 on the new system, restarted Liberty under that version of Java and all seems to be well now.
Configuration: Eclipse (Juno) 4.2.2
IBM Worklight version: 6.2.0.01
Java version:
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)
JDK: jdk1.7.0_71.jdk
Java Compiler: 1.7
My worklight studio was previously working and suddenly stops working after I had to force quit my eclipse. Even after reinstallation of the plugins, the error still recurs.
Here's a screenshot of the initial error log before 'Worklight server failed to start' and 'Failed to deploy application in the worklight server'. Any help to fix this issue will be deeply appreciated. Worklight studio issues like this is starting to get frustrating.
I uninstalled java from my mac. Reinstalled Java (JDK & JRE), new Eclipse (Juno 4.2.2) -> Then installed IBM Worklight Studio plugin. Figured it was the problem with Java as it was throwing the java exception 'unable to read the manifest'. Probably there was some issue after updating to Yosemite.
I had the same problem. You need to set correct IP for Worklight server. It doesn't work with "localhost" or "*".
It looks Java EE got corrupted somehow,
So as suggested the best approach would be to use a fresh Eclipse instance with a new plug-in installation and a new workspace as well. This way it makes sure everything is fresh and new.
I am getting following error when I try to start the server in Eclipse
Launching WorkLight_new (WebSphere Application Server 8.5.5.1/wlp-1.0.4.cl50120131011-1639) on Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_05-b13 (en_US)
[AUDIT ] CWWKE0001I: The server WorkLight_new has been launched.
[AUDIT ] CWWKE0055I: Server shutdown requested on Monday, September 29, 2014 at 5:49 PM. The server WorkLight_new is shutting down.
[AUDIT ] CWWKZ0058I: Monitoring dropins for applications.
[AUDIT ] CWWKF0011I: The server WorkLight_new is ready to run a smarter planet.
[AUDIT ] CWWKE0036I: The server WorkLight_new stopped after 1 minutes, 0.818 seconds.
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Dev environment:-
Windows 7 Pro x64
Eclipse J2ee Juno SR2 x64
JDK 1.8.0_05 x64
Worklight Server 6.2(online install)
Any help will be greatly appreciated.
----Update----
I have uploaded the server startup logs in 2 parts on pastebin. Below are the URLs
Part 1 - http://pastebin.com/601dDV0b
Part 2 - http://pastebin.com/aY5t398D
I Hope this helps
Why does it say "WorkLight_new"? This name suggests to me that you have created a 'new' server to work with instead of the default-provided Worklight Development Server, but you do not provide any details on what you've done while creating it.
My suggestion to you is to first test with the default configuration. Easiest is to simply start Eclipse with a new workspace and start the default server instead. Otherwise, you need to provide something more substantial than what you provided in the question.
Additionally,
This may also happen due to using Java 1.8 (see IBM Worklight 6.1 - Error TRAS0033E).
Downgrade to either 1.6 or 1.7 and make sure to setup Eclipse to use the JRE of 1.6 or 1.7.
On command prompt check java -version. Ensure that is 1.6 or 1.7
Open Eclipse > Window > Preferences > Java > Installed JREs. Ensure that is JDK 1.6 or 1.7
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.