JPPF Issue Tracker
JPPF (jppf)
June 25, 2017
bug_report_tiny.png 10:45  Bug report JPPF-509 - Regression: topology monitoring API does not detect peer to peer connections anymore
lolocohen : Issue closed
bug_report_tiny.png 10:45  Bug report JPPF-509 - Regression: topology monitoring API does not detect peer to peer connections anymore
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 10:45  Bug report JPPF-509 - Regression: topology monitoring API does not detect peer to peer connections anymore
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 10:45  Bug report JPPF-509 - Regression: topology monitoring API does not detect peer to peer connections anymore
lolocohen : lolo4j ⇒ Not being worked on
bug_report_tiny.png 09:03  Bug report JPPF-509 - Regression: topology monitoring API does not detect peer to peer connections anymore
lolocohen : Assignee changed: lolo4j
bug_report_tiny.png 09:03  Bug report JPPF-509 - Regression: topology monitoring API does not detect peer to peer connections anymore
lolocohen : Issue created
I've noticed in the admin console that peer to peer driver connections are not detected anymore. Looking at the logs, I could see that the toplogy monitoring API never logs peer connections. I suspect this due to the JPPFNodeForwardingMBean excluding peer nodes when retrieving nodes specified with a NodeSelector.
bug_report_tiny.png 09:03  Bug report JPPF-509 - Regression: topology monitoring API does not detect peer to peer connections anymore
lolocohen : 'JPPF 5.2.7' added
feature_request_tiny.png 08:17  Feature request JPPF-508 - Peer to peer connection pooling
lolocohen : Description updated
feature_request_tiny.png 08:15  Feature request JPPF-508 - Peer to peer connection pooling
lolocohen : Description updated
feature_request_tiny.png 08:13  Feature request JPPF-508 - Peer to peer connection pooling
lolocohen : Issue created
Currently, in a multi-server topology where servers are connected to each other, each server can only send one job at a time to each of its peers. This has an impact on scalability.

It is possible to "trick" each server into connecting multiple times to the same peer, but this only works with manual peer configuration, for example:
jppf.peers = driver2a driver2b
jppf.peer.driver2a.server.host = localhost
jppf.peer.driver2a.server.port = 11111
jppf.peer.driver2b.server.host = localhost
jppf.peer.driver2b.server.port = 11111
However, this is quite cumbersome and is not possible with auto discovery of peer drivers.

We propose to enable the definition of connection pools instead, with a configurable pool size:
jppf.peers = driver2
# five connections to driver2
jppf.peer.driver2.pool.size = 5
jppf.peer.driver2.server.host = localhost
jppf.peer.driver1a.server.port = 11111
or, with peer discovery enabled:
jppf.peer.discovery.enabled = true
# five connections to each discovered peer
jppf.peer.pool.size = 5
feature_request_tiny.png 07:01  Feature request JPPF-480 - Jobs persistence in the driver
lolocohen : Feature request JPPF-507 now depends on the solution of this Feature request
feature_request_tiny.png 07:01  Feature request JPPF-507 - New persisted jobs view in the web and desktop admin consoles
lolocohen : This Feature request now depends on the solution of Feature request JPPF-480
feature_request_tiny.png 07:00  Feature request JPPF-507 - New persisted jobs view in the web and desktop admin consoles
lolocohen : Issue created
The feature request JPPF-480 provides a pluggable way for the driver to persist jobs, to enable both job failover/recovery and the ability to execute jobs and retrieve their results offline. In particular, it provides a client-side API to administer persisted jobs.

We propose to add an administration interface to the web and desktop consoles to allow users to perform these tasks graphically in addition to programmatically.
bug_report_tiny.png 06:45  Bug report JPPF-506 - Client side load-balancer does not use the configuration passed to the JPPFClient constructor
lolocohen : Issue closed
bug_report_tiny.png 06:45  Bug report JPPF-506 - Client side load-balancer does not use the configuration passed to the JPPFClient constructor
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 06:45  Bug report JPPF-506 - Client side load-balancer does not use the configuration passed to the JPPFClient constructor
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 06:45  Bug report JPPF-506 - Client side load-balancer does not use the configuration passed to the JPPFClient constructor
lolocohen : lolo4j ⇒ Not being worked on
June 24, 2017
bug_report_tiny.png 06:46  Bug report JPPF-506 - Client side load-balancer does not use the configuration passed to the JPPFClient constructor
lolocohen : Assignee changed: lolo4j
bug_report_tiny.png 06:46  Bug report JPPF-506 - Client side load-balancer does not use the configuration passed to the JPPFClient constructor
lolocohen : Issue created
When using the constructor JPPFClient(String uuid, TypedProperties config, ConnectionPoolListener... listeners), the load-balancer for this client is not using the TypedProperties object, but instead uses the global configuration via a static call to JPPFConfiguration.getProperties(). This will cause wrong settings for the client load-balancer.

