That's because non-container managed threads are not supported by the
EE spec. In GF 2 your only supported choice is and EJB Timer.
On Nov 28, 2009, at 10:16 PM, Cam Bazz <cambazz_at_gmail.com> wrote:
> Hello,
>
> My experience is that whenever you put a thread or a timer inside
> glassfish, it causes problems. Currently I am using cronjobs
> triggering a servlet, and I am waiting for the new @Timer in GF3 GA.
>
> Best,
> -C.B.
>
> On Sat, Nov 28, 2009 at 10:07 PM, <glassfish_at_javadesktop.org> wrote:
>> So back to my original question. If you are not using EJBs, and
>> hence no EJBContext, what is the best practice for getting timer
>> services?
>>
>> Should I just create a Thread or a java.util.Timer in a JSF-managed
>> application-scope bean, or is there some other service available
>> via the Application object that should be used?
>> [Message sent by forum member 'alan94539' ]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=373677
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>