Lewis' Blog Tales from the trenches of information technology

More fixes for 64-bit OES (ConsoleOne)

I don't know. This whole 64-bit thing is a bit of a pain. Essentially, one must maintain two sets of libs: one 64-bit and one 32-bit. Yes, that's right. For those of you who haven't yet had the joy of working on a 64-bit system, there's quite a bit of fun in store for you.

Take ConsoleOne, for example. On 64-bit OES2, after fixing the iManager (Tomcat) issue (see Fixing a Broken iManager 2.7.3 install on OES2 SP1 Linux), I happened to log in again today and by chance hit the launcher I placed on the desktop for ConsoleOne. Oops...

ConsoleOne appeared to start, then gave me:

ERROR: java.lang.NoClassDefFoundError: java/lang/StringBuilder

Wasn't that nice?

Dropping to a terminal, I moved to /usr/ConsoleOne/bin and tried to start it like so:

./ConsoleOne -debug -windowout

which revealed nothing in any greater detail (although I suspect that had I taken the time to explore the output thoroughly, there was probably a bigger hint in there...somewhere).

A quick search through the Novell knowledgebase came up with TID #7002647, which was just what I needed. Indeed, ConsoleOne was trying to launch using the default JVM (64-bit) instead of the bundled 32-bit JVM.

All that was required to fix it was a quick edit of /usr/ConsoleOne/bin/ConsoleOne to add:

export  C1_JRE_HOME=/usr/lib/jvm/jre-1.5.0-ibm

to the environment for the app, and indeed, this is something of a "known" issue.

Just another one of those 64-bit annoyances...

Last Updated on February 13th, 2010 by LewisR