Print

[bd]

Is there any reason why a JPPFTask cannot|should not act as a client and submit its own JPPFTasks?  I'm going to start experimenting with this arrangement, but if there's something obviously wrong with doing this, I'd appreciated hearing about it.

thanks

bd

[lolo]

Hello bd,

The biggest problem you will have is about class loading.
In effect, the application classes that you are executing in your tasks are physically deployed on the client side, and downloaded by the node when needed.

However, if you submit some of these tasks from a node, which is a client from this point of view, then the 2nd node, executing these new tasks, will be unable to find your classes in the 1st node's class path, unless your application classes are also deployed to the first node's class path.

So basically, you will need to add the following to the first node's class path:

• jppf-common.jar
• jppf-client.jar
• your application classes and jar files

Another thing you should be careful about is where you submit these new tasks, and that nodes will effectively be available to execute them.

I hope this helps,
-Laurent

[bd]

Thanks, that helps a great deal.  I'd completely forgotten about the class server.