Failed to start Bonita 7.2 Community

1
0
-1

I followed all the steps to install "Bonita 7.2 Tomcat bundle." And after several attempts I get this error when running startup.bat. Any suggestions?

2016-02-18 20:51:50.971 +0100 org.apache.catalina.core.AprLifecycleListener org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFORMACIÓN: La biblioteca nativa de Apache Tomcat basada en ARP que permite un rendimiento óptimo en entornos de desarrollo no ha sido hallada en java.library.path: C:\Program Files (x86)\Java\jre1.8.0_66\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;.
2016-02-18 20:51:51.568 +0100 org.apache.coyote.http11.Http11Protocol org.apache.coyote.AbstractProtocol init
INFORMACIÓN: Initializing ProtocolHandler ["http-bio-8080"]
2016-02-18 20:51:51.580 +0100 org.apache.coyote.ajp.AjpProtocol org.apache.coyote.AbstractProtocol init
INFORMACIÓN: Initializing ProtocolHandler ["ajp-bio-8009"]
2016-02-18 20:51:51.584 +0100 org.apache.catalina.startup.Catalina org.apache.catalina.startup.Catalina load
INFORMACIÓN: Initialization processed in 1068 ms
2016-02-18 20:51:51.584 +0100 bitronix.tm.integration.tomcat55.BTMLifecycleListener bitronix.tm.integration.tomcat55.BTMLifecycleListener lifecycleEvent
INFORMACIÓN: Starting Bitronix Transaction Manager
2016-02-18 20:51:51.619 +0100 bitronix.tm.BitronixTransactionManager bitronix.tm.BitronixTransactionManager logVersion
INFORMACIÓN: Bitronix Transaction Manager version 2.1.3
2016-02-18 20:51:51.623 +0100 bitronix.tm.Configuration bitronix.tm.Configuration buildServerIdArray
INFORMACIÓN: JVM unique ID:
2016-02-18 20:51:51.853 +0100 bitronix.tm.resource.ResourceLoader bitronix.tm.resource.ResourceLoader init
INFORMACIÓN: reading resources configuration from E:\BonitaBPM/conf/bitronix-resources.properties
2016-02-18 20:51:52.252 +0100 bitronix.tm.recovery.Recoverer bitronix.tm.recovery.Recoverer run
INFORMACIÓN: recovery committed 0 dangling transaction(s) and rolled back 0 aborted transaction(s) on 2 resource(s) [jdbc/BusinessDataDSXA, jdbc/bonitaDSXA] (restricted to serverId 'bonita-tomcat-btm-node0')
2016-02-18 20:51:52.299 +0100 org.apache.catalina.core.StandardService org.apache.catalina.core.StandardService startInternal
INFORMACIÓN: Arrancando servicio Catalina
2016-02-18 20:51:52.303 +0100 org.apache.catalina.core.StandardEngine org.apache.catalina.core.StandardEngine startInternal
INFORMACIÓN: Starting Servlet Engine: Apache Tomcat/7.0.67
2016-02-18 20:51:52.322 +0100 org.apache.catalina.startup.HostConfig org.apache.catalina.startup.HostConfig deployDescriptor
INFORMACIÓN: Desplieque del descriptor de configuración E:\BonitaBPM\conf\Catalina\localhost\bonita.xml
2016-02-18 20:51:52.393 +0100 org.apache.catalina.startup.ContextConfig org.apache.catalina.startup.ContextConfig beforeStart
GRAVE: Excepción arreglando docBase: /bonita
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(Unknown Source)
at java.util.zip.ZipFile.(Unknown Source)
at java.util.jar.JarFile.(Unknown Source)
at java.util.jar.JarFile.(Unknown Source)
at sun.net.www.protocol.jar.URLJarFile.(Unknown Source)
at sun.net.www.protocol.jar.URLJarFile.getJarFile(Unknown Source)
at sun.net.www.protocol.jar.JarFileFactory.get(Unknown Source)
at sun.net.www.protocol.jar.JarURLConnection.connect(Unknown Source)
at sun.net.www.protocol.jar.JarURLConnection.getJarFile(Unknown Source)
at org.apache.catalina.startup.ExpandWar.expand(ExpandWar.java:111)
at org.apache.catalina.startup.ContextConfig.fixDocBase(ContextConfig.java:754)
at org.apache.catalina.startup.ContextConfig.beforeStart(ContextConfig.java:863)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:388)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
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.deployDescriptor(HostConfig.java:677)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1939)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

