1/31/2012 JPPF 3.0 release notes
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
Administration console, management and monitoring improvements
All implemented feature requests
Admin console and management