Hi,
We tried to roll out a database in an 8.5.1 environment but we have serious issues.
Under application properties (or in the xsp.properties file) we set the persistence mode to ‘file’ for best scalability, because otherwise the http task constantly runs out of memory.
After setting it and restarting the http task it started to throw ClassNotFoundExceptions.
We have some java classes in the application that otherwise work just fine.
Based on the stack trace the problem happens during the deserialization, and looks like the deserialization process cannot locate the application class loader/application class and fails. I don’t know the HTTP/XPages related class loader hierarchy (and couldn’t find any documentation about it) but there must be some JVM classloaders and some application classloaders (NSFClassLoader). The deserialization process wants to load classes with the JVM classloader and I think that’s the point where it fails.
I managed to get a workaround for it by placing the application specific (and serializable) classes to the system shared classpath.
Could someone confirm it or help me with this issue?
Thank you,
Tibor