JPPF Issue Tracker
JPPF (jppf)
January 30, 2018
icon_milestone.png 12:36 JPPF 5.1
A new milestone has been reached
January 18, 2018
icon_milestone.png 14:25 JPPF 5.0
A new milestone has been reached
January 17, 2018
bug_report_tiny.png 09:01  Bug report JPPF-521 - Document the "jppf.node.provisioning.master.uuid" configuration property
lolocohen : Issue closed
bug_report_tiny.png 09:01  Bug report JPPF-521 - Document the "jppf.node.provisioning.master.uuid" configuration property
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 09:01  Bug report JPPF-521 - Document the "jppf.node.provisioning.master.uuid" configuration property
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 09:01  Bug report JPPF-521 - Document the "jppf.node.provisioning.master.uuid" configuration property
lolocohen : lolo4j ⇒ Not being worked on
bug_report_tiny.png 08:21  Bug report JPPF-525 - Deadlock in the driver during automated test run
lolocohen : Issue closed
bug_report_tiny.png 08:21  Bug report JPPF-525 - Deadlock in the driver during automated test run
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 08:21  Bug report JPPF-525 - Deadlock in the driver during automated test run
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 08:21  Bug report JPPF-525 - Deadlock in the driver during automated test run
lolocohen : lolo4j ⇒ Not being worked on
January 13, 2018
bug_report_tiny.png 08:41  Bug report JPPF-525 - Deadlock in the driver during automated test run
lolocohen : Reproducability changed: Reproduction steps updated
bug_report_tiny.png 08:40  Bug report JPPF-525 - Deadlock in the driver during automated test run
lolocohen : Reproducability changed: Reproduction steps updated
bug_report_tiny.png 08:10  Bug report JPPF-525 - Deadlock in the driver during automated test run
lolocohen : Assignee changed: lolo4j
bug_report_tiny.png 08:08  Bug report JPPF-525 - Deadlock in the driver during automated test run
lolocohen : Issue created
During the run of the tests for test.org.jppf.client.event.TestJobListener on 5.2.8, the following deadlock was detected:
- thread id 23 "JPPF NIO-0004" is waiting to lock java.util.concurrent.locks.ReentrantLock$NonfairSync@6c452fb4 which is held by thread id 20 "JPPF NIO-0001"
- thread id 20 "JPPF NIO-0001" is waiting to lock java.util.concurrent.locks.ReentrantLock$NonfairSync@71183515 which is held by thread id 23 "JPPF NIO-0004"

Stack trace information for the threads listed above

"JPPF NIO-0004" - 23 - state: WAITING - blocked count: 3 - blocked time: 0 - wait count: 33 - wait time: 11618
at sun.misc.Unsafe.park(Native Method)
- waiting on java.util.concurrent.locks.ReentrantLock$NonfairSync@6c452fb4
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214)
at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290)
at org.jppf.server.protocol.AbstractServerJobBase.addBundle(AbstractServerJobBase.java:229)
at org.jppf.server.queue.JPPFPriorityQueue.addBundle(JPPFPriorityQueue.java:121)
at org.jppf.server.nio.client.WaitingJobState.performTransition(WaitingJobState.java:88)
at org.jppf.server.nio.client.WaitingJobState.performTransition(WaitingJobState.java:34)
at org.jppf.nio.StateTransitionTask.run(StateTransitionTask.java:78)
- locked org.jppf.nio.SelectionKeyWrapper@158778fd
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Locked ownable synchronizers:
- java.util.concurrent.locks.ReentrantLock$NonfairSync@71183515
- java.util.concurrent.ThreadPoolExecutor$Worker@6524a69

