[JBoss JIRA] Created: (JBAS-4042) Timer service fails to create TIMERS table is table exists in other schema
3:28 a.m.
Timer service fails to create TIMERS table is table exists in other schema
--------------------------------------------------------------------------
Key: JBAS-4042
URL: http://jira.jboss.com/jira/browse/JBAS-4042
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.0.4.GA
Environment: Reported against Oracle 9i
Reporter: Darran Lofthouse
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.1.CR1
The TIMER service does not allow the name of the table to be used by the timer service to
be overriden.
To check is the table already exists the following is called: -
rs = dmd.getTables(catalog, schema, tableName, null);
return rs.next();
For the timer service no schema is specified so this returns the TIMER tables for all
schemas so we do not create the table for the current schema even though it is not
available.
If the table name is specified as SCHEMA_NAME.TABLE_NAME then the search will be
restricted to the schema so will prevent tables from other schemas being picked up.
--
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:03 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4042) Timer service fails to create TIMERS table is table exists in other schema
[ http://jira.jboss.com/jira/browse/JBAS-4042?page=all ]
Dimitris Andreadis updated JBAS-4042:
-------------------------------------
Issue Type: Feature Request (was: Bug)
Fix Version/s: JBossAS-4.2.0.GA
JBossAS-5.0.0.Beta3
JBossAS-4.0.5.SP1
(was: JBossAS-4.2.1.CR1)
Timer service fails to create TIMERS table is table exists in other
schema
--------------------------------------------------------------------------
Key: JBAS-4042
URL: http://jira.jboss.com/jira/browse/JBAS-4042
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.0.4.GA
Environment: Reported against Oracle 9i
Reporter: Darran Lofthouse
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.0.5.SP1 , JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3
The TIMER service does not allow the name of the table to be used by the timer service to
be overriden.
To check is the table already exists the following is called: -
rs = dmd.getTables(catalog, schema, tableName, null);
return rs.next();
For the timer service no schema is specified so this returns the TIMER tables for all
schemas so we do not create the table for the current schema even though it is not
available.
If the table name is specified as SCHEMA_NAME.TABLE_NAME then the search will be
restricted to the schema so will prevent tables from other schemas being picked up.
--
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:05 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4042) Allow configuration of timers table name (and schema)
[ http://jira.jboss.com/jira/browse/JBAS-4042?page=all ]
Dimitris Andreadis updated JBAS-4042:
-------------------------------------
Summary: Allow configuration of timers table name (and schema) (was: Timer service
fails to create TIMERS table is table exists in other schema)
Allow configuration of timers table name (and schema)
-----------------------------------------------------
Key: JBAS-4042
URL: http://jira.jboss.com/jira/browse/JBAS-4042
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.0.4.GA
Environment: Reported against Oracle 9i
Reporter: Darran Lofthouse
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.0.5.SP1 , JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3
The TIMER service does not allow the name of the table to be used by the timer service to
be overriden.
To check is the table already exists the following is called: -
rs = dmd.getTables(catalog, schema, tableName, null);
return rs.next();
For the timer service no schema is specified so this returns the TIMER tables for all
schemas so we do not create the table for the current schema even though it is not
available.
If the table name is specified as SCHEMA_NAME.TABLE_NAME then the search will be
restricted to the schema so will prevent tables from other schemas being picked up.
--
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:07 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-4042) Allow configuration of timers table name (and schema)
[ http://jira.jboss.com/jira/browse/JBAS-4042?page=all ]
Dimitris Andreadis closed JBAS-4042.
------------------------------------
Resolution: Done
The timers table name (and optionally schema) can be configured through the
deploy/ejb-deployer.xml descriptor:
...
<!--
A persistence policy that persists timers to a database.
The 2 supported db persistence plugins are:
org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin
org.jboss.ejb.txtimer.OracleDatabasePersistencePlugin
The table name defaults to "TIMERS". It can be overriden using the
'TimersTable' attribute if the persistence plugin supports it.
When overriding the timers table, an optional schema can be specified
using the syntax [schema.]table
-->
<mbean code="org.jboss.ejb.txtimer.DatabasePersistencePolicy"
name="jboss.ejb:service=EJBTimerService,persistencePolicy=database">
<!-- DataSourceBinding ObjectName -->
<depends
optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
<!-- The plugin that handles database persistence -->
<attribute
name="DatabasePersistencePlugin">org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin</attribute>
<!-- The timers table name -->
<attribute name="TimersTable">TIMERS</attribute>
</mbean>
...
Allow configuration of timers table name (and schema)
-----------------------------------------------------
Key: JBAS-4042
URL: http://jira.jboss.com/jira/browse/JBAS-4042
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.0.4.GA
Environment: Reported against Oracle 9i
Reporter: Darran Lofthouse
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3, JBossAS-4.0.5.SP1
The TIMER service does not allow the name of the table to be used by the timer service to
be overriden.
To check is the table already exists the following is called: -
rs = dmd.getTables(catalog, schema, tableName, null);
return rs.next();
For the timer service no schema is specified so this returns the TIMER tables for all
schemas so we do not create the table for the current schema even though it is not
available.
If the table name is specified as SCHEMA_NAME.TABLE_NAME then the search will be
restricted to the schema so will prevent tables from other schemas being picked up.
--
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:09 a.m.
New subject: [JBoss JIRA] Reopened: (JBAS-4042) Allow configuration of timers table name (and schema)
[ http://jira.jboss.com/jira/browse/JBAS-4042?page=all ]
Dimitris Andreadis reopened JBAS-4042:
--------------------------------------
Allow configuration of timers table name (and schema)
-----------------------------------------------------
Key: JBAS-4042
URL: http://jira.jboss.com/jira/browse/JBAS-4042
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.0.4.GA
Environment: Reported against Oracle 9i
Reporter: Darran Lofthouse
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.0.5.SP1 , JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3
The TIMER service does not allow the name of the table to be used by the timer service to
be overriden.
To check is the table already exists the following is called: -
rs = dmd.getTables(catalog, schema, tableName, null);
return rs.next();
For the timer service no schema is specified so this returns the TIMER tables for all
schemas so we do not create the table for the current schema even though it is not
available.
If the table name is specified as SCHEMA_NAME.TABLE_NAME then the search will be
restricted to the schema so will prevent tables from other schemas being picked up.
--
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:11 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-4042) Allow configuration of timers table name (and schema)
[ http://jira.jboss.com/jira/browse/JBAS-4042?page=all ]
Dimitris Andreadis closed JBAS-4042.
------------------------------------
Resolution: Done
Allow configuration of timers table name (and schema)
-----------------------------------------------------
Key: JBAS-4042
URL: http://jira.jboss.com/jira/browse/JBAS-4042
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.0.4.GA
Environment: Reported against Oracle 9i
Reporter: Darran Lofthouse
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3, JBossAS-4.0.5.SP1
The TIMER service does not allow the name of the table to be used by the timer service to
be overriden.
To check is the table already exists the following is called: -
rs = dmd.getTables(catalog, schema, tableName, null);
return rs.next();
For the timer service no schema is specified so this returns the TIMER tables for all
schemas so we do not create the table for the current schema even though it is not
available.
If the table name is specified as SCHEMA_NAME.TABLE_NAME then the search will be
restricted to the schema so will prevent tables from other schemas being picked up.
--
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:11 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4042) Allow configuration of timers table name (and schema)
[ http://jira.jboss.com/jira/browse/JBAS-4042?page=all ]
Dimitris Andreadis updated JBAS-4042:
-------------------------------------
Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration]
Allow configuration of timers table name (and schema)
-----------------------------------------------------
Key: JBAS-4042
URL: http://jira.jboss.com/jira/browse/JBAS-4042
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.0.4.GA
Environment: Reported against Oracle 9i
Reporter: Darran Lofthouse
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.0.5.SP1 , JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3
The TIMER service does not allow the name of the table to be used by the timer service to
be overriden.
To check is the table already exists the following is called: -
rs = dmd.getTables(catalog, schema, tableName, null);
return rs.next();
For the timer service no schema is specified so this returns the TIMER tables for all
schemas so we do not create the table for the current schema even though it is not
available.
If the table name is specified as SCHEMA_NAME.TABLE_NAME then the search will be
restricted to the schema so will prevent tables from other schemas being picked up.
--
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
7050
days inactive
7121
days old
6 comments
2 participants
participants (2)
-
Darran Lofthouse (JIRA) -
Dimitris Andreadis (JIRA)