[JBoss jBPM] - Graphical Process Designer Problems
by miroth
Hello,
I'm an absolute beginner in jbpm so I started today to install the Graphical Process Designer.
1. I downloaded and extracted the the package jbpm-jpdl-suite-3.2.2.zip
2. I downloaded the package eclipse-SDK-3.3-win32.zip as it is adviced in the designer subdirectory
3. I download and extracted the package apache-ant-1.7.0-bin.zip
4. I changed to f:/jbpm-jpdl-3.2.2/designer
5. I opened the file build.properties with the editor and change the following line
eclipse.local.path=f:/download/eclipse
6. I started ant with "ant.bat install"
Everything works !!
When I start the designer now and create a new process project and click on the src/main/jdpl/simple/processdefintion.xml file the editor opens. The problem is that the context menu (right mouse button) seems not complete, when I click on a node I just get the Eclipse menus like "Run as" "Debug as" and so on, but I miss the menu entries like "add task" or "add actions". The swimlane tab is also vanished.
What I am doing wrong ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096076#4096076
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096076
18Â years, 9Â months
[Messaging, JMS & JBossMQ] - Re: JMS msg get redelivered although setting retry to 0
by adrianï¼ jboss.org
Ok, I think I understand what the problem is.
The issue is that the failover node doesn't know that the message was already
delivered. The node (the original node) that did know has crashed.
The problem comes because the failover node uses the transaction log
to recover the state to the "last known good state" of the message
(which was in your case before the message was delivered to the MDB).
The only way I can see to fix the problem, would be to update the
redelivered status and redelivery count of the message in the database
before the message is delivered to the client (instead of when the server
receives the NACK/rollback - which it won't do if the server crashes
- it will do it if the problem is just the client loosing connectivity).
i.e. in BasicQueue
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/jbossmq/src/main...
This would involve moving the code in "nackMessage()"
| try
| {
| ...
|
| // Set redelivered, vendor-specific flags
| message.invalidate();
| // Update the persistent message outside the transaction
| // We want to know the message might have been delivered regardless
| if (message.isPersistent())
| server.getPersistenceManager().update(message, null);
| }
| catch (JMSException e)
| {
| log.error("Error setting redelivered " + message, e);
| }
| }
|
To the setupMessageAcknowledgement() method instead (which is always
invoked before delivering the message).
But, this would obviously have a deterimental effect on performance
since it would always update persistent messages with the redelivered status
in the database regardless of whether it is was actually redelivered or not
(if it doesn't get redelivered, i.e. it is ACKed/committed, it will be deleted so the
early change in status is irrelevant).
Do you want to try that patch?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096074#4096074
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096074
18Â years, 9Â months