Hi all.I tried installing Linux 8.0.1 on openSUSE 10.3 .
Installation went ok, but upon starting Notes, a BIG (doesn’t fit on screen) dialog box comes out saying “JVM terminated. Exit code=160”. Beneath this error, one can see ALL the JVM options used to startup Notes.
I have verified all packages required (according to rel notes) are there.
Has anyone come across this?
Best regards,
Michelangelo Gambacorta
Subject: Notes 801 on Linux: JVM terminated. Exit code=160
Hey,
Similar issue here, after an Ubuntu upgrade, Notes 8.0.0 (where do you get 0.1 or 0.2?) failed after coming up, logging in and starting to show the ‘welcome’ page (crash details on request). Following the xulrunner hints (do have xulrunner-1.9) I found an old copy of libxul.so and copied that over the xulrunner-1.9 (yes, not the best idea, but it was just to test). Logged in, got a page about “no more handles” and swt unsatisfied link but a click and up comes the welecome page etc.
Unable to do the roll back trick yet but …
Subject: Notes 801 on Linux: JVM terminated. Exit code=160
Just a further followup - my original was on 8.0.0, now on 8.0.2 and the result is the same. Swapping the libxul.so works to get Notes running, just have to remember not to click on any URLs or try to run an external program on an attachment.
Subject: Problem Resolved
I am running OpenSuse 11.0 x64.
xulrunner was the culprit for me. Notes needs xulrunner 1.8x-32bit not 1.9x. Try uninstalling xulrunner1.9x and its components (It will uninstall firefox 3.0 too, but don’t worry we can reinstall it) . Then open your lotus notes. once you are done with notes, close that. and reinstall firefox 3.0 (use YAST) (it will reinstall xulrunner1.9x too,but this time notes will work with it). You will have both firefox 3.0 and notes.
It worked for me…I hope it will work for you too. Leave your comments.
Subject: did not make it for me
I tried installing on a non updated (new install system). Install failed. Then updated everything except Mozilla and Thungerbird to keep xulrunner 1.8. Install then completed, but upon starting it, I still get the same error.I get to see the blue window (empty in the center), with the New button on upper left corner, but then it goes away and the dialog with error and options as explained before comes out.
But my situation is different: openSuSE 10.3 32bits; you are on openSuSE 11.0 64 bits.
Thanks anyway.
Subject: Problem NOT resolved for me
Hello,
I try this solution but when I uninstall xulrunner, lotus running fine, so install firefox and also xulrunner lotus will fail to run.
What can I do?
Subject: more info about problem: CWPPK0203E:Error registering PortletServiceHome with JNDI
As part of troubleshooting, I tried starting notes from a shell. Interestingly, there is output that suggests there might be problems in eclipse.
What follows is a paste of the standard output after trying to start notes.
2008/07/13 00:19:43.473 CONFIG eclipse.buildId=build20080213-2253
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20071005 (JIT enabled)
J9VM - 20071004_14218_lHdSMR
JIT - 20070820_1846ifx1_r8
GC - 200708_10
BootLoader constants: OS=linux
, ARCH=x86
, WS=gtk
, NL=en_US
Framework arguments: -dir ltr -personality com.ibm.rcp.platform.personality -product com.ibm.notes.branding.notes -plugincustomization /opt/ibm/lotus/notes/framework/rcp/plugin_customization.ini
Command-line arguments: -os linux -ws gtk -arch x86 -dir ltr -personality com.ibm.rcp.platform.personality -product com.ibm.notes.branding.notes -data /home/michelangelo/lotus/notes/data/workspace -plugincustomization /opt/ibm/lotus/notes/framework/rcp/plugin_customization.ini ::class.method=com.ibm.rcp.core.internal.logger.frameworkhook.writeSession() ::thread=main ::loggername=com.ibm.rcp.core.internal.logger.frameworkhook
2008/07/13 00:19:44.030 SEVERE CWPPK0203E:Error registering PortletServiceHome with JNDI (portletservice/com.ibm.portal.propertybroker.service.PropertyBrokerService) ::class.method=com.ibm.rcp.propertybroker.internal.Activator$initJob.run() ::thread=Worker-0 ::loggername=com.ibm.rcp.propertybroker
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:259)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:296)
at javax.naming.InitialContext.bind(InitialContext.java:371)
at com.ibm.rcp.propertybroker.internal.Activator$initJob.run(Activator.java:830)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Unhandled exception
Type=Illegal instruction vmState=0x00040000
J9Generic_Signal_Number=00000010 Signal_Number=00000004 Error_Value=00000000 Signal_Code=00000002
Handler1=B7CF1B68 Handler2=B7CBA7BC
EDI=BFD95EB8 ESI=08E95F20 EAX=08E9C294 EBX=9169F164
ECX=00000000 EDX=08E9C294
EIP=910FF118 ES=0000007B DS=0000007B ESP=BFD95E3C
EFlags=00010246 CS=00000073 SS=0000007B EBP=BFD95E54
Module=/opt/ibm/lotus/notes/framework/…/libnotes.so
Module_base_address=8FD56000
Target=2_30_20071004_14218_lHdSMR (Linux 2.6.22.18-0.2-default)
CPU=x86 (1 logical CPUs) (0x3f3b1000 RAM)
JVMDUMP006I Processing Dump Event “gpf”, detail “” - Please Wait.
JVMDUMP007I JVM Requesting System Dump using ‘/home/michelangelo/lotus/notes/data/workspace/logs/core.20080712.221954.23105.dmp’
JVMDUMP010I System Dump written to /home/michelangelo/lotus/notes/data/workspace/logs/core.20080712.221954.23105.dmp
JVMDUMP007I JVM Requesting Snap Dump using ‘/home/michelangelo/lotus/notes/data/workspace/logs/Snap0002.20080712.221954.23105.trc’
JVMDUMP010I Snap Dump written to /home/michelangelo/lotus/notes/data/workspace/logs/Snap0002.20080712.221954.23105.trc
JVMDUMP007I JVM Requesting Java Dump using ‘/home/michelangelo/lotus/notes/data/workspace/logs/javacore.20080712.221954.23105.txt’
JVMDUMP010I Java Dump written to /home/michelangelo/lotus/notes/data/workspace/logs/javacore.20080712.221954.23105.txt
JVMDUMP013I Processed Dump Event “gpf”, detail “”.