2016-02-18 20:51:52.752 +0100 org.apache.catalina.startup.TldConfig org.apache.catalina.startup.TldConfig execute
INFORMACIÓN: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
2016-02-18 20:51:52.768 +0100 org.apache.tomcat.jdbc.pool.ConnectionPool org.apache.tomcat.jdbc.pool.ConnectionPool checkPoolConfiguration
ADVERTENCIA: maxIdle is larger than maxActive, setting maxIdle to: 17
2016-02-18 20:51:52.994 +0100 org.apache.tomcat.jdbc.pool.ConnectionPool org.apache.tomcat.jdbc.pool.ConnectionPool checkPoolConfiguration
ADVERTENCIA: maxIdle is larger than maxActive, setting maxIdle to: 17
2016-02-18 20:51:53.292 +0100 org.apache.catalina.startup.HostConfig org.apache.catalina.startup.HostConfig deployDescriptor
INFORMACIÓN: Deployment of configuration descriptor E:\BonitaBPM\conf\Catalina\localhost\bonita.xml has finished in 965 ms
2016-02-18 20:51:53.295 +0100 org.apache.catalina.startup.HostConfig org.apache.catalina.startup.HostConfig deployDirectory
INFORMACIÓN: Despliegue del directorio E:\BonitaBPM\webapps\manager de la aplicación web
2016-02-18 20:51:53.463 +0100 org.apache.catalina.startup.TldConfig org.apache.catalina.startup.TldConfig execute
INFORMACIÓN: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
2016-02-18 20:51:53.475 +0100 org.apache.catalina.startup.HostConfig org.apache.catalina.startup.HostConfig deployDirectory
INFORMACIÓN: Deployment of web application directory E:\BonitaBPM\webapps\manager has finished in 180 ms
2016-02-18 20:51:53.475 +0100 org.apache.catalina.startup.HostConfig org.apache.catalina.startup.HostConfig deployDirectory
INFORMACIÓN: Despliegue del directorio E:\BonitaBPM\webapps\ROOT de la aplicación web
2016-02-18 20:51:53.616 +0100 org.apache.catalina.startup.TldConfig org.apache.catalina.startup.TldConfig execute
INFORMACIÓN: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
2016-02-18 20:51:53.623 +0100 org.apache.catalina.startup.HostConfig org.apache.catalina.startup.HostConfig deployDirectory
INFORMACIÓN: Deployment of web application directory E:\BonitaBPM\webapps\ROOT has finished in 148 ms
2016-02-18 20:51:53.627 +0100 org.apache.coyote.http11.Http11Protocol org.apache.coyote.AbstractProtocol start
INFORMACIÓN: Starting ProtocolHandler ["http-bio-8080"]
2016-02-18 20:51:53.635 +0100 org.apache.coyote.ajp.AjpProtocol org.apache.coyote.AbstractProtocol start
INFORMACIÓN: Starting ProtocolHandler ["ajp-bio-8009"]
2016-02-18 20:51:53.639 +0100 org.apache.catalina.startup.Catalina org.apache.catalina.startup.Catalina start
INFORMACIÓN: Server startup in 2052 ms

Comments

Submitted by Sean McP on Sun, 02/21/2016 - 09:24

I think the download is corrupt, I would download it again...

regards
Seán

1 answer

1
0
-1

Hi,

Your stack trace tells your running your tomcat using java 1.8

using java 1.7 it should work

Comments

Submitted by Sean McP on Thu, 02/25/2016 - 06:44

I use 1.8.x_7x (whatever the latest is and it works fine....

regards

Notifications