April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Reopened: (JBAS-1690) Timer.cancel in a transaction never calls TimerImpl.killTimer

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1690?page=all ] Dimitris Andreadis reopened JBAS-1690: -------------------------------------- > Timer.cancel in a transaction never calls TimerImpl.killTimer > ------------------------------------------------------------- > > Key: JBAS-1690 > URL: http://jira.jboss.com/jira/browse/JBAS-1690 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.1 SP1 > Reporter: ?ystein Hansen > Assigned To: Dimitris Andreadis > Fix For: JBossAS-5.0.0.Beta1, JBossAS-4.0.4RC1 > > Attachments: TimerTestBean.java, TimerTestClient.java > > > Calling Timer.cancel in a Transaction does not delete the timer. > The Timer is marked as CANCELED if transaction is commited, thus ejbTimeout is not called. > However - the TimerImpl.TimerTask.run does nothing if Timer.isActive is false. > Proposed solution: > Either call killTimer in TimerTask.run, or treat CANCELED and EXPIRED the same way. > See JBoss Forum for source code (SessionBean+UnitTest) to reproduce the problem -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-1394) TimerService.getTimers() does not seem to work when called at ServletContextListener.contextInitialised time

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1394?page=all ] Dimitris Andreadis reopened JBAS-1394: -------------------------------------- > TimerService.getTimers() does not seem to work when called at ServletContextListener.contextInitialised time > ------------------------------------------------------------------------------------------------------------ > > Key: JBAS-1394 > URL: http://jira.jboss.com/jira/browse/JBAS-1394 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.1 Final > Environment: Suse Linux 9.1, JBoss 4.0.1 > Reporter: Steve Bostock > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.0.4RC1 > > > I have a stateless session bean that implements TimedObject. It has a schedule() method that gets called from the contextInitialized method of a WebApp. The schedule method first calls getTimers() and cancels any timers it finds, it then creates new ones. This call to getTimers never finds any existing timers, even though they exist in the TIMERS table in the DB. The net effect is, that after a reboot, I end up with duplicate timers. > If I call the same schedule() method from a client program at a later time, it correctly finds and cancels all extant timers before creating new ones. > From looking at the debug log, it appears that the restore > DEBUG [org.jboss.ejb.txtimer.DatabasePersistencePolicy] Restoring 2 timer(s) > is happening sometime after contextInitialized gets called. > This problem is repeatable. > Steve -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-1091) Allow ejb timers to persist across server restarts

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1091?page=all ] Dimitris Andreadis closed JBAS-1091. ------------------------------------ Resolution: Done > Allow ejb timers to persist across server restarts > -------------------------------------------------- > > Key: JBAS-1091 > URL: http://jira.jboss.com/jira/browse/JBAS-1091 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assigned To: Dimitris Andreadis > Fix For: JBossAS-5.0.0.Beta1, JBossAS-4.0.4RC1 > > > SourceForge Submitter: starksm . > Reviewing the ejb 2.1 spec, the only persistence > guarentee for timers is that they survive a server > crash. It does not say anything about timers needing to > be persisted across normal shutdowns, even for entity > beans. I think this could be a useful feature, but its > not something that is defined by the spec. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1091) Allow ejb timers to persist across server restarts

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1091?page=all ] Dimitris Andreadis updated JBAS-1091: ------------------------------------- Component/s: Scheduling/Timers (was: EJB2) > Allow ejb timers to persist across server restarts > -------------------------------------------------- > > Key: JBAS-1091 > URL: http://jira.jboss.com/jira/browse/JBAS-1091 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.0.4RC1, JBossAS-5.0.0.Beta1 > > > SourceForge Submitter: starksm . > Reviewing the ejb 2.1 spec, the only persistence > guarentee for timers is that they survive a server > crash. It does not say anything about timers needing to > be persisted across normal shutdowns, even for entity > beans. I think this could be a useful feature, but its > not something that is defined by the spec. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-1091) Allow ejb timers to persist across server restarts

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1091?page=all ] Dimitris Andreadis reopened JBAS-1091: -------------------------------------- > Allow ejb timers to persist across server restarts > -------------------------------------------------- > > Key: JBAS-1091 > URL: http://jira.jboss.com/jira/browse/JBAS-1091 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.0.4RC1, JBossAS-5.0.0.Beta1 > > > SourceForge Submitter: starksm . > Reviewing the ejb 2.1 spec, the only persistence > guarentee for timers is that they survive a server > crash. It does not say anything about timers needing to > be persisted across normal shutdowns, even for entity > beans. I think this could be a useful feature, but its > not something that is defined by the spec. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-2273) createDDL for timers does not take care of pk-contraint-template

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2273?page=all ] Dimitris Andreadis reopened JBAS-2273: -------------------------------------- > createDDL for timers does not take care of pk-contraint-template > ---------------------------------------------------------------- > > Key: JBAS-2273 > URL: http://jira.jboss.com/jira/browse/JBAS-2273 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.3 Final > Environment: JBoss 4.0.3RC3, JDK 1.5.0_05, Solaris/SPARC 9 > Reporter: Frank Langelage > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.4RC1, JBossAS-5.0.0.Beta1 > > Attachments: diff.txt, GeneralPurposeDatabasePersistencePlugin.java > > > I recently switched the persistence of timers and messages to an Informix datasource instead of hypersonic. > The creation of table timers did not succeed, because the order of the constraint name for the PK and the PK's columns has to be just the other way round for informix. For CMP EJB's the is a pk-contraint-template in standardjbosscmp-jdbc.xml. I extended GeneralPurposeDatabasePersistencePlugin.java to use this. > The modified file and the cvs diff will be attached shortly. > A second issue was the datatype mapping for java.lang.Object. > sql-type blob with informix means, you'll have to create an additional dbspace for blob data if you don't have one. The column's data will be stored there. > As an alternative you can use datatype byte. The data will be stored inline with the table data in the same dbspace. This is, in my opinion, the better way. So I modified the informix type mapping for this type to jdbc-type LONGVARBINARY and sql-type BYTE. > The cvs diff is also attached. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2273) createDDL for timers does not take care of pk-contraint-template

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2273?page=all ] Dimitris Andreadis updated JBAS-2273: ------------------------------------- Component/s: Scheduling/Timers (was: EJB2) > createDDL for timers does not take care of pk-contraint-template > ---------------------------------------------------------------- > > Key: JBAS-2273 > URL: http://jira.jboss.com/jira/browse/JBAS-2273 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.3 Final > Environment: JBoss 4.0.3RC3, JDK 1.5.0_05, Solaris/SPARC 9 > Reporter: Frank Langelage > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.4RC1, JBossAS-5.0.0.Beta1 > > Attachments: diff.txt, GeneralPurposeDatabasePersistencePlugin.java > > > I recently switched the persistence of timers and messages to an Informix datasource instead of hypersonic. > The creation of table timers did not succeed, because the order of the constraint name for the PK and the PK's columns has to be just the other way round for informix. For CMP EJB's the is a pk-contraint-template in standardjbosscmp-jdbc.xml. I extended GeneralPurposeDatabasePersistencePlugin.java to use this. > The modified file and the cvs diff will be attached shortly. > A second issue was the datatype mapping for java.lang.Object. > sql-type blob with informix means, you'll have to create an additional dbspace for blob data if you don't have one. The column's data will be stored there. > As an alternative you can use datatype byte. The data will be stored inline with the table data in the same dbspace. This is, in my opinion, the better way. So I modified the informix type mapping for this type to jdbc-type LONGVARBINARY and sql-type BYTE. > The cvs diff is also attached. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2273) createDDL for timers does not take care of pk-contraint-template

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2273?page=all ] Dimitris Andreadis closed JBAS-2273. ------------------------------------ Resolution: Done > createDDL for timers does not take care of pk-contraint-template > ---------------------------------------------------------------- > > Key: JBAS-2273 > URL: http://jira.jboss.com/jira/browse/JBAS-2273 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.3 Final > Environment: JBoss 4.0.3RC3, JDK 1.5.0_05, Solaris/SPARC 9 > Reporter: Frank Langelage > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-5.0.0.Beta1, JBossAS-4.0.4RC1 > > Attachments: diff.txt, GeneralPurposeDatabasePersistencePlugin.java > > > I recently switched the persistence of timers and messages to an Informix datasource instead of hypersonic. > The creation of table timers did not succeed, because the order of the constraint name for the PK and the PK's columns has to be just the other way round for informix. For CMP EJB's the is a pk-contraint-template in standardjbosscmp-jdbc.xml. I extended GeneralPurposeDatabasePersistencePlugin.java to use this. > The modified file and the cvs diff will be attached shortly. > A second issue was the datatype mapping for java.lang.Object. > sql-type blob with informix means, you'll have to create an additional dbspace for blob data if you don't have one. The column's data will be stored there. > As an alternative you can use datatype byte. The data will be stored inline with the table data in the same dbspace. This is, in my opinion, the better way. So I modified the informix type mapping for this type to jdbc-type LONGVARBINARY and sql-type BYTE. > The cvs diff is also attached. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-1193) EJB Timer DatabasePersistencePlugin issue

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1193?page=all ] Dimitris Andreadis closed JBAS-1193. ------------------------------------ Resolution: Done > EJB Timer DatabasePersistencePlugin issue > ----------------------------------------- > > Key: JBAS-1193 > URL: http://jira.jboss.com/jira/browse/JBAS-1193 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assigned To: Thomas Diesler > Fix For: Closed issues from sourceforge > > > SourceForge Submitter: pyuill . > In 4.0.1 RC1 the > GeneralPurposeDatabasePersistencePlugin was changed > to use constants from the DatabasePersistencePlugin > interface for column names of the Timer table instead of > settable properties. One of the columns (INTERVAL) is a > reserved word in MySQL 4.1 > I can see three possible routes for the GPDPP: > 1) Reinstate the column name properties (perhaps > defaulting to the standard values). > 2) Respect the reserved word list in standardjbosscmp- > jdbc.xml (which can be easily expanded for particular a > DBMS). > 3) Change the INTERVAL column name. > Regards, > Peter Yuill -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1193) EJB Timer DatabasePersistencePlugin issue

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1193?page=all ] Dimitris Andreadis updated JBAS-1193: ------------------------------------- Component/s: Scheduling/Timers > EJB Timer DatabasePersistencePlugin issue > ----------------------------------------- > > Key: JBAS-1193 > URL: http://jira.jboss.com/jira/browse/JBAS-1193 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assigned To: Thomas Diesler > Fix For: Closed issues from sourceforge > > > SourceForge Submitter: pyuill . > In 4.0.1 RC1 the > GeneralPurposeDatabasePersistencePlugin was changed > to use constants from the DatabasePersistencePlugin > interface for column names of the Timer table instead of > settable properties. One of the columns (INTERVAL) is a > reserved word in MySQL 4.1 > I can see three possible routes for the GPDPP: > 1) Reinstate the column name properties (perhaps > defaulting to the standard values). > 2) Respect the reserved word list in standardjbosscmp- > jdbc.xml (which can be easily expanded for particular a > DBMS). > 3) Change the INTERVAL column name. > Regards, > Peter Yuill -- 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

19 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2007