Issue starting Tomcat with the lastest Viewer version

GroupDocs.Viewer Product Family
1

Hi,


we upgraded Viewer for Java to the latest version and now we’re seeing the following exception in the log when Tomcat is starting (Xss is configured to a very high value already: 32Mb)

Caused by: java.lang.IllegalStateException: Unable to complete the scan for annotations for web application [/cara] due to a StackOverflowError. Possible root causes include a too low setting for -Xss and illegal cyclic inheritance dependencies. The class hierarchy being processed was [com.groupdocs.viewer.internal.c.a.e.internal.ah.O->com.groupdocs.viewer.internal.c.a.e.internal.ah.M->com.groupdocs.viewer.internal.c.a.e.internal.ah.O]
at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:2109)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2056)


Any idea why is it happening? With previous version it works fine.

Thanks,
Mariusz
2

This is a full stack trace, it fails all the time:


SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/cara]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1229)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1875)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalStateException: Unable to complete the scan for annotations for web application [/cara] due to a StackOverflowError. Possible root causes include a too low setting for -Xss and illegal cyclic inheritance dependencies. The class hierarchy being processed was [com.groupdocs.viewer.internal.c.a.e.internal.ah.O->com.groupdocs.viewer.internal.c.a.e.internal.ah.M->com.groupdocs.viewer.internal.c.a.e.internal.ah.O]
at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:2109)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2056)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1931)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1897)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1882)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1314)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:873)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:371)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5355)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 10 more

Dec 10, 2015 4:16:51 AM org.apache.catalina.startup.HostConfig deployDirectory

3
Hello Mariusz,

Thank you for your request.

Basically this error indicates that you have low memory setting for -Xss and that you should increase it. Could you please specify all your JVM options for your environment . Did you try to increase this parameter to 64mb?

We will investigate the issue on our side with your JVM options and we will try to find a reason with our new version of the library.

We will wait your information.

-------

Best regards,
Evgen Efimov

http://groupdocs.com
Your Document Collaboration APIs
Follow us on LinkedIn, Twitter, Facebook and Google+

4

This setting used to be 16mb and v2.13 works fine with that setting, I increased it already since v2.14 is failing, but no luck. I will try with a bigger setting, but anyway that issue points to some stack issue in the library.

Maximum memory pool is configured to 4gb, max perm size is 512mb. I have several applications running on that Tomcat instance and only the one with viewer 2.14 fails to start.
5
Hello Mariusz,

Thank you for your details.

We are sorry but we can't reproduce the issue on our side. Seems that we need your project example to investigate this issue that depends from our library. Could you please share it with us and we 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+

6

Nevermind… I just realized that I had both v2.13 and v2.14 jars in my webapp.

After removing the old one it works fine. Sorry for the confusion. Thanks anyway!

Mariusz
7
Hello again,

We glad to hear this. 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+