It's all about the answers!

Ask a question

IOException: Creating Password File with Jazz Build Engine


Takashi Kumita (61) | asked Jun 22 '09, 5:48 a.m.
I'm trying to create an encrypted password file to configure Jazz Build Engine.

I extracted "RTC-BuildSystemToolkit-1.0.1-Win.zip" and ran the command following the online manual Creating an encrypted password file. But I got IOException in the "configuration/1245661876843.log" file (attached below) and the password file was not created.

Do you have any ideas?
(I found the same error in this post but there are no replies...)


!SESSION 2009-06-22 18:11:16.484 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20080315 (JIT enabled)
J9VM - 20080314_17962_lHdSMr
JIT - 20080130_0718ifx2_r8
GC - 200802_08
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ja_JP
Framework arguments: -createPasswordFile pass.txt
Command-line arguments: -os win32 -ws win32 -arch x86 -createPasswordFile pass.txt

!ENTRY org.eclipse.osgi 4 0 2009-06-22 18:11:18.625
!MESSAGE Application error
!STACK 1
java.io.IOException: ハンドルが無効です。
at java.io.FileInputStream.read(FileInputStream.java:229)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:265)
at java.io.BufferedInputStream.read(BufferedInputStream.java:324)
at java.io.FilterInputStream.read(FilterInputStream.java:113)
at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:353)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:251)
at java.io.InputStreamReader.read(InputStreamReader.java:212)
at java.io.BufferedReader.fill(BufferedReader.java:157)
at java.io.BufferedReader.readLine(BufferedReader.java:320)
at java.io.BufferedReader.readLine(BufferedReader.java:383)
at com.ibm.team.build.internal.engine.BuildEngineApplication.getPasswordFromUser(BuildEngineApplication.java:226)
at com.ibm.team.build.internal.engine.BuildEngineApplication.start(BuildEngineApplication.java:104)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)

!ENTRY org.eclipse.osgi 2 0 2009-06-22 18:11:18.625
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-06-22 18:11:18.625
!MESSAGE Bundle update@plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.3.R33x_v20080118/ [34] was not resolved.
!SUBENTRY 2 org.eclipse.equinox.launcher.gtk.linux.x86 2 0 2009-06-22 18:11:18.625
!MESSAGE Platform filter did not match: (& (osgi.ws=gtk) (osgi.os=linux) (osgi.arch=x86))

4 answers



permanent link
Nick Edgar (6.5k711) | answered Jun 22 '09, 12:14 p.m.
JAZZ DEVELOPER
I recommend always specifying the JDK explicitly using -vm. Otherwise, it uses the system default JDK or JRE, which can cause various problems. For example, if it's a JRE instead of a JDK, the Ant <javac> task will fail since the JRE does not included the java compiler (javac.exe).

permanent link
Nick Edgar (6.5k711) | answered Jun 22 '09, 12:12 p.m.
JAZZ DEVELOPER
Can you provide a translation of the error message:
java.io.IOException: ハンドルが無効です。

Is it the same as the originally reported 'java.io.IOException: The handle is invalid. '?

If so, the problem is likely that the jbe process chose to run the javaw executable instead of the java executable (or its DLL).

Could you try running with the -vm command line argument pointing to the java (not javaw) executable from the RTC client install?
For example:
jbe -vm {path_to_rtc_client}\jazz\client\eclipse\jdk\bin\java -createPasswordFile

permanent link
Takashi Kumita (61) | answered Jun 22 '09, 12:34 p.m.
Thanks nedgar!

The error has gone after specifying the JDK using -vm.

(You are right. The error messages is the same as "The handle is invalid.")

permanent link
Nick Edgar (6.5k711) | answered Jun 22 '09, 1:22 p.m.
JAZZ DEVELOPER
Glad to hear. Thanks for confirming.

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.