• Bug
  • Status: Open
  • 2 Major
  • Resolution:
  • DSO:L1
  • prodmgmt
  • Reporter:
  • August 14, 2008
  • 0
  • Watchers: 0
  • March 19, 2010

Description

What does this mean and what am I supposed to do when it happens?

2008-08-14 17:48:51,979 INFO - Terracotta 2.6.2, as of 20080626-150627 (Revision 8952 by [email protected] from 2.6) 2008-08-14 17:48:52,567 INFO - Configuration loaded from the file at ‘/Users/orion/Documents/workspace/locking-examples/tc-config.xml’. 2008-08-14 17:48:52,770 INFO - Log file: ‘/Users/orion/Documents/workspace/locking-examples/terracotta/client-logs/terracotta-client.log’. java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.tc.object.bytecode.hook.impl.ClassProcessorHelper.createGlobalContext(ClassProcessorHelper.java:627) at com.tc.object.bytecode.hook.impl.ClassProcessorHelper.init(ClassProcessorHelper.java:417) at com.tc.object.bytecode.hook.impl.ClassProcessorHelper.systemLoaderInitialized(ClassProcessorHelper.java:805) at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1382) at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1341) Caused by: com.tc.config.schema.setup.ConfigurationSetupException: ******************************************************************************* com.tc.object.tools.InvalidBootJarMetaDataException: Incompatible DSO meta data: tcversion; expected ‘2.6.2’ but was (in boot jar): ‘2.6.0’ *******************************************************************************

at com.tc.object.config.StandardDSOClientConfigHelperImpl.<init>(StandardDSOClientConfigHelperImpl.java:283)
at com.tc.object.config.StandardDSOClientConfigHelperImpl.<init>(StandardDSOClientConfigHelperImpl.java:199)
at com.tc.object.bytecode.hook.impl.DSOContextImpl.getGlobalConfigHelper(DSOContextImpl.java:203)
at com.tc.object.bytecode.hook.impl.DSOContextImpl.createGlobalContext(DSOContextImpl.java:62)
... 9 more Caused by: java.lang.RuntimeException: com.tc.object.tools.InvalidBootJarMetaDataException: Incompatible DSO meta data: tcversion; expected '2.6.2' but was (in boot jar): '2.6.0'
at com.tc.object.config.StandardDSOClientConfigHelperImpl.doAutoconfig(StandardDSOClientConfigHelperImpl.java:814)
at com.tc.object.config.StandardDSOClientConfigHelperImpl.<init>(StandardDSOClientConfigHelperImpl.java:281)
... 12 more Caused by: com.tc.object.tools.InvalidBootJarMetaDataException: Incompatible DSO meta data: tcversion; expected '2.6.2' but was (in boot jar): '2.6.0'
at com.tc.object.tools.BootJar$BootJarMetaData.<init>(BootJar.java:382)
at com.tc.object.tools.BootJar.getBootJarForReading(BootJar.java:94)
at com.tc.object.tools.BootJar.getBootJarForReading(BootJar.java:77)
at com.tc.object.tools.BootJar.getDefaultBootJarForReading(BootJar.java:126)
at com.tc.object.config.StandardDSOClientConfigHelperImpl.doAutoconfig(StandardDSOClientConfigHelperImpl.java:800)
... 13 more

Comments

Alex Miller 2008-08-14

Well this part: “Incompatible DSO meta data: tcversion; expected ‘2.6.2’ but was (in boot jar): ‘2.6.0’” is pretty clear I think. The version is recorded in the boot jar. When you start up, it verifies that the boot jar version == kit version. But being wrapped in an InvocationTargetException and the stack traces don’t help much. Also, seems like it should tell you how to fix it (by rebuilding your boot jar).

Fiona OShea 2008-08-15

Should be resolved exactly as Alex describes

Fiona OShea 2008-08-15

PM: Please give text for message