ejb - Deploying Java @Schedule with Wildfly 8.1.0 Final -


i trying test @schedule annotation following code:

import javax.ejb.schedule; import javax.ejb.singleton; import javax.ejb.startup;  @singleton @startup public class timertest {      public timertest() {      }      @schedule(second = "*", minute = "*", hour = "*")     public void sayhello() {         system.out.println("hello");     }  } 

however, when deploy standalone instance of wildfly 8.1.0 (final) getting following error messages in logs:

2014-09-23 08:38:03,076 error [org.jboss.msc.service.fail] (msc service thread 1-4) msc000001: failed start service jboss.deployment.unit."test-server.war".component.timertest.ejb3.timerservice: org.jboss.msc.service.startexception in service jboss.deployment.unit."test-server.war".component.timertest.ejb3.timerservice: failed start service     @ org.jboss.msc.service.servicecontrollerimpl$starttask.run(servicecontrollerimpl.java:1904) [jboss-msc-1.2.2.final.jar:1.2.2.final]     @ java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1145) [rt.jar:1.7.0_25]     @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:615) [rt.jar:1.7.0_25]     @ java.lang.thread.run(thread.java:724) [rt.jar:1.7.0_25] caused by: java.lang.nullpointerexception     @ org.jboss.as.ejb3.timerservice.timerserviceimpl.doestimeoutmethodmatch(timerserviceimpl.java:959)     @ org.jboss.as.ejb3.timerservice.timerserviceimpl.restoretimers(timerserviceimpl.java:710)     @ org.jboss.as.ejb3.timerservice.timerserviceimpl.start(timerserviceimpl.java:202)     @ org.jboss.msc.service.servicecontrollerimpl$starttask.startservice(servicecontrollerimpl.java:1948) [jboss-msc-1.2.2.final.jar:1.2.2.final]     @ org.jboss.msc.service.servicecontrollerimpl$starttask.run(servicecontrollerimpl.java:1881) [jboss-msc-1.2.2.final.jar:1.2.2.final]     ... 3 more  2014-09-23 08:38:07,098 error [org.jboss.as.controller.management-operation] (controller boot thread) jbas014613: operation ("deploy") failed - address: ([("deployment" => "test-server.war")]) - failure description: {"jbas014671: failed services" => {"jboss.deployment.unit.\"test-server.war\".component.timertest.ejb3.timerservice" => "org.jboss.msc.service.startexception in service jboss.deployment.unit.\"test-server.war\".component.timertest.ejb3.timerservice: failed start service     caused by: java.lang.nullpointerexception"}}  2014-09-23 08:38:07,145 info  [org.jboss.as.controller] (controller boot thread) jbas014774: service status report jbas014777:   services failed start:      service jboss.deployment.unit."test-server.war".component.timertest.ejb3.timerservice: org.jboss.msc.service.startexception in service jboss.deployment.unit."test-server.war".component.timertest.ejb3.timerservice: failed start service  jbas014777:   services failed start:      service jboss.deployment.unit."test-server.war".component.timertest.ejb3.timerservice 

any ideas causing this?

i've seen before. in wildfly directory, asuming did standalone deployment, there directory standalone/data/timer-service-data. there old timerservice data in directory. shut down server, delete data , try again.

this data test run did not complete before server shut down. remember timerservice persistent. if there pending tasks when shut down server, try pick tasks first. if updated war timer processes not match processes in war anymore.


Comments

Popular posts from this blog

php - Submit Form Data without Reloading page -

linux - Rails running on virtual machine in Windows -

php - $params->set Array between square bracket -