I've solved this myself; my solution is documented below.
1. For unlimited re-attempts at delivering the message, I used the ActivationConfigProperty annotations to set the "useDLQ" property of the MDB activation to "false".
2. For delayed re-attempts, configure the queue as an MBean explicity with RedeliveryDelay set to the number of milliseconds (minimum) between successive delivery attempts at the same message. This is a PER-MESSAGE delay; four messages being redelivered will cause delivery attempts to arrive 4x as fast. This was acceptable for my use case.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066391#4066391
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066391
Just tried to add an issue in Jira - it won't let me add new issues (or add comments to existing issues) at the moment. I'll try again later.
Is putting "proper" process definitions under a source folder new for gpd 3.1?
I'm fairly certain that this wasn't a requirement in 3.0 (I have projects using gpd 3..0.x where the process definitions go under a standard folder).
Is there some strange eclipse reason that means you need to use a source folder for process definitions?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066388#4066388
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066388
Dear all,
Today I tried using entity-transaction with Toplink as the persistence provider and it didn't work because of ClassCastException. When I digged in to the Seam source, it looks like that entity-transaction is tightly coupled with Hibernate. Is this true? I hope I'm wrong about this.
Is there any reason why does the entity-transaction component is only supported for Hibernate?
Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066382#4066382
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066382