[EJB 3.0] - TimerService: Canceling Timer in stop()- of @Service
by periklis
Hi,
i am writing on a small service based on the @Service+@Management Features of EJB3. In this service i create via TimerService a new Timer in the start()-Method, which waits 10 minutes and invokes the @Timeout-Method every one hour. When i undeploy my service i invoke the timer cancelation in my Service's stop()-Method.
As far as i understood, timers are getting persisted in a secondary storage, so that they are available even after a system crash. Hence i should expect, that when i cancel a timer this timer should also get removed also from the secondary storage. In my case they aren't getting removed.
I am seeing this phenomenon in the jmx-console. During undeployment the timers listed in the section service=EJBTimerService per listTimers() are getting canceled and removed, but this is not the case in the section persistencePolicy=database,service=EJBTimerService.
My system is based on:
JBoss 4.0.5 GA
EJB3+RC9+patch1
MacOSX 10.4.8 with actual JVM 1.5
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006402#4006402
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006402
19 years, 2 months
[Installation, Configuration & Deployment] - Alternative for using jvm-arg
by newgro
Hello *,
i'm trying to solve a little problem. I already asked the goo... but i didnt found a proper solution.
I have two applications deployed in an own server instance (default and ports-01). The clients get their library-updates from a folder located near the server. This folder is now accessible by a jvm-arg. Everything works fine so long.
But i try to merge both applications into one server. And so im looking for a possibility to assign a different value for the two library-update-folders for the application.
--- myJBossInstallations
|--- appl-1
| |--- bin
| |--- lib
| |--- client
| |--- docs
| |--- client-update-folder
| |--- server
| |--- default
|--- appl-2
| |--- bin
| |--- lib
| |--- client
| |--- docs
| |--- client-update-folder
| |--- server
| |--- ports-01
Now the servers are started by
run.sh -c default -DmyArg.to.client.update.folder=../ext ...
and
run.sh -c ports-01 -DmyArg.to.client.update.folder=../ext ...
The folder is not to be configurable. Its enough if its set at startup.
Can you please give me tip? I prefer a simple solution :-)
I hope i described the problem clearly. If not please ask.
Thanks 4 help
Per
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006397#4006397
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006397
19 years, 2 months