Jazz SCM Command-line Utility NumberFormatException
We have an automated shell script that calls The Jazz scm command-line utility many times thoughout the day. Since November, we've seen the error message below occur four times. Each time, the error message has been the same: java.lang.NumberFormatException: For input string: "_bkZjcdt". The error appears to be some kind of uncaught exception. It appears to reference something that looks like a UUID, but we can find no UUIDs used in the command that match it.
For now, we are going to update our shell script to consider it an error when the exit code is zero and there is output in standard error.
Here is the error message. Does this happen to be any kind of a known issue?
!SESSION 2012-11-08 12:12:38.749 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110624_85526 (JIT enabled, AOT enabled)
J9VM - 20110624_085526
JIT - r9_20101028_17488ifx17
GC - 20101027_AA
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: --show-uuid yes compare snapshot _EiEIYCnPEeKfld23yFy0qg snapshot _o-UW8ym3EeKfld23yFy0qg --include-types cbwsf --username someuser --password somepassword --repository-uri https://rtc/jazz
Command-line arguments: -os linux -ws gtk -arch x86 -data @noDefault --show-uuid yes compare snapshot _EiEIYCnPEeKfld23yFy0qg snapshot _o-UW8ym3EeKfld23yFy0qg --include-types cbwsf --username someuser --password somepassword --repository-uri https://rtc/jazz
!ENTRY org.eclipse.osgi 2 1 2012-11-08 12:12:40.789
!MESSAGE NLS missing message: PendingChangesUtil_36 in: com.ibm.team.filesystem.cli.client.internal.messages
!ENTRY org.eclipse.osgi 4 0 2012-11-08 12:12:51.318
!MESSAGE Application error
!STACK 1
java.lang.NumberFormatException: For input string: "_bkZjcdt"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:59)
at java.lang.Long.parseLong(Long.java:421)
at java.lang.Long.valueOf(Long.java:536)
at com.ibm.team.filesystem.cli.core.internal.aliases.AliasLoader.parseLine(AliasLoader.java:148)
at com.ibm.team.filesystem.cli.core.internal.aliases.AliasLoader.load(AliasLoader.java:106)
at com.ibm.team.filesystem.cli.core.internal.aliases.UuidAliasRegistry.load(UuidAliasRegistry.java:153)
at com.ibm.team.filesystem.cli.core.internal.aliases.UuidAliasRegistry.findAliasByName(UuidAliasRegistry.java:375)
at com.ibm.team.filesystem.cli.core.util.RepoUtil.lookupUuidAndAlias(RepoUtil.java:1210)
at com.ibm.team.filesystem.cli.core.cliparser.CommandLineArgument.validateAlias(CommandLineArgument.java:74)
at com.ibm.team.filesystem.cli.core.cliparser.CommandLineArgument.getRepositorySelector(CommandLineArgument.java:50)
at com.ibm.team.filesystem.cli.core.util.RepoUtil.loginUrlArgAncestor(RepoUtil.java:459)
at com.ibm.team.filesystem.cli.client.internal.subcommands.CompareCmd.resolveItem(CompareCmd.java:357)
at com.ibm.team.filesystem.cli.client.internal.subcommands.CompareCmd.run(CompareCmd.java:167)
at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:651)
at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.doStart(SubcommandLauncher.java:398)
at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:175)
at com.ibm.team.filesystem.cli.core.internal.Application.start(Application.java:39)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
!ENTRY org.eclipse.osgi 2 0 2012-11-08 12:12:51.426
!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 2012-11-08 12:12:51.426
!MESSAGE Bundle org.eclipse.core.filesystem.win32.ia64_1.1.201.v20100520-0800 [17] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.426
!MESSAGE Bundle org.eclipse.swt.win32.win32.x86.nl2_3.5.2.v201002231411 [21] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.426
!MESSAGE Bundle org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519 [38] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.426
!MESSAGE Bundle org.eclipse.core.filesystem.linux.s390x_3.0.1.v20110623_0150 [40] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.426
!MESSAGE Bundle org.eclipse.core.filesystem.solaris.sparc_1.1.1.R35x_v201000319-0930 [46] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.426
!MESSAGE Bundle org.eclipse.core.filesystem.linux.x86_64_1.1.1.R35x_v201000319-0930 [93] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.core.resources.win32.x86_3.5.0.v20081020 [98] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.ui.win32.nl2_3.2.100.v201002231411 [100] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.core.filesystem.aix.ppc_1.0.1.R35x_v201000319-0930 [109] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.core.filesystem.linux.ppc_1.0.100.v20080604-1400 [111] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.core.filesystem.win32.x86.nl1_1.1.0.v201002231411 [112] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.core.filesystem.win32.x86_1.1.100.R35x_v20100928-0452 [150] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.core.filesystem.solaris.sparcv9_1.0.1.R35x_v201000319-0930 [160] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.core.filesystem.aix.ppc64_1.0.1.R35x_v201000319-0930 [241] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.core.filesystem.macosx_1.2.1.R35x_v201000319-0930 [267] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.compare.win32.nl1_1.0.0.v201002231411 [286] was not resolved.
!SUBENTRY 2 org.eclipse.compare.win32.nl1 2 0 2012-11-08 12:12:51.427
!MESSAGE Missing host org.eclipse.compare.win32_[1.0.0,1.1.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.core.filesystem.win32.x86.nl2_1.1.0.v201002231411 [296] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.update.core.win32_3.2.100.v20080107 [307] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.swt.win32.win32.x86.nl1_3.5.2.v201002231411 [308] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.swt.win32.win32.x86_3.5.2.v3557f [316] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.ui.win32.nl1_3.2.100.v201002231411 [323] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.427
!MESSAGE Bundle org.eclipse.compare.win32_1.0.0.I20090430-0408 [329] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.428
!MESSAGE Bundle org.eclipse.core.filesystem.zos.s390x_3.0.1.v20110623_0150 [332] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.428
!MESSAGE Bundle org.eclipse.core.filesystem.zos.s390_3.0.1.v20110623_0150 [337] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.428
!MESSAGE Bundle org.eclipse.compare.win32.nl2_1.0.0.v201002231411 [340] was not resolved.
!SUBENTRY 2 org.eclipse.compare.win32.nl2 2 0 2012-11-08 12:12:51.428
!MESSAGE Missing host org.eclipse.compare.win32_[1.0.0,1.1.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.428
!MESSAGE Bundle org.eclipse.core.filesystem.win32.x86_64_1.1.100.R35x_v20100928-0452 [360] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.428
!MESSAGE Bundle org.eclipse.ui.win32_3.2.100.v20090429-1800 [361] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-08 12:12:51.428
!MESSAGE Bundle org.eclipse.core.filesystem.linux.s390_3.0.1.v20110623_0150 [367] was not resolved.
Accepted answer
Hi Kirk.
I suspect that the jazz-scm/aliases file that the SCM CLI maintains is somehow corrupt. It's contents should be similar to this:
Make ˜/.jazz-scm/repositories.txt and ˜/.jazz-scm/aliases thread and process safe (138106)
I suspect that the jazz-scm/aliases file that the SCM CLI maintains is somehow corrupt. It's contents should be similar to this:
### Jazz UUID Aliases 1 lastAllocated=1010 lastRun=0 _9mLjsGQLEeKLjORpjofCGg 1000 _Apae4XHPEeGVVtgAMFkwMQ https://localhost:9443/jazz/ 0 _WSY3gLyDEeGdY4Fis3h-Ng 1001 _Apae4XHPEeGVVtgAMFkwMQ https://localhost:9443/jazz/ 0 _VKIqcLyNEeGdY4Fis3h-Ng 1002 _Apae4XHPEeGVVtgAMFkwMQ https://localhost:9443/jazz/ 0There is a known issue with very old versions of the product (2.0.0.2). What version are you running?
Make ˜/.jazz-scm/repositories.txt and ˜/.jazz-scm/aliases thread and process safe (138106)
Comments
Ah, yes. The aliases file does have references to the UUID-like entry I noticed in the error (_bkZjcdt):
_gZgkcKNIEeG_5sbhJAlSrA 0177 _bkZjcdt7Ed2msfEYJ5Ii1w https://rtc/jazz/ 31126 _znmYkHNEEd-gZIkAZVMVng 0178 _bkZjcdt7Ed2msfEYJ5Ii1w https://rtc/jazz/ 31126
I wonder whether there still is an issue, even after the fix in v2 that you referenced. We have two automated jobs that run the Jazz SCM utility on the same machine using the same user. There is a chance that they both could be running at the same time. Might there still be some kind of synchronization issue on the aliases file?
Here our our version details:
$ scm version com.ibm.team.filesystem.cli.client, version 3.0.2.v20110831_0247 com.ibm.team.filesystem.cli.tools, version 3.0.2.v20110831_0247 com.ibm.team.filesystem.cli.core, version 3.0.2.v20110819_0209
Hi Kirk.
The SCM CLI uses a lock file to synchronize access to the aliases file, so it's unlikely that your two concurrent jobs are causing the problem. To eliminate this possibility, have the two jobs use different config directories ("scm --config <alternate-config-directory> . . .") so the aliases file won't be shared.
-Matt