Camunda mit Tomcat TomEE PluME

417 views
Skip to first unread message

kstoe...@gmail.com

unread,
Mar 23, 2015, 10:28:31 AM3/23/15
to camunda-...@googlegroups.com, karl-hein...@gmx.at
Hallo zusammen,

ich bin neu hier und und versuche gerade mich etwas mit Camunda zu beschäftigen. Genau gesagt versuche ich gerade Camunda auf einer eigenen Tomcat Umgebung zu installieren.
Es geht um die Tomcat TomEE PluME (http://tomee.apache.org/downloads.html)

Ich bin der Anleitung http://docs.camunda.org/latest/guides/installation-guide/tomcat/#bpm-platform-install-the-platform-on-a-vanilla-tomcat gefolgt.

Bin jedoch auf 2 Probleme gestoßen, bei denen ich einfach nicht weiterkomme :(

1.) Im ersten Schritt habe ich versucht auf eine MySQL Datenbank zuzugreifen. Dazu habe ich eine Datenbank mit dem Namen "option-store" angelegt. Dann bin ich so wie in der Anleitung beschrieben vorgegangen und habe die SQL Scripts zum erstellen der Tabellen ausgeführt. (Tabellen sind in der Datenbank angelegt)
Ich habe mir den mysql-connector-java-5.1.34 Driver heruntergeladen und in den Ordner apache-tomee-1.7.1-plume\lib abgelegt.
In der conf/server.xml habe ich dann die Verbindung angegeben:
<Resource
name="jdbc/option-store" type="javax.sql.DataSource"
maxActive="100" maxIdle="30" maxWait="10000"
url="jdbc:mysql://localhost:3306/option-store"
driverClassName="com.mysql.jdbc.Driver"
username="root" password=""
/>


Auch die libs habe ich kopiert. Von camunda-bpm-tomcat-7.2.0\lib nach apache-tomee-1.7.1-plume\lib
und den Bootstrap Server Listener habe ich in der server.xml hinzugefügt:
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
<!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
<Listener className="org.apache.catalina.core.JasperListener" />
<!-- Prevent memory leaks due to use of particular java/javax APIs-->
<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />

<Listener className="org.camunda.bpm.container.impl.tomcat.TomcatBpmPlatformBootstrap" />

<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
<Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />

Wenn ich jedoch dann Tomcat starten will, sieht man kurz das CMD Fenster und es läuft kurz etwas durch, aber dann verschwindet es wieder und nichts ist passiert. Im Catalina-log File des Tomcat ist folgende Exception aufgetreten:
Mär 23, 2015 12:02:45 PM org.camunda.bpm.engine.impl.jobexecutor.SequentialJobAcquisitionRunnable run
Information: JobExecutor[org.camunda.bpm.engine.impl.jobexecutor.RuntimeContainerJobExecutor] stopped job acquisition
Mär 23, 2015 12:02:45 PM org.apache.catalina.startup.Catalina start
Schwerwiegend: The required Server component failed to start so Tomcat is unable to start.
org.apache.catalina.LifecycleException: Failed to start component [StandardServer[8005]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.startup.Catalina.start(Catalina.java:689)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:321)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
Caused by: org.camunda.bpm.engine.ProcessEngineException: Exception while performing 'deploy BPM platform => Start process engine default': couldn't lookup datasource from java:jdbc/ProcessEngine: Name [ProcessEngine] is not bound in this Context. Unable to find [ProcessEngine].
at org.camunda.bpm.container.impl.spi.DeploymentOperation.execute(DeploymentOperation.java:134)
at org.camunda.bpm.container.impl.jmx.MBeanServiceContainer.executeDeploymentOperation(MBeanServiceContainer.java:148)
at org.camunda.bpm.container.impl.spi.DeploymentOperation$DeploymentOperationBuilder.execute(DeploymentOperation.java:209)
at org.camunda.bpm.container.impl.tomcat.TomcatBpmPlatformBootstrap.deployBpmPlatform(TomcatBpmPlatformBootstrap.java:69)
at org.camunda.bpm.container.impl.tomcat.TomcatBpmPlatformBootstrap.lifecycleEvent(TomcatBpmPlatformBootstrap.java:55)
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.setState(LifecycleBase.java:347)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:732)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 7 more
Caused by: org.camunda.bpm.engine.ProcessEngineException: couldn't lookup datasource from java:jdbc/ProcessEngine: Name [ProcessEngine] is not bound in this Context. Unable to find [ProcessEngine].
at org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl.initDataSource(ProcessEngineConfigurationImpl.java:661)
at org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl.init(ProcessEngineConfigurationImpl.java:484)
at org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl.buildProcessEngine(ProcessEngineConfigurationImpl.java:454)
at org.camunda.bpm.container.impl.jmx.services.JmxManagedProcessEngineController.start(JmxManagedProcessEngineController.java:34)
at org.camunda.bpm.container.impl.jmx.MBeanServiceContainer.startService(MBeanServiceContainer.java:67)
at org.camunda.bpm.container.impl.jmx.MBeanServiceContainer.startService(MBeanServiceContainer.java:53)
at org.camunda.bpm.container.impl.deployment.StartProcessEngineStep.performOperationStep(StartProcessEngineStep.java:114)
at org.camunda.bpm.container.impl.spi.DeploymentOperation.execute(DeploymentOperation.java:117)
... 17 more
Caused by: javax.naming.NameNotFoundException: Name [ProcessEngine] is not bound in this Context. Unable to find [ProcessEngine].
at org.apache.naming.NamingContext.lookup(NamingContext.java:819)
at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
at org.apache.naming.NamingContext.lookup(NamingContext.java:830)
at org.apache.naming.NamingContext.lookup(NamingContext.java:167)
at org.apache.naming.SelectorContext.lookup(SelectorContext.java:156)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl.initDataSource(ProcessEngineConfigurationImpl.java:659)
... 24 more

