JPPF Issue Tracker
JPPF (jppf)
October 18, 2018
feature_request_tiny.png 09:52  Feature request JPPF-551 - Possibility to setup default execution policy in jppf client config
lolocohen : Issue closed
October 15, 2018
feature_request_tiny.png 10:13  Feature request JPPF-554 - AcceptAll, RejectAll execution policy
zorba128 : Issue created
To simplify execution policy customization it would be nice if there were "AcceptAll" and "RejectAll" execution policies available.
Or simply "empty" but then it is non-obvious if if accepts or rejects everything.
These are useful for eg. disabling parts of rule "and(config, rejectAll)" / "or(config/ acceptAll)".

marcin

bug_report_tiny.png 04:47  Bug report JPPF-553 - Configuration documentation demo still uses HTTP urls
lolocohen : Issue closed
bug_report_tiny.png 04:45  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : Issue closed
bug_report_tiny.png 04:07  Bug report JPPF-553 - Configuration documentation demo still uses HTTP urls
lolocohen : Issue created
In the "Configuration documentation" generator demo, the generated HTML page uses http links for the stylesheet and favicon:


This causes problems when viewed from the JPPF web site: some styles are lost, due to non-safe https-to http links (the browser does not load the stylesheet).
October 13, 2018
enhancement_tiny.png 10:17  Enhancement JPPF-552 - Improve job API to enable tasks as lambdas
lolocohen : Issue created
We propose to add APIs to the JPPFJob class, in order to allow tasks as lambda expressions.

For example, for Callable and Runnable tasks:
public Task addRunnable(JPPFRunnableTask task);

public Task addCallable(JPPFCallable task);
where JPPFRunnableTask is defined as:
public class JPPFRunnableTask extends Runnable, Serializable { }
and JPPFCallable is defined as:
public class JPPFCallable extends Callable, Serializable { }
We need to ensure the tasks are serializable.

We could then add a callable task as a lambda expression, such as:
JPPFJob job = new JPPFJob();
job.addCallable(() -> "hello, world");
October 11, 2018
feature_request_tiny.png 11:23  Feature request JPPF-551 - Possibility to setup default execution policy in jppf client config
zorba128 : Issue created
Provide jppf.properties configuration option to setup default execution policy for newly created jobs, something similar to:
jppf.jobSLA.defaultPolicy = "jppf.policy.xml"
jppf.jobSLA.defaultPolicy.javascript = "return true"
it might support inline policy or loading policy from external file
October 08, 2018
bug_report_tiny.png 15:26  Bug report JPPF-550 - log4j dependency in jppf.commons
zorba128 : Issue created
When trying to use JPPF client library log4j gets sucked into project by transitive dependencies.

Rather than that - jppf client (or - to be more specific - jppf commons) should depend on slf4j api only, leaving decision of which logger binding to use to client application.

So from dependencies below all but first should be removed.


org.slf4j
slf4j-api
1.7.25


org.slf4j
slf4j-log4j12
1.7.25
runtime


log4j
log4j
1.2.15
runtime

If node/driver/web ui/admin ui want to use log4j for logging - it should become their runtime dependency.
October 07, 2018
feature_request_tiny.png 07:50  Feature request JPPF-549 - Asynchonous communication between server and client
lolocohen : Issue created
Currently, the communication between JPPF servers and client is based on a synchronous request/response model. As a consequence, a connection can only handle a single job at a time. This can impair the scalability of JPPF applications.

We propose to switch to an asynchronous model where each connection can handle multiple jobs, removing or mitigating the need for multiple connections.
feature_request_tiny.png 07:35  Feature request JPPF-548 - Drop support for JDK 7 and switch to JDK 8 or later
lolocohen : Issue created
JPPF 6.1 will stop supporting Java 7, whose end-of-life happened a long time ago.
The first step will be to make the compilation, build and tests pass without errors or warnings.
Usage of Java 8 new features and APIs will be either progressive, while writing new code or updating existing code, or systematic in some cases if we determine that the benefits are worth it.

The first difficulty will be to refactor or rewrite the custom doclet code we use for the @exclude tag used in the javadoc.
October 06, 2018
icon_build.png 13:00 JPPF 6.0
New version released
feature_request_tiny.png 10:24  Feature request JPPF-528 - Restructuring of and major improvements to the documentation
lolocohen : Issue closed
September 26, 2018
enhancement_tiny.png 07:06  Enhancement JPPF-547 - Improvements to the handling of jobs classpath
lolocohen : Issue closed
September 17, 2018
feature_request_tiny.png 06:23  Feature request JPPF-546 - Use ScriptScriptDefinition objects wherever JSR 223 compliant scripts are used
lolocohen : Issue closed
September 13, 2018
enhancement_tiny.png 09:04  Enhancement JPPF-547 - Improvements to the handling of jobs classpath
lolocohen : Issue created
The SLA of each JPPF job has a classpath attribute which allows the job to transport a set of jar files to dynamically add to its classloader when it is executed on a node.

