Hi.
I'm using GroupDocs.Annotations to open mostly PDF files. I created a application which uses this component to open files. The same application is deployed on two environments.
On the development environment, the PDF file is opened and the cache folder stores cache files and keeps growing when I open unopened files.
On the tests environment, the GroupDocs viewer is shown, but the number of pages is zero, the labels and titles on the viewer are in english (I translated it to Portuguese -- this translation occurs only when the file is successfully loaded on GroupDocs Viewer), no thumbnails is shown and the message "Loading your content..." stays on the screen indefinitely. The cache folder stays on 28KB, even when I try to open new files. The only files that are on the 'cache' folder are anotation.db, data.db and an empty folder named ye. I tried to wait for more than 4 minutes, without response. The log file of Wildfly server on the tests is attached to this message, but nothing indicates a problem using GroupDocs or on the application. There's no message of warning of error on the Javascript console panel (pressing F12 on Google Chrome).
- On both environment we are using Wildfly Application Server 8.2.0, with JDK 8.
- Doesn't matter wich file I try to open. I tried simple and complex PDF and TIFF files. The results are always the same.
- Both environments have enough memory and processing to open the application and to use GroupDocs.
- I'm using Google Chrome browser to test the application
With your experience, what can be happening to make this problem happen? I'm without tips where I can search for the problem, because both environment are much similar.
Hello,
Thank you for your request.
Could you please specify next: Do you use quite the identical applications on both servers , or you made any changes in application.properties file ? If you have any changes in this file, then you should bring them to a common mind and try again . Also we recommend you to test any of our examples for these servers and maybe you will be able to find the reason.
As we can see from your log file, that yes, all works normal , but we suspect that the problem also can depends from css stiles. Please check these both applications on other web browsers. Some time ago we had similar problems with our GroupDocs.Viewer for Java library and in other browsers these problems were not reproducible.
Please follow our advices and if you will have any new information then please share it with us.
-------
Best regards,
Evgen Efimov
http://groupdocs.com
Your Document Collaboration APIs
Follow us on LinkedIn, Twitter, Facebook and Google+
Hi.
About the differences, I will confirm that there's no difference between the code of both applications o the environments. I'm almost sure that is the same codebase.
About using different browsers to see if the problem happens, I tried with IE10, Chrome 47 and Firefox Developer Edition 44. The test results are the same on the browsers.
One thing I noticed now is that the problem is occurring only with PDF files. I thought that I had tested with TIFF files, but today when I tried to use a TIFF file with the viewer the visualization worked fine. Tested with multipaged, simple and image-only Tiff files and it worked well. Tried with different PDF files, big, small, with text, with images, complex and simple. Every one of them failed to open on the viewer.
Hello Rafael ,
Thank you for coming back.
It's really strange issue and without your source of application we can't help you with this issue . As we understand that you get the issue only with your test server and for your development server all files are shown well?
To be able to help you, we need next info :
- your sample application, that can reproduce the issue with guide;
- your server configuration (OS , version of browser)
- from your previous post , we understand that you use Wildfly Application Server 8.2.0, with JDK 8. But please specify the exact version of JDK.
We will wait your details and will be glad to help you .
-------
Best regards,
Evgen Efimov
http://groupdocs.com
Your Document Collaboration APIs
Follow us on LinkedIn, Twitter, Facebook and Google+
Thank you. I will try to resolve the problem here before submit a sample application for you.
How can I enable some logging framework to use with GroupDocs or SQLite? Is there a configuration for SLF4J or log4j which I can use to enable debug logging?
Hello ,
Basically, our library already uses Java standard API for handling the logs. It's java.util.logging API and we not provide any specific configurations for it or for other frameworks for logging.
At the moment you can show an error in console via this code :
Logger.getLogger(getClass().getName()).log(Level.SEVERE, "test message");
Also you can independently configure this logger, if you will use standart configuration for java.util.logging API.
If you will have more questions please feel free to contact us.
-------
Best regards,
Evgen Efimov
http://groupdocs.com
Your Document Collaboration APIs
Follow us on LinkedIn, Twitter, Facebook and Google+
I mean if there’s no specific configuration for enabling logging of internal classes of GroupDocs, SQLite or OrmLite. For example, to enable logging of Atomikos library for log4j we have to put the lines described in http://www.atomikos.com/Documentation/ConfiguringTheLogs#Log4J. The log4j were extensively used to write the internal classes of Atomikos, but to enable logging we have to configure the properties file of log4j to enable the printing of it.
Hello Rafael ,
Unfortunately no , at the moment we don't provide any logging configurations for internal classes of GroupDocs, SQLite or OrmLite. But our Product team was informed about your request and we have created a ticket in our system (ANNOTATIONJAVA-886). When the improvement will be released you’ll get an email notification.
We apologize for the inconvenience.
--------
Best regards,
Evgen Efimov
http://groupdocs.com
Your Document Collaboration APIs
Follow us on LinkedIn, Twitter, Facebook and Google+
I figured out what was the problem. It’s a bug using Aspose PDF version 10.3.0. I had to change to version 9.7.1 to resolve it.
First, I could debug the code on Wildfly server to see where the code was hanging. It were on the ViewDocumentServlet, method AnnotaionHandler.viewDocumentHandler() like on the attached image. Unfortunately I couldn’t reproduce the problem on another environment. I tried to reproduce it on a machine of a coleague, which runs Linux Mint. We put the app on a WildFly server on domain mode, but the problem doesn’t occur.
The only thing I was sure was that the viewer worked on the production server few weeks ago. So I deployed a old version of the application to verify. And discovered that the problem occurred when I upgraded GroupDocs.Annotation from version 1.9.0 to 2.0.0. On that upgrade, the version of dependent libraries of Aspose were upgraded too. GroupDocs.Annotations depends on the following Aspose libraries:
- aspose-cells-8.4.1.jar
- aspose-diagram-5.2.0.jar
- aspose-email-5.2.0.0.jar
- aspose-imaging-2.7.0.jar
- aspose-pdf-10.3.0.jar
- aspose-slides-15.4.0.jar
- aspose-tasks-8.3.0.jar
- aspose-words-15.4.0.jar
I tried to use the application with a more recent version of Aspose PDF (10.4.0) and with an older, but with the same features (10.0.0), but the problem were still working. So, I tried with the last version before version 10.0.0 and it worked. I’m using Aspose PDF 9.7.1 now. The other default Aspose JARs needed to use GroupDocs.Annotations 2.0.0 were kept.
The hardest part to discover the cause of this problem were that PDFs that were once viewed on the Viewer before the upgrade of GroupDocs.Annotation hadn’t any problems to open on the viewer. So, when I upgraded to newer version of GroupDocs.Annotations I didn’t have problems with this files, because it were cached and I thought that the viewer were ok. The problem only occured with new files or pages never shown on the viewer.
I extremmely recommend that you inform your customers that they can be faced with this problem. It were very difficult to discover and find its cause. For now, I don’t use a feature that probably were introduced with Aspose PDF 10, but I don’t want to keep using an older library. Will you investigate this bug?
Hello Rafael,
Thank you for this information.
We will investigate this issue with our Product team and will notify you when we will have any results .
We apologize for the inconvenience.
-------
Best regards,
Evgen Efimov
http://groupdocs.com
Your Document Collaboration APIs
Follow us on LinkedIn, Twitter, Facebook and Google+
Hello Rafael,
We tried to reproduce your issue with our GroupDocs.Annotation library on WildFly server, but unsuccessfully. We have ran our library in standalone mode for WildFly server but the issue is not occurs . All .pdf documents rendered well, we also have removed the cache and tried again , but without effect.
May be you can create step by step guide for us , for example with our servlet sample with your full configuration, that we can reproduce the issue on our side . And then we will be able to fix this issue.
We will wait for your guide and will be glad to help you .
------
Best regards,
Evgen Efimov
http://groupdocs.com
Your Document Collaboration APIs
Follow us on LinkedIn, Twitter, Facebook and Google+
Hi, Evgen. The problem only occurs on Wildfly on Domain mode. I tried to reproduce it on another machine, but I couldn’t. When I can give you a step by step guide to reproduce the problem I will tell you. What I can tell now is that switching Aspose PDF to version 9.7.1 resolved my problem.
Hello ,
We glad to hear that you have resolved your issue.
We also will try to reproduce the issue with domain mode. But your guide will speed up our investigation, so, we still wait for it.
---------
Best regards,
Evgen Efimov
http://groupdocs.com
Your Document Collaboration APIs
Follow us on LinkedIn, Twitter, Facebook and Google+