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
feature_request_tiny.png 09:52  Feature request JPPF-551 - Possibility to setup default execution policy in jppf client config
lolocohen : Status changed: New ⇒ Closed
feature_request_tiny.png 09:52  Feature request JPPF-551 - Possibility to setup default execution policy in jppf client config
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
feature_request_tiny.png 09:52  Feature request JPPF-551 - Possibility to setup default execution policy in jppf client config
lolocohen : lolo4j ⇒ Not being worked on
October 16, 2018
feature_request_tiny.png 07:32  Feature request JPPF-554 - AcceptAll, RejectAll execution policy
lolocohen : Assignee changed: lolo4j
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:47  Bug report JPPF-553 - Configuration documentation demo still uses HTTP urls
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 04:47  Bug report JPPF-553 - Configuration documentation demo still uses HTTP urls
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 04:47  Bug report JPPF-553 - Configuration documentation demo still uses HTTP urls
lolocohen : lolo4j ⇒ Not being worked on
bug_report_tiny.png 04:45  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : Issue closed
bug_report_tiny.png 04:45  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 04:45  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 04:45  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : lolo4j ⇒ Not being worked on
bug_report_tiny.png 04:08  Bug report JPPF-553 - Configuration documentation demo still uses HTTP urls
lolocohen : Description updated
bug_report_tiny.png 04:08  Bug report JPPF-553 - Configuration documentation demo still uses HTTP urls
lolocohen : Assignee changed: lolo4j
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).
bug_report_tiny.png 04:07  Bug report JPPF-553 - Configuration documentation demo still uses HTTP urls
lolocohen : 'JPPF 6.0' added
October 14, 2018
feature_request_tiny.png 07:45  Feature request JPPF-551 - Possibility to setup default execution policy in jppf client config
lolocohen : Description updated
feature_request_tiny.png 07:45  Feature request JPPF-551 - Possibility to setup default execution policy in jppf client config
lolocohen : Assignee changed: lolo4j
October 13, 2018
enhancement_tiny.png 10:20  Enhancement JPPF-552 - Improve job API to enable tasks as lambdas
lolocohen : Description updated
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");
enhancement_tiny.png 10:17  Enhancement JPPF-552 - Improve job API to enable tasks as lambdas
lolocohen : 'JPPF trunk' added
October 11, 2018
feature_request_tiny.png 13:02  Feature request JPPF-551 - Possibility to setup default execution policy in jppf client config
zorba128 : Description updated
feature_request_tiny.png 11:24  Feature request JPPF-551 - Possibility to setup default execution policy in jppf client config
zorba128 : Description updated
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 09, 2018
feature_request_tiny.png 08:23  Feature request JPPF-548 - Drop support for JDK 7 and switch to JDK 8 or later
lolocohen : Description updated
feature_request_tiny.png 07:41  Feature request JPPF-25 - Remove the limitation on maximum concurrent jobs
lolocohen : Target milestone changed: Not determined ⇒ Irrelevant
feature_request_tiny.png 07:41  Feature request JPPF-235 - Task SLA
lolocohen : Target milestone changed: Not determined ⇒ Irrelevant
bug_report_tiny.png 07:41  Bug report JPPF-228 - OutOfMemoryException with many nodes
lolocohen : Target milestone changed: Not determined ⇒ Irrelevant
bug_report_tiny.png 07:29  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : Severity changed: Not determined ⇒ Low
bug_report_tiny.png 07:29  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : Reproducability changed: Not determined ⇒ Always
bug_report_tiny.png 07:27  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : Category changed: Not determined ⇒ Build
bug_report_tiny.png 07:27  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : Assignee changed: lolo4j
bug_report_tiny.png 07:27  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : Target milestone changed: JPPF 6.1 ⇒ JPF 6.0.1
bug_report_tiny.png 07:27  Bug report JPPF-550 - log4j dependency in jppf.commons
lolocohen : Description updated
October 08, 2018
bug_report_tiny.png 15:26  Bug report JPPF-550 - log4j dependency in jppf.commons
zorba128 : 'JPPF 6.0' added
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
enhancement_tiny.png 07:52  Enhancement JPPF-433 - Add missing value snapshots to the server statistics
lolocohen : Description updated
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.
October 06, 2018
icon_build.png 13:00 JPPF 6.0
New version released
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
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
icon_milestone.png 08:23 JPPF 5.2.6
A new milestone has been reached
icon_milestone.png 08:12 JPPF 5.2.4
A new milestone has been reached
icon_milestone.png 07:35 JPPF 5.1.3
A new milestone has been reached
icon_milestone.png 07:11 JPPF 5.1.5
A new milestone has been reached
icon_milestone.png 07:04 JPPF 5.2.8
A new milestone has been reached
icon_milestone.png 06:43 JPPF 4.2
A new milestone has been reached
Show moreaction_add_small.png