When trying to start/open essential viewer, by running start.bat I get the following error :
installation is somehow finished (and viewer is running, but the several components seem not to be installed, so I'm getting other errors (probably file/directory missing) using the app. (example :
net.sf.saxon.s9api.SaxonApiException: I/O error reported by XML parser processing file:/C:/standalone_essential_v615/standalone_essential_v615/Tomcat7_essentialviewer/webapps/essential_viewer/editors/application/application-editor/core_application_editor.html: C:\standalone_essential_v615\standalone_essential_v615\Tomcat7_essentialviewer\webapps\essential_viewer\editors\application\application-editor\core_application_editor.html (The system cannot find the path specified)
)
org.apache.catalina.startup.ContextConfig processAnnotationsJar
SEVERE: Unable to process Jar entry [META-INF/versions/9/module-info.class] from Jar [jar:file:/C:/standalone_essential_v615/standalone_essential_v615/Tomcat7_essentialimport/webapps/essential_import_utility/WEB-INF/lib/bcprov-jdk15on-1.70.jar!/] for annotations
org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 19
at org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:97)
at org.apache.tomcat.util.bcel.classfile.ConstantPool.<init>(ConstantPool.java:55)
at org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:176)
at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:85)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2089)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1965)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1931)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1916)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1330)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:889)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:386)
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:5405)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
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:652)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1095)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1960)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Error installing v615 - Essential in a Box -
Can you open Tomcat and see if the viewer is showing and running OK from Tomcat's perspective
1) Put http://localhost:8080/manager/html in the url
The username/password is usually [email protected]/admin when you first install. (it may be admin/admin)
2) Can you see essential_viewer in the applications? Is it running? what happens if you click essential_viewer?
Thanks
1) Put http://localhost:8080/manager/html in the url
The username/password is usually [email protected]/admin when you first install. (it may be admin/admin)
2) Can you see essential_viewer in the applications? Is it running? what happens if you click essential_viewer?
Thanks
- neil.walsh
- Posts: 474
- Joined: 16 Feb 2009, 13:45
- Contact:
Hi boumako,
It sounds like some files which don't belong in Essential Open Source have made it into the release. These files may be source of the issue.
I'll take a look at get back to you on this.
Cheers
Neil
It sounds like some files which don't belong in Essential Open Source have made it into the release. These files may be source of the issue.
I'll take a look at get back to you on this.
Cheers
Neil