Mär 23, 2015 12:02:45 PM org.camunda.bpm.container.impl.tomcat.TomcatBpmPlatformBootstrap undeployBpmPlatform
Information: camunda BPM platform stopped.
Mär 23, 2015 12:02:45 PM org.apache.catalina.util.LifecycleBase destroy
Warnung: Calling stop() on failed component [StandardServer[8005]] to trigger clean-up did not complete.
org.apache.catalina.LifecycleException: Failed to stop component [StandardServer[8005]]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:272)
at org.apache.catalina.startup.Catalina.start(Catalina.java:693)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:321)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
Caused by: org.apache.catalina.LifecycleException: An invalid Lifecycle transition was attempted ([before_stop]) for component [StandardService[Catalina]] in state [INITIALIZED]
at org.apache.catalina.util.LifecycleBase.invalidTransition(LifecycleBase.java:409)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:219)
at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:760)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
... 8 more

Mär 23, 2015 12:02:45 PM org.apache.coyote.AbstractProtocol destroy
Information: Destroying ProtocolHandler ["http-bio-8080"]
Mär 23, 2015 12:02:45 PM org.apache.coyote.AbstractProtocol destroy
Information: Destroying ProtocolHandler ["ajp-bio-8009"]

2.) Ich habe dann auch noch versucht nicht die MySQL Datenbank sondern wie bei dem Standalone Camunda Tomcat die h2 Datenbank zu verwenden. Hierzu habe ich einfach die server.xml vom camunda-bpm-tomcat-7.2.0 kopiert und dann versucht den Tomcat zu starten.
Das hat funktioniert und auch die Camunda welcome page konnte ich öffnen (das war im Fall mit der MySQL DB nicht möglich). Wenn ich dann aber das Camunda Cockpit und die Taskliste installieren will, geht das leider nicht. Ich habe das war file wie im Punkt "Install camunda Cockpit and Tasklist" beschrieben heruntergeladen und in den webapp Ordner gegeben, wenn ich dann aber den Tomcat starte dann bekomme ich einen Error:

