[jBPM] - jBPM 5.1 released
by Kris Verlaenen
Kris Verlaenen [http://community.jboss.org/people/KrisVerlaenen] created the discussion
"jBPM 5.1 released"
To view the discussion, visit: http://community.jboss.org/message/611731#611731
--------------------------------------------------------------
http://kverlaen.blogspot.com/2011/06/jbpm-510-released.html http://kverlaen.blogspot.com/2011/06/jbpm-510-released.html
We're proud to announce the release of jBPM 5.1.0.
> jBPM is a flexible open-source Business Process Management (BPM) Suite. The core of jBPM is a light-weight, extensible workflow engine written in pure Java that allows you to execute business processes using the latest BPMN 2.0 specification. It can run in any Java environment, embedded in your application or as a service. On top of that, it supports a lot of tooling to support the business process through its entire life cycle, both for developers and business users. This includes an Eclipse plugin, web-based Designer, repository, management console, etc.
>
You can download everything https://sourceforge.net/projects/jbpm/files/jBPM%205/jbpm-5.1.0.Final/ here.
jBPM 5.1 includes a lot of small bug fixes and feature enhancements based on the feedback we received from the community (for http://kverlaen.blogspot.com/2011/01/jbpm-50-released.html jBPM 5.0). Most important improvements include:
* The web-based http://docs.jboss.org/jbpm/v5.1/userguide/ch10.html Designer has been extended significantly to support all BPMN 2.0 constructs and to allow full round-tripping between the Eclipse-based and the web-based editor. It also supports domain-specific nodes now, can be embedded, etc.
* A new http://docs.jboss.org/jbpm/v5.1/userguide/ch08.html jbpm-examples module contains a large number of example processes to show features like human tasks (including data passing and task forms), looping, multiple instances, rule-based integration, etc. I will describe some of these examples in more detail in some additional blog entries in the next few days.
* Improved testing and debugging capabilities so you can easily http://kverlaen.blogspot.com/2011/04/junit-testing-your-jbpm5-processes.html JUnit-test your processes.
* The http://docs.jboss.org/jbpm/v5.1/userguide/ documentation has been refactored, updated and extended. There's a new http://docs.jboss.org/jbpm/v5.1/userguide/ch01.html Overview and http://docs.jboss.org/jbpm/v5.1/userguide/ch02.html Getting Started chapter, and much more. And we'll continue this work in the next few weeks as well, so you can expect more details soon.
* The http://docs.jboss.org/jbpm/v5.1/userguide/ch09.html new BPMN 2.0 Eclipse plugin has made significant steps forward as well. The goal of this new editor is to support the full BPMN 2.0 specification . It's still work in progress but it can already be used to create executable BPMN2 processes and execute them on jBPM5. We'll be working hard to improve the usability in the next few months.
* Smaller feature enhancements, like
* Automatic synchronization of processes in the jbpm-console when new proceses are deployed on the Guvnor repository
* Simplified data passing to and from human tasks (and forms)
* Extended BPMN2 engine with support for repeating timers
* Support for multi-threading
A full overview of everything that was included can be found in the https://issues.jboss.org/browse/JBPM jBPM JIRA.
http://docs.jboss.org/jbpm/v5.1/userguide/images/Chapter-Overview/Overvie... http://docs.jboss.org/jbpm/v5.1/userguide/images/Chapter-Overview/Overvie...
jBPM 5.1.0 is synchronized with Drools 5.2.0, which also has just been released. If you want to know more, take a look http://blog.athico.com/2011/06/drools-52-released.html here.
I'd like to thank everyone that contributed to this release! This includes not just the core developers obviously, but everyone in the community that contributed in one way or another, from testing, improving documentation, creating examples, bug reporting to submitting patches and feature contributions!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/611731#611731]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 5 months
[jBPM] - Tasks definition extension points
by Marco Piraccini
Marco Piraccini [http://community.jboss.org/people/mpiraccini] created the discussion
"Tasks definition extension points"
To view the discussion, visit: http://community.jboss.org/message/612158#612158
--------------------------------------------------------------
Hi Guys,
I'm looking for a (smart) way of extending Tasks definitions with custom attributes, in a way similar to the one used with "drools" attributes.
For instance, if we have:
<bpmn2:task id="(...)" drools:taskName="Application" name="Task2">
(...)
</bpmn2:task>
...I'd like also to define:
<bpmn2:task id="(...)" drools:taskName="Application" custom:group="test" name="Task2">
(...)
</bpmn2:task>
...where the "group" attibute is defined by me.
Now, I'd like to get these values in my WorkItems, so that I can use them in my (custom) WorkItemHandler.
Looking at the JBPM code, the correct strategy seems to be (correct me, if I'm wrong) to load them in the org.jbpm.bpmn2.xmlAbstractWorkHandler class and to put them as WorkItem "Metadata".
Now the question is: Is my reasoning is correct ore there's a smarter way to obtain the same thing? Becaus if i'm not wrong, I have to modify the JBPM code to implement that...
Marco.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/612158#612158]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 5 months
[jBPM] - jbpm5 Exception:Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#2]
by cheney-dut
cheney-dut [http://community.jboss.org/people/cheney-dut] created the discussion
"jbpm5 Exception:Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#2]"
To view the discussion, visit: http://community.jboss.org/message/611023#611023
--------------------------------------------------------------
Today, i write a demo. i get the following exception when runing.
Anyone can help?
Thanks!
| 17895 2011-06-20 22:49:50,151[main] ERROR event.def.AbstractFlushingEventListener.performExecutions - Could not synchronize database state with session
org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#2]
at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1792)
at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2435)
at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2335)
at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2635)
at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:115)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:168)
at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027)
at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:365)
at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:504)
at bitronix.tm.BitronixTransaction.fireBeforeCompletionEvent(BitronixTransaction.java:397)
at bitronix.tm.BitronixTransaction.commit(BitronixTransaction.java:147)
at bitronix.tm.BitronixTransactionManager.commit(BitronixTransactionManager.java:95)
at com.sinosig.claim.bpm.factory.ProcessInstanceTest.testNext(ProcessInstanceTest.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at org.springframework.test.ConditionalTestCase.runBare(ConditionalTestCase.java:76)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
17902 2011-06-20 22:49:50,158[main] WARN bitronix.tm.BitronixTransaction.fireBeforeCompletionEvent - Synchronization.beforeCompletion() call failed for org.hibernate.ejb.AbstractEntityManagerImpl$1@1611aec, marking transaction as rollback only
javax.persistence.OptimisticLockException: org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#2]
at org.hibernate.ejb.AbstractEntityManagerImpl.wrapStaleStateException(AbstractEntityManagerImpl.java:630)
at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:588)
at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:513)
at bitronix.tm.BitronixTransaction.fireBeforeCompletionEvent(BitronixTransaction.java:397)
at bitronix.tm.BitronixTransaction.commit(BitronixTransaction.java:147)
at bitronix.tm.BitronixTransactionManager.commit(BitronixTransactionManager.java:95)
at com.sinosig.claim.bpm.factory.ProcessInstanceTest.testNext(ProcessInstanceTest.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at org.springframework.test.ConditionalTestCase.runBare(ConditionalTestCase.java:76)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#2]
at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1792)
at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2435)
at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2335)
at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2635)
at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:115)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:168)
at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027)
at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:365)
at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:504)
... 21 more |
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/611023#611023]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 5 months
[JBoss Messaging] - Re: close jms conection cause block
by Ivan Nushev
Ivan Nushev [http://community.jboss.org/people/ivannushev] created the discussion
"Re: close jms conection cause block"
To view the discussion, visit: http://community.jboss.org/message/611357#611357
--------------------------------------------------------------
Hi all. Just to add that I succeeded to make remote JMS MessageListeners reliable using sslservlet remoting transport. To achieve this goal I use the remoting servlet configuration packed in JBM 1.4.6.GA.SP1:
http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_6_GA_SP1... http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_6_GA_SP1...
plus a few settings for SSL flavour and a JMS Connection' javax.jms.ExceptionListener which recreate the JMS Connection and Topic subscription in case of connection exception. I attach the exact configuration used:
<mbean code="org.jboss.remoting.transport.Connector"
name="jboss.remoting:service=connector,transport=sslservlet,target=jms,loc=public"
display-name="JMS Public Servlet transport Connector">
<attribute name="Configuration">
<config>
<invoker transport="sslservlet">
<!-- There should be no reason to change these parameters - warning!
Changing them may stop JBoss Messaging working correctly -->
<attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
<attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
<attribute name="dataType" isParam="true">jms</attribute>
<attribute name="serverBindAddress">${jboss.bind.address}</attribute>
<attribute name="serverBindPort">443</attribute>
<attribute name="clientConnectAddress">${public.firewall.address}</attribute>
<attribute name="clientConnectPort">443</attribute>
<attribute name="numberOfCallRetries" isParam="true">1</attribute>
<attribute name="pingFrequency" isParam="true">214748364</attribute>
<attribute name="pingWindowFactor" isParam="true">10</attribute>
<attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
<attribute name="callbackStore">org.jboss.remoting.callback.BlockingCallbackStore</attribute>
<attribute name="unwrapSingletonArrays">true</attribute>
<attribute name="path">unified-invoker/PublicJmsServerInvokerServlet</attribute>
<attribute name="return-exception">true</attribute>
<attribute name="createUniqueObjectName">true</attribute>
<attribute name="useAllParams" isParam="true">true</attribute>
<!-- End immutable parameters -->
<attribute name="stopLeaseOnFailure" isParam="true">true</attribute>
<!-- Periodicity of client pings. Server window by default is twice this figure -->
<attribute name="clientLeasePeriod" isParam="true">10000</attribute>
<attribute name="validatorPingPeriod" isParam="true">10000</attribute>
<attribute name="validatorPingTimeout" isParam="true">5000</attribute>
<attribute name="failureDisconnectTimeout" isParam="true">0</attribute>
<attribute name="callbackErrorsAllowed">1</attribute>
<attribute name="registerCallbackListener">false</attribute>
<attribute name="useClientConnectionIdentity" isParam="true">true
</attribute>
<attribute name="timeout" isParam="true">0</attribute>
<!-- Max Number of connections in client pool. This should be significantly
higher than the max number of sessions/consumers you expect -->
<attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
<!-- Set this to true if you want the servlet transport to block waiting
for server->client traffic. Or false if you want it to poll for new traffic
periodically. Recommended is blocking -->
<attribute name="blockingMode" isParam="true">blocking</attribute>
<!-- Timeout for blocking. Only has relevance if blockingMode = blocking -->
<attribute name="blockingTimeout" isParam="true">30000</attribute>
<!-- The periodicity of polling. Only has relevance if blockingMode = nonblocking -->
<!--attribute name="callbackPollPeriod" isParam="true">10000</attribute -->
</invoker>
<handlers>
<handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler
</handler>
</handlers>
</config>
</attribute>
</mbean>
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/611357#611357]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 5 months
[JBoss Tools] - Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
by u j
u j [http://community.jboss.org/people/bcn] created the discussion
"Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported."
To view the discussion, visit: http://community.jboss.org/message/597020#597020
--------------------------------------------------------------
I try to run Eclipse with a JDK 64 bits.
Is there anything I can do to make it work?
Thanks,
Ulrich
org.jboss.tools.vpe.xulrunner.XulRunnerException: Current platform 'win32.win32.x86_64' is not supported.
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.wrapXulRunnerError(MozillaEditor.java:789)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.showXulRunnerError(MozillaEditor.java:705)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:639)
at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:902)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:231)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:440)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:164)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReferenc
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/597020#597020]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 5 months
[jBPM] - jBPM5.1 - eclipse BPMN process editor loses imports of script tasks
by Sebastien Lelarge
Sebastien Lelarge [http://community.jboss.org/people/slelarge] created the discussion
"jBPM5.1 - eclipse BPMN process editor loses imports of script tasks"
To view the discussion, visit: http://community.jboss.org/message/614763#614763
--------------------------------------------------------------
Hi all,
I am using the eclipse BPMN process editor v5.1.0.Final (not the new one BPMN visual editor) to design my processes and I have discovered something that is really annoying.
When using script tasks with Java code inside, I use the "imports" button to import external classes and make them available in the code executed from the task. When I save my process definition just after setting imports, they are successfully saved in the generated BPMN file for this process.
The problem is that the imports disappear when I re-open the process definition in editor to update it and then save it. When the process is saved after the update, then the imports are lost.
Is this a known problem for the plugin ? Is there something am I doing wrong in task config ?
How can I solve this problem ?
I am still using this editor because I think the new one is not very useable to configure script & user tasks. Maybe future versions will be easier and intuitive to use.
regards
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/614763#614763]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 5 months
[Performance Tuning] - Large number of threads/connections marked "keep alive"
by Ben Hsu
Ben Hsu [http://community.jboss.org/people/benhsu_at_bluefly] created the discussion
"Large number of threads/connections marked "keep alive""
To view the discussion, visit: http://community.jboss.org/message/587341#587341
--------------------------------------------------------------
Hello
We're seeing an issue where the performance of our application would degrade over time, to the point where its unresponsive. Based on what I see, I think it might be related to how we're configuring keep-alive, and I'm wondering where I can find more information about configuring keep-alive in JBoss.
The symptoms:
- The application's performance would degrade over the day
- eventually we will get a message saying "all 200 threads are busy, please increase the maximum thread count"
- at this point, doing a thread dump (using "kill -3") shows many threads in the following state:
<blockquote>
"TP-Processor200" daemon prio=1 tid=0x0000002b31e372c0 nid=0x651a runnable [0x000000005408e000..0x000000005408ec30]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
- locked <0x0000002b082abec0> (a java.io.BufferedInputStream)
at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:620)
at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:558)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:685)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
</blockquote>
- when I look at the "connection scoreboard" in the JBoss web console, I see 200 connections marked with a "K" for "keep alive", also these connections look like they've been around for a long time (around 7,000,000ms, which will be 2 hours), long after we've killed all the clientsd
Based on what I saw above and some googling, I'm thinking this might be related to how we're configuring keep alive. I haven't been able to go further than this, because I don't know much about JBoss configuration. Does anybody have any information about how keep alive is being configured in JBoss?
We are using JBoss version 4.0.5 GA
Thank you!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/587341#587341]
Start a new discussion in Performance Tuning at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months