"JPPF NIO-0001" - 20 - state: WAITING - blocked count: 7 - blocked time: 1 - wait count: 32 - wait time: 11579
at sun.misc.Unsafe.park(Native Method)
- waiting on java.util.concurrent.locks.ReentrantLock$NonfairSync@71183515
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214)
at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290)
at org.jppf.server.queue.JPPFPriorityQueue.getJob(JPPFPriorityQueue.java:286)
at org.jppf.server.queue.JPPFPriorityQueue.getBundleForJob(JPPFPriorityQueue.java:371)
at org.jppf.server.nio.client.CompletionListener.removeJobFromQueue(CompletionListener.java:121)
at org.jppf.server.nio.client.CompletionListener.taskCompleted(CompletionListener.java:74)
at org.jppf.server.protocol.ServerTaskBundleClient.fireTasksCompleted(ServerTaskBundleClient.java:361)
at org.jppf.server.protocol.ServerTaskBundleClient.resultReceived(ServerTaskBundleClient.java:218)
at org.jppf.server.protocol.ServerJob.resultsReceived(ServerJob.java:139)
at org.jppf.server.protocol.ServerTaskBundleNode.resultsReceived(ServerTaskBundleNode.java:197)
at org.jppf.server.protocol.ServerJob.handleCancelledStatus(ServerJob.java:241)
at org.jppf.server.protocol.ServerJob.cancel(ServerJob.java:276)
at org.jppf.server.nio.client.ClientContext.cancelJobOnClose(ClientContext.java:279)
at org.jppf.server.nio.client.ClientContext.handleException(ClientContext.java:121)
at org.jppf.nio.StateTransitionTask.run(StateTransitionTask.java:94)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Locked ownable synchronizers:
- java.util.concurrent.locks.ReentrantLock$NonfairSync@6c452fb4
- java.util.concurrent.ThreadPoolExecutor$Worker@69663655
Attaching the whole logs zip for this test run.
bug_report_tiny.png 08:08  Bug report JPPF-525 - Deadlock in the driver during automated test run
lolocohen : 'JPPF 5.2.8' added
January 09, 2018
bug_report_tiny.png 13:45  Bug report JPPF-524 - Stream isn't closed properly in org.jppf.utils.VersionUtils#createVersionInfo
lolocohen : Issue closed
bug_report_tiny.png 13:45  Bug report JPPF-524 - Stream isn't closed properly in org.jppf.utils.VersionUtils#createVersionInfo
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 13:45  Bug report JPPF-524 - Stream isn't closed properly in org.jppf.utils.VersionUtils#createVersionInfo
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 13:45  Bug report JPPF-524 - Stream isn't closed properly in org.jppf.utils.VersionUtils#createVersionInfo
lolocohen : lolo4j ⇒ Not being worked on
bug_report_tiny.png 13:44  Bug report JPPF-524 - Stream isn't closed properly in org.jppf.utils.VersionUtils#createVersionInfo
lolocohen : Description updated
bug_report_tiny.png 11:53  Bug report JPPF-524 - Stream isn't closed properly in org.jppf.utils.VersionUtils#createVersionInfo
lolocohen : Assignee changed: lolo4j
January 08, 2018
bug_report_tiny.png 16:52  Bug report JPPF-524 - Stream isn't closed properly in org.jppf.utils.VersionUtils#createVersionInfo
igor : Issue created
During restart of a payara server i see sometimes this warning in logs:
[2018-01-08T13:31:47.119+0100] [Payara 4.1] [WARNING] [NCLS-COMUTIL-00023] [javax.enterprise.system.util] [[
Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace
java.lang.Throwable
at com.sun.enterprise.loader.ASURLClassLoader$SentinelInputStream.(ASURLClassLoader.java:1284)
at com.sun.enterprise.loader.ASURLClassLoader$InternalJarURLConnection.getInputStream(ASURLClassLoader.java:1392)
at java.net.URLClassLoader.getResourceAsStream(URLClassLoader.java:238)
at com.sun.enterprise.loader.ASURLClassLoader.getResourceAsStream(ASURLClassLoader.java:936)
at org.jppf.utils.VersionUtils.createVersionInfo(VersionUtils.java:59)
at org.jppf.utils.VersionUtils.(VersionUtils.java:42)
at org.jppf.client.AbstractJPPFClient.(AbstractJPPFClient.java:97)
at org.jppf.client.AbstractGenericClient.(AbstractGenericClient.java:87)
at org.jppf.client.JPPFClient.(JPPFClient.java:61)
bug_report_tiny.png 16:52  Bug report JPPF-524 - Stream isn't closed properly in org.jppf.utils.VersionUtils#createVersionInfo
igor : 'JPPF 5.1.6' added
January 04, 2018
bug_report_tiny.png 13:38  Bug report JPPF-523 - nullpointer in org.jppf.utils.SystemUtils.addOtherSystemProperties
lolocohen : Issue closed
bug_report_tiny.png 13:38  Bug report JPPF-523 - nullpointer in org.jppf.utils.SystemUtils.addOtherSystemProperties
lolocohen : Status changed: New ⇒ Closed
bug_report_tiny.png 13:38  Bug report JPPF-523 - nullpointer in org.jppf.utils.SystemUtils.addOtherSystemProperties
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
bug_report_tiny.png 13:38  Bug report JPPF-523 - nullpointer in org.jppf.utils.SystemUtils.addOtherSystemProperties
lolocohen : lolo4j ⇒ Not being worked on
January 02, 2018
bug_report_tiny.png 10:43  Bug report JPPF-523 - nullpointer in org.jppf.utils.SystemUtils.addOtherSystemProperties
lolocohen : Description updated
bug_report_tiny.png 10:41  Bug report JPPF-523 - nullpointer in org.jppf.utils.SystemUtils.addOtherSystemProperties
lolocohen : Assignee changed: lolo4j
January 01, 2018
bug_report_tiny.png 22:54  Bug report JPPF-523 - nullpointer in org.jppf.utils.SystemUtils.addOtherSystemProperties
subes : Issue created
The following NullpointerException is thrown:
2018-01-01 21:46:26,498 [ |JPPF Client-0001 ] ERROR org.jppf.client.balancer.JobManagerClient.addConnection - Error while adding connection p://invesdwin.de:5532-1[invesdwin.de:5532] : NEW
java.lang.NullPointerException: null
at java.util.Hashtable.put(Hashtable.java:460)
at java.util.Properties.setProperty(Properties.java:166)
at org.jppf.utils.SystemUtils.addOtherSystemProperties(SystemUtils.java:124)
at org.jppf.utils.SystemUtils.getSystemProperties(SystemUtils.java:101)
at org.jppf.management.JPPFSystemInformation.populate(JPPFSystemInformation.java:282)
at org.jppf.management.JPPFSystemInformation.(JPPFSystemInformation.java:107)
at org.jppf.management.JPPFSystemInformation.(JPPFSystemInformation.java:83)
at org.jppf.client.balancer.ChannelWrapperRemote.(ChannelWrapperRemote.java:68)
at org.jppf.client.balancer.JobManagerClient.addConnection(JobManagerClient.java:198)
at org.jppf.client.balancer.JobManagerClient$3.connectionAdded(JobManagerClient.java:139)
at org.jppf.client.AbstractJPPFClient.fireConnectionAdded(AbstractJPPFClient.java:307)
at org.jppf.client.AbstractGenericClient.newConnection(AbstractGenericClient.java:328)
at org.jppf.client.AbstractGenericClient.submitNewConnection(AbstractGenericClient.java:311)
at org.jppf.client.AbstractGenericClient$4.run(AbstractGenericClient.java:263)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
This is caused by a system property "jmockit-instrumentation" with value . A proper fix would be to ignore null values when adding other properties:

private static void addOtherSystemProperties(final TypedProperties props) {
try {
// run as privileged so we don't have to set write access on all properties in the security policy file.
Properties sysProps = AccessController.doPrivileged(new PrivilegedAction() {
@Override
public Properties run() {
return System.getProperties();
}
});
Enumeration en = sysProps.propertyNames();
while (en.hasMoreElements()) {
String name = (String) en.nextElement();
try {
''' if (!props.contains(name)) {'''
''' Object value = System.getProperty(name);'''
''' if(value != null) {'''
''' props.setProperty(name, value);'''
''' }'''
''' }'''
} catch(SecurityException e) {
if (debugEnabled) log.debug(e.getMessage(), e);
else log.info(e.getMessage());
}
}
} catch(SecurityException e) {
if (debugEnabled) log.debug(e.getMessage(), e);
else log.info(e.getMessage());
}
}
bug_report_tiny.png 22:54  Bug report JPPF-523 - nullpointer in org.jppf.utils.SystemUtils.addOtherSystemProperties
subes : 'JPPF 5.2.8' added
December 07, 2017
icon_milestone.png 07:30 JPPF 5.1.1
A new milestone has been reached
December 02, 2017
icon_milestone.png 02:53 JPPF 5.0.5
A new milestone has been reached
November 28, 2017
enhancement_tiny.png 13:55  Enhancement JPPF-522 - Enhancements to the pluggable view sample
lolocohen : Issue closed
enhancement_tiny.png 13:55  Enhancement JPPF-522 - Enhancements to the pluggable view sample
lolocohen : Status changed: New ⇒ Closed
enhancement_tiny.png 13:55  Enhancement JPPF-522 - Enhancements to the pluggable view sample
lolocohen : Resolution changed: Not determined ⇒ RESOLVED
enhancement_tiny.png 13:55  Enhancement JPPF-522 - Enhancements to the pluggable view sample
lolocohen : lolo4j ⇒ Not being worked on
enhancement_tiny.png 09:00  Enhancement JPPF-522 - Enhancements to the pluggable view sample
lolocohen : Description updated
enhancement_tiny.png 09:00  Enhancement JPPF-522 - Enhancements to the pluggable view sample
lolocohen : Description updated
enhancement_tiny.png 08:59  Enhancement JPPF-522 - Enhancements to the pluggable view sample
lolocohen : Assignee changed: lolo4j
enhancement_tiny.png 08:59  Enhancement JPPF-522 - Enhancements to the pluggable view sample
lolocohen : Issue created
Currently, the sample view displays job dispatch/return events as "job x dispatched to node y". We propose to add the following missing information:
* the drivers which dispatches or to which the job is returned
* whether the node is a real node or a peer driver seen as a node
The display would then look like:
* for a dispatch event: "job x dispatched to {node | peer node} y by driver z"
* for a returned event: "job x returned from {node | peer node} y to driver z"
enhancement_tiny.png 08:59  Enhancement JPPF-522 - Enhancements to the pluggable view sample
lolocohen : 'JPPF 5.2.8' added
October 20, 2017
bug_report_tiny.png 09:17  Bug report JPPF-521 - Document the "jppf.node.provisioning.master.uuid" configuration property
lolocohen : Assignee changed: lolo4j
bug_report_tiny.png 09:16  Bug report JPPF-521 - Document the "jppf.node.provisioning.master.uuid" configuration property
lolocohen : Issue created
The "jppf.node.provisioning.master.uuid" property, also represented as [http://jppf.org/javadoc/5.2/org/jppf/utils/configuration/JPPFProperties.html#PROVISIONING_MASTER_UUID '''JPPFProperties.PROVISIONING_MASTER_UUID'''] in the configuration API is a property that is only set on slave nodes and contains the UUID of the master node that started them.

It appears this property is only documented in the Javadoc and nowhere else. We should add something about it in the [http://www.jppf.org/doc/5.2/index.php?title=Node_provisioning '''provisioning'''] documentation.
August 10, 2017
icon_build.png 10:00 JPPF 5.2.8
New version released
June 12, 2017
icon_build.png 10:00 JPPF 5.2.7
New version released
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
Show moreaction_add_small.png