Information: Deployed Application(path=C:\Users\Charly\Desktop\apache-tomee-1.7.1-plume\webapps\camunda-webapp-tomcat-7.2.0)
Mär 23, 2015 11:31:05 AM org.apache.openejb.observer.ObserverManager$MethodInvocation invoke
Schwerwiegend: error invoking org.apache.tomee.webservices.TomeeJaxRsService@18c6d42c
java.lang.NoClassDefFoundError: org/apache/http/HttpException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2493)
at java.lang.Class.getConstructors(Class.java:1517)
at org.apache.openejb.server.cxf.rs.CxfRsHttpListener$ProviderFactory.newInstance(CxfRsHttpListener.java:687)
at org.apache.openejb.assembler.classic.util.ServiceInfos.resolve(ServiceInfos.java:98)
at org.apache.openejb.server.cxf.rs.CxfRsHttpListener.providers(CxfRsHttpListener.java:330)
at org.apache.openejb.server.cxf.rs.CxfRsHttpListener.configureFactory(CxfRsHttpListener.java:651)
at org.apache.openejb.server.cxf.rs.CxfRsHttpListener.deployApplication(CxfRsHttpListener.java:393)
at org.apache.openejb.server.rest.RESTService.deployApplication(RESTService.java:463)
at org.apache.openejb.server.rest.RESTService.afterApplicationCreated(RESTService.java:233)
at org.apache.tomee.webservices.TomeeJaxRsService.afterApplicationCreated(TomeeJaxRsService.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.openejb.observer.ObserverManager$MethodInvocation.invoke(ObserverManager.java:399)
at org.apache.openejb.observer.ObserverManager$InvocationList.invoke(ObserverManager.java:514)
at org.apache.openejb.observer.ObserverManager.doFire(ObserverManager.java:110)
at org.apache.openejb.observer.ObserverManager.fireEvent(ObserverManager.java:99)
at org.apache.openejb.loader.SystemInstance.fireEvent(SystemInstance.java:134)
at org.apache.tomee.catalina.TomcatWebAppBuilder.afterStart(TomcatWebAppBuilder.java:1651)
at org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:116)
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:168)
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:649)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1083)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1880)
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.ClassNotFoundException: org.apache.http.HttpException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at org.apache.tomee.catalina.LazyStopWebappClassLoader.loadClass(LazyStopWebappClassLoader.java:129)
... 36 more


Kann mir hier bitte jemand weiterhelfen? Mein Ziel wäre das der TomcatEE PluME mit einer MySQL Datenbank läuft.
Ich benötige ein BPMS Tool für die Umsetzung meiner Masterarbeit und ich würde da gerne Camunda verwenden, wenn ich diese Konfiguration jedoch nicht hinbekomme, muss ich ein anderes Tool wählen.

Vielen Dank!
Karl-Heinz Stöckler

Christian Lipphardt

unread,
Mar 23, 2015, 11:44:38 AM3/23/15
to camunda-...@googlegroups.com, karl-hein...@gmx.at, kstoe...@gmail.com
Hi Karl-Heinz,

Regarding your first question, you used the wrong name for the DataSource. It must be 'jdbc/ProcessEngine' like:

<Resource
       
name="jdbc/ProcessEngine" type="javax.sql.DataSource"

       
maxActive="100" maxIdle="30" maxWait="10000"
       
url="jdbc:mysql://localhost:3306/option-store"
        driverClassName="com.mysql.jdbc.Driver"
       
username="root" password=""
/>

The second problem seems to be related to ClassLoading. Did you use the WAR download from [1] or the WAR inside the camunda tomcat distribution[2]?

Cheers,
Christian

