[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
2:08 p.m.
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: http://jira.jboss.com/jira/browse/JBSEAM-1839
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Michael Yuan
Assigned To: Michael Yuan
Fix For: 2.0.0.GA
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:04 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
[ http://jira.jboss.com/jira/browse/JBSEAM-1839?page=all ]
Norman Richards updated JBSEAM-1839:
------------------------------------
Fix Version/s: 2.0.1.GA
(was: 2.0.0.GA)
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: http://jira.jboss.com/jira/browse/JBSEAM-1839
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Michael Yuan
Assigned To: Michael Yuan
Fix For: 2.0.1.GA
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:25 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
[ http://jira.jboss.com/jira/browse/JBSEAM-1839?page=all ]
Michael Yuan reassigned JBSEAM-1839:
------------------------------------
Assignee: Michael Yuan (was: Michael Yuan)
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: http://jira.jboss.com/jira/browse/JBSEAM-1839
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Michael Yuan
Assigned To: Michael Yuan
Fix For: 2.0.1.GA
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:27 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
[ http://jira.jboss.com/jira/browse/JBSEAM-1839?page=comments#action_12379735 ]
Michael Yuan commented on JBSEAM-1839:
--------------------------------------
There seems to be a Quartz issue since I encountered this exact error:
http://jira.opensymphony.com/browse/QUARTZ-609
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: http://jira.jboss.com/jira/browse/JBSEAM-1839
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Michael Yuan
Assigned To: Michael Yuan
Fix For: 2.0.1.GA
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:33 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
[ http://jira.jboss.com/jira/browse/JBSEAM-1839?page=all ]
Norman Richards updated JBSEAM-1839:
------------------------------------
Fix Version/s: 2.0.x
(was: 2.0.1.GA)
Description:
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
was:
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
Priority: Minor (was: Major)
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: http://jira.jboss.com/jira/browse/JBSEAM-1839
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Michael Yuan
Assigned To: Michael Yuan
Priority: Minor
Fix For: 2.0.x
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
[ http://jira.jboss.com/jira/browse/JBSEAM-1839?page=all ]
Pete Muir updated JBSEAM-1839:
------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.0.x)
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: http://jira.jboss.com/jira/browse/JBSEAM-1839
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Michael Yuan
Assigned To: Michael Yuan
Priority: Minor
Fix For: 2.1.0.GA
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:44 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
[ http://jira.jboss.com/jira/browse/JBSEAM-1839?page=all ]
Pete Muir updated JBSEAM-1839:
------------------------------
Component/s: Async
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: http://jira.jboss.com/jira/browse/JBSEAM-1839
Project: JBoss Seam
Issue Type: Feature Request
Components: Async
Reporter: Michael Yuan
Assigned To: Michael Yuan
Priority: Minor
Fix For: 2.1.0.GA
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:59 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
[ http://jira.jboss.com/jira/browse/JBSEAM-1839?page=all ]
Norman Richards updated JBSEAM-1839:
------------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.A1)
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: http://jira.jboss.com/jira/browse/JBSEAM-1839
Project: JBoss Seam
Issue Type: Feature Request
Components: Async
Reporter: Michael Yuan
Assigned To: Michael Yuan
Priority: Minor
Fix For: 2.1.0.GA
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:29 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
[ http://jira.jboss.com/jira/browse/JBSEAM-1839?page=all ]
Pete Muir updated JBSEAM-1839:
------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.BETA1)
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: http://jira.jboss.com/jira/browse/JBSEAM-1839
Project: JBoss Seam
Issue Type: Feature Request
Components: Async
Reporter: Michael Yuan
Assigned To: Michael Yuan
Priority: Minor
Fix For: 2.1.0.GA
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:29 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
[ http://jira.jboss.com/jira/browse/JBSEAM-1839?page=all ]
Pete Muir updated JBSEAM-1839:
------------------------------
Fix Version/s: 2.1.x
(was: 2.1.0.GA)
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: http://jira.jboss.com/jira/browse/JBSEAM-1839
Project: Seam
Issue Type: Feature Request
Components: Async
Reporter: Michael Yuan
Assigned To: Michael Yuan
Priority: Minor
Fix For: The future
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:41 p.m.
New subject: [JBoss JIRA] Assigned: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS
[
https://jira.jboss.org/browse/JBSEAM-1839?page=com.atlassian.jira.plugin....
]
Shane Bryzak reassigned JBSEAM-1839:
------------------------------------
Assignee: (was: Michael Yuan)
Use HSQL to store Quartz jobs when deployed on JBoss AS
-------------------------------------------------------
Key: JBSEAM-1839
URL: https://jira.jboss.org/browse/JBSEAM-1839
Project: Seam
Issue Type: Feature Request
Components: Async
Reporter: Michael Yuan
Priority: Minor
Fix For: The future
Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started
when the server reboots. The user can use persistence job stores by using a custom quartz
property file. However, in JBoss AS, we should store jobs in the HSQL DB by default:
* In the dispatcher component, we can have a "jboss=true" attribute
* If this attribute is true, the QuartzDispatcher will setup Quartz tables for this
particular app in the HSQL at startup, and then use the HSQL DB as persistent job store.
This way, when the application deploys again, all the jobs for this application will be
auto-started again.
--
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
4956
days inactive
6118
days old
10 comments
4 participants
participants (4)
-
Michael Yuan (JIRA) -
Norman Richards (JIRA)
-
Pete Muir (JIRA)
-
Shane Bryzak (JIRA)