last time we got it it was cause the schedule was not undeployed correctly on redeployment and then the BeanContext instance was wrong for scheduled tasks(no link with this property).
If you have a sample maven project we can test against it would ease it since it was fixed months ago Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-07-21 13:14 GMT+02:00 Andy Gumbrecht <[email protected]>: > Bjorn, > > We actually check for and explicitly set this property with the default to > skip. > > System.setProperty("org.terracotta.quartz.skipUpdateCheck" > , System.getProperty("org.terracotta.quartz.skipUpdateCheck", > "true")); > > The 'only' thing I can imagine is that the value is not being read as > 'true' - maybe a typo or codepage issue (check the file encoding of the > system.properties file). > The actual update check is in Quartz and it uses a host name that needs to > be DNS resolved, and then actually polls their server (which can take ages > sometimes). > > It uses this URL 'http://www.terracotta.org/kit/reflector?kitID=quartz&; > pageID=update.properties', so just out of interest can you try and browse > that on the machine that hangs? > > Thanks, > > Andy. > > PS. I hope you're not using TomEE to 'spam spam spam' people :-P > > > On 21/07/2014 12:53, Bjorn Danielsson wrote: > >> Thanks Andy. Here is the code I used: >> >> package foo; >> >> import javax.ejb.*; >> import java.util.logging.Logger; >> >> @Singleton >> @Lock(LockType.READ) >> @Startup >> public class BugBean { >> static final Logger logger = Logger.getLogger(BugBean. >> class.getName()); >> >> @Lock(LockType.WRITE) >> @Schedule(second="*/5", minute="*", hour="*") >> public void spam() { >> logger.info("Spam spam spam"); >> } >> >> } >> >> > -- > Andy Gumbrecht > > http://www.tomitribe.com > [email protected] > https://twitter.com/AndyGeeDe > > TomEE treibt Tomitribe! | http://tomee.apache.org > >
