closed.please ignore this issue.

[sunruns]

when ant kafka-0.9 , there is following error. I have no idea how to resolve. please help. CDISP9211E ERROR: The MessagingResource.xlf xliff file was not converted. CDISP0786E ERROR: The generation of the MessagingResource resource bucket failed.

[sunruns]

after I changed the jars in $STREAMS_INSTALL/java/jre/lib/ext and $JAVA_HOME, the error changed to the following: [streamsadmin@pnbcs02 com.ibm.streamsx.messaging]$ ant kafka-0.9 Buildfile: /home/streamsadmin/streamsx.messaging-5.3.1/com.ibm.streamsx.messaging/build.xml

kafka-0.9:

init: [mkdir] Created dir: /home/streamsadmin/streamsx.messaging-5.3.1/com.ibm.streamsx.messaging/impl/java/bin [mkdir] Created dir: /home/streamsadmin/streamsx.messaging-5.3.1/com.ibm.streamsx.messaging/impl/lib [mkdir] Created dir: /home/streamsadmin/streamsx.messaging-5.3.1/com.ibm.streamsx.messaging/impl/java/src-gen

copyresources: [copy] Copying 57 files to /home/streamsadmin/streamsx.messaging-5.3.1/com.ibm.streamsx.messaging/impl/java/bin

compile: [javac] Compiling 68 source files to /home/streamsadmin/streamsx.messaging-5.3.1/com.ibm.streamsx.messaging/impl/java/bin [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details.

jar: [jar] Building jar: /home/streamsadmin/streamsx.messaging-5.3.1/com.ibm.streamsx.messaging/impl/lib/com.ibm.streamsx.messaging.jar [delete] Deleting directory /home/streamsadmin/streamsx.messaging-5.3.1/com.ibm.streamsx.messaging/impl/java/bin

toolkit: [echo] Tookit to index: /home/streamsadmin/streamsx.messaging-5.3.1/com.ibm.streamsx.messaging [exec] CDISP9211E ERROR: The MessagingResource.xlf xliff file was not converted. [exec] CDISP0786E ERROR: The generation of the MessagingResource resource bucket failed. [exec] Result: 1 Caught an exception while logging the end of the build. Exception was: java.lang.NoSuchMethodError: com/ibm/icu/impl/ICUBinary.getData(Ljava/lang/ClassLoader;Ljava/lang/String;Ljava/lang/String;)Ljava/nio/ByteBuffer; at com.ibm.icu.impl.ICUResourceBundleReader$ReaderCache.createInstance(ICUResourceBundleReader.java:335) at com.ibm.icu.impl.ICUResourceBundleReader$ReaderCache.createInstance(ICUResourceBundleReader.java:324) at com.ibm.icu.impl.SoftCache.getInstance(SoftCache.java:58) at com.ibm.icu.impl.ICUResourceBundleReader.getReader(ICUResourceBundleReader.java:380) at com.ibm.icu.impl.ICUResourceBundle.createBundle(ICUResourceBundle.java:1276) at com.ibm.icu.impl.ICUResourceBundle.instantiateBundle(ICUResourceBundle.java:1145) at com.ibm.icu.impl.ICUResourceBundle.getBundleInstance(ICUResourceBundle.java:1083) at com.ibm.icu.util.UResourceBundle.getRootType(UResourceBundle.java:499) at com.ibm.icu.util.UResourceBundle.instantiateBundle(UResourceBundle.java:550) at com.ibm.icu.impl.ICUResourceBundle.createULocaleList(ICUResourceBundle.java:565) at com.ibm.icu.impl.ICUResourceBundle.access$100(ICUResourceBundle.java:32) at com.ibm.icu.impl.ICUResourceBundle$AvailEntry.getULocaleList(ICUResourceBundle.java:736) at com.ibm.icu.impl.ICUResourceBundle.getAvailableULocales(ICUResourceBundle.java:487) at com.ibm.icu.impl.ICUResourceBundle.getAvailableULocales(ICUResourceBundle.java:495) at com.ibm.icu.impl.javaspi.ICULocaleServiceProvider.getLocales(ICULocaleServiceProvider.java:133) at com.ibm.icu.impl.javaspi.ICULocaleServiceProvider.getAvailableLocales(ICULocaleServiceProvider.java:53) at com.ibm.icu.impl.javaspi.util.CurrencyNameProviderICU.getAvailableLocales(CurrencyNameProviderICU.java:39) at sun.util.locale.provider.SPILocaleProviderAdapter$CurrencyNameProviderDelegate.addImpl(SPILocaleProviderAdapter.java:497) at sun.util.locale.provider.SPILocaleProviderAdapter$CurrencyNameProviderDelegate.addImpl(SPILocaleProviderAdapter.java:491) at sun.util.locale.provider.SPILocaleProviderAdapter$1.run(SPILocaleProviderAdapter.java:109) at sun.util.locale.provider.SPILocaleProviderAdapter$1.run(SPILocaleProviderAdapter.java:86) at java.security.AccessController.doPrivileged(AccessController.java:559) at sun.util.locale.provider.SPILocaleProviderAdapter.findInstalledProvider(SPILocaleProviderAdapter.java:86) at sun.util.locale.provider.AuxLocaleProviderAdapter.getLocaleServiceProvider(AuxLocaleProviderAdapter.java:82) at sun.util.locale.provider.LocaleServiceProviderPool.(LocaleServiceProviderPool.java:145) at sun.util.locale.provider.LocaleServiceProviderPool.getPool(LocaleServiceProviderPool.java:123) at java.util.Currency.getSymbol(Currency.java:537) at java.text.DecimalFormatSymbols.initialize(DecimalFormatSymbols.java:659) at java.text.DecimalFormatSymbols.(DecimalFormatSymbols.java:124) at sun.util.locale.provider.DecimalFormatSymbolsProviderImpl.getInstance(DecimalFormatSymbolsProviderImpl.java:97) at java.text.DecimalFormatSymbols.getInstance(DecimalFormatSymbols.java:191) at sun.util.locale.provider.NumberFormatProviderImpl.getInstance(NumberFormatProviderImpl.java:190) at sun.util.locale.provider.NumberFormatProviderImpl.getIntegerInstance(NumberFormatProviderImpl.java:143) at java.text.NumberFormat.getInstance(NumberFormat.java:895) at java.text.NumberFormat.getInstance(NumberFormat.java:872) at java.text.NumberFormat.getIntegerInstance(NumberFormat.java:519) at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:650) at java.text.SimpleDateFormat.(SimpleDateFormat.java:616) at org.apache.tools.ant.util.DateUtils.(DateUtils.java:69) at org.apache.tools.ant.DefaultLogger.formatTime(DefaultLogger.java:328) at org.apache.tools.ant.DefaultLogger.buildFinished(DefaultLogger.java:177) at org.apache.tools.ant.Project.fireBuildFinished(Project.java:2110) at org.apache.tools.ant.Main.runBuild(Main.java:878) at org.apache.tools.ant.Main.startAnt(Main.java:236) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:287) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:113)

