JPPF, java, parallel computing, distributed computing, grid computing, parallel, distributed, cluster, grid, cloud, open source, android, .net

The open source
grid computing

 Home   About   Features   Download   Documentation   On Github   Forums 

3/6/2019 JPPF 6.1-beta release notes


Download - Documentation - Javadoc - previous JPPF 6.1 alpha 2 release

New features highlights

JVM health monitoring enhancements

  • new monitored data elements were added: peak threads count, total started threads count and JVM uptime
  • custom value converters can now be associated with each monitored datum, to enable customized rendering of their value

Preference execution policy

The new preference policy attribute, in the job SLA, defines an ordered set of execution policies, such that eligble channels or nodes will be chosen from those that satisfy the policy with the foremost position.

New convenience execution policies

A new set of execution policy rules were added, to simplify policies with cumbersome rules. For instance, new IsMasterNode() conveniently replaces new Equals("jppf.node.provisioning.master", true).

See: IsMasterNode - IsSlaveNode - IsLocalChannel - IsPeerDriver

Node provisioning notifications

The node provisioning service of each master node now emits JMX notifications each time a slave node is started or stopped.

New MavenLocation class

MavenLocation is a Location implementation which allows downloading artifacts from any maven repository. COnsequently, MavenCentralLocation is now a specialized subclass pointing to the Maven Central repository.

Deprecation of the "blocking" job attribute

A job should be submittable either synchronously or asynchronously, regardless of its state and at the user's choice at the time of submission. To this effect, the job's "blocking" attribute was deprecated. So was the "JPPFClient.submitJob()" method, which is now replaced with "JPPFClient.submit()" and "JPPFClient.submitAsync()".

Feature removals

Following the move of JPPF to Java 8, we deeply regret to announce the removal of two integration features:
  • .Net bridge: the jni4net project, on which the .Net bridge is based, is no longer actively maintained and does not support some of the Java 8 language constructs
  • Android port: we no longer have the bandwidth to maintain the Android node integration. In particular: porting to a version of Android which supports Java 8 language features.

All implemented issues




JPPF Copyright © 2005-2020 Get JPPF at Fast, secure and Free Open Source software downloads