A possible workaround is to dynamically set the load-balancer configuration once the client is initialized, using JPPFClient.setLoadBalancerSettings(String algorithm, Properties config).
bug_report_tiny.png 06:46  Bug report JPPF-506 - Client side load-balancer does not use the configuration passed to the JPPFClient constructor
lolocohen : 'JPPF 5.2.7' added
June 20, 2017
enhancement_tiny.png 07:03  Enhancement JPPF-505 - Ability to disable the bias towards local node in the driver
lolocohen : Issue closed
enhancement_tiny.png 07:03  Enhancement JPPF-505 - Ability to disable the bias towards local node in the driver
lolocohen : Status changed: New ⇒ Closed
enhancement_tiny.png 07:03  Enhancement JPPF-505 - Ability to disable the bias towards local node in the driver
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
enhancement_tiny.png 07:03  Enhancement JPPF-505 - Ability to disable the bias towards local node in the driver
lolocohen : lolo4j ⇒ Not being worked on
enhancement_tiny.png 06:41  Enhancement JPPF-505 - Ability to disable the bias towards local node in the driver
lolocohen : Assignee changed: lolo4j
enhancement_tiny.png 06:41  Enhancement JPPF-505 - Ability to disable the bias towards local node in the driver
lolocohen : Issue created
Currently, when a driver is configured with a local (same JVM) node, this local node is always given priority for job scheduling. We propose to give users the ability to disable this behavior via a driver configuration proeprty such as "jppf.local.node.bias = false", with a default value of "true" to keep compatibility with previous versions.
enhancement_tiny.png 06:41  Enhancement JPPF-505 - Ability to disable the bias towards local node in the driver
lolocohen : 'JPPF 5.2.7' added
June 15, 2017
bug_report_tiny.png 06:53  Bug report JPPF-504 - Local node never completes connection to server
lolocohen : Issue closed
bug_report_tiny.png 06:53  Bug report JPPF-504 - Local node never completes connection to server
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 06:53  Bug report JPPF-504 - Local node never completes connection to server
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 06:53  Bug report JPPF-504 - Local node never completes connection to server
lolocohen : lolo4j ⇒ Not being worked on
June 14, 2017
bug_report_tiny.png 06:47  Bug report JPPF-504 - Local node never completes connection to server
lolocohen : Assignee changed: lolo4j
bug_report_tiny.png 06:47  Bug report JPPF-504 - Local node never completes connection to server
lolocohen : Issue created
When starting a JPPF driver with a local node, the local node does not complete its connection with the driver it is embedded in, even though it display a message "Node successfully initialized". The node then behaves as if it were not started at all, and does not appear in the administration console.
bug_report_tiny.png 06:47  Bug report JPPF-504 - Local node never completes connection to server
lolocohen : 'JPPF 5.2.6' added
June 12, 2017
icon_build.png 10:00 JPPF 5.2.7
New version released
feature_request_tiny.png 08:06  Feature request JPPF-480 - Jobs persistence in the driver
lolocohen : Feature request JPPF-372 now depends on the solution of this Feature request
feature_request_tiny.png 08:06  Feature request JPPF-372 - Intelligent recovery of executing tasks
lolocohen : This Feature request now depends on the solution of Feature request JPPF-480
feature_request_tiny.png 08:06  Feature request JPPF-372 - Intelligent recovery of executing tasks
lolocohen : This issue no longer depends on the solution of issue JPPF-480
feature_request_tiny.png 08:06  Feature request JPPF-480 - Jobs persistence in the driver
lolocohen : Issue JPPF-372 no longer depends on the solution of this issue
feature_request_tiny.png 08:05  Feature request JPPF-480 - Jobs persistence in the driver
lolocohen : This Feature request now depends on the solution of Feature request JPPF-372
feature_request_tiny.png 08:05  Feature request JPPF-372 - Intelligent recovery of executing tasks
lolocohen : Feature request JPPF-480 now depends on the solution of this Feature request
April 27, 2017
icon_milestone.png 21:36 JPPF 5.1.7
A new milestone has been reached
icon_milestone.png 16:16 JPPF 4.2.9
A new milestone has been reached
icon_milestone.png 15:29 JPPF 4.2.8
A new milestone has been reached
April 02, 2017
icon_build.png 22:00 JPPF 5.2.6
New version released
icon_build.png 21:30 JPPF 5.1.6
New version released
March 10, 2017
icon_build.png 10:00 JPPF 5.2.5
New version released
January 18, 2017
icon_build.png 10:00 JPPF 5.2.4
New version released
January 07, 2017
icon_milestone.png 13:15 JPPF 5.1.5
A new milestone has been reached
January 05, 2017
icon_milestone.png 22:35 JPPF 4.2.4
A new milestone has been reached
November 27, 2016
icon_build.png 11:00 JPPF 5.2.3
New version released
November 13, 2016
icon_milestone.png 08:09 JPPF 5.0.4
A new milestone has been reached
November 09, 2016
icon_milestone.png 17:29 JPPF 5.0.2
A new milestone has been reached
October 16, 2016
icon_milestone.png 01:33 JPPF 4.2.1
A new milestone has been reached
icon_milestone.png 01:29 JPPF 4.2.5
A new milestone has been reached
icon_milestone.png 01:08 JPPF 4.2.3
A new milestone has been reached
October 15, 2016
icon_milestone.png 18:55 JPPF 5.2
A new milestone has been reached
icon_milestone.png 10:41 JPPF 4.1
A new milestone has been reached
icon_milestone.png 08:42 JPPF 5.0
A new milestone has been reached
icon_milestone.png 07:14 JPPF 2.5.5
A new milestone has been reached
Show moreaction_add_small.png