JPPF 3.0 Released
JPPF makes it easy to parallelize computationally intensive tasks and execute them on a Grid
What's new in JPPF 3.0
Simplification and improvement of the configuration
- Servers, nodes and clients now only require a single TCP port instead of 3 for executing jobs.
- Adoption of the JMXMP remote connector allows JMX-based management to use a single port instead of 2.
- Server discovery and manual configuration can now be mixed for clients and servers in P2P.
Improved recovery and failover on the client side
- A persistence manager allows job states to be recovered after an applicationr crash.
The persistence manager is an API which allows storing the states of the jobs on the fly and recover them after an application crash or restart. A default implementation is provided and demonstrated in a new sample.
- Upon recovery of a client connection to the server, only the un-executed tasks in each job are resubmitted
- Applications can now receive notifications when a job is sent to the server, and when the final results are returned.
- The distributed class loading mechanism is now fully documented.
- New extensions enable the optimization of the class loading overhead at node startup, along with the ability to update the classpath at runtime.
- New class loader delegation model enables faster class loading.
- A new sample illustrates how to automate the management of remote library repositories on the grid nodes.
New customizations and extension points
- Ability to receive node connection events in the server.
- Node initialization hooks enable sophisticated strategies for failover and recovery of broken server connections.
- The node life cycle listener extension can now be deployed both at the server and node level.
Administration console, management and monitoring improvements
- The server statistics panel now displays jobs data.
- The priority of each job can now be dynamically and remotely updated.
- The driver system information can now be displayed in the admin console as for the nodes
- The number of idle nodes is now monitored in the server statistics
- How to receive notifications of nodes connecting and disconnecting on the server
- Job recovery after an application crash
- Using a node initialization hook to implement a sophisticated failover mechanism
- Using the JPPF class loading extensions to automate the deployment and management of application libraries in the nodes at runtime
JPPF Links:- Web Site
- User forums
- SourceForge.net project site
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)