facebook

Reports project deploying to Tomcat – SHA1 digest error

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #345392 Reply

    Installed MyEclipse 2014 64-bit all in one, and created new Report Web Project and deployed to MyEclipse Tomcat 7. No other changes made to the project.

    When I start the MyEclipse Tomcat 7 server, i got the following errors:
    Dec 19, 2013 10:28:07 AM org.apache.catalina.core.ContainerBase addChildInternal
    SEVERE: ContainerBase.addChild: start:
    org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/reports]]
    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:618)
    at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1100)
    at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1618)
    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:744)
    Caused by: java.lang.SecurityException: SHA1 digest error for org/eclipse/birt/core/framework/PlatformServletContext$1.class
    at sun.security.util.ManifestEntryVerifier.verify(ManifestEntryVerifier.java:220)
    at java.util.jar.JarVerifier.processEntry(JarVerifier.java:229)
    at java.util.jar.JarVerifier.update(JarVerifier.java:216)
    at java.util.jar.JarVerifier$VerifierStream.read(JarVerifier.java:471)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
    at java.io.DataInputStream.readInt(DataInputStream.java:387)
    at org.apache.tomcat.util.bcel.classfile.ClassParser.readID(ClassParser.java:237)
    at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:114)
    at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2101)
    at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1977)
    at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1943)
    at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1928)
    at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1322)
    at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
    at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
    at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    … 10 more
    Dec 19, 2013 10:28:07 AM org.apache.catalina.startup.HostConfig deployDirectory
    SEVERE: Error deploying web application directory C:\Projects\Workspace2014\.metadata\.me_tcat7\webapps\reports
    java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/reports]]
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:618)
    at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1100)
    at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1618)
    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:744)

    #345404 Reply

    support-swapna
    Moderator

    Srikode,

    Sorry that you are seeing this issue. I could replicate the issue at my end. I have filed a PR for the dev team and they are looking into it. I will keep you posted about any workaround or fix for the issue.

    Sorry for inconvenience caused.

    #345562 Reply

    Hi Swapna,

    Any update on workaround or fix?

    Thanks,
    Srinivas

    #345632 Reply

    smcdowell
    Member

    Hi,
    We have the exact same problem after upgrading our myeclipse to the latest release on linux 64bit, running with tomcat 7.0.47.

    To correct this until they patch the dist.
    1) go to the eclipse birt site and download the runtime zip.
    http://www.eclipse.org/downloads/download.php?file=/birt/downloads/drops/R-R1-4_3_1-201309181142/birt-runtime-4_3_1.zip

    2) extract it out to a folder of your choice.

    3) find the jar file: org.eclipse.birt.runtime_4.3.1.v20130918-1142.jar and copy it to your WEB-INF/lib folder in your project to replace the shite one they distributed.

    4) Redeploy your project …Bobs you’re uncle.. It works now.

    Note: this is all we needed. Your mileage may vary. You may need to replace all the jars distributed in addition to the engine and the viewer. Just download the full package from birt site extract then overwrite the jars/folders in your project.

    #345690 Reply

    Following the steps from smcdowell post, I am able to resolve the issue, thanks to smcdowell.

    #345714 Reply

    support-swapna
    Moderator

    srikode,

    Apologies for the delayed response.

    We have fixed the issue and the fix will be out with the upcoming maintenance release for 2014 in a week’s time.

    smcdowell ,

    Thank you for posting the workaround. It will be very helpful to other users till the fix is out.

    Let us know if you see any issues.

    #351300 Reply

    Escolaris
    Member

    Tks for the solution.

Viewing 7 posts - 1 through 7 (of 7 total)
Reply To: Reports project deploying to Tomcat – SHA1 digest error

You must be logged in to post in the forum log in