It's all about the answers!

Ask a question

RTC502 error SCM java.lang.VerifyError: JVMVRFY013 class loading


praveen patidar (8613144) | asked May 25 '15, 10:06 p.m.
Nothing to say.. just the below error keep on appearing in the scm load command. deleting the .jazz-scm helps for a while but not it is breaking automation more frequently. 

 24 PM                   EXEC      Unexpected exception

85781    5/25/15 1:24 PM                               EXEC      java.lang.VerifyError: JVMVRFY013 class loading constraint violated; class=com/ibm/team/filesystem/client/internal/marshalling/ExceptionHandlingJSONDeserializer, method=deserializeErrorObj(Lcom/ibm/team/repository/common/json/JSONObject;Ljava/lang/ClassLoader;Lcom/ibm/team/repository/common/serialize/IStackAdjuster;)Ljava/lang/Throwable;, pc=0

85782    5/25/15 1:24 PM                               EXEC                      at java.lang.J9VMInternals.verifyImpl(Native Method)

85783    5/25/15 1:24 PM                               EXEC                      at java.lang.J9VMInternals.verify(J9VMInternals.java:73)

85784    5/25/15 1:24 PM                               EXEC                      at java.lang.J9VMInternals.initialize(J9VMInternals.java:135)

85785    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.filesystem.client.internal.marshalling.EObjectJSONDeserializer.deserializeError(EObjectJSONDeserializer.java:64)

85786    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeRequest(RestInvocationHandler.java:267)

85787    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeAndReturnResult(RestInvocationHandler.java:221)

85788    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invokeInternal(RestInvocationHandler.java:368

EXEC                      at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invoke(RestInvocationHandler.java:311)

85790    5/25/15 1:24 PM                               EXEC                      at com.sun.proxy.$Proxy0.postLoadCFA(Unknown Source)

85791    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.run(LoadCmd.java:165)

85792    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmdLauncher.run(LoadCmdLauncher.java:185)

85793    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)

85794    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601)

85795    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)

85796    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)

85797    5/25/15 1:24 PM                               EXEC                      at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41)

85798    5/25/15 1:24 PM                               EXEC                      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

85799    5/25/15 1:24 PM                               EXEC                      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

85800    5/25/15 1:24 PM                               EXEC                      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79

85801    5/25/15 1:24 PM                               EXEC                      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)

85802    5/25/15 1:24 PM                               EXEC                      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

85803    5/25/15 1:24 PM                               EXEC                      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

85804    5/25/15 1:24 PM                               EXEC                      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)

85805    5/25/15 1:24 PM                               EXEC                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

85806    5/25/15 1:24 PM                               EXEC                      at java.lang.reflect.Method.invoke(Method.java:611)

85807    5/25/15 1:24 PM                               EXEC                      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)

85808    5/25/15 1:24 PM                               EXEC                      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)

85809    5/25/15 1:24 PM                               EXEC                      at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

85810    5/25/15 1:24 PM                               EXEC      Scm:

85811    5/25/15 1:24 PM                               EXEC      An error has occurred. See the log file

2 answers



permanent link
Donald Nong (14.4k314) | answered May 26 '15, 1:08 a.m.
I have previously seen such errors in WebSphere environments only, where the class loading policy may have some impacts on which class to load when duplicate classes can be found in the class loading path. But the error that you posted, I am quite curious - do you have multiple copies of the SCM runtime in the class loading path, or you have extended any existing APIs?

permanent link
praveen patidar (8613144) | answered May 26 '15, 3:19 a.m.
Hello Donald, 

There is no issue in the SCM tool, we are using the default scm only. RTC Application is installed on WAS that is true. But is the issue appearing due to some server side configuration or there is any issue in Local scm install. or anything related to JVM ?

Thanks 
Praveen 

Comments
Donald Nong commented May 26 '15, 3:26 a.m.

If everything is in the default configuration, I cannot imagine how this issue can happen. Based on the stack trace, the issue occurs on the client side (the SCM command), which is even harder to understand. I suggest you contact Support to get it checked out thoroughly.

Your answer


Register or to post your answer.