[jBPM] - Re: Is jBPM the right tool for what I'm trying to achieve?
by Maciej Swiderski
Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion
"Re: Is jBPM the right tool for what I'm trying to achieve?"
To view the discussion, visit: https://community.jboss.org/message/827037#827037
--------------------------------------------------------------
Egor, jBPM can definitely support your case but it is much more capable than this and thus you see all these dependencies. Some of them are transitive dependencies due to various features require them but it does not have to mean you will need them too. For example CXF are used for web service invocation and are brought to the picture by jbpm-workitems. If you're not going to use web service feel free to exclude these dependencies which will make your end application much smaller and without not needed libraries.
Human task module is indeed complex but it has ist reason to be like this - WS HT specification and the features in brings such as life cycle of the task and its operations.
If you use CDI and REST you should definitely look at version 6 as it's built for CDI - complete human task module is redesigned to follow CDI approach. That might be much better fit for your case.
HTH
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/827037#827037]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 4 months
[jBPM] - Restoring and continuing a jPBM5 ProcessInstance
by mvermand
mvermand [https://community.jboss.org/people/mvermand] created the discussion
"Restoring and continuing a jPBM5 ProcessInstance"
To view the discussion, visit: https://community.jboss.org/message/826344#826344
--------------------------------------------------------------
Hi,
After a few years of using JBPM4, we are evaluating JBPM5.
In our project we have lots of long-running processes, so we need to persist them.
We want a tight integration with our application and therefore we decided not to use Guvnor (maybe we should non the less?).
Anyway, at the moment we use one ksession per process instance.
Now I am wondering how to "revive" the kbase which is needed to load the ksession:
ksessionStatefull = JPAKnowledgeService.loadStatefulKnowledgeSession(sessionId, *kbase*, null, env);
As process instances can last days or weeks, it is quit possible that process definitions have been altered,
so to continue a ksession we need to restore the same kbase as used to start the session (we need to know version of the process definition which was used when creating the process instance), right?
(How) should we store the kbase which is needed to reload the ksession?
Thanks!
Michiel
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/826344#826344]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 4 months
[jBPM] - Re: Can guvnor maintain multiple versions of a BPMN definition with same id?
by Maciej Swiderski
Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion
"Re: Can guvnor maintain multiple versions of a BPMN definition with same id?"
To view the discussion, visit: https://community.jboss.org/message/826993#826993
--------------------------------------------------------------
> mvermand wrote:
>
> Hi,
>
> In jBPM4.4 you can deploy a jPDL with the same name multiple times. The different versions automatically get a different version number and processInstances will keep using the version that was current when the processInstance started.
> You do not need to select specified Process Definitions upon engine startup. All is retrieved from the database as needed.
>
> In jBPM5.4 things seem to be different. If I am correct the Knowledge base needs to be filled at startup with all Process Definitions which are needed by any running process.
> If I need multiple versions of the same Process Definition in the kBase to complete process instances started with a different version, it seems I cannot use the same id for the different "versions" of the "same" process definition.
> Adding two process definitions with the same id but a different version number does not seem to work.
>
> 1) Am I right so far?
that is correct, you cannot have same process id for different process definitions within same kbase. If you try to do that one will override the other and the order of override will be same as the order of adding resources to knowledge base.
> mvermand wrote:
> If (1) == yes then
> 2) what it the use of the version number?
you can still use version number as part of the runtime, so the scenario is:
* create process definition with id abc, name process1 and version 1
* create process definition with id abcd, name process1, version 2
with that you can have both versions running in the same kbase and ksession as the ids are unique. Then you can use some helper classes to start process by name that will take into account the version number and ensure that the latest version will be used. See http://docs.jboss.org/jbpm/v5.4/javadocs/org/jbpm/process/instance/StartP... this helper class for details
> mvermand wrote:
> 3) will everything work if I change the ProcessDefinitions with as id the original processDefinition id concattenated with the version number?
>
it will work fine as long as you have them separated. Consider case that you model process version 1 deploy it to runtime start process of it and then you go and change the exact same process definition that will cause the situation where new process definition will be replaced. Most important piece of information is when you do new version of the process make a copy of the origin process def and work on the copy to produce new version, don't change the existing one as it will impact currently running instances of that process id.
> mvermand wrote:
> 4) does Guvnor support automatic version management?: create BPMN with id a.b.c , start processInstance for this BPMN, change BPMN (keep id, but increment version), start second processInstance. ProcessInstance 1 will keep using version 1 of BPMN, ProcessInstance 2 will use the updated version of the BPMN
>
see comment above. And in general, Guvnor is authoring tool based on JCR so it does support versioning of assets it maintains, but it's not the same versioning you have in mind. It keeps versions of the asset modifications, like history of what has changed and when, etc. It does not affect the runtime engine. To keep the isolation between running instances and version of the process make sure that you have process definition versions in separate files, that way all will work properly as it will be able to refer to the version it needs
> mvermand wrote:
> If (4) == no then how does Guvnor handle changes to BPMN definitions?
> Are you supposed to upgrade all running versions of a Process Definition?
Again Guvnor does not deal with it, there is KnowledgeAgent that transfers the build packages to runtime environment as soon as they are ready to update the kbase in the runtime. With that all rules given above apply and might be that you would need to upgrade the process instance if that is the strategy you have chosen - for example you need to change given version of the process definition instead of creating new one.
HTH
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/826993#826993]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 4 months
Re: [jboss-user] [JBoss Messaging] - JBoss7 integration with Tibco EMS using 'Generic JMS RA'
by tareq zaman
tareq zaman [https://community.jboss.org/people/tareq_zaman] commented on the document
"JBoss7 integration with Tibco EMS using 'Generic JMS RA'"
To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47346#comment-12392
--------------------------------------------------
Hi,
I have followed the steps mentioned above , however not able to get it working. I guess I have misssed something. Trying this on AS 7.1.1 final. Tibco EMS 6.3. Getting this exception. Would some one help me?
Thanks.
12:11:30,870 INFO [org.jboss.as.ejb3] (MSC service thread 1-14) JBAS014142: Started message driven bean 'SampleMdb' with 'genericra' resource adapter
12:11:31,093 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."ezsystemEAR.ear"."ezsystem.jar".component.SampleMdb.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."ezsystemEAR.ear"."ezsystem.jar".component.SampleMdb.START: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
Caused by: java.lang.RuntimeException: javax.resource.spi.InvalidPropertyException: String index out of range: -1
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:171)
at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
Caused by: javax.resource.spi.InvalidPropertyException: String index out of range: -1
at com.sun.genericra.util.ExceptionUtils.newInvalidPropertyException(ExceptionUtils.java:42)
at com.sun.genericra.util.ObjectBuilderFactory$JndiObjectBuilder.createObject(ObjectBuilderFactory.java:100)
at com.sun.genericra.util.ObjectBuilder.build(ObjectBuilder.java:99)
at com.sun.genericra.inbound.AbstractConsumer.initializeAdministeredObjects(AbstractConsumer.java:95)
at com.sun.genericra.inbound.AbstractConsumer.<init>(AbstractConsumer.java:63)
at com.sun.genericra.inbound.async.EndpointConsumer.<init>(EndpointConsumer.java:57)
at com.sun.genericra.inbound.EndpointConsumerFactory.createEndpointConsumer(EndpointConsumerFactory.java:45)
at com.sun.genericra.GenericJMSRA.endpointActivation(GenericJMSRA.java:215)
at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:164)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:169)
... 6 more
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1911) [rt.jar:1.7.0_25]
at com.sun.genericra.util.ObjectBuilder.parseToProperties(ObjectBuilder.java:86)
at com.sun.genericra.util.ObjectBuilderFactory$JndiObjectBuilder.createObject(ObjectBuilderFactory.java:92)
... 14 more
12:11:31,203 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "genericra.rar" was rolled back with no failure message
12:11:31,213 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "ezsystemEAR.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"ezsystemEAR.ear\".\"ezsystem.jar\".component.SampleMdb.START" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"ezsystemEAR.ear\".\"ezsystem.jar\".component.SampleMdb.START: Failed to start service"}}
12:11:31,349 INFO [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015877: Stopped deployment genericra.rar in 143ms
12:11:31,411 INFO [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015877: Stopped deployment ezsystem.jar in 189ms
12:11:31,442 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment ezsystemEAR.ear in 226ms
12:11:31,451 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.subunit."ezsystemEAR.ear"."ezsystem.jar".component.SampleMdb.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."ezsystemEAR.ear"."ezsystem.jar".component.SampleMdb.START: Failed to start service
--------------------------------------------------
12 years, 4 months