Intermittent ClassNotFoundException when using the Build Forge agent integration
When using the Build Forge agent integration with RTC on WAS I intermittently get a:
Java.net.SocketException: java.Lang.ClassNotFoundException cannot find the specified class com.ibm.websphere.ssl.protocol.sslSocketFactory
Nothing seems to consistently resolve this, but restarting the WAS server seems to occasionally help.
~Spencer
|
Accepted answer
This is a complicated issue at the root. An article will come out soon on jazz.net to fully describe the issue, but quickly the cause is the RTC OSGi not communicating with the WAS OSGi layer. To resolve the issue we can do one of the following:
1) Change the java.security settings to use the Java JDK implementation of the SSLSocketFactory rather than the WAS implementation. This is what we do internally for our selfhosting. This does not use the WAS security implementation which may be problematic in some WAS situations.
2) Change the following entries in <ccm web app deploy location>\ccm\WEB-INF\eclipse\launch.ini to 'fwk', like so:
osgi.parentClassloader=fwk
osgi.contextClassLoaderParent=fwk
This will disable RTC logging as the WAS OSGi logging with override RTC's, but it will use the WAS security implmentation.
3) Write another application to run with RTC that will call SSLSocketFactory.getDefault(). That will run outside the RTC OSGi and will have access to the WAS implementation. Once the class is loaded, RTC can access it. This application will then have to be run whenever the ClassNotFoundException occurs.
~Spencer
Spencer Murata selected this answer as the correct answer
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.