[1]: http://camunda.org/release/camunda-bpm/tomcat/7.2/camunda-webapp-tomcat-standalone-7.2.0.war
[2]: http://camunda.org/release/camunda-bpm/tomcat/7.3/camunda-bpm-tomcat-7.3.0-alpha2.zip

kstoe...@gmail.com

unread,
Mar 23, 2015, 12:23:35 PM3/23/15
to camunda-...@googlegroups.com, karl-hein...@gmx.at, kstoe...@gmail.com
Hi Christian,

regarding the first question you have beern right. Thanks a lot.

Now at least the Tomcat starts properly!


Regarding the second point:
For copying the libs (for the step "Add necessary libraries to vanilla Tomcat 7" in the guide: http://docs.camunda.org/latest/guides/installation-guide/tomcat/#bpm-platform) I used this one: http://camunda.org/release/camunda-bpm/tomcat/7.2/camunda-bpm-tomcat-7.2.0.zip

And for Installing the Cockpit and Tasklist I used the this one https://app.camunda.com/nexus/content/groups/public/org/camunda/bpm/webapp/camunda-webapp-tomcat/7.2.0/camunda-webapp-tomcat-7.2.0.war

Now I also tried the one [1]camunda-webapp-tomcat-standalone-7.2.0.war which you provided instead of the camunda-webapp-tomcat-7.2.0.war. With this one Tomcat starts without the error, but I can not open the camunda welcome page, cockpit or tasklist.

I tried the links:
- http://localhost:8080/camunda-welcome/index.html
- http://localhost:8080/camunda/app/cockpit/
- http://localhost:8080/camunda/app/tasklist
which worked for the prepackaged camunda tomcat

In my \apache-tomee-1.7.1-plume\webapps Folder there are now the following folders/elements:
- camunda-webapp-tomcat-standalone-7.2.0
- docs
- host-manager
- manager
- ROOT
- tomee
- camunda-webapp-tomcat-standalone-7.2.0.war

I did not find any war file in the [2] Link you provided

Thanks
Karl-Heinz

Christian Lipphardt

unread,
Mar 24, 2015, 4:00:26 AM3/24/15
to camunda-...@googlegroups.com, karl-hein...@gmx.at, kstoe...@gmail.com
Hi Karl-Heinz,

Okay, you used the correct artifacts previously. Please delete the `camunda-webapp-tomcat-
standalone-7.2.0.war`, it is off no use to you.

1. Did you copy all files located in the 'libs'-folder from [1] to '<APACHE_PLUME_HOME>/lib/? Should be 22 jar files.
2. Add your database driver (mysql in your case) to '<APACHE_PLUME_HOME>/lib/'
3. Add bpm-platform.xml to '<APACHE_PLUME_HOME>/conf/'. You can use the default one bundled inside [1]'s 'conf'-folder.
4. Add the Camunda BPM Bootstrap listener in '<APACHE_PLUME_HOME>/conf/server.xml':

<Listener className="org.camunda.bpm.container.impl.tomcat.TomcatBpmPlatformBootstrap" />

5. Configure your database in '<APACHE_PLUME_HOME>/conf/server.xml'. Eg:


<Resource
       
name="jdbc/ProcessEngine" type="javax.sql.DataSource"

       
maxActive="100" maxIdle="30" maxWait="10000"
       
url="jdbc:mysql://localhost:3306/option-store"
        driverClassName="com.mysql.jdbc.Driver"
       
username="root" password=""
/>

6. Start the server and make sure you get something along the following output:

Mrz 24, 2015 8:35:31 AM org.camunda.bpm.container.impl.tomcat.deployment.TomcatParseBpmPlatformXmlStep lookupBpmPlatformXmlFromCatalinaConfDirectory
INFORMATION: Found camunda bpm platform configuration in CATALINA_BASE/CATALINA_HOME conf directory [/Users/hawky4s/Downloads/apache-tomee-plume-1.7.1/conf/bpm-platform.xml] at file:/Users/hawky4s/Downloads/apache-tomee-plume-1.7.1/conf/bpm-platform.xml
Mrz 24, 2015 8:35:32 AM org.camunda.bpm.engine.impl.jobexecutor.JobExecutor start
INFORMATION: Starting up the JobExecutor[org.camunda.bpm.engine.impl.jobexecutor.RuntimeContainerJobExecutor].
Mrz 24, 2015 8:35:32 AM org.camunda.bpm.engine.impl.jobexecutor.SequentialJobAcquisitionRunnable run
INFORMATION: JobExecutor[org.camunda.bpm.engine.impl.jobexecutor.RuntimeContainerJobExecutor] starting to acquire jobs
Mrz 24, 2015 8:35:32 AM org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl invokePreInit
INFORMATION: PLUGIN ProcessApplicationEventListenerPlugin activated on process engine default
Mrz 24, 2015 8:35:32 AM org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl invokePreInit
INFORMATION: PLUGIN SpinProcessEnginePlugin activated on process engine default
Mrz 24, 2015 8:35:32 AM org.camunda.commons.logging.BaseLogger logInfo
INFORMATION: SPIN-01010 Discovered Spin data format provider: org.camunda.spin.impl.json.jackson.format.JacksonJsonDataFormatProvider[name = application/json]
Mrz 24, 2015 8:35:32 AM org.camunda.commons.logging.BaseLogger logInfo
INFORMATION: SPIN-01010 Discovered Spin data format provider: org.camunda.spin.impl.xml.dom.format.DomXmlDataFormatProvider[name = application/xml]
Mrz 24, 2015 8:35:32 AM org.camunda.commons.logging.BaseLogger logInfo
INFORMATION: SPIN-01009 Discovered Spin data format: org.camunda.spin.impl.xml.dom.format.DomXmlDataFormat[name = application/xml]
Mrz 24, 2015 8:35:32 AM org.camunda.commons.logging.BaseLogger logInfo
INFORMATION: SPIN-01009 Discovered Spin data format: org.camunda.spin.impl.json.jackson.format.JacksonJsonDataFormat[name = application/json]
Mrz 24, 2015 8:35:32 AM org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl invokePreInit
INFORMATION: PLUGIN ConnectProcessEnginePlugin activated on process engine default
Mrz 24, 2015 8:35:32 AM org.camunda.commons.logging.BaseLogger logInfo
INFORMATION: CNCT-01004 Discovered provider for connector id 'http-connector' and class 'org.camunda.connect.httpclient.impl.HttpConnectorImpl': 'org.camunda.connect.httpclient.impl.HttpConnectorProviderImpl'
Mrz 24, 2015 8:35:32 AM org.camunda.commons.logging.BaseLogger logInfo
INFORMATION: CNCT-01004 Discovered provider for connector id 'soap-http-connector' and class 'org.camunda.connect.httpclient.soap.impl.SoapHttpConnectorImpl': 'org.camunda.connect.httpclient.soap.impl.SoapHttpConnectorProviderImpl'
Mrz 24, 2015 8:35:33 AM org.camunda.bpm.engine.impl.db.sql.DbSqlSession executeSchemaResource
INFORMATION: performing create on engine with resource org/camunda/bpm/engine/db/create/activiti.h2.create.engine.sql
Mrz 24, 2015 8:35:33 AM org.camunda.bpm.engine.impl.db.sql.DbSqlSession executeSchemaResource
INFORMATION: performing create on history with resource org/camunda/bpm/engine/db/create/activiti.h2.create.history.sql
Mrz 24, 2015 8:35:33 AM org.camunda.bpm.engine.impl.db.sql.DbSqlSession executeSchemaResource
INFORMATION: performing create on identity with resource org/camunda/bpm/engine/db/create/activiti.h2.create.identity.sql
Mrz 24, 2015 8:35:33 AM org.camunda.bpm.engine.impl.db.sql.DbSqlSession executeSchemaResource
INFORMATION: performing create on case.engine with resource org/camunda/bpm/engine/db/create/activiti.h2.create.case.engine.sql
Mrz 24, 2015 8:35:33 AM org.camunda.bpm.engine.impl.db.sql.DbSqlSession executeSchemaResource
INFORMATION: performing create on case.history with resource org/camunda/bpm/engine/db/create/activiti.h2.create.case.history.sql
Mrz 24, 2015 8:35:33 AM org.camunda.bpm.engine.impl.SchemaOperationsProcessEngineBuild checkHistoryLevel
INFORMATION: No historyLevel property found in database.
Mrz 24, 2015 8:35:33 AM org.camunda.bpm.engine.impl.SchemaOperationsProcessEngineBuild dbCreateHistoryLevel
INFORMATION: Creating historyLevel property in database with value: full
Mrz 24, 2015 8:35:33 AM org.camunda.bpm.engine.impl.ProcessEngineImpl <init>
INFORMATION: ProcessEngine default created
Mrz 24, 2015 8:35:33 AM org.camunda.bpm.container.impl.tomcat.TomcatBpmPlatformBootstrap deployBpmPlatform
INFORMATION: camunda BPM platform sucessfully started on Apache Tomcat (TomEE)/7.0.55 (1.7.1).

7. After you successfully solved the previous steps, download the 'camunda-webapp-tomcat-7.2.0.war' from [2]. Rename the WAR to 'camunda.war' and deploy it inside '<APACHE_PLUME_HOME/webapps'.
8. Go to 'localhost:8080/camunda'. You should be redirected to the admin creation site.


Hint: You cannot access 'localhost:8080/camunda-welcome' as this is only available in the complete distro.
Hint_2: I tried all steps above and it works.

Cheers,
Christian

[1]: http://camunda.org/release/camunda-bpm/tomcat/7.2/camunda-bpm-tomcat-7.2.0.zip
[2]: https://app.camunda.com/nexus/service/local/repositories/camunda-bpm/content/org/camunda/bpm/webapp/camunda-webapp-tomcat/7.2.0/camunda-webapp-tomcat-7.2.0.war

kstoe...@gmail.com

unread,
Mar 24, 2015, 1:04:02 PM3/24/15
to camunda-...@googlegroups.com, karl-hein...@gmx.at, kstoe...@gmail.com
Hi Christian,

Thank you! I followed your steps.
Now everything worked fine until I put the renamed file camunda.war into the webapp folder. When the war file is deployed I receive the following error:

Mär 24, 2015 5:22:43 PM org.apache.openejb.observer.ObserverManager$MethodInvocation invoke
Schwerwiegend: error invoking org.apache.tomee.webservices.TomeeJaxRsService@3b2000a5
Mär 24, 2015 5:22:43 PM org.apache.catalina.startup.HostConfig deployWAR
Information: Deployment of web application archive C:\Users\Charly\Desktop\apache-tomee-1.7.1-plume\webapps\camunda.war has finished in 22,797 ms
Mär 24, 2015 5:22:55 PM org.jboss.resteasy.logging.impl.Slf4jLogger info
Information: Deploying javax.ws.rs.core.Application: class org.camunda.bpm.webapp.impl.engine.EngineRestApplication


I can access the site 'localhost:8080/camunda' where I created a user. This also worked. Then I added a test process (loan-approval.war) to the webapps folder and I tried the process, and it worked fine.
Then I tried another process which is more advanced, the (pizza-order process). This process includes some xhtml forms, for example for starting the process it uses the app:placeorder.jsf which opens the placeorder.xhtml form. To open and fill out the form works correct, but when I try to submit the form I get an error again:

Mär 24, 2015 5:52:18 PM org.apache.openejb.core.transaction.EjbTransactionUtil handleSystemException
Schwerwiegend: EjbTransactionUtil.handleSystemException:
Internal Exception: java.sql.SQLSyntaxErrorException: user lacks privilege or object not found: SEQUENCE
Error Code: -5501
Call: UPDATE SEQUENCE SET SEQ_COUNT = SEQ_COUNT + ? WHERE SEQ_NAME = ?
bind => [2 parameters bound]
Query: DataModifyQuery(name="SEQUENCE" sql="UPDATE SEQUENCE SET SEQ_COUNT = SEQ_COUNT + ? WHERE SEQ_NAME = ?")
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.2.v20130514-5956486): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: user lacks privilege or object not found: SEQUENCE
Error Code: -5501
Call: UPDATE SEQUENCE SET SEQ_COUNT = SEQ_COUNT + ? WHERE SEQ_NAME = ?
bind => [2 parameters bound]
Query: DataModifyQuery(name="SEQUENCE" sql="UPDATE SEQUENCE SET SEQ_COUNT = SEQ_COUNT + ? WHERE SEQ_NAME = ?")
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:333)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:646)
...

