Install Camunda 7.2.0 on Openshift with jbossas 7.1.1

540 views
Skip to first unread message

Iryna Saturina

unread,
Dec 2, 2014, 9:30:07 AM12/2/14
to camunda-...@googlegroups.com
Hi, 
I am trying to run camunda 7.2.0  on on Openshift with jbossas 7.1.1. Is it supported? Or did I something wrong? I see in logs this: 

2014/12/02 09:19:31,518 INFO  [org.jboss.modules] (main) JBoss Modules version 1.1.1.GA
2014/12/02 09:19:32,122 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA
2014/12/02 09:19:32,255 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
2014/12/02 09:19:36,381 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("parallel-extension-add") failed - address: ([]): java.lang.RuntimeException: JBAS014670: Failed initializing module org.camunda.bpm.jboss.camunda-jboss-subsystem
at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:99) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:149) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:190) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.ServerService.boot(ServerService.java:291) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.ServerService.boot(ServerService.java:266) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: org/jboss/as/controller/ResourceBuilder$Factory
at java.util.concurrent.FutureTask.report(FutureTask.java:122) [rt.jar:1.7.0_71]
at java.util.concurrent.FutureTask.get(FutureTask.java:188) [rt.jar:1.7.0_71]
at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:91) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
... 9 more
Caused by: java.lang.NoClassDefFoundError: org/jboss/as/controller/ResourceBuilder$Factory
at org.camunda.bpm.container.impl.jboss.extension.BpmPlatformExtension.initialize(BpmPlatformExtension.java:68)
at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:88) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:113) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
Caused by: java.lang.ClassNotFoundException: org.jboss.as.controller.ResourceBuilder$Factory from [Module "org.camunda.bpm.jboss.camunda-jboss-subsystem:main" from local module loader @33e3e0 (roots: /var/lib/openshift/547dab12e0b8cdce570000c7/app-root/runtime/repo/.openshift/config/modules,/var/lib/openshift/547dab12e0b8cdce570000c7/jbossas/modules)]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
... 9 more
2014/12/02 09:19:36,392 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

Thank you 
Regards, Iren

Christian Lipphardt

unread,
Dec 2, 2014, 9:42:34 AM12/2/14
to camunda-...@googlegroups.com
Hi Iryna,

Camunda BPM is compatible with JBoss AS 7.2.x and EAP 6.x.
So just switch to JBoss EAP and your are good to go.

Cheers,
Christian

--
You received this message because you are subscribed to the Google Groups "camunda BPM users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to camunda-bpm-us...@googlegroups.com.
To post to this group, send email to camunda-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/camunda-bpm-users/070487a0-c69d-4295-827d-fab985a6b78f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

thorben....@camunda.com

unread,
Dec 2, 2014, 9:45:27 AM12/2/14
to camunda-...@googlegroups.com
Hi Iryna,

We test camunda BPM 7.2 against JBoss 7.2.0. There is an earlier discussion on working with camunda 7.0 on JBoss 7.1.1: https://groups.google.com/forum/#!searchin/camunda-bpm-users/jboss/camunda-bpm-users/Se_9O0D90W4/-IwQ2vI7ZqUJ
At that time, the asking user already had compilation issues so I think that's also the case with camunda 7.2. You can try Christian's suggestion from the referenced thread, have a look at the sources, and fix any compilation issues. Of course, you then have to build the JBoss distribution from the sources yourself.

Best regards,
Thorben

Iryna Saturina

unread,
Dec 3, 2014, 1:45:48 PM12/3/14
to camunda-...@googlegroups.com
Hi Thorben, 

Thank you for the answer. I tried to switch to EAP 6, now it fails with OOM: 