There are currently a number of problems with the classpath itself and with the way it is handled by the node:
* classpath elements refer to a "local" and a "remote" location. The semantics here is confusing and we propose to use "source" and "target" locations instead
* there is currently no way to avoid downloading jar files if they already exists on the file system. We should allow a flow to allow it, make it default to false to preserve the existing behavior as a default
* the notion of "force classloader reset" isn't clear ly explained and does not work as documented. This shouid be fixed
September 10, 2018
feature_request_tiny.png 08:09  Feature request JPPF-546 - Use ScriptScriptDefinition objects wherever JSR 223 compliant scripts are used
lolocohen : Issue created
Many JPPF classes use JSR 223-compliant scripts to perform their functionality:
* scripted tasks
* scripted execution policies
* scripted node selectors
* scripted job selectors
* scripted validation function in ClassPathElementImpl
We propose to introduce a new class ScriptDefinition which groups the attributes needed to execute the scripts:
* language: the scripting language, e.g. "javascript", "groovy"
* script: the actual script content as text
* bindings: an optional set of variable bindings made available to the script
* reusableId: an optional identifier for the script which allows reusing the compiled form of the script so as to avoid uncessary recompilation of the script
One of the objectives is to simplify the code that uses scripts, in particular so as to hide the internal mechanism to cache and pool the scripting engines and reusable compiled scripts.
A longer-term objective (targetting JPPF v6.1) is to expose the ScriptDefinition class wherever scripts are used in the public APIs. This will simplify the exposed APIs while increasing flexibility and add consistency with regards to scripting.
September 08, 2018
feature_request_tiny.png 09:07  Feature request JPPF-545 - New sample: JPPF properties documentation generator
lolocohen : Issue closed
feature_request_tiny.png 06:34  Feature request JPPF-545 - New sample: JPPF properties documentation generator
lolocohen : Issue created
We propose to add a new sample which uses the configuration API to generate an HTML page which documents all predefined JPPF configuration properties, grouped by tag.
August 22, 2018
bug_report_tiny.png 19:00  Bug report JPPF-544 - Wrong handling of broadcast job monitoring
lolocohen : Issue closed
August 21, 2018
bug_report_tiny.png 08:28  Bug report JPPF-544 - Wrong handling of broadcast job monitoring
lolocohen : Issue created
From [https://www.jppf.org/forums/index.php/topic,8052.0.html '''this forum post''']

The admin console displays the wrong information about how the dispatches of a broadcast job. It should only dispaly the job itself plus all the nodes on which it is executing.
August 04, 2018
icon_milestone.png 22:19 JPPF 5.2.9
A new milestone has been reached
August 01, 2018
icon_milestone.png 22:00 JPPF 4.0
A new milestone has been reached
task_tiny.png 06:16  Task JPPF-438 - Normalize the package names in common and node modules
lolocohen : Issue closed
July 31, 2018
feature_request_tiny.png 07:58  Feature request JPPF-543 - Enable P2P connectivity between drivers to be used only for failover
lolocohen : Issue closed
task_tiny.png 04:57  Task JPPF-541 - Upgrade third-party libraries and update build accordingly
lolocohen : Issue closed
July 25, 2018
bug_report_tiny.png 08:02  Bug report JPPF-542 - Job dispatch expiration does not work in multi-server topology
lolocohen : Issue closed
feature_request_tiny.png 06:39  Feature request JPPF-543 - Enable P2P connectivity between drivers to be used only for failover
lolocohen : Issue created
We propose to add a configuration property in the JPPF driver, to specify that it should route jobs to other drivers only when its number of nodes is at most a given threshold. For example, if we define:
jppf.peers.load.balance.threshold = 3
then the driver will only route jobs to peer drivers when it has less than 3 nodes. The default value would be infinite (say Integer.MAX_VALUE) to preserve the current default behavior. A value of 0 or less would mean that jobs are never routed to a peer driver.
July 24, 2018
bug_report_tiny.png 08:54  Bug report JPPF-542 - Job dispatch expiration does not work in multi-server topology
lolocohen : Issue created
When setting [https://www.jppf.org/doc/6.0/index.php?title=Job_Service_Level_Agreement#Expiration_of_job_dispatches '''job dispatch expiration'''] in a multi-server toplogy where the serers communicate with each other, if a job is dispatched by driver D1 to its peer driver D2, then upon expiration the job is not cancelled is D2 and remains stuck there unless manually cancelled (via the admin console or via API).
July 22, 2018
task_tiny.png 07:01  Task JPPF-541 - Upgrade third-party libraries and update build accordingly
lolocohen : Issue created
It's as good a time as ever to upgrade our third-party libs and try to update the build to avoid having the libraries in the SCM
July 21, 2018
icon_milestone.png 18:43 JPPF 5.2.2
A new milestone has been reached
icon_milestone.png 18:07 JPPF 5.1.6
A new milestone has been reached
icon_milestone.png 12:23 JPPF 5.2.5
A new milestone has been reached
icon_milestone.png 11:22 JPPF 5.2.1
A new milestone has been reached
icon_milestone.png 10:59 JPPF 2.5.5
A new milestone has been reached
icon_milestone.png 10:33 JPPF 5.1.2
A new milestone has been reached
icon_milestone.png 10:09 JPPF 5.1.7
A new milestone has been reached
icon_milestone.png 09:46 JPPF 5.2.7
A new milestone has been reached
icon_milestone.png 09:36 JPPF 4.1
A new milestone has been reached
icon_milestone.png 09:26 JPPF 5.2.3
A new milestone has been reached
icon_milestone.png 09:11 JPPF 5.1.4
A new milestone has been reached
Show moreaction_add_small.png