|
[ View full size screenshot ] |
| Version | Date Released | Status | Release Notes |
| 3.1 Beta | Mar 21, 2012 | New Release | · 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 application 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. Class loading |
| 3.0 | Feb 1, 2012 | New Release | · 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 application 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. Class loading |
| 3.0 Beta 2 | Jan 15, 2012 | New Release | · Driver doesn't recognize that client connection was closed http://sourceforge.net/tracker/?func=detail&aid=3438303&group_id=135654&atid=733518 JPPFExecutorService.submit(Callable) doesn't handle JPPFTask http://sourceforge.net/tracker/?func=detail&aid=3442606&group_id=135654&atid=733518 · Broadcasting service does not recover from network breakdown http://sourceforge.net/tracker/?func=detail&aid=3454260&group_id=135654&atid=733518 · Broadcast job not executed when local execution is enabled http://sourceforge.net/tracker/?func=detail&aid=3398676&group_id=135654&atid=733518 |
| 3.0 Beta 1 | Nov 29, 2011 | New Release | Bugs fixes: · Use of direct buffers causes mem leak and perf hotspot Mishandling of file permissions in ResourceCache · JPPFTaskFuture.get(time, unit) does not wait · Empty jobs are not handled properly · Node failover isn't working as expected JMXDriverConnectionWrapper.getAllJobIds() throws Exception |
| 2.5.4 | Nov 15, 2011 | New Release | Bugs fixes: · Use of direct buffers causes mem leak and perf hotspot Mishandling of file permissions in ResourceCache · JPPFTaskFuture.get(time, unit) does not wait · Empty jobs are not handled properly · Node failover isn't working as expected JMXDriverConnectionWrapper.getAllJobIds() throws Exception |