It's all about the answers!

Ask a question

BuildToolKit4.0.1:starting JBE from command prompt endless repeating error:java.lang.NoClassDefFoundError

Don Yang (7.7k21110138) | asked Jun 20 '13, 1:57 a.m.
Buildtoolkit 3.0 and 4.0.1 on the client machine with RFT Eclipse 4.0.1 client
as well on XP.

CCM 4.0.1 , Websphere , DB2 9.7 on 2008 server SP1

When starting JBE engine from command line:
jbe -repository https://xx:9443/ccm -userid myusername -pass mypassword -engineID vsbuildengine

There is endless repeating error: java.lang.NoClassDefFoundError: org.eclipse.emf.ecore.util.EcoreUtil

If trying with -VM parameter pointing to TeamConcert Eclipse client 4.0.1,
the same result received.
JAVA_HOME points to local team concert client's JDK bin as well.

The version of JRE is:

C:\Program Files\IBM\TeamConcert\jdk\bin>java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr11-20120806_01(SR11))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr11-20120
801_118201 (JIT enabled, AOT enabled)
J9VM - 20120801_118201
JIT  - r9_20120608_24176ifx1
GC   - 20120516_AA)
JCL  - 20120713_01

On this machine, running 3.0 buildtoolkit with the same command(with no -VM) has no problem at all.
It does not seem that XP is supported for Eclipse client and etc but system requirement does not mention whether buildtoolkit is supported or not.

What else we can check here to workaround this error in JBE start up?
Appreciate if you can provide any ideas.

Error screenshot

2 answers

permanent link
Nick Edgar (6.5k711) | answered Jun 20 '13, 12:11 p.m.
Your setup looks OK to me.  Was the 4.0.1 toolkit installed on top of another one, or anything like that?  Could you try a clean install?  Can you try on a different machine?  Also note that the user needs write access in the current working directory when JBE is launched, but if that was the problem I'd expect the error to be different (not a class loading error).

Don Yang commented Jun 20 '13, 8:40 p.m.

Thanks Nick.
The install is clean and unzip toolkit also got the same problem as installing through IM. This occurs to all client machines. It turns out JBE directory needs full permission to workaround the errors.

permanent link
Don Yang (7.7k21110138) | answered Jun 24 '13, 3:41 a.m.
Hi, King

Regarding "could not create the java virtual machine" when install Eclipse 4.0.1 IDE, please see more discussions in another forum entry from me and there is useful info you can try with:

Hopefully this helps.

Don Yang commented Jun 24 '13, 8:43 p.m.

Hi, King

You are right. there are suggestions in

1) using plain zip Eclipse client. Using this, you don't need to use Installation Manager to install. Then the unzipped client has eclipse.ini and you can point VM to the right one.
2) Installation Manager itself is actually Eclipse client and you can try with some suggestion in the above forum entry in using other approach from Installation Manager.(see the details in the above forum entry) Thanks

Your answer

Register or to post 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.