JPPF Issue Tracker
JPPF (jppf)
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
feature_request_tiny.png 10:59  Feature request JPPF-371 - New sample to upgrade Windows nodes to .Net-capable status
lolocohen : Status changed: New ⇒ Closed
feature_request_tiny.png 10:59  Feature request JPPF-371 - New sample to upgrade Windows nodes to .Net-capable status
lolocohen : Resolution changed: Not determined ⇒ WON'T FIX
feature_request_tiny.png 10:59  Feature request JPPF-371 - New sample to upgrade Windows nodes to .Net-capable status
lolocohen : lolo4j ⇒ Not being worked on
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
bug_report_tiny.png 08:12  Bug report JPPF-615 - ProcessLauncher should not explicitely rely on Log4j for logging
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 08:12  Bug report JPPF-615 - ProcessLauncher should not explicitely rely on Log4j for logging
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 08:12  Bug report JPPF-615 - ProcessLauncher should not explicitely rely on Log4j for logging
lolocohen : lolo4j ⇒ Not being worked on
January 16, 2020
bug_report_tiny.png 09:46  Bug report JPPF-615 - ProcessLauncher should not explicitely rely on Log4j for logging
lolocohen : Assignee changed: lolo4j
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 09:46  Bug report JPPF-616 - Build broken due to Maven central switching to HTTPS only
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 09:46  Bug report JPPF-616 - Build broken due to Maven central switching to HTTPS only
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 09:46  Bug report JPPF-616 - Build broken due to Maven central switching to HTTPS only
lolocohen : lolo4j ⇒ Not being worked on
bug_report_tiny.png 07:35  Bug report JPPF-616 - Build broken due to Maven central switching to HTTPS only
lolocohen : Assignee changed: lolo4j
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
bug_report_tiny.png 07:34  Bug report JPPF-616 - Build broken due to Maven central switching to HTTPS only
lolocohen : 'JPPF 6.1.4' added
January 15, 2020
icon_milestone.png 22:27 JPPF 5.2.5
A new milestone has been reached
icon_milestone.png 21:06 JPPF 5.2.9
A new milestone has been reached
icon_milestone.png 20:49 JPPF 5.2.7
A new milestone has been reached
icon_milestone.png 19:22 JPPF 5.2.4
A new milestone has been reached
icon_milestone.png 19:20 JPPF 3.2
A new milestone has been reached
icon_milestone.png 19:20 JPPF 4.1
A new milestone has been reached
icon_milestone.png 19:14 JPPF 5.2.2
A new milestone has been reached
icon_milestone.png 19:13 JPPF 5.2
A new milestone has been reached
icon_milestone.png 19:12 JPPF 5.2.1
A new milestone has been reached
icon_milestone.png 08:57 JPPF 4.2
A new milestone has been reached
January 10, 2020
bug_report_tiny.png 08:45  Bug report JPPF-615 - ProcessLauncher should not explicitely rely on Log4j for logging
lolocohen : Issue created
The [https://github.com/jppf-grid/JPPF/blob/master/common/src/java/org/jppf/process/ProcessLauncher.java ProcessLauncher] class is used to launch drivers and nodes and allows them to be restarted remotely. We have found [https://github.com/jppf-grid/JPPF/blob/master/common/src/java/org/jppf/process/ProcessLauncher.java#L176 here] that it always sets the "log4j.configuration" system property, even if the value of the property is null, which may happen if another logging framework is used. This results in an error being printed at startup.
bug_report_tiny.png 08:45  Bug report JPPF-615 - ProcessLauncher should not explicitely rely on Log4j for logging
lolocohen : 'JPPF 6.1.4' added
January 04, 2020
bug_report_tiny.png 12:04  Bug report JPPF-614 - Race condition in the client prevents job recovery upon disconnection
lolocohen : Issue closed
bug_report_tiny.png 12:04  Bug report JPPF-614 - Race condition in the client prevents job recovery upon disconnection
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 12:04  Bug report JPPF-614 - Race condition in the client prevents job recovery upon disconnection
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 12:04  Bug report JPPF-614 - Race condition in the client prevents job recovery upon disconnection
lolocohen : lolo4j ⇒ Not being worked on
bug_report_tiny.png 10:36  Bug report JPPF-614 - Race condition in the client prevents job recovery upon disconnection
lolocohen : Reproducability changed: Reproduction steps updated
bug_report_tiny.png 10:36  Bug report JPPF-614 - Race condition in the client prevents job recovery upon disconnection
lolocohen : Assignee changed: lolo4j
bug_report_tiny.png 10:35  Bug report JPPF-614 - Race condition in the client prevents job recovery upon disconnection
lolocohen : Issue created
Sometimes a job that is executing is not recovered when the client gets disconnected from the driver.
bug_report_tiny.png 10:35  Bug report JPPF-614 - Race condition in the client prevents job recovery upon disconnection
lolocohen : 'JPPF 6.1.4' added
January 02, 2020
icon_milestone.png 19:34 JPPF 6.1.4
A new milestone has been reached
icon_milestone.png 17:21 JPPF 6.0.5
A new milestone has been reached
December 24, 2019
enhancement_tiny.png 07:51  Enhancement JPPF-599 - Add job persistence capabilities to docker swarm and kubernetes deployments
lolocohen : Target milestone changed: JPPF 6.2 ⇒ JPPF Vision
feature_request_tiny.png 07:20  Feature request JPPF-372 - Intelligent recovery of executing tasks
lolocohen : Target milestone changed: JPPF 6.2 ⇒ JPPF Vision
feature_request_tiny.png 07:20  Feature request JPPF-491 - Node statistics
lolocohen : Target milestone changed: JPPF 6.2 ⇒ JPPF Vision
December 21, 2019
icon_build.png 08:00 JPPF 6.1.4
New version released
feature_request_tiny.png 07:32  Feature request JPPF-19 - Enable access control
lolocohen : Target milestone changed: JPPF 6.2 ⇒ JPPF Vision
December 20, 2019
enhancement_tiny.png 10:15  Enhancement JPPF-610 - Add an API to instrospect the properties defined in the monitoring data providers
lolocohen : Issue closed
enhancement_tiny.png 10:15  Enhancement JPPF-610 - Add an API to instrospect the properties defined in the monitoring data providers
lolocohen : Status changed: New ⇒ Closed
enhancement_tiny.png 10:15  Enhancement JPPF-610 - Add an API to instrospect the properties defined in the monitoring data providers
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
enhancement_tiny.png 10:15  Enhancement JPPF-610 - Add an API to instrospect the properties defined in the monitoring data providers
lolocohen : lolo4j ⇒ Not being worked on
enhancement_tiny.png 02:09  Enhancement JPPF-610 - Add an API to instrospect the properties defined in the monitoring data providers
lolocohen : Assignee changed: lolo4j
December 19, 2019
bug_report_tiny.png 09:28  Bug report JPPF-613 - NPE due to race condition in the server leads to losing node connections
lolocohen : Issue closed
bug_report_tiny.png 09:28  Bug report JPPF-613 - NPE due to race condition in the server leads to losing node connections
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 09:28  Bug report JPPF-613 - NPE due to race condition in the server leads to losing node connections
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 09:28  Bug report JPPF-613 - NPE due to race condition in the server leads to losing node connections
lolocohen : lolo4j ⇒ Not being worked on
bug_report_tiny.png 09:07  Bug report JPPF-613 - NPE due to race condition in the server leads to losing node connections
lolocohen : Reproducability changed: Reproduction steps updated
October 13, 2019
icon_milestone.png 12:06 JPPF 6.0.3
A new milestone has been reached
October 08, 2019
icon_build.png 10:00 JPPF 6.1.3
New version released
Show moreaction_add_small.png