This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


~Yoshi Nimkroskiakol
Jun 21, 2014, 1:59 AM
31 Posts

Log Error: 06/20/2014 09:52:37 PM Xsp Initialization error - Could not load class or methods

  • Category: Domino Server
  • Platform: Windows
  • Release: 9.0.1
  • Role:
  • Tags:
  • Replies: 6

We just upgraded and 8.5.1 32 bit Domino server to 9.0.1 FP1 64 bit domino server.  One of our databases is acting up, and I noticed this error in the log on startup.  I'm not sure if it is related.

"06/20/2014 09:52:37 PM  Xsp Initialization error - Could not load class or methods"

 

Here is the log:

06/20/2014 09:52:37 PM  HTTP JVM: java.lang.reflect.InvocationTargetException

06/20/2014 09:52:37 PM  HTTP JVM: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/20/2014 09:52:37 PM  HTTP JVM: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
06/20/2014 09:52:37 PM  HTTP JVM: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
06/20/2014 09:52:37 PM  HTTP JVM: at java.lang.reflect.Method.invoke(Method.java:611)
06/20/2014 09:52:37 PM  HTTP JVM: at com.ibm.domino.http.bootstrap.BootstrapOSGIClassLoader.loadClassFromBundle(BootstrapOSGIClassLoader.java:136)
06/20/2014 09:52:37 PM  HTTP JVM: at com.ibm.domino.http.bootstrap.BootstrapOSGIClassLoader.launchOSGIFramework(BootstrapOSGIClassLoader.java:82)
06/20/2014 09:52:37 PM  HTTP JVM: at com.ibm.domino.http.bootstrap.BootstrapOSGIClassLoader.loadClass(BootstrapOSGIClassLoader.java:63)
06/20/2014 09:52:37 PM  HTTP JVM: at java.lang.ClassLoader.loadClass(ClassLoader.java:643)
06/20/2014 09:52:37 PM  HTTP JVM: at com.ibm.domino.http.bootstrap.BootstrapClassLoader.findClass(BootstrapClassLoader.java:79)
06/20/2014 09:52:37 PM  HTTP JVM: Caused by: 
06/20/2014 09:52:37 PM  HTTP JVM: java.lang.ClassNotFoundException: Cannot load "com.ibm.domino.xsp.adapter.osgi.OSGIService" because the bundle "update@../../shared/eclipse/plugins/com.ibm.domino.xsp.adapter.osgi_9.0.1.20131004-1200.jar" cannot be resolved.
06/20/2014 09:52:37 PM  HTTP JVM: at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)
06/20/2014 09:52:37 PM  HTTP JVM: at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1288)
06/20/2014 09:52:37 PM  HTTP JVM: ... 9 more
06/20/2014 09:52:37 PM  HTTP JVM: java.lang.ClassNotFoundException
06/20/2014 09:52:37 PM  HTTP JVM: at java.lang.ClassLoader.findClass(ClassLoader.java:377)
06/20/2014 09:52:37 PM  HTTP JVM: at java.lang.ClassLoader.loadClass(ClassLoader.java:677)
06/20/2014 09:52:37 PM  HTTP JVM: at com.ibm.domino.http.bootstrap.BootstrapOSGIClassLoader.loadClass(BootstrapOSGIClassLoader.java:68)
06/20/2014 09:52:37 PM  HTTP JVM: at java.lang.ClassLoader.loadClass(ClassLoader.java:643)
06/20/2014 09:52:37 PM  HTTP JVM: at com.ibm.domino.http.bootstrap.BootstrapClassLoader.findClass(BootstrapClassLoader.java:79)
06/20/2014 09:52:37 PM  Xsp Initialization error - Could not load class or methods

 

Any ideas how to fix this?  I've reinstalled several times, without any luck.

~Sven Nimgerosterflar
Jun 21, 2014, 2:16 AM
46 Posts
Possible issue with the JVM upgrade
It is unable to locate the 901 jar file reported in the error.  My guess would be that somehow the installer did not update the jvm correctly.
You can verify the version by issuing the command "show jvm"

This is what I am seeing on my 901 FP1

[32323:00002-4102154624] 06/20/2014 10:33:52 PM  JVM version: JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr15-20131231_180656 (JIT enabled, AOT enabled) J9VM - 20131231_180656 JIT  - r9_20130920_46510ifx3 GC   - GA24_Java6_SR15_20131231_1152_B180656

To solve this you could try the following.

1. Stop the server
2. Delete the JVM folder
3. Run the 901 installer. (not the FP1 just the 901 Domino installer with no fix packs)
4. Start the server and verify that you are no longer seeing the issue
5. stop the server and upgrade to Fp1 .



~Yoshi Nimkroskiakol
Jun 21, 2014, 3:40 AM
31 Posts
Error came back after installing the FP1

Thanks for your response.

I followed your suggestion, and the error did disappear after installing 9.0.1.  But, once I installed FP1 the error came back.  I ran the install as an administrator.

Any other ideas?

~August Opjumisonynds
Jun 23, 2014, 3:13 PM
60 Posts
Could you post UPGRADE.log and jvmpatcher,.log
Both located in Domino program Directory.
Both created by fixpack.
Some process (e.g. NSD or monitoring software)  could be hogging jvm or osgi plugins during attempt to update them.
~Yoshi Nimkroskiakol
Jun 21, 2014, 3:41 AM
31 Posts
JVM Version after FP1

Here is the JVM version I see after installing FP1:

JVM version: JRE 1.6.0 IBM J9 2.4 Windows Server 2008 R2 amd64-64 jvmwa6460sr15-20131231_180656 (JIT enabled, AOT enabled)
J9VM - 20131231_180656
JIT  - r9_20130920_46510ifx3
GC   - GA24_Java6_SR15_20131231_1152_B180656
~Sven Nimgerosterflar
Jun 21, 2014, 4:12 AM
46 Posts
Some additional info while you test the FP1 installer
So I took a look at the fix pack content (you can use the -contents switch )  and my FP1 upgrade log

The fix pack contents is showing the new OSGI jar files in question with a new date.  So it is definitely supposed to update the osgi directory

Once again the guess here is that something went wrong during the patching of  FP1

This is what I see in my log

Release 9.0.1|October 14, 2013            
DetermineMode: destination version  Release 9.0.1FP1|April  03, 2014


Applying patch...
Jvm patch successful...
Cabbing old jvm...
Cabing successful!
Deleting old jvm directory ...
Old jvm directory delete successful!
Renaming new jvm...
Renamed new jvm successfully

Rename: canFileName: osgi\shared\eclipse\plugins\com.ibm.domino.xsp.adapter.osgi_9.0.1.20140402-0834.jar

etc...

My guess is that in your case we are failing to upgrade the proper files.  
Do you have another server running 901 FP1?  If so you could copy the OSGI  directory from there
~Yoshi Nimkroskiakol
Jun 21, 2014, 5:49 AM
31 Posts
Would a 32 bit version of the 9.0.1 FP1 OSGI directory work?

Would a 32 bit version of the 9.0.1 FP1 OSGI  directory work?


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal