JPPF 3.1 brings a new security layer by performing all network communications through SSL/TLS, providing data encryption, data integrity and certificate-based authentication. Switching from plain to secure connections is as easy as toggling a single configuration flag. In this new context, a JPPF driver can serve both plain and secure connections, whereas clients and nodes attach via either. Secure communication has been implemented on top of all connections used by JPPF: client to server, node to server, server to server and JMX remote connectors.

Management and monitoring

A new graph view of the grid topology has been added to the administration console.
A new management API was added to test execution policies against the current grid state.
Jobs can now be cancelled directly from a standalone JPPF client or from the J2EE connector.

Executor services

Job SLAs and metadata, along with task timeout and cancel handlers, can now be dynamically configured for tasks and jobs submitted from a JPPFExecutorService


The load balancing between local and remote execution is now fully configurable in the client. The same algorithms and configuration parameters as for the server are available.


A new node extension enables switching the node execution model to a local fork/join model, using the JDK 7 APIs.

JPPF Links:

Web Site - Downloads - Documentation - User forums