the error has about 500 lines

I is true that I do not have an Sequence Object but I do not have any Idea how this Object should look like. I guess a table which is called SEQUENCE but what columns (SEQ_COUNT, SEQ_NAME,...?) are required and what values should the entries have for this database entries. The Pizza example I used was working on the camunda-bpm-jboss-7.2.0 Server which I downloaded from the camunda website.

Thank you!
Greetings
Karl-Heinz

Christian Lipphardt

unread,
Mar 25, 2015, 5:51:49 AM3/25/15
to camunda-...@googlegroups.com, karl-hein...@gmx.at, kstoe...@gmail.com
Hi Karl-Heinz,

This is not directly related to Camunda BPM platform. The PizzaOrder example should have a 'META-INF/persistence.xml' and you have to configure the auto-creation of the necessary entity tables accordingly to EclipseLink (the TomEE JPA implementation).

Why do you want to use Apache TomEE PluMe and not another application server like JBoss/Wildfly?

Cheers,
Christian

kstoe...@gmail.com

unread,
Mar 25, 2015, 9:07:38 AM3/25/15
to camunda-...@googlegroups.com, karl-hein...@gmx.at, kstoe...@gmail.com
Hi Christian,

> Why do you want to use Apache TomEE PluMe and not another application server like JBoss/Wildfly?

