Print

[kidmtt94]

Hi admin,

I set broadcast for my job like following code:

JPPFJob job = new JPPFJob();
job.setBlocking(false);
job.getSLA().setCancelUponClientDisconnect(false);
job.getSLA().setBroadcastJob(isBroadCast);

After submitting job, it often can not dispatch jobs to nodes, just sometimes work correctly (it work correctly after restart server). But on UI i appear some strange thing. I had attached image for this problems.
Please help me to review this.
I make sure use all default configuration
Thanks

[lolo]

Hello,

The behavior you observe is registered as a bug: JPPF-544 Wrong handling of broadcast job monitoring. We are working on it and will provide a patch when it is fixed.

Regarding the fact that the job is not dispatched to the nodes, could you please have a look a the server and nodes logs and let us know if there is any relavant exception or error there. In particular, there may be one or more ClassNotFoundException in the nodes. This could be due to the fact that your job is non-blocking and that you may be closing the client before the job is dispatched to the nodes, thus preventing the node distributed class loader from working.

To check this, you can also try to set the job as blocking and verify if it actually gets dispatched to the nodes.

Thanks,
-Laurent

[kidmtt94]

Hi Laurent,
I don't need to wait result of jobs, because we just submit and kill that process submitting. So broadcast don't work normally.
Do u have any solution for us ? 

[lolo]

Hi,

The problem may be due to the fact that the client process is killed too soon and the JPPF client doesn't have time to send the job to the server.
If this is the problem, then a possible solution is to wait until the job is dispatched to the server, and then kill the client process. An easy way to do this, is to use a job listener associated with a synchronization aid such as a CountDownLatch:

Code: [Select]

JPPFJob job = new JPPFJob();
job.setName("broadcast");
job.add(new MyTask(10_000L));
job.setBlocking(false);
job.getSLA().setBroadcastJob(true);
job.getSLA().setCancelUponClientDisconnect(false);
final CountDownLatch latch = new CountDownLatch(1);
// a job listener that notifies when the job is dispatched to the server
job.addJobListener(new JobListenerAdapter() {
  @Override
  public void jobDispatched(JobEvent event) {
    latch.countDown();
  }
});
client.submitJob(job);
// wait until the job has been dispatched
latch.await();
// kill this client
System.exit(0);
Could you please try this andf let us know if that fixes the problem?

Additionally, I have fixed the issue with the display of broadcast jobs in the admin console (JPPF-544) and the fix is now available in patch 02 for JPPF 5.2.9.

-Laurent

[kidmtt94]

Your solution is ok. I had tried it .
Thanks for your hard-working.
But it still has one problem. After you kill process, and then you create new process to submit with broadcast, if a job of old process has done executed, I don't know why all jobs of old and new process is cancel
So I decided to choose solution don't kill process and setBlocking(true).

Many thanks Laurent.