[schubon]

Hi sunruns,

I tried to reproduce even by downloading the streamsx.messaging-5.3.1 source package under releases, but on my machine it runs (I even forcefully deleted xlf compile result files in trying to provoke the error). The big difference though between your and my build log is, that I have a block where dependencies are copied from Maven. Additionally, in your log I see: ... toolkit: [echo] Tookit to index: /home/streamsadmin/streamsx.messaging-5.3.1/com.ibm.streamsx.messaging [exec] CDISP9211E ERROR: The MessagingResource.xlf xliff file was not converted. [exec] CDISP0786E ERROR: The generation of the MessagingResource resource bucket failed. [exec] Result: 1 Caught an exception while logging the end of the build. Exception was: java.lang.NoSuchMethodError: com/ibm/icu/impl/ICUBinary.getData(Ljava/lang/ClassLoader;Ljava/lang/String;Ljava/lang/String;)Ljava/nio/ByteBuffer; ...

Checking for ICUBinary shows JARs that belong to the Maven distribution.

This leads to the question: Do you have Maven installed on your machine?

Kind regards Norbert

[sunruns]

Hi Norbert, thanks for you help. In my quick start vm, there is internet connection. so ant kafka-0.9 or all or clean is okay. then I copied the jars in the opt/downloaded directory to a linux node which can't access internet. there are maven and ant installed in the linux machine, but just can't download the jars from maven repository. there is no ICUBinary jar in those jars which downloaded. so could you please tell me which jar i should download , then i can copy into opt/downloaded. as the xiliff part, it should be another problem. for sometimes there is no icu error when ant, but the xlf error always exists.

[schubon]

Hi sunruns,

as I see it ICUBinary is not used within the toolkit but by Maven. So if you have Maven installed it should already be on your machine. I have tested on my development machine and not in a Quickstart Edition (QSE). Couple of questions: You are using the latest QSE? Which runs Red Hat 7? You are using the streamsx.messaging toolkit that has been delivered with QSE (you did not download it from GitHub)? Then you build and move over to a different machine? Does your package have the .../impl/nl directory in it and is it filled (with include subDir and MessageResource.dat and Locale directories?

Kind regards Norbert

[sunruns]

Hi Norbert, to clarify, all work fine on my vm. On the metal machine, it failed. the streams version is 4.0.1.0. the os is redhat 6.5. I downloaded the streams.messaging toolkit source code 5.3.1 from github.com. I also installed ant and maven on this test machine. and for the 1st time, ant built successfully. but after I changed the jars in the $STREAMS_INSTALL/java/jre/lib/ext and a different JAVA_HOME, ant built failed with the error. I don't know how to resolve this error.

[schubon]

Hi sunruns,

can you detail this sentence of yours, please:

... but after I changed the jars in the $STREAMS_INSTALL/java/jre/lib/ext and a different JAVA_HOME, ant built failed with the error

1) Have you changed back to the original state and rerun the build successfully? 2) What exactly did you exchange? 3) Why? 4) What are the current values/contents of JAVA_HOME and $STREAMS_INSTALL/java/jre/lib/ext ?

Kind regards Norbert

[schubon]

Hi sunruns, there is one thing I missed in your last answer. The part that doesn't compile is in the translation which only has been introduced with streams v4.2.1. Thus the main problem here is, that you are using a Streams installation that is too old.

Kind regards Norbert

[sunruns]

Hi Robert, I am testing if this toolkit can produce and consume to Kafka 0.9 broker. I have successfully compile this toolkit with ant all in the streams v4.0.1 env, then successfully produce and consume to Kafka 0.10 broker. In the very first time it succeed with ant kafka-0.9, but failed to produce and consume message to kafka 0.9 broker (the error was failed to update metadata). so I changed different JAVA_HOME and different kafka library and other java library, but finally failed to compile with ICU error.

Thanks a lot Richard

[schubon]

Hi Richard,

first of all, my recommendation to work with an appropriate Streams environment (according to your other error at least v4.2.0, better v4.2.1) still holds true. I don't understand how the compile can go through given that the "StateHandler" interface of Streams and toolkit do not match. Furthermore, I don't understand why, when you encounter compilation errors, you start messing around with your JAVA_HOME environment. What, exactly, was the motivation behind that?

Kind regards Norbert

[schubon]

Hi Richard, have you upgraded Streams or downgraded the toolkit and made progress?

Kind regards Norbert