JBossDeveloper

i don't think we need to do it that way tom. Wouldn't this just work with no JBPM changes?

@MessageDriven(activationConfig= {
 ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
 ActivationConfigProperty(propertyName="messageSelector", propertyValue="jobId IS NOT NULL"),
 ActivationConfigProperty(propertyName="destination", propertyValue="queue/DLQ")})
public class DLQFailureHandler implements MessageListener
{
 JbpmConfiguration jbpmConfiguration = null;
 @Resource(name="JbpmCfgResource") String jbpmCfgResource = null;

 @PostConstruct
 public void initJbpm() {
 jbpmConfiguration = JbpmConfiguration.getInstance(jbpmCfgResource);
 }

 public void onMessage(Message message) {
 long jobId = 0;
 try {
 jobId = message.getLongProperty("jobId");
 } catch (JMSException ignored) {
 // message selector confirms existence
 }

 JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
 try {
 JobSession jobSession = jbpmContext.getJobSession();
 Job job = jobSession.loadJob(jobId);
 if (!(job instanceof ExecuteNodeJob)) {
 // do some other failure handling
 jbpmContext.close();
 return;
 }
 ExecuteNodeJob executeNodeJob = (ExecuteNodeJob)job;
 if (executeNodeJob.getNode().hasLeavingTransition("failure")) {
 executeNodeJob.getProcessInstance().signal("failure");
 jobSession.deleteJob(job);
 }
 else {
 // push to a different DLQ?
 }
 } finally {
 jbpmContext.close();
 }
 }
}

Srry...let me continue....Just write an MDB that activates on the DLQ. There isn't any modification to jbpm code. I don't think it could work the way you describe anyways.

For JBoss at least, the retry count is configured at the MDB level. You pass it in as container configuration or as an activation property.

Felt like writing about this here:

http://bill.burkecentral.com/2007/08/06/guaranteed-jbpm-failure-handling/

I discussed why the Synchronization approach wouldn't work.