2014/12/03 13:30:58,750 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222082: error on connection failure check: java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method) [rt.jar:1.7.0_71]
at java.lang.Thread.start(Thread.java:714) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360) [rt.jar:1.7.0_71]
at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor.execute(OrderedExecutorFactory.java:134) [hornetq-core-client.jar:2.3.21.Final-redhat-1]
at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$FailureCheckAndFlushThread.run(RemotingServiceImpl.java:651) [hornetq-server.jar:2.3.21.Final-redhat-1]
2014/12/03 13:31:00,867 INFO  [org.jboss.web] (ServerService Thread Pool -- 67) JBAS018210: Register web context: /engine-rest
2014/12/03 13:31:04,501 INFO  [org.jboss.web] (ServerService Thread Pool -- 72) JBAS018210: Register web context: /camunda
2014/12/03 13:31:06,559 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) JBAS018559: Deployed "camunda-welcome.war" (runtime-name : "camunda-welcome.war")
2014/12/03 13:31:06,559 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) JBAS018559: Deployed "camunda-webapp-jboss-7.2.0.war" (runtime-name : "camunda-webapp-jboss-7.2.0.war")
2014/12/03 13:31:06,559 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) JBAS018559: Deployed "camunda-engine-rest-7.2.0.war" (runtime-name : "camunda-engine-rest-7.2.0.war")
2014/12/03 13:31:06,559 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) JBAS018559: Deployed "ROOT.war" (runtime-name : "ROOT.war")
2014/12/03 13:31:06,570 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.naming.context.java.jboss.datasources.ProcessEngine (missing) dependents: [service org.camunda.bpm.platform.process-engine.default] 
2014/12/03 13:31:06,669 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.2.134.1:9990/management
2014/12/03 13:31:06,670 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.2.134.1:9990
2014/12/03 13:31:06,670 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.3.2.GA (AS 7.4.2.Final-redhat-2) started (with errors) in 28836ms - Started 472 of 590 services (1 services failed or missing dependencies, 153 services are lazy, passive or on-demand)
2014/12/03 13:31:10,185 ERROR [org.xnio.listener] (Remoting "camunda-bkbpm.rhcloud.com:MANAGEMENT" read-1) A channel event listener threw an exception: java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method) [rt.jar:1.7.0_71]
at java.lang.Thread.start(Thread.java:714) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360) [rt.jar:1.7.0_71]
at org.xnio.XnioWorker.execute(XnioWorker.java:572) [xnio-api.jar:3.0.11.GA-redhat-2]
at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:337) [jboss-remoting.jar:3.3.3.Final-redhat-1]
at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:139) [jboss-remoting.jar:3.3.3.Final-redhat-1]
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api.jar:3.0.11.GA-redhat-2]
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) [xnio-api.jar:3.0.11.GA-redhat-2]
at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) [xnio-api.jar:3.0.11.GA-redhat-2]
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api.jar:3.0.11.GA-redhat-2]
at org.xnio.nio.NioHandle.run(NioHandle.java:90)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)
2014/12/03 13:31:19,070 ERROR [org.xnio.listener] (Remoting "camunda-bkbpm.rhcloud.com:MANAGEMENT" read-1) A channel event listener threw an exception: java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method) [rt.jar:1.7.0_71]
at java.lang.Thread.start(Thread.java:714) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360) [rt.jar:1.7.0_71]
at org.xnio.XnioWorker.execute(XnioWorker.java:572) [xnio-api.jar:3.0.11.GA-redhat-2]
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:241) [jboss-remoting.jar:3.3.3.Final-redhat-1]
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45) [jboss-remoting.jar:3.3.3.Final-redhat-1]
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api.jar:3.0.11.GA-redhat-2]
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) [xnio-api.jar:3.0.11.GA-redhat-2]
at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) [xnio-api.jar:3.0.11.GA-redhat-2]
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api.jar:3.0.11.GA-redhat-2]
at org.xnio.nio.NioHandle.run(NioHandle.java:90)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)

вторник, 2 декабря 2014 г., 16:45:27 UTC+2 пользователь thorben....@camunda.com написал:

Christian Lipphardt

unread,
Dec 5, 2014, 12:39:01 PM12/5/14
to camunda-...@googlegroups.com
Hi Iryna,

