https://www.jppf.org:443/tracker/tbg/ JPPF issue tracking and project management en-us https://www.jppf.org:443/tracker/tbg/header.png https://www.jppf.org:443/tracker/tbg/ Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-160 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-160 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-186 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-186 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-199 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-199 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-140 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-140 (a java.util.concurrent.ThreadPoolExecutor$Worker) "AWT-EventQueue-0" prio=6 tid=0x000000000ad17800 nid=0xe20 waiting for monitor entry [0x000000000e53e000] java.lang.Thread.State: BLOCKED (on object monitor) at java.awt.Component.invalidate(Component.java:2916) - waiting to lock (a java.awt.Component$AWTTreeLock) at java.awt.Container.invalidate(Container.java:1580) at javax.swing.JComponent.revalidate(JComponent.java:4851) at javax.swing.plaf.basic.BasicTextUI$RootView.preferenceChanged(BasicTextUI.java:1406) at javax.swing.text.View.preferenceChanged(View.java:289) at javax.swing.text.PlainView.updateDamage(PlainView.java:554) at javax.swing.text.PlainView.insertUpdate(PlainView.java:451) at javax.swing.plaf.basic.BasicTextUI$RootView.insertUpdate(BasicTextUI.java:1602) at javax.swing.plaf.basic.BasicTextUI$UpdateHandler.insertUpdate(BasicTextUI.java:1861) at javax.swing.text.AbstractDocument.fireInsertUpdate(AbstractDocument.java:202) at javax.swing.text.AbstractDocument.handleInsertString(AbstractDocument.java:749) at javax.swing.text.AbstractDocument.insertString(AbstractDocument.java:708) at javax.swing.text.PlainDocument.insertString(PlainDocument.java:130) at javax.swing.text.AbstractDocument.replace(AbstractDocument.java:670) at javax.swing.text.JTextComponent.setText(JTextComponent.java:1718) at org.jppf.ui.options.TextAreaOption$1.run(TextAreaOption.java:118) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:701) at java.awt.EventQueue.access$000(EventQueue.java:102) at java.awt.EventQueue$3.run(EventQueue.java:662) at java.awt.EventQueue$3.run(EventQueue.java:660) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:671) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:244) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:163) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:147) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:139) at java.awt.EventDispatchThread.run(EventDispatchThread.java:97) Locked ownable synchronizers: - None]]> Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-148 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-148 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-164 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-164 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-172 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-172 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-189 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-189 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-138 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-138 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-145 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-145 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-151 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-151 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-162 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-162 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-179 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-179 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-200 java.lang.NegativeArraySizeException at org.jppf.io.MultipleBuffersLocation.(MultipleBuffersLocation.java:70) at org.jppf.io.IOHelper.createDataLocationMemorySensitive(IOHelper.java:74) at org.jppf.server.nio.AbstractNioMessage.readNextObject(AbstractNioMessage.java:155) at org.jppf.server.nio.AbstractNioMessage.read(AbstractNioMessage.java:106) at org.jppf.server.nio.nodeserver.AbstractNodeContext.readMessage(AbstractNodeContext.java:232) at org.jppf.server.nio.nodeserver.WaitingResultsState.performTransition(WaitingResultsState.java:69) at org.jppf.server.nio.nodeserver.WaitingResultsState.performTransition(WaitingResultsState.java:1) at org.jppf.server.nio.StateTransitionTask.run(StateTransitionTask.java:82) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) This is due to a limitation in the communication protocol between node and server. Each message between node and server is made of serialized objects, where each serialized object is preceded by an integer that determines its size. When the size is > 2GB, there is an integer overflow which can cause the node to write, and the server to raed, a negative size. I also see that this causes the server to disconnect form the node, and resubmiit the task to the same or another node, thus the job never terminates. The same kind of issue would occur between client and server and needs to be addressed as well.]]> Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-157 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-157 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-166 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-166 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-174 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-174 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-185 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-185 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-198 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-198 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-139 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-139 (a java.util.concurrent.locks.ReentrantLock$NonfairSync) 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.nio.StateTransitionManager.transitionChannel(StateTransitionManager.java:122) at org.jppf.server.nio.StateTransitionManager.transitionChannel(StateTransitionManager.java:108) at org.jppf.server.nio.classloader.ClassContext.processRequests(ClassContext.java:200) - locked (a org.jppf.server.nio.classloader.ClassContext) at org.jppf.server.nio.classloader.ClassContext.addRequest(ClassContext.java:189) at org.jppf.server.nio.classloader.node.WaitingNodeRequestState.processDynamic(WaitingNodeRequestState.java:186) at org.jppf.server.nio.classloader.node.WaitingNodeRequestState.processResource(WaitingNodeRequestState.java:102) at org.jppf.server.nio.classloader.node.WaitingNodeRequestState.performTransition(WaitingNodeRequestState.java:77) at org.jppf.server.nio.classloader.node.WaitingNodeRequestState.performTransition(WaitingNodeRequestState.java:37) at org.jppf.server.nio.StateTransitionTask.run(StateTransitionTask.java:82) - locked (a org.jppf.server.nio.SelectionKeyWrapper) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Two users also reported a similar deadlock, for which I'm attaching the related thread dumps]]> Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-147 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-147 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-163 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-163 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-171 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-171 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-180 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-180 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-188 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-188 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-203 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-203 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-142 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-142 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-150 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-150 Sat, 27 Dec 2014 07:01:48 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-207 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-207 Sat, 27 Dec 2014 07:01:48 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-248 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-248 Sat, 14 Mar 2015 09:30:41 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-377 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-377 Sat, 15 Oct 2022 22:42:38 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-154 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-154 Sat, 15 Oct 2022 22:42:38 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-153 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-153 Sat, 28 Jan 2023 08:21:10 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-169 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-169 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-168 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-168 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-178 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-178 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-183 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-183 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-141 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-141 Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-149 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-149 (); The link is made by the common Long value. This is very inefficient and the 2 maps should be merged into a single one: protected final Map>(); This will also simplify the code maintaining the associations. 2) We use an Executor to execute the tasks but still use Object.wait() and Object.notify() to synchronize on the completion of a task bundle. This could be much simplified by using an ExecutorCompletionService on top of the executor and receiving the results asynchronously until they're all recieved. 3) The synchronization within NodeExecutionManagerImpl is too broad. Instead of using synchronized method we shoudl use more granular synchronization on specific objects on which cocurrency applies: synchronized(futureMap) { // ... do some stuff ... }]]> Sat, 27 Dec 2014 06:59:33 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-118 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-118 Sun, 16 Oct 2022 00:46:46 +0200 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-187 https://www.jppf.org:443/tracker/tbg/jppf/issues/JPPF-187