Build failed in Jenkins: river-qa-refactor-solaris #4

See Changes: [peter_firmstone] After considerable testing using a multi threaded Executor and Runnable tasks to CAS an AtomicLong to generate 100% cpu load, no data races were found, it is suspected that Object.wait is subject

Re: Build failed in Jenkins: river-qa-refactor-win #34

That proves wait returning early wasn't the problem. - Original message - > See > > Changes: > > [peter_firmstone] After considerable testing using a multi threaded > Executor and Runnable tasks to CAS an AtomicLong to gene

Re: VOTE: add Startable to Jini specification

People may also find the following interesting: http://www.azulsystems.com/blog/cliff/2011-10-17-writing-to-final-fields-via-reflection Regards, Peter. - Original message - > > On Dec 20, 2013, at 2:49 PM, Dan Creswell wrote: > > > > BUT > > > > The critical aspect is not releasing

Build failed in Jenkins: river-qa-refactor-win #35

See -- Started by an SCM change Building remotely on windows1 in workspace Cleaning local Directory trunk java.io.IOException: remote file op

Build failed in Jenkins: river-qa-refactor-win #34

See Changes: [peter_firmstone] After considerable testing using a multi threaded Executor and Runnable tasks to CAS an AtomicLong to generate 100% cpu load, no data races were found, it is suspected that Object.wait is subject to

Re: svn commit: r1553097 - in /river/jtsk/skunk/qa_refactor/trunk: qa/src/com/sun/jini/qa/harness/ qa/src/com/sun/jini/test/impl/norm/ qa/src/com/sun/jini/test/impl/outrigger/notify/ qa/src/com/sun/ji

Thanks Gregg. On 24/12/2013 3:04 AM, Gregg Wonderly wrote: The value for “now” needs to be reestablished in the loop, or else this loop will wait too long on a spurious wake up. Gregg On Dec 23, 2013, at 5:52 AM, peter_firmst...@apache.org wrote: Author: peter_firmstone Date: Mon Dec 23 11:

Re: VOTE: add Startable to Jini specification

On Dec 20, 2013, at 2:49 PM, Dan Creswell wrote: > > BUT > > The critical aspect is not releasing the reference to an object to another > thread before construction completes but that other thread READING that > final variable using that reference before construction is complete. > > i.e. ther

Re: Expected behavior on the remote service when the local caller is interrupted? Should the remote method be interrupted as well?

This is one of the places where a lease could help. An extension of the existing JERI details could add a lease into the dispatcher layer so that a constant “I am here” message would come through to the service. If the client thread is interrupted it would no longer be pinging/notifying of it’

Re: svn commit: r1553097 - in /river/jtsk/skunk/qa_refactor/trunk: qa/src/com/sun/jini/qa/harness/ qa/src/com/sun/jini/test/impl/norm/ qa/src/com/sun/jini/test/impl/outrigger/notify/ qa/src/com/sun/ji

The value for “now” needs to be reestablished in the loop, or else this loop will wait too long on a spurious wake up. Gregg On Dec 23, 2013, at 5:52 AM, peter_firmst...@apache.org wrote: > Author: peter_firmstone > Date: Mon Dec 23 11:52:40 2013 > New Revision: 1553097 > > URL: http://svn.apa

Build failed in Jenkins: river-qa-refactor-jdk7 #133

See -- [...truncated 198 lines...] at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 32 more Caused by: svn: E175002: OPTIONS reques

Jenkins build is back to normal : river-qa-refactoring #132

See

Build failed in Jenkins: river-qa-refactor-win3 #11

See Changes: [peter_firmstone] After considerable testing using a multi threaded Executor and Runnable tasks to CAS an AtomicLong to generate 100% cpu load, no data races were found, it is suspected that Object.wait is subject to