5:21 p.m.
EJB3 based job processor
------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Fix For: jBPM 3.2.10
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:43 a.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2945) EJB3 based job processor
[
https://jira.jboss.org/browse/JBPM-2945?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar reassigned JBPM-2945:
--------------------------------------
Assignee: Alejandro Guizar
EJB3 based job processor
------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:45 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2945) EJB3 based job processor
[
https://jira.jboss.org/browse/JBPM-2945?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2945:
-----------------------------------
EJB3 based job processor
------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:25 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2945) Job processor based on EJB3
[
https://jira.jboss.org/browse/JBPM-2945?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2945:
-----------------------------------
Summary: Job processor based on EJB3 (was: EJB3 based job processor)
Job processor based on EJB3
---------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:05 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2945) Job processor based on EJB3
[
https://jira.jboss.org/browse/JBPM-2945?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar commented on JBPM-2945:
----------------------------------------
Derived job processor based on Java EE 5 from existing enterprise module.
Produced web console overlay adapted to Java EE 5 job processor.
Job processor based on EJB3
---------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:05 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2945) Job processor based on EJB3
[
https://jira.jboss.org/browse/JBPM-2945?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar resolved JBPM-2945.
------------------------------------
Resolution: Done
Job processor based on EJB3
---------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:05 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2945) Job processor based on EJB3
[
https://jira.jboss.org/browse/JBPM-2945?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2945:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Job processor based on EJB3
---------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:05 a.m.
New subject: [JBoss JIRA] Reopened: (JBPM-2945) Job processor based on EJB3
[
https://jira.jboss.org/browse/JBPM-2945?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar reopened JBPM-2945:
------------------------------------
Job processor based on EJB3
---------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:05 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2945) Job processor based on EJB3
[
https://jira.jboss.org/browse/JBPM-2945?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar commented on JBPM-2945:
----------------------------------------
Reopening to deal with the following observations:
* In JBoss AS, JMS connections are pooled. "Creating" a connection each time one
is needed is therefore a better option than reusing a cached connection.
* Queue timers apart from other job types to prevent timers from falling behind.
Job processor based on EJB3
---------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:11 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2945) Job processor based on EJB3
[
https://jira.jboss.org/browse/JBPM-2945?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar resolved JBPM-2945.
------------------------------------
Resolution: Done
Job processor based on EJB3
---------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:11 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2945) Job processor based on EJB3
[
https://jira.jboss.org/browse/JBPM-2945?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar commented on JBPM-2945:
----------------------------------------
Addressed the above suggestions.
Job processor based on EJB3
---------------------------
Key: JBPM-2945
URL: https://jira.jboss.org/browse/JBPM-2945
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
There have some issues with how the retry mechanism works with Timers, and we recommend
not ditching the XA driver for 2 phase commit.
We will be changing how the JMS Listener works for jBPM; currently, it used JCA Inflow
Adapter, which is an element of JBoss SOA-P. We would like to instead use Message Driven
Beans; this is a really stable project and an element of EJB 3.0. We believe that the
issue with hung commits probably internally has something to do with JCA Inflow Adapter
and its transaction management. By using MDB, we will get Container Managed Transactions,
which is a stable and standard TX implementation which is well documented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5202
days inactive
5206
days old
10 comments
1 participants
participants (1)
-
Alejandro Guizar (JIRA)