users@glassfish.java.net

Re: access glassfish thread pool

From: Lachezar Dobrev <l.dobrev_at_gmail.com>
Date: Fri, 28 Sep 2012 14:36:10 +0300

  Well... You're not supposed to create threads.
  Although I am still using Quartz and ActiveMQ in my applications
(both have their own Thread pools).

  Maybe you should consider re-factoring into scheduled tasks (for
periodic jobs), and JMS for asynchronous processing.

  @Schedule:
  http://docs.oracle.com/javaee/6/tutorial/doc/bnboy.html

  @Asynchronous:
  http://docs.oracle.com/javaee/6/tutorial/doc/gkkqg.html

  P.S. Apologies for resending.
  I am still not sure how the forums-email integration works.

2012/9/28 Nicolas Beck <Nicolas-Beck_at_gmx.de>:
> I want to use the glassfish Threadpool since creating own threads within my
> jee application is not avoidable. Since glassfish API changed it is not
> possible to use spring frameworks GlassFishWorkManagerTaskExecutor any more
> for this
> [http://forum.springsource.org/showthread.php?85272-GlassFishWorkManagerTaskExecutor-spring-and-glassfish-v3-exception]
> But there must be a way to have access to the thread pool. I can't
> understand why this is so restrictive?