Could you please post the whole stacktrace for the EAP?
It seems to me the DataSource for the ProcessEngine is missing?

Cheers,
Christian
--
You received this message because you are subscribed to the Google Groups "camunda BPM users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to camunda-bpm-us...@googlegroups.com.
To post to this group, send email to camunda-...@googlegroups.com.
signature.asc

Iryna Saturina

unread,
Dec 5, 2014, 2:43:54 PM12/5/14
to camunda-...@googlegroups.com
Hi Christian, 

Here is how I declare datasource: 

<xa-datasource jndi-name="java:jboss/datasource/ProcessEngine" pool-name="ProcessEngine" enabled="true" use-ccm="false">
  <xa-datasource-property name="URL">postgresql://$OPENSHIFT_POSTGRESQL_DB_HOST:$OPENSHIFT_POSTGRESQL_DB_PORT</xa-datasource-property>
  <driver>postgresql</driver>
  <xa-pool>
    <max-pool-size>10</max-pool-size>
    <is-same-rm-override>false</is-same-rm-override>
    <interleaving>false</interleaving>
    <pad-xid>false</pad-xid>
    <wrap-xa-resource>false</wrap-xa-resource>
  </xa-pool>
  <security>
  <user-name>${env.OPENSHIFT_POSTGRESQL_DB_USERNAME}</user-name>
<password>${env.OPENSHIFT_POSTGRESQL_DB_PASSWORD}</password>
 </security>
  <validation>
    <validate-on-match>false</validate-on-match>
    <background-validation>false</background-validation>
    <background-validation-millis>1</background-validation-millis>
  </validation>
  <statement>
    <prepared-statement-cache-size>0</prepared-statement-cache-size>
    <share-prepared-statements>false</share-prepared-statements>
  </statement>
</xa-datasource>

And here are my logs from Openshift's JBoss: 

