• New Feature
  • Status: Resolved
  • 2 Major
  • Resolution: Won't Fix
  • DSO:L1
  • interfaces
  • Reporter: foshea
  • February 06, 2009
  • 0
  • Watchers: 1
  • February 12, 2014
  • February 12, 2014


When an Unknown Architecture(aka Untested/Unsupported Architecture) is encountered, Terracotta Client will fail to create the boot jar with the following error

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:593) at com.tc.object.bytecode.hook.impl.ClassProcessorHelper.initialize(ClassProcessorHelper.java:393) at com.tc.object.bytecode.hook.impl.ClassProcessorHelper.defineClass0Pre(ClassProcessorHelper.java:632) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) Caused by: com.tc.config.schema.setup.ConfigurationSetupException: ************************************************* Unknown Solaris architecture: (“os.arch” = amd64) *************************************************


Fiona OShea 2009-02-06

From DRB in CDV-1110 We want to a. Get rid of Stack trace and give clear error message b. Have the ability to turn the check off c. Make sure new error message describes how to turn check off

Verify new error message with PM

From Alex in CDV-1110

a) We can definitely print a clearer error message. Right now throwing an exception is the way this error is getting propagated back into the container. Should we exit the VM or something? Or just print an error message but throw no exception? If we did the latter, I think dso would be half-initialized.

b) I don’t think we can do that? We’re checking here that the boot jar matches the vm (and the boot jar is tagged with the os). Seems kind of dangerous to turn that off?

c) Sure, pending above.

Fiona OShea 2009-02-11

We still want to check if the bootjar matches the kit version We want a flag to disable supported platform check

Hung Huynh 2014-02-12

DSO is discontinued