I am afraid I have not yet completed my testing over Linux environment because I have encountered some issues over my Linux instance. However I am trying my level best to get them fixed ASAP so that I can try replicating this scenario over it. Please spare us little more time. Please accept our humble apologies for the delay and inconvenience.
I have further investigated this problem on Linux RedHat Enterprise 5 and I am able to notice the same Exception. However I am also unable to notice this problem on Windows Operating system. For the sake of correction, I have logged this problem as PDFJAVA-28967 in our issue tracking system. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.
we have a release of our product on this 31st July. Could you please let me know when will this fix be available ?
This is working on 2.7.0 and its failing in the latest version 2.9.0 which should not be the case for a product like Aspose. Some extra fixes/functionalities should go with the latest releases and not SOME EXTRA ADDITIONAL BUGS.
We have further investigated this issue and have found that Aspose.Pdf for Java is working correctly over Ubuntu OS. Can you please share which version of Linux you are using ?
We are really sorry for the delay and inconvenience.
It will really help us in replicating this issue in our environment. We will try our level best to get it fixed ASAP. Your patience and comprehension is greatly appreciated in this regard. We apologize for your inconvenience.
We have been able to figure out some reasons that might be causing this issue and our development team is still working hard to get it fixed ASAP. Nevertheless I have request them to share the ETA regarding its resolution. Please be patient and spare us little time. We are really sorry for the delay and inconvenience.
I am pleased to share that the issue reported earlier has been fixed but further investigation have revealed some other issues that might have occurred because of this problem. Our development team is trying to fix all the related issues. We will keep you posted on the status of correction.
Our humble request is to please be little patient and spare us little time. We are really sorry for this inconvenience.
I am pleased to inform you that the issue reported earlier has been fixed. Please try using the attached HotFix and in case the problem still persists, please feel free to contact.
Please note that by default DPI for headless environment is set to 96, However you can change it to any reasonable value (i.e. 72,120,160) by setting aspose.pdf.dpi property. For example: java -Daspose.pdf.dpi=120 …
Instead of using the earlier version, please replace it with this HotFix. Try compiling and executing the code with this version and in case you encounter any problem, please feel free to contact.
I have the same issue. After downloading the hot fix, it is still same error in Unix:
hd:[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' Wed Aug 03 13:35:34 EDT 2011 gds.util.Form1MLMailer(getPDFfromXml:352) Stack Trace..java.lang.RuntimeException: Couldn't convert image stream: null at aspose.pdf.figure.Abi.a(SourceFile:95) at aspose.pdf.figure.Aba.a(SourceFile:166) at aspose.pdf.figure.Aba.a(SourceFile:96) at aspose.pdf.xml.Abh.a(SourceFile:226) at aspose.pdf.xml.Abh.a(SourceFile:632) at aspose.pdf.xml.Abi.a(SourceFile:577) at aspose.pdf.xml.Acc.a(SourceFile:796) at aspose.pdf.xml.Aar.a(SourceFile:97) at aspose.pdf.xml.Aba.a(SourceFile:112) at aspose.pdf.Pdf.save(SourceFile:1166) at aspose.pdf.Pdf.save(SourceFile:1112) at gds.util.Form1MLMailer.getPDFfromXml(Form1MLMailer.java:335)
Thanks for using the hotfix and sharing the StackTrace.
We will further look into this stacktrace information and see if we can figure out some idea regarding its resolution. Please be patient and spare us little time. We are sorry for your inconvenience.
I have discussed this matter with development team and it seems to be another new bug related to our GifDecoder. Please try using the attached HotFix. It might not resolve your problem but it will show full stack trace about the exception. Thanks for your cooperation.