TeamPlatform.startup() giving error on RTC3.0.1
Hello,
I'm running a server side java script (osgi, non eclipse) that was developed against RTC2.0.2 and worked without any problems when we upgraded to RTC3.0. We upgraded our version to RTC3.0.1 last week and updated all the libraries to the newer versions but since then the script has been failing. I have isolated the error to the satck below which origintaes from a call to the TeamPlatform.startup() method Exception in thread "main" java.lang.ExceptionInInitializerError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at org.eclipse.core.runtime.spi.RegistryStrategy.createExecutableExtension(RegistryStrategy.java:222) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:874) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51) at com.ibm.team.repository.common.internal.util.StandaloneAdapterRegistry.loadFactory(StandaloneAdapterRegistry.java:46) at com.ibm.team.repository.common.internal.util.StandaloneAdapterRegistry.handleExtensionAdded(StandaloneAdapterRegistry.java:32) at com.ibm.team.repository.common.util.ExtensionReader.internalReadElement(ExtensionReader.java:196) at com.ibm.team.repository.common.util.ExtensionReader.readRegistry(ExtensionReader.java:344) at com.ibm.team.repository.common.util.ExtensionReader.start(ExtensionReader.java:374) at com.ibm.team.repository.common.internal.util.InternalTeamPlatform.initializeAdapterRegistry(InternalTeamPlatform.java:248) at com.ibm.team.repository.common.internal.util.InternalTeamPlatform.start(InternalTeamPlatform.java:105) at com.ibm.team.repository.client.TeamPlatform.startup(TeamPlatform.java:49) at AmendRTCBuildSchedule.main(AmendRTCBuildSchedule.java:211) Caused by: java.lang.NullPointerException at org.eclipse.debug.internal.ui.elements.adapters.StackFrameSourceDisplayAdapter.<init>(StackFrameSourceDisplayAdapter.java:46) at org.eclipse.debug.internal.ui.views.launch.DebugElementAdapterFactory.<clinit>(DebugElementAdapterFactory.java:81) ... 15 more Does anyone have any suggestions on what might be causing this. The source code being run has not changed since the upgrade and a preliminary serach through the 3.0.1 libraries shows all the required classes are there. Thanks, Kelly |
One answer
Resolved, it was a classpath config error making it unable to find the plain java libs
Cheers |
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.