Domino 9.0.1FP3IF1: java.policy vs java.pol

Monday, February 23, 2015 at 10:49 AM UTC

We encountered problems after upgrading one of our Domino dev machines from 9.0.1FP2 to 9.0.1FP3IF1. The upgrade was performed at one step, i.e. we installed FP3 and IF1 together (no period with FP3 only).

For one of our projects we had to customize the java.policy file. Aware of that this file will be overwritten when upgradinig the server we backed this file and put it in place after the upgrade so our custom settings were available afterwards. This procedure is somewhat well known, if not then read the blog post from John Dalsgaard to gain more information about it.

For some reason the upgraded server didn't recongnize our setting after restart. In this case we received the following error on the console that told us that a library could not be loaded:

20.02.2015 16:14:03 HTTP JVM: com.fasterxml.jackson.databind.JsonMappingException: Can not access public de.ulc.model.HttpResponseModel() (from class de.ulc.model.HttpResponseModel; failed to set access: Access denied (java.lang.reflect.ReflectPermission suppressAccessChecks)
20.02.2015 16:14:03 HTTP JVM: at com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(

This is a well known scenery - when you don't grant access for that kind of action - but we did!

I don't know the main reason but there is a workaround to solve this problem: do as John recommends, use a java.pol file where you define your settings. Another benefit is that this file won't be overwritten while doing future upgrades on the server.

With that you are also able to run your dev machine in "slut mode" again:

grant { permission; };

Again, thanks John for your direct assistance! L├Ąchelnd

p.s.: AS/400 users find their custom java.policy file under ${user.home}/.java.policy

Leave a comment right here