I know that EJB3 Timer is persistent but is-it normal that JBoss add new
timeout in its database each times the application is deployed?
I haven't the problem with Glassfish.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4111652#4111652
Reply to the post :
@damianharvey:
Sorry, you had right. The calls were due to EJBTimer timeout's that was saved
by JBoss during previous deployment. Is it a bug of JBoss?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4111233#4111233
Reply to the post :
No, I'm not using hot deploy. Anyway, I've the problem both with Quartz and
TimerService.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110905#4110905
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110905
I've a Stateless local Session Bean which defines an asynchronous method which
is launched at startup by an observer method.
Everything works fine except that the method is triggered multiple times
simultaneously. Any idea why?
Neither the TimeService implementation nor the Quartz
Hello,
I'm using Seam 2.0GA.
I've a rich:dataTable that displays the values of a DataModel outjected from a
search component. Each row defines a s:link with an action that triggers the
call to a select method of an info component throuh a pageflow. The two
components are in a the same
