Skip to content

Troubleshooting

Jump to bottom
Jesse Gallagher edited this page Jul 20, 2018 · 7 revisions

Troubleshooting

Missing *.LSS Files on Linux

Due to the way Domino deals with case sensitivity on Linux, it's possible that LotusScript code importing *.lss files with capitalized names may fail to compile. The quickest fixes are:

  • Modify the code to reference lowercase file names, which will work on Linux and Windows, or
  • Create symlinks on the Linux server, e.g. ln -s lsconst.lss LSCONST.LSS et al

Jar Dependencies From jvm/lib/ext

If your app expects that some Jars will be deployed to jvm/lib/ext and not included in a dependent plugin or in the NSF, currently the best way to handle that is to also deploy those jars to the compilation server. This is slated to be remedied in Issue #54.

SSL Chain Problems in Maven

Depending on the server setup and JVM you're using, you may hit an exception like this:

Failed to execute goal org.openntf.maven:nsfodp-maven-plugin:1.4.0:compile (default-compile) on project some-project: Exception while compiling the NSF: com.ibm.jsse2.util.h: No trusted certificate found -> [Help 1]

In this case, the server is using a Let's Encrypt certificate and Maven was running under the IBM J9 JVM shipped with Notes FP10, which doesn't have built-in trust of those certs. The quickest fix in this case is to switch to using an Oracle JVM to run Maven (in the Java -> Installed JREs Eclipse prefs).

Unexpected Connection Close in Maven

Exception while compiling the NSF: Premature end of chunk coded message body: closing chunk expected

This occurs particularly if you have a reverse proxy in front of Domino: because compilation may take a long time, reverse proxies may need to have their timeouts bumped up to prevent prematurely cutting off the client. For nginx, that can be accomplished with this:

proxy_connect_timeout 600;
proxy_send_timeout 6300;
proxy_read_timeout 600;
send_timeout 600;
Clone this wiki locally