JPPF Issue Tracker
JPPF (jppf)
March 14, 2020
enhancement_tiny.png 11:06  Enhancement JPPF-626 - Implement a NotEqual execution policy
lolocohen : Issue created
Currently we can do new Equal(...).not(). We propose to add a less cumbersome format such as new NotEqual(...)
March 07, 2020
feature_request_tiny.png 18:52  Feature request JPPF-622 - New sample: grid failover
lolocohen : Issue closed
March 06, 2020
feature_request_tiny.png 08:38  Feature request JPPF-625 - Allow nodes to connect to multiple drivers
lolocohen : Issue created
Now that nodes can process multiple jobs concurrently, it seems the next logical step is to allow these jobs to come from any number of JPPF drivers. In particular, this will address the problem of the driver being a single point of failure more efficiently.

This will impact manay areas of the code, including:
* processing within the node (of course)
* handling of connection/disconnection events in the node (node connection strategy, when should a node reconnect)
* should we allow the driver connections to be prioritized, as in the client, and permit a failover hierarchy of drivers?
* grid topology monitoring: the topology will no longer be a tree. In particular, the nodes will have multiple drivers as parents, which is a significanty change in the monitoring object model
* how iwll it affect load-balancing?
February 26, 2020
feature_request_tiny.png 21:15  Feature request JPPF-624 - Task dependency - depend on result of dependent task
wimvc : Issue created
JPPF 6.2 introduced the concept of dependencies between Tasks and also between Jobs. It would be nice if this feature could be expanded with Tasks/Jobs having access to the result-value of the tasks/jobs it depends on.
February 23, 2020
feature_request_tiny.png 05:39  Feature request JPPF-619 - Ability to force a node to reconnect without restarting
lolocohen : Issue closed
February 20, 2020
feature_request_tiny.png 08:00  Feature request JPPF-620 - Ability to disable stdout output in the client
lolocohen : Issue closed
task_tiny.png 07:35  Task JPPF-623 - Refresh of the configuration properties reference
lolocohen : Issue created
Just a reminder to regenerate the reference doc for the configuration properties and update the offline and online docs.
feature_request_tiny.png 07:29  Feature request JPPF-622 - New sample: grid failover
lolocohen : Issue created
We propose to implement a sample to demonstrate how to avoid JPPF drivers as single points of failure, with the following aspects:
* multiple drivers, not connected to each other (i.e. in pure failover mode). Each driver has a priority, the nodes connect only to the driver that is running with the highest priority
* a specific [https://www.jppf.org/doc/6.3/index.php?title=Defining_the_node_connection_strategy node connection strategy] for all the nodes, which allows the nodes to connect the driver that is up with highest priority
* a JPPF client as a controller, to detect when a driver with the highest priority goes back up, and force the nodes to reconnect to it
February 18, 2020
enhancement_tiny.png 06:08  Enhancement JPPF-621 - Client local executor as a JPPFClientConnection
lolocohen : Issue closed
enhancement_tiny.png 05:18  Enhancement JPPF-621 - Client local executor as a JPPFClientConnection
lolocohen : Issue created
We propose to refactor the class representing the local executor in a JPPFClient, such that it implements the [https://www.jppf.org/javadoc/6.3/org/jppf/client/JPPFClientConnection.html JPPFClientConnection] interface. This will, in particular, allow a clearer semantics for the connection status events. Consequently, JPPFClientConnection should allow to distinguish between local and remote connections (with a isLocal() method for instance).
February 16, 2020
feature_request_tiny.png 08:52  Feature request JPPF-620 - Ability to disable stdout output in the client
lolocohen : Issue created
Whenever a JPPFClient attempts to connect to a driver, it will print out the status of the connection attempt to stdout. This can generate a lot of output whe'n there are many connections, and it may be desirable to disable the output. It will still be printed to the log.
feature_request_tiny.png 08:24  Feature request JPPF-619 - Ability to force a node to reconnect without restarting
lolocohen : Issue created
Currently, a node will reconnect to a driver only if the driver connection is broken (e.g. when the driver is terminated or there are network problems) or when the node is restarted.

We propose to add a management function to force a node to disconnect, then reconnect, without having to restart.
February 13, 2020
enhancement_tiny.png 09:35  Enhancement JPPF-617 - Add one or more unit test for executing a job from an executing task
lolocohen : Issue closed
bug_report_tiny.png 09:35  Bug report JPPF-618 - Forwarding notification listeners are not registered properly
lolocohen : Issue closed
bug_report_tiny.png 08:57  Bug report JPPF-618 - Forwarding notification listeners are not registered properly
lolocohen : Issue created
Due to an error in the code, when registering multiple [https://www.jppf.org/doc/6.2/index.php?title=Managing_and_monitoring_the_nodes_through_the_driver#Registering_JMX_notification_listeners forwarding notification listeers], only the first one is properly registered, causing the others to not receive notifications from the nodes.
February 09, 2020
enhancement_tiny.png 11:59  Enhancement JPPF-617 - Add one or more unit test for executing a job from an executing task
lolocohen : Issue created
JPPF provides the ability to submit a job from a task already running in a node, but I realized we do not have any automated tests fro this feature
February 08, 2020
icon_build.png 14:00 JPPF 6.2
New version released
February 07, 2020
icon_milestone.png 03:23 JPPF 5.2.9
A new milestone has been reached
icon_milestone.png 03:21 JPPF 5.2.7
A new milestone has been reached
icon_milestone.png 03:19 JPPF 5.2.5
A new milestone has been reached
icon_milestone.png 03:06 JPPF 4.1
A new milestone has been reached
icon_milestone.png 02:56 JPPF 5.2.4
A new milestone has been reached
icon_milestone.png 02:53 JPPF 3.2
A new milestone has been reached
icon_milestone.png 02:50 JPPF 5.2
A new milestone has been reached
icon_milestone.png 02:48 JPPF 5.2.2
A new milestone has been reached
icon_milestone.png 02:40 JPPF 5.2.1
A new milestone has been reached
January 28, 2020
icon_milestone.png 11:21 JPPF 5.2.10
A new milestone has been reached
January 26, 2020
feature_request_tiny.png 10:59  Feature request JPPF-371 - New sample to upgrade Windows nodes to .Net-capable status
lolocohen : Issue closed
January 24, 2020
icon_milestone.png 19:45 JPPF 6.1.3
A new milestone has been reached
icon_milestone.png 10:50 JPPF 3.3
A new milestone has been reached
icon_milestone.png 10:49 JPPF 5.1
A new milestone has been reached
icon_milestone.png 10:47 JPPF 6.0
A new milestone has been reached
icon_milestone.png 10:40 JPPF 6.0.2
A new milestone has been reached
icon_milestone.png 10:37 JPPF 2.5.5
A new milestone has been reached
icon_milestone.png 10:30 JPPF 5.2.8
A new milestone has been reached
January 21, 2020
icon_milestone.png 14:38 JPPF 4.0
A new milestone has been reached
January 17, 2020
bug_report_tiny.png 08:12  Bug report JPPF-615 - ProcessLauncher should not explicitely rely on Log4j for logging
lolocohen : Issue closed
January 16, 2020
bug_report_tiny.png 09:46  Bug report JPPF-616 - Build broken due to Maven central switching to HTTPS only
lolocohen : Issue closed
bug_report_tiny.png 07:34  Bug report JPPF-616 - Build broken due to Maven central switching to HTTPS only
lolocohen : Issue created
The Maven central repository has switched to HTTPS only as of January 15th, 2020. As a consequence, the JPPF build fails to download its dependencies, since it uses http://repo.maven.apache.org/maven2/ as a basde url. this causes the compilation and the build to fail.

This affects the trunk/master, 6.1.x and 6.0.x versions
January 15, 2020
icon_milestone.png 08:57 JPPF 4.2
A new milestone has been reached
Show moreaction_add_small.png