特定の時間にキューにアクセスするためのメッセージドリブンBeanをスケジュールしますか？

Question

1）特定の時刻にのみキューにアクセスするようにメッセージ駆動型Beanをスケジュールできますか？

たとえば、ユーザーには、9 am-5pmと5 pm-10pmの2つの連絡先オプションがあります。私は午前9時から午後5時までと午後3時から午後10時まで有効な2つのMDBを持っていたいと思います。

両方のキューには1日を通してメッセージが送信されますが、特定の時刻にのみ処理したいと思います。

理想的には@スケジュールは動作しますが、残念ながらそれはありません。

Glassfish 3.1.2とActiveMQ 5.5.1を使用していますが、実装に関する具体的な質問ではありません。

編集デプロイメントのエラーを取得する1

コード

@MessageDriven(
    activationConfig = { 
     @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), 
     @ActivationConfigProperty(propertyName = "destination", propertyValue = "jms/queue/amqmsg") 
}) 
public class ExampleMessageBean implements MessageListener { 

@Schedule(second="*", minute="*", hour="9-17", persistent = false) 
public void onMessage(Message message) { 
    try { 
     System.out.println("We've received a message: " + message.getJMSMessageID()); 

     System.out.println("\n\n Message\n\n" + message); 

    } catch (JMSException e) { 
     e.printStackTrace(); 
    } 
} 

}

。このように@Scheduleを使用することはできないと思います。誰でも確認できますか？

SEVERE: Exception while invoking class org.glassfish.ejb.startup.EjbDeployer load method java.lang.RuntimeException: EJB Container initialization error 
at org.glassfish.ejb.startup.EjbApplication.loadContainers(EjbApplication.java:242) 
at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:299) 
at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:105) 
at org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:186) 
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:264) 
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:460) 
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240) 
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259) 
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461) 
at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212) 
at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179) 
at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117) 
at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354) 
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195) 
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849) 
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746) 
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045) 
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228) 
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) 
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) 
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) 
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) 
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) 
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) 
at com.sun.grizzly.ContextTask.run(ContextTask.java:71) 
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) 
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) 
at java.lang.Thread.run(Thread.java:662) 
Caused by: javax.ejb.EJBException: Invalid @Timeout or @Schedule signature for: public void com.name.mdb.ExampleMessageBean.onMessage(javax.jms.Message) @Timeout or @Schedule method must return void and be a no-arg method or take a single javax.ejb.Timer param 
at com.sun.ejb.containers.BaseContainer.processEjbTimeoutMethod(BaseContainer.java:2219) 
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:743) 
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:142) 
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:121) 
at org.glassfish.ejb.startup.EjbApplication.loadContainers(EjbApplication.java:230) 
... 33 more 

    SEVERE: Exception while loading the app 
    INFO: No timers to be deleted for id: 87558812344647680 
    SEVERE: Exception while loading the app : EJB Container initialization error 
    javax.ejb.EJBException: Invalid @Timeout or @Schedule signature for: public void com.test.mdb.ExampleMessageBean.onMessage(javax.jms.Message) @Timeout or @Schedule method must return void and be a no-arg method or take a single javax.ejb.Timer param 
at com.sun.ejb.containers.BaseContainer.processEjbTimeoutMethod(BaseContainer.java:2219) 
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:743) 
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:142) 
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:121) 
at org.glassfish.ejb.startup.EjbApplication.loadContainers(EjbApplication.java:230) 
at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:299) 
at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:105) 
at org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:186) 
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:264) 
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:460) 
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240) 
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259) 
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461) 
at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212) 
at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179) 
at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117) 
at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354) 
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195) 
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849) 
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746) 
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045) 
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228) 
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) 
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) 
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) 
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) 
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) 
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) 
at com.sun.grizzly.ContextTask.run(ContextTask.java:71) 
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) 
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) 
at java.lang.Thread.run(Thread.java:662) 

Answer 1

スケジュールはメッセージparamを持つあなたのメソッドで呼び出されているようです。どのようにこの議論を知るだろうか。

アイテムをキューに追加して別々に処理するだけです。

@MessageDriven(
    activationConfig = { 
     @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), 
     @ActivationConfigProperty(propertyName = "destination", propertyValue = "jms/queue/amqmsg") 
}) 
public class ExampleMessageBean implements MessageListener { 

private BlockingQueue<Message> queue = new ArrayBlockingQueue<Message>() ; 

@Schedule(second="*", minute="*", hour="9-17", persistent = false) 
public void process() 
{ 
    //process queue here. 
} 
public void onMessage(Message message) { 
    try { 
     System.out.println("We've received a message: " + message.getJMSMessageID()); 
     queue.add(message); 
     System.out.println("\n\n Message\n\n" + message); 

    } catch (JMSException e) { 
     e.printStackTrace(); 
    } 
}