-
1. jBPM 5 on JBoss AS 6.
voikonomidou Feb 11, 2011 3:30 AM (in response to francisco_barros)Hi Francisco,
I am currently trying to adapt jbpm 5 in jboss 6 and i have the same question with you. One thing I noticed, is that after a specific build the installation ant scripts do not support other versions of Jboss, except 5.1. In addition, you have to exclude a number of jars from the installation war files in order to deploy guvnor and jbpm succesfully on jboss 6. As for Seam 3, I think that currently there is no decision made in the version of Jbpm that will be used. I read on a forum that probably jbpm 5 will be included in Seam 3.1. Anyone else that has an answer on this?
Regards,
Vasiliki.
-
2. jBPM 5 on JBoss AS 6.
francisco_barros Feb 16, 2011 5:47 AM (in response to voikonomidou)Hi Vasiliki! Thank you very much for your response.
Would you, please, detail "In addition, you have to exclude a number of jars from the installation war files in order to deploy guvnor and jbpm succesfully on jboss 6."?
What are the changes that you have made?
Greetings.
Francisco Barros.
-
3. jBPM 5 on JBoss AS 6.
mpiraccini Feb 17, 2011 4:52 AM (in response to francisco_barros)Hi guys,
I'm interested in this topic too. Vasiliki, can tell us which jar have you excluded and why?
Anyone knows when JBPM will be ufficially ported on JBoss 6?
Marco.
-
4. jBPM 5 on JBoss AS 6.
voikonomidou Feb 17, 2011 5:56 AM (in response to mpiraccini)Hi,
The jars that I have excluded are the following:
From drools-guvnor.war :
- jta-1.0.1.jar
- slf4j-api-1.6.0.jar
- slf4j-log4j12-1.6.0.jar
- jsf-api-1.2.jar
- javassist-3.4.GA.jar
From jbpm-gwt-console.war :
- slf4j-api-1.6.0.jar
- slf4j-log4j12-1.6.0.jar
From jbpm-gwt-console-server.war :
- jaxrs-api-1.0.2.GA.jar
- el-api.jar
- slf4j-api-1.6.0.jar
- slf-log4j12-1.6.0.jar
- slf4j-api-1.5.2.jar
- slf4j-log4j12-1.5.2.jar
- slf4j-simple-1.5.2.jar
From designer.war :
- slf4j-api-1.5.11.jar
- slf4j-jdk14-1.5.11.jar
Nevertheless, I am not sure if the removal of the specific jar files is the correct one. But it was the only way to deploy them without any errors on Jboss 6, otherwise the server could not start correctly.
-
5. jBPM 5 on JBoss AS 6.
francisco_barros Feb 17, 2011 6:33 AM (in response to voikonomidou)Hi Vasiliki. Thank you!
-
6. jBPM 5 on JBoss AS 6.
voikonomidou Feb 17, 2011 6:46 AM (in response to francisco_barros)Hi Francisco,
You are welcome.I hope it helps you.
Regards,
Vasiliki.
-
7. jBPM 5 on JBoss AS 6.
cindy.c Mar 18, 2011 7:15 AM (in response to francisco_barros)Hello,
Did someone succeeded in installing jbpm 5 on JBoss AS6 ?
I tried and did the delettion of jars like said Vasiliki but I still have deployment error while starting JBoss.
Thanks for feedback,
Cindy
-
8. jBPM 5 on JBoss AS 6.
voikonomidou Mar 18, 2011 9:07 AM (in response to cindy.c)Hi cindy,
what is the deployment error you are getting?
Regards,
Vasiliki.
-
9. jBPM 5 on JBoss AS 6.
cindy.c Mar 18, 2011 10:19 AM (in response to francisco_barros)Here is the log while starting jBoss:
...
23:23:10,304 INFO [RARDeployment] Required license terms exist, view vfs:/apps/jboss-6.0.0.Final/server/default/deploy/mail-ra.rar/META-INF/ra.xml
23:23:10,317 INFO [RARDeployment] Required license terms exist, view vfs:/apps/jboss-6.0.0.Final/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
23:23:10,466 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: Thread-2
23:23:10,529 INFO [SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
23:23:10,529 INFO [QuartzScheduler] Quartz Scheduler v.1.8.3 created.
23:23:10,531 INFO [RAMJobStore] RAMJobStore initialized.
23:23:10,533 INFO [QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v1.8.3) 'JBossQuartzScheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
23:23:10,533 INFO [StdSchedulerFactory] Quartz scheduler 'JBossQuartzScheduler' initialized from an externally opened InputStream.
23:23:10,533 INFO [StdSchedulerFactory] Quartz scheduler version: 1.8.3
23:23:10,533 INFO [QuartzScheduler] Scheduler JBossQuartzScheduler_$_NON_CLUSTERED started.
23:23:11,075 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
23:23:13,036 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
23:23:13,428 INFO [xnio] XNIO Version 2.1.0.CR2
23:23:13,435 INFO [nio] XNIO NIO Implementation Version 2.1.0.CR2
23:23:14,242 INFO [remoting] JBoss Remoting version 3.1.0.Beta2
23:23:14,350 INFO [TomcatDeployment] deploy, ctxPath=/
23:23:14,626 INFO [TomcatDeployment] deploy, ctxPath=/designer
23:23:14,866 INFO [TomcatDeployment] deploy, ctxPath=/drools-guvnor
23:23:15,012 INFO [TomcatDeployment] deploy, ctxPath=/jbpm-gwt-console-server
23:23:15,176 INFO [TomcatDeployment] deploy, ctxPath=/jbpm-gwt-console
23:23:15,236 INFO [service] Removing bootstrap log handlers
23:23:15,420 ERROR [ProfileServiceBootstrap] Failed to load profile:: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "jboss.ejb:persistencePolicy=database,service=EJBTimerService" is missing the following dependencies:
Dependency "jboss.jdbc:datasource=DefaultDS,service=metadata" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jdbc:datasource=DefaultDS,service=metadata' **")
Deployment "jboss.ejb:service=EJBTimerService" is missing the following dependencies:
Dependency "jboss.ejb:persistencePolicy=database,service=EJBTimerService" (should be in state "Create", but is actually in state "Configured")
DEPLOYMENTS IN ERROR:
Deployment "jboss.jdbc:datasource=DefaultDS,service=metadata" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jdbc:datasource=DefaultDS,service=metadata' **
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]
at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2]
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final]
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]
at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
23:23:15,435 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
23:23:15,438 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
23:23:15,438 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.Final "Neo"] Started in 1m:741ms
Thanks for helping.
Regards,
Cindy
-
10. Re: jBPM 5 on JBoss AS 6.
dmanibtech Jun 6, 2012 5:03 AM (in response to cindy.c)Hey guys,
Any conclusion on porting jBPM 5 over JBoss 6?
Regards,
Mani
-
11. Re: jBPM 5 on JBoss AS 6.
while_true Nov 19, 2012 8:12 AM (in response to cindy.c)Hey cindy.c,
You've probably deleted your hsqldb-ds.xml file.
Try to put it back again or create a datasource that maps the "DefaultDS" jndi-name.
Regards.
-
12. Re: jBPM 5 on JBoss AS 6.
rahulamt Nov 27, 2012 2:30 AM (in response to voikonomidou)Are you aware of the jars to be removed for successul deployment on jboss.5.1.0.GA?