@kenglover: Thanks, but i'm using Quartz not EJB-Timers. I'm sorry, should have told it.
@pete.muir: I tried the approach by scheduling an asynchronous task at startup, which performs some operations and gives the control for the next operation to a new asynchronous task. This works fine for some time, but it always ends up in a java.lang.StackOverflowError. | Caused by: java.lang.StackOverflowError | at java.lang.ClassLoader.findBootstrapClass(Native Method) | at java.lang.ClassLoader.findBootstrapClass0(ClassLoader.java:891) | at java.lang.ClassLoader.loadClass(ClassLoader.java:301) | at java.lang.ClassLoader.loadClass(ClassLoader.java:299) | at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) | at java.lang.ClassLoader.loadClass(ClassLoader.java:299) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) | at org.apache.log4j.spi.ThrowableInformation.getThrowableStrRep(ThrowableInformation.java:58) | at org.apache.log4j.spi.LoggingEvent.getThrowableStrRep(LoggingEvent.java:342) | at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:304) | at org.apache.log4j.RollingFileAppender.subAppend(RollingFileAppender.java:236) | at org.apache.log4j.WriterAppender.append(WriterAppender.java:159) | at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230) | at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65) | at org.apache.log4j.Category.callAppenders(Category.java:203) | at org.apache.log4j.Category.forcedLog(Category.java:388) | at org.apache.log4j.Category.log(Category.java:853) | at org.jboss.seam.log.Log4JProvider.error(Log4JProvider.java:57) | at org.jboss.seam.log.LogImpl.error(LogImpl.java:121) | The new instance is created by calling. | (Task) Component.getInstance(Task.NAME, ScopeType.STATELESS, true); | I'm a little frustrated about this .. I'd like to poll the database for new messages (they are stored in a table) and perform some tasks/checks with it to get it into another sink (another table). It's a system where n foreign processes send messages via http/POST. They get serialized into the first table and are processed later in a synchron recurring way by the Task. (because reordering has to be done, etc.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092008#4092008 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092008 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user