=========================================================================
2014/12/05 14:32:37,083 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.4.Final-redhat-1
2014/12/05 14:32:39,286 INFO  [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
2014/12/05 14:32:40,056 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.3.2.GA (AS 7.4.2.Final-redhat-2) starting
2014/12/05 14:32:47,481 WARN  [org.jboss.as.messaging] (Controller Boot Thread) JBAS011608: Element CLUSTERED is deprecated and will not be taken into account
2014/12/05 14:32:51,806 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 14) JBAS014627: Attribute clustered is deprecated, and it might be removed in future version!
2014/12/05 14:32:51,818 WARN  [org.jboss.messaging] (ServerService Thread Pool -- 14) JBAS011618: There is no resource matching the expiry-address jms.queue.ExpiryQueue for the address-settings #, expired messages from destinations matching this address-setting will be lost!
2014/12/05 14:32:51,849 WARN  [org.jboss.messaging] (ServerService Thread Pool -- 14) JBAS011619: There is no resource matching the dead-letter-address jms.queue.DLQ for the address-settings #, undelivered messages from destinations matching this address-setting will be lost!
2014/12/05 14:32:52,030 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found camunda-welcome.war in deployment directory. To trigger deployment create a file called camunda-welcome.war.dodeploy
2014/12/05 14:32:52,355 WARN  [org.jboss.as.server] (Controller Boot Thread) JBAS015883: No security realm defined for native management service; all access will be unrestricted.
2014/12/05 14:32:52,361 INFO  [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.11.GA-redhat-2
2014/12/05 14:32:52,490 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.11.GA-redhat-2
2014/12/05 14:32:52,551 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
2014/12/05 14:32:52,553 WARN  [org.jboss.as.server] (Controller Boot Thread) JBAS015884: No security realm defined for http management service; all access will be unrestricted.
2014/12/05 14:32:52,728 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.3.3.Final-redhat-1
2014/12/05 14:32:53,029 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 35) JBAS016200: Activating ConfigAdmin Subsystem
2014/12/05 14:32:53,163 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) JBAS010280: Activating Infinispan subsystem.
2014/12/05 14:32:53,226 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 62) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
2014/12/05 14:32:53,308 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 59) JBAS013171: Activating Security Subsystem
2014/12/05 14:32:53,402 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 46) JBAS010260: Activating JGroups subsystem.
2014/12/05 14:32:53,404 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 41) JBAS016300: Activating JacORB Subsystem
2014/12/05 14:32:53,512 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 53) JBAS011800: Activating Naming Subsystem
2014/12/05 14:32:53,460 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 54) JBAS011906: Activating OSGi Subsystem
2014/12/05 14:32:53,477 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 49) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
2014/12/05 14:32:53,640 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.7.128.129:9999
2014/12/05 14:32:53,467 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 64) JBAS015537: Activating WebServices Extension
2014/12/05 14:32:54,208 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.7.128.129:4447
2014/12/05 14:32:54,489 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.19.SP8-redhat-1
2014/12/05 14:32:54,617 INFO  [org.jboss.jaxr] (MSC service thread 1-2) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
2014/12/05 14:32:54,619 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
2014/12/05 14:32:54,756 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.28.Final-redhat-1)
2014/12/05 14:32:54,947 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
2014/12/05 14:32:55,353 INFO  [org.camunda.bpm.engine.impl.jobexecutor.JobExecutor] (MSC service thread 1-4) Starting up the JobExecutor[org.camunda.bpm.container.impl.jboss.service.MscRuntimeContainerJobExecutor].
2014/12/05 14:32:55,600 INFO  [org.camunda.bpm.engine.impl.jobexecutor.AcquireJobsRunnable] (job-executor-tp-threads - 1) JobExecutor[org.camunda.bpm.container.impl.jboss.service.MscRuntimeContainerJobExecutor] starting to acquire jobs
2014/12/05 14:32:55,981 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
2014/12/05 14:32:56,464 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
2014/12/05 14:32:57,033 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 8.4)
2014/12/05 14:33:00,769 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/127.7.128.129:8080
2014/12/05 14:33:01,440 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) JBWEB003000: Coyote HTTP/1.1 starting on: http-/127.7.128.129:8080
2014/12/05 14:33:02,070 WARN  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
2014/12/05 14:33:02,230 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 40) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2014/12/05 14:33:02,300 INFO  [org.jboss.as.jacorb] (MSC service thread 1-3) JBAS016330: CORBA ORB Service started
2014/12/05 14:33:02,535 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 40) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2014/12/05 14:33:03,174 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "camunda-welcome.war" (runtime-name: "camunda-welcome.war")
2014/12/05 14:33:03,198 INFO  [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.1.Final-redhat-1
2014/12/05 14:33:03,324 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "ROOT.war" (runtime-name: "ROOT.war")
2014/12/05 14:33:03,352 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "camunda-engine-rest-7.2.0.war" (runtime-name: "camunda-engine-rest-7.2.0.war")
2014/12/05 14:33:03,353 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "camunda-webapp-jboss-7.2.0.war" (runtime-name: "camunda-webapp-jboss-7.2.0.war")
2014/12/05 14:33:03,632 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /var/lib/openshift/548202dbe0b8cd484d000191/jbosseap/standalone/deployments
2014/12/05 14:33:03,754 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/var/lib/openshift/548202dbe0b8cd484d000191/jbosseap/standalone/data/messagingjournal,bindingsDirectory=/var/lib/openshift/548202dbe0b8cd484d000191/jbosseap/standalone/data/messagingbindings,largeMessagesDirectory=/var/lib/openshift/548202dbe0b8cd484d000191/jbosseap/standalone/data/messaginglargemessages,pagingDirectory=/var/lib/openshift/548202dbe0b8cd484d000191/jbosseap/standalone/data/messagingpaging)
2014/12/05 14:33:03,780 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221006: Waiting to obtain live lock
2014/12/05 14:33:04,466 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221013: Using NIO Journal
2014/12/05 14:33:06,038 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221034: Waiting to obtain live lock
2014/12/05 14:33:06,038 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221035: Live Server Obtained live lock
2014/12/05 14:33:06,563 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016328: CORBA Naming Service started
2014/12/05 14:33:08,218 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
2014/12/05 14:33:08,219 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/PostgreSQLDS]
2014/12/05 14:33:08,476 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasource/ProcessEngine]
2014/12/05 14:33:10,499 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 127.7.128.129:5455 for CORE protocol
2014/12/05 14:33:10,658 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 127.7.128.129:5445 for CORE protocol
2014/12/05 14:33:10,753 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221007: Server is now live
2014/12/05 14:33:10,754 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221001: HornetQ Server version 2.3.21.Final (2.3.21, 123) [878746fc-7cb2-11e4-bc13-9b45f65a11f4] 
2014/12/05 14:33:11,677 INFO  [org.jboss.web] (ServerService Thread Pool -- 70) JBAS018210: Register web context: /camunda-welcome
2014/12/05 14:33:11,731 INFO  [org.jboss.web] (ServerService Thread Pool -- 68) JBAS018210: Register web context: 
2014/12/05 14:33:12,367 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 66) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
2014/12/05 14:33:13,261 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 67) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
2014/12/05 14:33:13,990 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/JmsXA
2014/12/05 14:33:15,365 INFO  [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started
2014/12/05 14:33:15,366 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra
2014/12/05 14:33:15,370 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
2014/12/05 14:33:15,755 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014612: Operation ("read-resource") failed - address: ([("subsystem" => "deployment-scanner")]) - failure description: "JBAS014807: Management resource '[(\"subsystem\" => \"deployment-scanner\")]' not found"
2014/12/05 14:33:15,859 INFO  [org.jboss.web] (ServerService Thread Pool -- 70) JBAS018210: Register web context: /engine-rest
2014/12/05 14:33:21,259 INFO  [org.jboss.web] (ServerService Thread Pool -- 68) JBAS018210: Register web context: /camunda
2014/12/05 14:33:22,771 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014612: Operation ("read-resource") failed - address: ([("subsystem" => "deployment-scanner")]) - failure description: "JBAS014807: Management resource '[(\"subsystem\" => \"deployment-scanner\")]' not found"
2014/12/05 14:33:23,157 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) JBAS018559: Deployed "ROOT.war" (runtime-name : "ROOT.war")
2014/12/05 14:33:23,158 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) JBAS018559: Deployed "camunda-engine-rest-7.2.0.war" (runtime-name : "camunda-engine-rest-7.2.0.war")
2014/12/05 14:33:23,158 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) JBAS018559: Deployed "camunda-welcome.war" (runtime-name : "camunda-welcome.war")
2014/12/05 14:33:23,158 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) JBAS018559: Deployed "camunda-webapp-jboss-7.2.0.war" (runtime-name : "camunda-webapp-jboss-7.2.0.war")
2014/12/05 14:33:23,159 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.naming.context.java.jboss.datasources.ProcessEngine (missing) dependents: [service org.camunda.bpm.platform.process-engine.default] 
2014/12/05 14:33:23,353 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.7.128.129:9990/management
2014/12/05 14:33:23,353 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.7.128.129:9990
2014/12/05 14:33:23,354 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.3.2.GA (AS 7.4.2.Final-redhat-2) started (with errors) in 47899ms - Started 472 of 590 services (1 services failed or missing dependencies, 153 services are lazy, passive or on-demand)
2014/12/05 14:34:31,170 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/camunda].[default]] (http-/127.7.128.129:8080-1) JBWEB000236: Servlet.service() for servlet default threw exception: java.lang.RuntimeException: org.camunda.bpm.webapp.impl.IllegalWebAppConfigurationException: No process engine found. camunda Webapp cannot work without a process engine. 
at org.camunda.bpm.webapp.impl.security.auth.AuthenticationFilter$1.execute(AuthenticationFilter.java:61) [classes:]
at org.camunda.bpm.webapp.impl.security.auth.AuthenticationFilter$1.execute(AuthenticationFilter.java:56) [classes:]
at org.camunda.bpm.webapp.impl.security.SecurityActions.runWithAuthentications(SecurityActions.java:38) [classes:]
at org.camunda.bpm.webapp.impl.security.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:56) [classes:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web.jar:7.4.2.Final-redhat-2]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:621) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb.jar:7.4.9.Final-redhat-1]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
Caused by: org.camunda.bpm.webapp.impl.IllegalWebAppConfigurationException: No process engine found. camunda Webapp cannot work without a process engine. 
at org.camunda.bpm.webapp.impl.engine.ProcessEnginesFilter.getDefaultEngineName(ProcessEnginesFilter.java:188) [classes:]
at org.camunda.bpm.webapp.impl.engine.ProcessEnginesFilter.serveIndexPage(ProcessEnginesFilter.java:102) [classes:]
at org.camunda.bpm.webapp.impl.engine.ProcessEnginesFilter.applyFilter(ProcessEnginesFilter.java:70) [classes:]
at org.camunda.bpm.webapp.impl.filter.AbstractTemplateFilter.doFilter(AbstractTemplateFilter.java:42) [classes:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.camunda.bpm.webapp.impl.security.filter.SecurityFilter.doFilterSecure(SecurityFilter.java:67) [classes:]
at org.camunda.bpm.webapp.impl.security.filter.SecurityFilter.doFilter(SecurityFilter.java:51) [classes:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb.jar:7.4.9.Final-redhat-1]
at org.camunda.bpm.webapp.impl.security.auth.AuthenticationFilter$1.execute(AuthenticationFilter.java:59) [classes:]
... 17 more

пятница, 5 декабря 2014 г., 19:39:01 UTC+2 пользователь Christian Lipphardt написал:

Christian Lipphardt

unread,
Dec 7, 2014, 5:55:46 PM12/7/14
to camunda-...@googlegroups.com
Hi Iryna,

I think you have a typo in the DataSource configuration. The jndi-name should be "java:jboss/datasources/ProcessEngine" not "java:jboss/datasource/ProcessEngine". The "s" from datasource is missing in your case.

Cheers,
Christian
...

Iryna Saturina

unread,
Dec 8, 2014, 3:04:02 AM12/8/14
to camunda-...@googlegroups.com
Hi Christian, 

Thank you so much for help! It works now. 
This is how correct xa-datasource should look like: 

<xa-datasource jndi-name="java:jboss/datasources/ProcessEngine" pool-name="ProcessEngine" enabled="true" use-ccm="false">
  <driver>postgresql</driver>
    <xa-datasource-property name="ServerName">${env.OPENSHIFT_POSTGRESQL_DB_HOST}</xa-datasource-property>
    <xa-datasource-property name="PortNumber">${env.OPENSHIFT_POSTGRESQL_DB_PORT}</xa-datasource-property>
    <xa-datasource-property name="DatabaseName">camunda</xa-datasource-property>
  <xa-pool>
    <max-pool-size>10</max-pool-size>
    <is-same-rm-override>false</is-same-rm-override>
    <interleaving>false</interleaving>
    <pad-xid>false</pad-xid>
    <wrap-xa-resource>false</wrap-xa-resource>
  </xa-pool>
  <security>
  <user-name>${env.OPENSHIFT_POSTGRESQL_DB_USERNAME}</user-name>
<password>${env.OPENSHIFT_POSTGRESQL_DB_PASSWORD}</password>
 </security>
  <validation>
    <validate-on-match>false</validate-on-match>
    <background-validation>false</background-validation>
    <background-validation-millis>1</background-validation-millis>
  </validation>
  <statement>
    <prepared-statement-cache-size>0</prepared-statement-cache-size>
    <share-prepared-statements>false</share-prepared-statements>
  </statement>
</xa-datasource>

понедельник, 8 декабря 2014 г., 0:55:46 UTC+2 пользователь Christian Lipphardt написал:
...
Reply all
Reply to author
Forward
0 new messages