Actually there is no real reason why I want to use the Apache Tomcat. The only reason was because Tomcat was the only application server which I have been working with before.

> This is not directly related to Camunda BPM platform. The PizzaOrder example should have a 'META-INF/persistence.xml' and you have to configure the auto-creation of the necessary entity tables accordingly to EclipseLink (the TomEE JPA implementation).

Do I also have to configure the persistence.xml file if I use the JBoss or Wildfly server?

What are the differences between the four application servers which are available here: http://camunda.org/download/


Thanks,
Karl-Heinz

Christian Lipphardt

unread,
Mar 26, 2015, 4:58:37 AM3/26/15
to camunda-...@googlegroups.com, karl-hein...@gmx.at, kstoe...@gmail.com
Hi,

I dont know if you have to reconfigure the persistence.xml for JBoss/Wildfly but I suspect not. If I remember right it was done for demoing on JBoss.

For the differences of the application servers (jboss,wildfly,glassfish) and servlet container (tomcat), you should try googling. Application servers offer JavaEE features (JPA, CDI, Transactions etc.) while Tomcat is only a servlet container missing those features by default.

Cheers,
Christian

kstoe...@gmail.com

unread,
Mar 26, 2015, 9:34:42 AM3/26/15
to camunda-...@googlegroups.com, karl-hein...@gmx.at, kstoe...@gmail.com
Hi Christian,

thank you for all your help.
I think I will switch to the JBoss/Wildfly application server.

Greeting
Karl-Heinz
Reply all
Reply to author
Forward
0 new messages