JPPF Issue Tracker
JPPF (jppf)
April 20, 2019
bug_report_tiny.png 11:10  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : Issue closed
bug_report_tiny.png 11:10  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 11:10  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 11:10  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : lolo4j ⇒ Not being worked on
bug_report_tiny.png 11:07  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : Reproducability changed: Reproduction steps updated
feature_request_tiny.png 07:22  Feature request JPPF-589 - Docker images for JPPF components
lolocohen : Issue created
We propose to add Docker images for JPPF, for drivers, nodes and web admin console. The configuration of a JPPF grid with docker should allow any kind of JPPF topology, including multi-server topologies.
bug_report_tiny.png 07:10  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : Category changed: Other ⇒ Persistence
bug_report_tiny.png 07:10  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : Assignee changed: lolo4j
bug_report_tiny.png 07:09  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : 'JPPF trunk' added
bug_report_tiny.png 07:09  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : 'JPPF 6.0.2' added
bug_report_tiny.png 07:08  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : Issue created
In a recently failed test of the file-based job persistence, I could find the following pattern in the driver log, where multilpe threads are performing 'store' and 'delete' opeations:
2019-04-19 08:07:34,852 [DEBUG][JPPF-0007][org.jppf.server.queue.PersistenceHandler.storeResults(116)] persisting 5 results for job ServerJob[id=2, job uuid=0282BA15-CE62-4C5D-AF33-5F92CFB2BB23, name=testSimplePersistedJob, submissionStatus=EXECUTING, status=EXECUTING, taskCount=0, nbBundles=1, jobExpired=false, pending=false, suspended=false]
...
2019-04-19 08:07:34,852 [DEBUG][JPPF-0007][org.jppf.job.persistence.impl.DefaultFilePersistence.store(97)] storing [PersistenceInfoImpl[type=TASK_RESULT, taskPosition=5, job=testSimplePersistedJob, jobUuid=0282BA15-CE62-4C5D-AF33-5F92CFB2BB23], PersistenceInfoImpl[type=TASK_RESULT, taskPosition=8, job=testSimplePersistedJob, jobUuid=0282BA15-CE62-4C5D-AF33-5F92CFB2BB23], PersistenceInfoImpl[type=TASK_RESULT, taskPosition=6, job=testSimplePersistedJob, jobUuid=0282BA15-CE62-4C5D-AF33-5F92CFB2BB23], PersistenceInfoImpl[type=TASK_RESULT, taskPosition=9, job=testSimplePersistedJob, jobUuid=0282BA15-CE62-4C5D-AF33-5F92CFB2BB23], PersistenceInfoImpl[type=TASK_RESULT, taskPosition=7, job=testSimplePersistedJob, jobUuid=0282BA15-CE62-4C5D-AF33-5F92CFB2BB23]]
2019-04-19 08:07:34,852 [DEBUG][JPPF-0005][org.jppf.server.job.JPPFJobManager.jobEnded(195)] jobId 'testSimplePersistedJob' ended
2019-04-19 08:07:34,853 [DEBUG][JPPF-0005][org.jppf.server.queue.PersistenceHandler.deleteJob(141)] removing job 0282BA15-CE62-4C5D-AF33-5F92CFB2BB23 from persistence store
2019-04-19 08:07:34,853 [DEBUG][JPPF-0005][org.jppf.job.persistence.impl.DefaultFilePersistence.deleteJob(168)] deleting job with uuid = 0282BA15-CE62-4C5D-AF33-5F92CFB2BB23
2019-04-19 08:07:34,854 [DEBUG][JPPF-0003][org.jppf.server.queue.PersistenceHandler.deleteJob(141)] removing job 0282BA15-CE62-4C5D-AF33-5F92CFB2BB23 from persistence store
2019-04-19 08:07:34,854 [DEBUG][JPPF-0003][org.jppf.job.persistence.impl.DefaultFilePersistence.deleteJob(168)] deleting job with uuid = 0282BA15-CE62-4C5D-AF33-5F92CFB2BB23
...
2019-04-19 08:07:34,858 [DEBUG][JPPF-0007][org.jppf.server.protocol.ServerJob.lambda$postResultsReceived$0(189)] received results for ServerTaskBundleClient[id=2, pendingTasks=0, cancelled=false, done=true, job=JPPFTaskBundle[name=testSimplePersistedJob, uuid=0282BA15-CE62-4C5D-AF33-5F92CFB2BB23, initialTaskCount=10, taskCount=10, bundleUuid=null, uuidPath=TraversalList[position=0, list=[4F5DEEB3-FEDE-4A18-A48F-9EE05CF06D94, d1]], nodeBundleId=null]; strategy=NodeResults]
2019-04-19 08:07:34,858 [DEBUG][JPPF-0007][org.jppf.server.protocol.ServerJob.taskCompleted(245)] requeue = false for bundle ServerTaskBundleNode[id=4, name=testSimplePersistedJob, uuid=0282BA15-CE62-4C5D-AF33-5F92CFB2BB23, initialTaskCount=10, taskCount=5, cancelled=false, requeued=false, channel=AsyncNodeContext[uuid=n2, peer=false, ssl=false, local=false, offline=false, maxJobs=1, jobEntries=0, sendQueue size=0, interestOps=1, executionStatus=EXECUTING]], job = ServerJob[id=2, job uuid=0282BA15-CE62-4C5D-AF33-5F92CFB2BB23, name=testSimplePersistedJob, submissionStatus=ENDED, status=DONE, taskCount=0, nbBundles=0, jobExpired=false, pending=false, suspended=false]
2019-04-19 08:07:34,859 [DEBUG][JPPF-0007][org.jppf.server.queue.PersistenceHandler.deleteJob(141)] removing job 0282BA15-CE62-4C5D-AF33-5F92CFB2BB23 from persistence store
2019-04-19 08:07:34,859 [DEBUG][JPPF-0007][org.jppf.job.persistence.impl.DefaultFilePersistence.deleteJob(168)] deleting job with uuid = 0282BA15-CE62-4C5D-AF33-5F92CFB2BB23
2019-04-19 08:07:34,860 [WARN ][JPPF-0003][org.jppf.utils.DeleteFileVisitor.visitFile(82)] error trying to delete file 'persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\result-7.tmp': java.nio.file.NoSuchFileException: persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\result-7.tmp
2019-04-19 08:07:34,860 [ERROR][JPPF-0007][org.jppf.server.queue.PersistenceHandler.deleteJob(145)] error deleting persistent job 0282BA15-CE62-4C5D-AF33-5F92CFB2BB23 : org.jppf.job.persistence.JobPersistenceException: java.nio.file.AccessDeniedException: persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\header.data
at org.jppf.job.persistence.impl.DefaultFilePersistence.deleteJob(DefaultFilePersistence.java:172)
at org.jppf.server.queue.PersistenceHandler.deleteJob(PersistenceHandler.java:143)
at org.jppf.server.queue.PersistenceHandler.deleteJob(PersistenceHandler.java:132)
at org.jppf.server.queue.RemoveBundleAction.run(RemoveBundleAction.java:63)
at org.jppf.server.protocol.AbstractServerJob.done(AbstractServerJob.java:333)
at org.jppf.server.protocol.AbstractServerJob.setSubmissionStatus(AbstractServerJob.java:418)
at org.jppf.server.protocol.ServerJob.taskCompleted(ServerJob.java:253)
at org.jppf.server.protocol.ServerJob.postResultsReceived(ServerJob.java:191)
at org.jppf.server.protocol.ServerJob.resultsReceived(ServerJob.java:142)
at org.jppf.server.protocol.ServerTaskBundleNode.resultsReceived(ServerTaskBundleNode.java:198)
at org.jppf.server.nio.nodeserver.async.AsyncNodeMessageHandler.processResults(AsyncNodeMessageHandler.java:337)
at org.jppf.server.nio.nodeserver.async.AsyncNodeMessageHandler.process(AsyncNodeMessageHandler.java:274)
at org.jppf.server.nio.nodeserver.async.AsyncNodeMessageHandler.resultsReceived(AsyncNodeMessageHandler.java:183)
at org.jppf.server.nio.nodeserver.async.AsyncNodeMessageReader.handleMessage(AsyncNodeMessageReader.java:73)
at org.jppf.nio.NioMessageReader$HandlingTask.run(NioMessageReader.java:134)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.nio.file.AccessDeniedException: persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\header.data
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:83)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
at sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:269)
at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103)
at java.nio.file.Files.delete(Files.java:1126)
at org.jppf.utils.DeleteFileVisitor.visitFile(DeleteFileVisitor.java:78)
at org.jppf.utils.DeleteFileVisitor.visitFile(DeleteFileVisitor.java:30)
at java.nio.file.Files.walkFileTree(Files.java:2670)
at java.nio.file.Files.walkFileTree(Files.java:2742)
at org.jppf.job.persistence.impl.DefaultFilePersistence.deleteJob(DefaultFilePersistence.java:170)
... 17 more
2019-04-19 08:07:34,861 [DEBUG][JPPF-0007][org.jppf.server.protocol.ServerJob.taskCompleted(254)] submissionStatus=ENDED, clientBundles=0 for ServerJob[id=2, job uuid=0282BA15-CE62-4C5D-AF33-5F92CFB2BB23, name=testSimplePersistedJob, submissionStatus=ENDED, status=DONE, taskCount=0, nbBundles=0, jobExpired=false, pending=false, suspended=false]
2019-04-19 08:07:34,861 [DEBUG][JPPF-0007][org.jppf.server.nio.nodeserver.async.AsyncNodeMessageHandler.processResults(338)] updated stats for AsyncNodeContext[uuid=n2, peer=false, ssl=false, local=false, offline=false, maxJobs=1, jobEntries=0, sendQueue size=0, interestOps=1, executionStatus=EXECUTING]
2019-04-19 08:07:34,860 [WARN ][JPPF-0005][org.jppf.utils.DeleteFileVisitor.visitFile(82)] error trying to delete file 'persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\header.data': java.nio.file.NoSuchFileException: persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\header.data
2019-04-19 08:07:34,862 [WARN ][JPPF-0005][org.jppf.utils.DeleteFileVisitor.visitFile(82)] error trying to delete file 'persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\result-0.data': java.nio.file.NoSuchFileException: persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\result-0.data
2019-04-19 08:07:34,862 [WARN ][JPPF-0005][org.jppf.utils.DeleteFileVisitor.visitFile(82)] error trying to delete file 'persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\result-1.data': java.nio.file.NoSuchFileException: persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\result-1.data
2019-04-19 08:07:34,862 [WARN ][JPPF-0005][org.jppf.utils.DeleteFileVisitor.visitFile(82)] error trying to delete file 'persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\result-2.data': java.nio.file.NoSuchFileException: persistence\0282BA15-CE62-4C5D-AF33-5F92CFB2BB23\result-2.data
bug_report_tiny.png 07:08  Bug report JPPF-588 - Concurrent operations with DefaultFilePersistence job persistence result in exceptions
lolocohen : 'JPPF 6.1' added
April 14, 2019
enhancement_tiny.png 05:56  Enhancement JPPF-587 - Ability to create JPPFSchedule instances using java.time.* APIs
lolocohen : Issue created
The class [https://www.jppf.org/javadoc/6.2/index.html?org/jppf/scheduling/JPPFSchedule.html JPPFSchedule] is used to specify the start or expiration schedule of a job, as well as the expiration schedule of a task. It currently has 2 basic constructors, one that takes an epoch time in millis, the other that takes a string which represents a date, along with a SimpleDateFormat-compliant format to parse it.

We propose to extends this class to enable building JPPFSchedule objects based on the classes in java.time.*, such as ZOnedDateTime, Duration, etc.
enhancement_tiny.png 05:56  Enhancement JPPF-587 - Ability to create JPPFSchedule instances using java.time.* APIs
lolocohen : 'JPPF trunk' added
April 13, 2019
feature_request_tiny.png 20:19  Feature request JPPF-583 - Tasks dependencies within a job
lolocohen : Assignee changed: lolo4j
enhancement_tiny.png 20:19  Enhancement JPPF-586 - Cache of class/resource definitions in the client
lolocohen : Issue closed
enhancement_tiny.png 20:19  Enhancement JPPF-586 - Cache of class/resource definitions in the client
lolocohen : Status changed: New ⇒ Closed
enhancement_tiny.png 20:19  Enhancement JPPF-586 - Cache of class/resource definitions in the client
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
enhancement_tiny.png 20:19  Enhancement JPPF-586 - Cache of class/resource definitions in the client
lolocohen : lolo4j ⇒ Not being worked on
April 12, 2019
enhancement_tiny.png 13:14  Enhancement JPPF-586 - Cache of class/resource definitions in the client
lolocohen : Assignee changed: lolo4j
task_tiny.png 13:13  Task JPPF-584 - Refactor the distributed class loader into the asynchronous Nio communication model
lolocohen : Issue closed
task_tiny.png 13:13  Task JPPF-584 - Refactor the distributed class loader into the asynchronous Nio communication model
lolocohen : Status changed: New ⇒ Closed
task_tiny.png 13:13  Task JPPF-584 - Refactor the distributed class loader into the asynchronous Nio communication model
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
task_tiny.png 13:13  Task JPPF-584 - Refactor the distributed class loader into the asynchronous Nio communication model
lolocohen : lolo4j ⇒ Not being worked on
April 08, 2019
enhancement_tiny.png 07:39  Enhancement JPPF-586 - Cache of class/resource definitions in the client
lolocohen : Description updated
enhancement_tiny.png 07:36  Enhancement JPPF-586 - Cache of class/resource definitions in the client
lolocohen : Issue created
When a job is dispatched to multiple nodes in parallel, this can result in the same class loading request being issued to the same client in parallel or in sequence. This would happen when identical requests are forwarded to the same client, before the first response is received by the server, and therefore before in can be added to the server-side cache. It could be worthwhile, from a perfromance perspective, to use a cache of class definitions, such that identical requests (same client-side class loader and same resource path) only result in a single lookup in the classpath.

To this effect, we propose to implement a cache in the client, as follows:
* an identity hash map whose keys are class loaders
* the values are hash maps where the key is a path in the classpath and the value is the byte[] for the resource located at that path. These could be implemented as [https://www.jppf.org/javadoc/6.2/index.html?org/jppf/utils/collections/SoftReferenceValuesMap.html SoftReferenceValueMap]s to avoid out of memory conditions due to the cache
enhancement_tiny.png 07:36  Enhancement JPPF-586 - Cache of class/resource definitions in the client
lolocohen : 'JPPF trunk' added
April 02, 2019
task_tiny.png 07:37  Task JPPF-584 - Refactor the distributed class loader into the asynchronous Nio communication model
lolocohen : Assignee changed: lolo4j
March 31, 2019
bug_report_tiny.png 09:43  Bug report JPPF-585 - The 6.1 tutorial still uses JPPFClient.submitJob() and blocking job attribute
lolocohen : Issue closed
bug_report_tiny.png 09:43  Bug report JPPF-585 - The 6.1 tutorial still uses JPPFClient.submitJob() and blocking job attribute
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 09:43  Bug report JPPF-585 - The 6.1 tutorial still uses JPPFClient.submitJob() and blocking job attribute
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 09:43  Bug report JPPF-585 - The 6.1 tutorial still uses JPPFClient.submitJob() and blocking job attribute
lolocohen : lolo4j ⇒ Not being worked on
bug_report_tiny.png 08:42  Bug report JPPF-585 - The 6.1 tutorial still uses JPPFClient.submitJob() and blocking job attribute
lolocohen : Assignee changed: lolo4j
bug_report_tiny.png 08:42  Bug report JPPF-585 - The 6.1 tutorial still uses JPPFClient.submitJob() and blocking job attribute
lolocohen : Issue created
The online and offline dosc still show, in the tutorial, code snippe that use the "blocking" job attribute, which is now deprecated, as well as job submission with JPPFClient.submitJob(), now deprecated and replace with submit() and submitAsync
bug_report_tiny.png 08:42  Bug report JPPF-585 - The 6.1 tutorial still uses JPPFClient.submitJob() and blocking job attribute
lolocohen : 'JPPF 6.1' added
March 30, 2019
task_tiny.png 07:19  Task JPPF-584 - Refactor the distributed class loader into the asynchronous Nio communication model
lolocohen : Issue created
This is about refactoring the distributed class loader communication model into the more efficient and scalable model introduced in JPPF 6.1 (see feature request JPPF-549 and feature request JPPF-564). This includes both driver/node and driver/client communication channels.

These are the last components to switch to the new model. Once it is done, we expect a number of benefits:
* we will be able to get rid of the old nio code, which should reduce the maintenance burden
* this should also increase the performance, simply because we will remove parts of the code inherited from the old model, which are still present but not used in the new model
* increased performance and scalability, because the new nio model is more efficient
March 28, 2019
task_tiny.png 20:13  Task JPPF-572 - Performance, endurance and stress testing
lolocohen : Issue closed
task_tiny.png 20:13  Task JPPF-572 - Performance, endurance and stress testing
lolocohen : Status changed: New ⇒ Closed
task_tiny.png 20:13  Task JPPF-572 - Performance, endurance and stress testing
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
task_tiny.png 20:13  Task JPPF-572 - Performance, endurance and stress testing
lolocohen : lolo4j ⇒ Not being worked on
icon_build.png 10:00 JPPF 6.1
New version released
November 24, 2018
icon_build.png 14:00 JPPF 6.0.1
New version released
icon_build.png 14:00 JPPF 5.2.10
New version released
icon_build.png 14:00 JPPF 5.1.7
New version released
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 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 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 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: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
July 18, 2018
icon_milestone.png 03:27 JPPF 5.2
A new milestone has been reached
icon_milestone.png 03:13 JPPF 3.2
A new milestone has been reached
icon_milestone.png 03:13 JPPF 5.0
A new milestone has been reached
icon_milestone.png 02:54 JPPF 3.3
A new milestone has been reached
Show moreaction_add_small.png