April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Reopened: (JBAS-1306) Can't create timer because TARGETID column is too small

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1306?page=all ] Dimitris Andreadis reopened JBAS-1306: -------------------------------------- > Can't create timer because TARGETID column is too small > ------------------------------------------------------- > > Key: JBAS-1306 > URL: http://jira.jboss.com/jira/browse/JBAS-1306 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.1 Final > Environment: JBoss 4.0.1, Oracle 9 > Reporter: Tim McCune > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.4RC1, JBossAS-5.0.0.Beta1 > > > I tried using the timer service in JBoss 4 for the first time today and the timer creation failed because the TARGETID column is defined as VARCHAR(80), and the code is trying to insert a value that is 88 chars long: > target=jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/Scheduler,service=EJB > Can you just increase the column size to something like 255 chars by default? -- 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-1306) Can't create timer because TARGETID column is too small

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1306?page=all ] Dimitris Andreadis updated JBAS-1306: ------------------------------------- Component/s: Scheduling/Timers (was: EJB2) > Can't create timer because TARGETID column is too small > ------------------------------------------------------- > > Key: JBAS-1306 > URL: http://jira.jboss.com/jira/browse/JBAS-1306 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.1 Final > Environment: JBoss 4.0.1, Oracle 9 > Reporter: Tim McCune > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.4RC1, JBossAS-5.0.0.Beta1 > > > I tried using the timer service in JBoss 4 for the first time today and the timer creation failed because the TARGETID column is defined as VARCHAR(80), and the code is trying to insert a value that is 88 chars long: > target=jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/Scheduler,service=EJB > Can you just increase the column size to something like 255 chars by default? -- 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-2438) Validate custom info objects stored with persisted timers, work for scoped deployments

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2438?page=all ] Dimitris Andreadis updated JBAS-2438: ------------------------------------- Component/s: Scheduling/Timers (was: EJB2) > Validate custom info objects stored with persisted timers, work for scoped deployments > -------------------------------------------------------------------------------------- > > Key: JBAS-2438 > URL: http://jira.jboss.com/jira/browse/JBAS-2438 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > Fix For: JBossAS-5.0.0.Beta1, JBossAS-4.0.4RC1 > > -- 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-2438) Validate custom info objects stored with persisted timers, work for scoped deployments

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2438?page=all ] Dimitris Andreadis reopened JBAS-2438: -------------------------------------- > Validate custom info objects stored with persisted timers, work for scoped deployments > -------------------------------------------------------------------------------------- > > Key: JBAS-2438 > URL: http://jira.jboss.com/jira/browse/JBAS-2438 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > Fix For: JBossAS-5.0.0.Beta1, JBossAS-4.0.4RC1 > > -- 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] Created: (JBAS-4278) Timers: PreparedStatement.setNull() should be used for null arguments

by Alexey Loubyansky (JIRA)

Timers: PreparedStatement.setNull() should be used for null arguments --------------------------------------------------------------------- Key: JBAS-4278 URL: http://jira.jboss.com/jira/browse/JBAS-4278 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky When a timer is inserted into the database PreparedStatement.setBytes(i, bytes) is called despite the bytes sometimes may be null. This doesn't work for all databases. -- 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

2
4
0 / 0

[JBoss JIRA] Updated: (JBAS-1310) EJB timer implementation on top of Quartz

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1310?page=all ] Dimitris Andreadis updated JBAS-1310: ------------------------------------- Component/s: Scheduling/Timers (was: EJB2) > EJB timer implementation on top of Quartz > ----------------------------------------- > > Key: JBAS-1310 > URL: http://jira.jboss.com/jira/browse/JBAS-1310 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.1 Final > Reporter: Tim McCune > Assigned To: Dimitris Andreadis > Priority: Minor > Attachments: quartzEJB.tar.gz > > > This is an implementation of the EJB timer API on top of Quartz. I originally posted this about a year ago at http://sourceforge.net/tracker/?func=detail&aid=881597&group_id=22866&ati... and am reposting it here in Jira at Scott's request. See http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863002 for more info. -- 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-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 updated JBAS-1690: ------------------------------------- Component/s: Scheduling/Timers (was: EJB2) > 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] Closed: (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 closed JBAS-1690. ------------------------------------ Resolution: Done > 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] Updated: (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 updated JBAS-1394: ------------------------------------- Component/s: Scheduling/Timers (was: EJB2) > 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-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 closed JBAS-1394. ------------------------------------ Resolution: Done > 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

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