Legacy ImageMagick Discussions Archive

Dear all,

I am using the the imagemagick 6.2.8 Q16 and the tomcat 5.5 to develop my program and face the following problem:

13:27:08,384 ERROR [EPassSuppDocBuilder] (AppScheduler_Worker-1) Image conversation failed, keep original!

com.pccw.ittis.image.exception.ImageIOException: IMGU1006 - Image processing exception
at com.pccw.ittis.image.ImageUtil.getImageIgnoreCorrupt(ImageUtil.java:228)
at com.pccw.ittis.image.ImageUtil.getImage(ImageUtil.java:199)
at es.app.interfacefile.common.builder.EPassSuppDocBuilder.makeOutput(EPassSuppDocBuilder.java:50)
at es.app.interfacefile.common.ImageInterfaceDataFile.makeOutput(ImageInterfaceDataFile.java:30)
at es.app.interfacefile.common.InterfaceDataFile.generateOutputDataFile(InterfaceDataFile.java:117)
at es.app.interfacefile.common.InterfaceDataFile.generateOutputDataFile(InterfaceDataFile.java:150)
at es.app.interfacefile.base.BaseInterfaceGenerator.expSuppDoc(BaseInterfaceGenerator.java:525)
at es.app.interfacefile.EPassInterfaceGenerator.generateInterfaceFile(EPassInterfaceGenerator.java:468)
at es.app.interfacefile.base.BaseInterfaceGenerator.doGenerateSubmissionIF(BaseInterfaceGenerator.java:898)
at es.app.interfacefile.EPassInterfaceGenerator.genSubmissionInterface(EPassInterfaceGenerator.java:111)
at es.app.interfacefile.EPassInterfaceGenerator.genInterface(EPassInterfaceGenerator.java:93)
at es.app.interfacefile.externalif.InterfaceFileGeneratorFacade.generateSubmissionInterface(InterfaceFileGeneratorFacade.java:188)
at es.app.interfacefile.scheduler.InterfaceFileGeneratorJob.execute(InterfaceFileGeneratorJob.java:40)
at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: magick.MagickException: Unable to retrieve handle
at magick.MagickImage.getCompression(Native Method)
at com.pccw.ittis.image.ImageUtil.getImageIgnoreCorrupt(ImageUtil.java:214)
... 14 more

Does anyone has any idea of what's wrong with it?

Nearly forget to mention , the most tricky point of this bug is that when the program is rerun again , this error DOES NOT COME OUT again. i.e. this is a random error during the running of the program

Heh , could anyone help me? Many thanks.