It's all about the answers!

Ask a question

JBE problems on Windows Server 2008


Tom Frauenhofer (1.3k58435) | asked Oct 01 '08, 9:48 p.m.
FYI:

I've setup a build machine on an otherwise unused Windows Server 2008
system. The box has both Java 5 and Java 6 installed (Java 6 is the
System JVM). There is no RTC client installed there, just the Build
toolkit.

When I run the jbe with any normal arguments (or even no arguments) it
writes nothing to the console.

This command fails: (no output at all)

jbe -repository https://host:9443/jazz -userId userid -pass password
-verbose

Setting the JAVA_HOME environment variable didn't help.




OTOH this command works:

jbe -repository https://host:9443/jazz -userId userid -pass password
-verbose -vm "c:\JRE"

Also, this command works:

java -jar plugins\org.eclpse.equinox.launcher_1.0.1.R33x_v20080118.jar
-repository https://host:9443/jazz -userId userid -pass password -verbose

2 answers



permanent link
Don Weinand (7851) | answered Oct 02 '08, 12:38 a.m.
JAZZ DEVELOPER
This seems wery familiar to the problem we had before we included the
requirement in the jbe RCP app that it run on Java 5. If a previous
verision of java prior to 5 was found on the search path first then the JBE
would fail to start and nothing would print out. Is java 6 first on your
windows search path?

Don Weinand
Jazz Team Build

"David Ward" <davidward> wrote in message
news:gc199a$3me$1@localhost.localdomain...
FYI:

I've setup a build machine on an otherwise unused Windows Server 2008
system. The box has both Java 5 and Java 6 installed (Java 6 is the
System JVM). There is no RTC client installed there, just the Build
toolkit.

When I run the jbe with any normal arguments (or even no arguments) it
writes nothing to the console.

This command fails: (no output at all)

jbe -repository https://host:9443/jazz -userId userid -pass
password -verbose

Setting the JAVA_HOME environment variable didn't help.




OTOH this command works:

jbe -repository https://host:9443/jazz -userId userid -pass
password -verbose -vm "c:\JRE"

Also, this command works:

java -jar
plugins\org.eclpse.equinox.launcher_1.0.1.R33x_v20080118.jar -repository
https://host:9443/jazz -userId userid -pass password -verbose


permanent link
Tom Frauenhofer (1.3k58435) | answered Oct 02 '08, 9:17 a.m.
This is a pretty new box. I don't think that there was any Java
installed before I began JBE work. I've searched the entire harddrive
and the only JRE's I find are IBM's Java5 and Java6. Java6 is the
'systerm JRE' and is what you get if you run java from a command line.

BTW I neglected to mention that the two working command variants (shown
below) work fine with both Java5 and Java6.

So, answering your question ... Java6 is found first in the windows
search path

Regards


Donald Weinand wrote:
This seems wery familiar to the problem we had before we included the
requirement in the jbe RCP app that it run on Java 5. If a previous
verision of java prior to 5 was found on the search path first then the JBE
would fail to start and nothing would print out. Is java 6 first on your
windows search path?

Don Weinand
Jazz Team Build

"David Ward" <davidward> wrote in message
news:gc199a$3me$1@localhost.localdomain...
FYI:

I've setup a build machine on an otherwise unused Windows Server 2008
system. The box has both Java 5 and Java 6 installed (Java 6 is the
System JVM). There is no RTC client installed there, just the Build
toolkit.

When I run the jbe with any normal arguments (or even no arguments) it
writes nothing to the console.

This command fails: (no output at all)

jbe -repository https://host:9443/jazz -userId userid -pass
password -verbose

Setting the JAVA_HOME environment variable didn't help.




OTOH this command works:

jbe -repository https://host:9443/jazz -userId userid -pass
password -verbose -vm "c:\JRE"

Also, this command works:

java -jar
plugins\org.eclpse.equinox.launcher_1.0.1.R33x_v20080118.jar -repository
https://host:9443/jazz -userId userid -pass password -verbose



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.