We encountered the following errors with a java agent after upgrading a Solaris server fromR5.0.11 to D6.5:
error message: Exception
error message: in thread “main”
error message: java.lang.UnsatisfiedLinkError: initIDs
error message: at java.util.zip.Inflater.initIDs(Native Method)
error message: at java.util.zip.Inflater.(Inflater.java:35)
error message: at java.util.zip.ZipInputStream.(ZipInputStream.java:50)
error message: at lotus.domino.ClassHashtable.explodeArchive(Unknown Source)
error message: at lotus.domino.ClassHashtable.addAttachment(Unknown Source)
error message: at lotus.domino.AgentLoader.addAttachment(Unknown Source)
JVM: The addAttachment (Ljava/lang/String;[B)V() method failed.
The first thing we did was look for all of the *.jar files in the Domino program directory
(/opt/lotus/notes/latest/sunspa). When comparing the jar files listed on the problem system
to another Solaris 8 Domino 6.5 system and to a Solaris 8 Domino 6.0.2CF1
system where the agent was working, we noticed that the problem server had two additional jar
files, i18n.jar and rt.jar. Recognizing that these are typically part of a standard JVM
installation and not Domino-specific, we renamed these files and restarted agent manager.
However, the agent still exhibited the same errors.
Suspecting that we were on the right track, we next looked for any files with “java” in the
filename and found java.bin and libjava.so only on the problem server and not on the others.
Once again, we renamed these files and restarted agent manager. This time, the agent failed
but explicitly complained about symbol references in libzip.so. Found a libzip.so in the problem
server and not the others. Renamed this file, restarted agent manager, and the java agent
started working again.