Domino not launching JVM with HTTP

HCL Domino Domino Forum
1

Hi I have a situation where one Domino server does not appear to be starting the Java Virtual Machine.

Essentially it is stopping Traveler from working.

The following is a console output from a properly configured server.

11/12/2008 20:35:06 HTTP Server: Using Internet Site Configuration View

11/12/2008 20:35:13 JVM: Java Virtual Machine initialized.

11/12/2008 20:35:13 HTTP Server: Java Virtual Machine loaded

11/12/2008 20:35:13 Servlet engine initialization was successful

11/12/2008 20:35:13 HTTP JVM: com.lotus.sync.servlet.TravelerServlet: init

11/12/2008 20:35:13 HTTP JVM: Traveler 8.0.1.2.200807181242: debug = false

Here’s the console output for the server that isn’t working:

lo http

15/12/2008 16:42:25 HTTP Server: SSL Error: Keyring file not found, key ring file [tpp-selfcert.kyr], [Default Server]

15/12/2008 16:42:25 HTTP Server: SSL Error: Keyring file not found, key ring file [tpp-selfcert.kyr], IP address [172.25.210.241]

15/12/2008 16:42:25 HTTP Server: Using Internet Site Configuration View

15/12/2008 16:42:29 HTTP Server: Started

You can see that there is no JVM being loaded. Does anyone have any idea why this may be the case?

  • Server is using Internet Sites

  • Domino Servlet Mgr enabled in the server doc

  • SH TA Reports Traveler is running

    Lotus Traveler Running: 0 of 0 users active. Completed 0 device and 0 prime syncs.

What am I missing?

Thanks

Mike

2

Subject: Check for HTTPDisableJVM=1 in the notes.ini

Check for HTTPDisableJVM=1 in the notes.ini file. This prevents the JVM (HTTP and Traveler both use the JVM) from loading. This is commonly inserted by the BES server; there are no known issues with BES with removing HTTPDisableJVM=1 from the notes.ini file.

Traveler appears to be loaded correctly, so the JVM is installed. The issue appears to just be getting HTTP to load the JVM. The Traveler servlet runs in the HTTP JVM process, but the rest of Traveler runs in the Traveler process itself.

3

Subject: Thanks for that

That solved it. Yes we added Traveler to our BES server, to build up a mobile device messaging platform.

Works a treat now - maybe future versions of Traveler could check for this parameter at installation time and advise the installer giving the option to change the parameter or cancel installation.

Thanks again

Mike

4

Subject: HTTPDisableJVM=1 check in next release

The check for HTTPDisableJVM=1 is already in the next release.

You are not the first person to hit this issue (which is also why I knew what to check for), so that’s why the next release will have the check for it.

Note: Traveler does all of its configuration when the task is loaded, so this check is at load time and not install.