The investigation that revealed problems in outrigger's FastList and
some of the corresponding test code started from a single failure of a
QA test that usually runs correctly. The failure did not reproduce with
the test as currently checked in. To investigate, I had to drastically
increase the
On 2/10/2011 3:22 PM, Dan Creswell wrote:
...
So I would say, add the more stressful versions and don't worry about the
time to test too much equally, don't expect to surface all concurrency bugs
this way.
...
Indeed, the next question is what to do about cases where I strongly
suspect a concu
On 2/9/2011 2:40 AM, Sim IJskes - QCG wrote:
Sim IJskes +1
Jeff Ramsdale -1
Patricia Shanahan -1
Greg Trasuk -1
Peter Firmstone -1
Tom Hobbs -1
Dan Creswell -1
Do these "TALLY" messages close the vote, or does it need to run for
more time?
Patricia
Sim IJskes - QCG wrote:
On 11-02-11 13:34, Benson Margulies wrote:
Holding a formal vote as a way of discovering (e.g. spelunking,
humorously) whether a consensus exists is fine. My point, such as it
was, is that once you have a supply of -1 votes, you're really done.
It doesn't matter exactly h
Sim IJskes - QCG wrote:
On 11-02-11 15:17, Patricia Shanahan wrote:
there is considerable opposition to dropping Java 5 support at this
time. The real question is whether we had allowed long enough for anyone
who objected to dropping 1.4 to say so. I think we have.
I do too. How do we proceed
I have rerun the RIVER-391 failing test, the enhanced version of
com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td,
with just the fixes for the synchronization idiom in the QA code. It has
not yet failed.
That means that the only evidence I have of failures in the outrigger
anything in the JIRA ticket or the code to tell me -
getting old, probably blind and missed it).
On 13 February 2011 09:16, Dan Creswell wrote:
Test program looks fine.
I'd like to know which JDK's you've run the test on so far please?
On 13 February 2011 00:34, Patricia Shanahan
On 2/13/2011 8:16 AM, Dan Creswell wrote:
On 13 February 2011 12:31, Patricia Shanahan wrote:
Thanks for looking at the code.
No worries - concurrency is a favourite topic of mine :)
Excellent. Perhaps you could also review my substitute FastList
implementation. It is in my skunk
On 2/13/2011 8:54 AM, Patricia Shanahan wrote:
On 2/13/2011 8:16 AM, Dan Creswell wrote:
On 13 February 2011 12:31, Patricia Shanahan wrote:
...
Alarmingly, an overnight repeated run of the QA test did not get any
FastList failures, but did get an unrelated NullPointerException from
I like this general idea. I have been becoming more and more concerned
that doing everything through moving code around is, in several ways, a
problem rather than an advantage.
I see the movable code idea as being most powerful for providing
versions of services that reduce communication cost
Thanks for your comments.
I realized I made a mistake when I had to reboot the VirtualBox, and the
second failure was also with the OpenJDK Client VM. I'm rerunning the
test now, but it is one failure every few hours.
On 2/16/2011 8:32 PM, Peter Firmstone wrote:
The code in ObjectOutputStrea
On 2/16/2011 9:48 PM, Patricia Shanahan wrote:
I realized I made a mistake when I had to reboot the VirtualBox, and the
second failure was also with the OpenJDK Client VM. I'm rerunning the
test now, but it is one failure every few hours.
I've now collected over 24 hours of continuo
only show
up with one JRE, or is a bug in the JRE.
Based on my analysis, I suspect the latter, in which case I should close
the JIRA and go on to something else.
Patricia
On 2/18/2011 12:37 AM, Dan Creswell wrote:
Yes, it could be JDK specific
On 17 February 2011 23:49, Patricia Sha
I'm converting my own informal tests of my FastList implementation into
a JUnit test that can be checked in for regression testing. Can I use
JUnit 4, or are we limited to JUnit 3?
Patricia
I want to get going on some performance tuning, but believe it is best
guided and controlled by well-organized benchmarks. To that end, I
propose adding a place for benchmarks to the River structure.
We will need several categories of benchmark code:
1. System level benchmarks. These benchmark
On 2/22/2011 12:16 AM, Peter Firmstone wrote:
Patricia Shanahan wrote:
I want to get going on some performance tuning, but believe it is best
guided and controlled by well-organized benchmarks. To that end, I
propose adding a place for benchmarks to the River structure.
We will need several
On 2/23/2011 6:26 PM, Peter Firmstone wrote:
Patricia Shanahan wrote:
On 2/22/2011 12:16 AM, Peter Firmstone wrote:
Patricia Shanahan wrote:
I want to get going on some performance tuning, but believe it is best
guided and controlled by well-organized benchmarks. To that end, I
propose adding
On 2/27/2011 11:19 PM, Peter Firmstone wrote:
Patricia Shanahan wrote:
On 2/23/2011 6:26 PM, Peter Firmstone wrote:
Patricia Shanahan wrote:
On 2/22/2011 12:16 AM, Peter Firmstone wrote:
Patricia Shanahan wrote:
I want to get going on some performance tuning, but believe it is
best
guided
Dennis Reedy wrote:
On Feb 28, 2011, at 1247AM, Patricia Shanahan wrote:
How would you propose handling a case like outrigger.FastList?
It is package access only, so changing its interface to the rest of outrigger
did not affect any public API. Several classes needed to be changed to handle
Dan Creswell wrote:
On 28 February 2011 14:50, Patricia Shanahan wrote:
Dennis Reedy wrote:
On Feb 28, 2011, at 1247AM, Patricia Shanahan wrote:
How would you propose handling a case like outrigger.FastList?
It is package access only, so changing its interface to the rest of
outrigger
Gregg Wonderly wrote:
...
Can you help me understand why multiple builds are not working? It just
seems to me that you'd build the existing code "once" to test, and then
iterate through your development practices to work on your "Experiment",
testing with that output as you go.
...
Performan
On 2/28/2011 1:38 PM, Peter wrote:
Hmm valuable insight into the future based on past experience.
Alternate code snippets sitting on the performance shelf need to be compilable
in their own right don't they?
But as you've mentioned, fastlist and its replacement, don't share a common
interface
Yup, my original idea was to have a separate directory structure for
this sort of thing, and rename classes in it for convenience. I was
thinking of putting in a readme.txt describing the mapping to the real
name for each source file that is in use in the trunk. For example, the
recently checke
Peter wrote:
Trunk's not quite ready for branching & release yet, but it is close.
Just waiting for people to finish recent work, then I'll cut the
release. This includes Patricia's outrigger improvements and Sim's
new configuration builder.
The only remaining action on my Outrigger work that
On 3/2/2011 6:51 AM, Patricia Shanahan wrote:
Peter wrote:
Trunk's not quite ready for branching & release yet, but it is close.
Just waiting for people to finish recent work, then I'll cut the
release. This includes Patricia's outrigger improvements and Sim's
new conf
On 3/4/2011 3:47 AM, Tom Hobbs (JIRA) wrote:
- Block the write method call until the RS is happy the entry is persisted
safely
Could you define what you mean by "persisted safely"? Do you count
getting it to non-volatile storage, or does it need to be stored on
multiple servers? If the tr
On 3/4/2011 4:06 AM, Cees de Groot (JIRA) wrote:
...
It's probably obvious, but a commercial resilient implementation is available
(GigaSpaces), and the ideas they implemented are pretty straightforward. It might prove
as "inspiration" :-)
...
Are there any copyright issues in looking at Giga
mistic writing" etc that I mentioned in the space
Without understanding more about how the thing will/might be used I'm
less inclined to start thinking about how to build it.
But like I said in the Jira, these things are what I naively think are
important - that doesn't mean that I didn&
On 3/5/2011 7:14 AM, Niclas Hedhman wrote:
On Sat, Mar 5, 2011 at 5:55 PM, Dan Creswell wrote:
Transactions don't actually matter in any of the above as they are just
another form of operation boundary. Transactions are "durable":
"The results of a transaction should be as persistent as the en
My next step on the distributed, fault tolerant transaction management
issue will be to wrote an annotated bibliography. Designing and proving
correctness of protocols and algorithms in this area is not easy, so it
is worth some reading and library search time to make sure we benefit
from all a
On 3/9/2011 11:16 AM, Tom Hobbs wrote:
Hi Patricia,
The basic rule is, if you're the first person doing it, then you get
to chose. And as you say, the result will be in a format that
everyone can read and see. I assume that your "left to myself" bit
describes a fairly standard way of doing thi
I know nothing about Lyx, so I'll have to look into it. What format does
it keep its files in?
Patricia
On 3/9/2011 1:32 PM, Peter Firmstone wrote:
For people who don't know TeX, it might be possible to use Lyx?
Peter.
Patricia Shanahan wrote:
On 3/9/2011 11:16 AM, Tom Hobbs
Makefiles... :-)
Chris
-Original Message-
From: Patricia Shanahan [mailto:p...@acm.org]
Sent: Wednesday, March 09, 2011 3:49 PM
To: dev@river.apache.org
Subject: Re: Bibliography format question
I know nothing about Lyx, so I'll have to look into it. What format does
it keep its files in?
I've started writing an annotated bibliography for background reading on
fault tolerance for River developers. It is checked in to
http://svn.apache.org/viewvc/river/jtsk/skunk/patsFaultTolerance. The
check-in includes the generated .pdf file, so that anyone can read it
even if they are not set
We have a SPARC-only QA failure that I'm willing to take a look at if
Peter sets up an account for me. Otherwise, I'm looking ahead to work on
fault tolerance.
Patricia
On 3/29/2011 2:25 PM, Tom Hobbs wrote:
Hi guys,
Everything's been a bit quiet recently. I was just wonder what (if
anythi
On 3/31/2011 5:41 PM, Niclas Hedhman wrote:
On Wed, Mar 30, 2011 at 5:48 AM, Jason Pratt wrote:
please don't release anything with failures. i've been a big fan/user of
jini since it was released. now that it is alive again via river, a good
release history will be key to success/survival
Ass
What is the definition of "new"? Remember we added a lot of QA tests
that were not being run previously, so for most QA tests we do not know
whether they would have passed on an earlier release.
If we can define "new" as being since some specific subversion
check-out, we can build that on a SP
On 4/1/2011 12:27 PM, Jason Pratt wrote:
i am stating that the first "graduated" release should work for everyone
period. after that if you want to release with known bugs and reduce/not
support sparc or whatever other platform you in your infinite wisdom deem
irrelevant , great. river should hav
In reviewing the code prior to applying the patch, I noticed the
following in the LookupDiscoveryListener.Notifier.run() method:
try {
loc = regs[i].getLocator();
} catch (Throwable ex) { /* ignore */ }
What do people think about ignoring Throwable?
Chris, Thanks for the patch. Do you happ
from dealing
in a faulty ServiceRegistrar that shouldn't ultimately disrupt the discovery
process.
Cheers,
Dan.
On 3 April 2011 04:35, Patricia Shanahan wrote:
In reviewing the code prior to applying the patch, I noticed the
following in the LookupDiscoveryListener.Notifier.run() me
I understand Tom's feeling against just logging, but I think it is
probably the best option for now. Once we log, we should be able to find
out if this is an issue, and if there are cases that are happening that
would benefit from some other action.
My really strong objection is to *silently*
I'm having a lot of trouble making up my mind about this. I understand
your comment, but here is the other side of it.
FINEST logging means that someone really wants to find out what is going
on in this area, probably because it may be involved in some bug.
As the code is now, the only indica
On 4/8/2011 7:18 PM, Greg Trasuk wrote:
Alternately, does someone know the correct svn incantation to point my
working directory at the new repository, then commit?
svn switch https://svn.apache.org/repos/asf/river/jtsk/trunk
--- Begin Message ---
Hi,
On Tue, Feb 8, 2011 at 12:22 AM, Jukka Zi
I've reviewed the proposed patch for
https://issues.apache.org/jira/browse/RIVER-395, and I think it should
be incorporated in the release. I'm working on a QA test for it, but
could check it in untested if you like.
Patricia
On 4/10/2011 1:09 PM, Tom Hobbs wrote:
Hi guys,
So including the
Although I'm taking time out to deal with the RIVER-395 patch, my main
River activity is educating myself about fault tolerant transactions, by
reading papers on the subject. That does not produce much in the way of
immediately visible results, but may be very useful in the long term.
Patricia
On 4/11/2011 7:59 AM, Christopher Dolan wrote:
...
These conditions are hard to reproduce in a typical lab, because they
require large numbers of machines and deliberately misconfigured DNS.
I'd appreciate any thoughts that others have about Reggie scaling
issues.
...
I can't comment on the spe
On 4/13/2011 9:56 AM, Christopher Dolan wrote:
...
Putting the loaderTable access in the "synchronized (key)" block means
that the HashMap can be modified from multiple threads. It seems to me
that you must either change the loaderTable to be some other kind of
concurrent map, or redo the lockin
I'm attempting to construct QA tests for the RIVER-395 by copying
existing tests of event delivery and adding a special listener that
throws exceptions. If the patch is correct, the modified test should
pass with all expected events going to the existing listeners despite
the exceptions.
I'm
it
doesn't seem possible to mock any of the providers, so to test it you
need an actual registrar, it appears.
For what it's worth, today I wrote my own private test that runs in my
djinn and verified the patch.
Chris
-Original Message-
From: Patricia Shanahan [mailto:p...@acm
the chances of finding any other notifyListener
type methods that have not been hardened.
Patricia
On 4/15/2011 11:45 AM, Patricia Shanahan wrote:
Thanks for looking at this. I agree with you about the impenetrability
of the test code - that is why I'm working by modifying existing te
Is it possible to check whether the QA tests have been run on the head
revision of River?
I made a copy for work on River-395, and am getting errors running
discovery-related QA tests against the unmodified code. The tests I'm
running are
locatordiscovery,discoverymanager,lookupdiscovery,serv
Running the same tests on the same version in a different virtual
machine works, so I think there must have been some left-over from a
previous failed run.
Patricia
On 4/20/2011 10:57 AM, Patricia Shanahan wrote:
Is it possible to check whether the QA tests have been run on the head
It makes the question non-urgent.
On 4/20/2011 10:42 PM, Tom Hobbs wrote:
Does that answer your question then?
The best guys to ask about the build are probably Jonathan, Sim or Peter.
Not heard from them for a while though.
On 21 Apr 2011 00:37, "Patricia Shanahan" wrote:
Runnin
I'll add them to my reading list. I've temporarily suspended reading
distributed transaction papers in favor of QA tests for the River-395 patch.
On 4/21/2011 2:14 AM, Tom Hobbs wrote:
I've found a bunch of links that might be useful when thinking about
distributed transactions and consistency.
st behavior and it
should be the caller's responsibility to catch their own broken
listener's exceptions.
Chris
P.S. sorry for the delay. I'm fresh back from vacation.
-----Original Message-
From: Patricia Shanahan [mailto:p...@acm.org]
Sent: Friday, April 15, 2011 5:46
This raises a more general question that has been troubling me: What
should we do about theoretical deadlocks and similar concurrency issues
that have not been demonstrated in practice?
On the one hand, I like to have a test to show that a change really
fixed something. On the other hand, a co
On 5/19/2011 12:32 PM, Tom Hobbs wrote:
Me again. I've decided to start a vote (you can always vote against!)
that we should do a release. I think that there's enough good stuff
already in the code base that our users aren't seeing specifically
because we've not released it.
I can't, off hand,
On 5/19/2011 12:29 PM, Tom Hobbs wrote:
...
Thoughts anyone?
...
I have a question. Should I start studying gradle at this time? There
are arguments both ways:
Pro: After learning about it, I might be able to contribute to
discussions of how to set up to use it.
Con: I have other stuff I
On 5/19/2011 3:31 PM, Jukka Zitting wrote:
Hi,
Is this a vote to have a vote on a release? ;-)
I interpreted it as a vote on a release, specifically "Release River
from current trunk".
Patricia
On 5/19/2011 6:29 PM, Jukka Zitting wrote:
Hi,
On Thu, May 19, 2011 at 6:12 PM, Patricia Shanahan wrote:
On 5/19/2011 3:31 PM, Jukka Zitting wrote:
Is this a vote to have a vote on a release? ;-)
I interpreted it as a vote on a release, specifically "Release River from
current trunk&
Attachments don't come through the mailing list. Could you upload it
somewhere, and post the link?
Patricia
On 5/22/2011 11:35 AM, Tom Hobbs wrote:
...
I've attached the report, does anyone have any idea what I'm supposed
to do with them?
...
On 5/21/2011 4:21 AM, Peter Firmstone wrote:
...
4. Have all committers add their signatures to the Keys file.
...
Do I need to get into the Apache web of trust? If so, any suggestions
for how to do it? I live in San Diego, but will be in London for a
couple of weeks later in the year.
Patr
On 6/1/2011 10:31 AM, James Grahn wrote:
...
I am now wondering: is the Gigaspaces code available? Under what
license? And is anyone there interested in contributing?
...
My understanding is that GigaSpaces is a commercial product, although a
limited version is available for free use. See
On 6/1/2011 6:19 PM, Peter Firmstone wrote:
The argument for generics in remote interfaces is to reduce boilerplate
code, the argument against is, it introduces unchecked type casts. (See
earlier discussion)
Is there another way to reduce the boilerplate code, using annotations
perhaps?
...
Co
On 6/2/2011 6:11 AM, James Grahn wrote:
On Thu, Jun 2, 2011 at 3:06 AM, Peter Firmstone
wrote:
Are you suggesting type safety is NOT a necessary language feature
in distributed code?
Not at all.
One of the big questions in O-O language design is the extent and timing
of type checking. At
Did people see that we are on the list of projects that need to clean up
incubator dist areas?
I'm afraid I won't be able to work on River this week. One of my former
adviser's students is finishing writing a paper based on my research,
and I need to spend all my computer science time this wee
Yes, it can be marked as fixed. I'm not satisfied with the state of
stress testing, but that should really be a separate issue.
Patricia
On Jun 6, 2011, at 8:40, Tom Hobbs wrote:
Can you give me a quick yes/no on if your Jira issue is fixed? It's
"RIVER-391 -Outrigger failure under stress"
It would have been helpful if the Apache web site had said *why* the
preferred names are preferred.
The command line user argument seems implausible to me.
I am a frequent command line user, but I would like "ls *.txt" to show
any license and similar files. I find it hard to imagine being both a
I'm available to work on River again. Is there something I can do to
contribute to getting the release out, given zero experience with Apache
release process?
Patricia
The early days of UNIX definitely suffered from developers acting as
though they had to pay for every character they typed. See command names
such as "ls" and "rm".
It may have been a reflection of use of paper-based terminals, such as
thermal printers, or of slow communication speeds. At 110 bau
ine, but it's always good to get others to check.
having said that, you might want to hold off some because Peter is going to
add some more things in and then I'll have to cut a new release.
Grammar and spelling have been sacrificed on the altar of messaging via
mobile device.
O
I'm working on the "Apache River Release Getting Started & More" page,
src-doc/static/info-index.html
I has several broken links. Some are easy to deal with - for example,
replacing incubator links with river.apache.org links.
How do you think we should handle references to jini.org and jini.
On 6/19/2011 9:21 PM, Peter Firmstone wrote:
Patricia Shanahan wrote:
...
We even have a link with title "starterkit-examples.jini.org (link
dead)". Unless someone can supply a working version of the link, I'm
going to delete the complete sentence.
The examples are now includ
On 6/26/2011 1:23 PM, Peter Firmstone wrote:
There's an interesting thread of discussion in the Porter mail archive
that Mark has uploaded for us (see River-311), relating to the TaskManager.
Here's a very interesting comment from Bob Scheifler:
Over the years we've been slowly eliminating use
On 6/26/2011 1:58 PM, Peter Firmstone wrote:
Patricia Shanahan wrote:
On 6/26/2011 1:23 PM, Peter Firmstone wrote:
There's an interesting thread of discussion in the Porter mail archive
that Mark has uploaded for us (see River-311), relating to the
TaskManager.
Here's a very i
On 6/26/2011 3:18 PM, Peter Firmstone wrote:
I think the way to look at this is to examine the non-trivial runAfter
implementations. If they have common elements that can be helped by some
utility classes, write those classes. If not, deal with each
individually.
We are now committed to 1.5, s
I downloaded the source, and tried a naive build on Windows XP, Cygwin.
I put a JDK 1.5 bin directory at the start of my path, and ran "ant
all.build". It failed with the following errors:
compile:
[javac] Compiling 1993 source files to C:\Documents and
Settings\Administrator\My
Documents
machines in my house!
Cheers,
Tom
Grammar and spelling have been sacrificed on the altar of messaging via
mobile device.
On 28 Jun 2011 04:42, "Patricia Shanahan" wrote:
I downloaded the source, and tried a naive build on Windows XP, Cygwin.
I put a JDK 1.5 bin directory at the
I think the problem may go deeper. sun.net.spi.nameservice.NameService
is a sun.net interface that can change from version to version. Is it
essential that we have our own implementation?
Patricia
On 6/28/2011 12:18 AM, Peter wrote:
Oops, I fixed that but didn't commit, sorry Not near my de
I've done a clean build with the classes in question deleted. It got a
"BUILD SUCCESSFUL". I'll start the QA tests that way, but I suggest
making that change. (I'm not checking in anything to the trunk right
now, to avoid risk of tripping up your efforts).
Patricia
On 6/29/2011 1:07 PM, Tom H
been around since the original Sun contribution, and the
log entries since then seem to be about the various reorganizations, so
I still don't know the purpose.
If this reminds anyone of any clues as to the purpose, please comment.
Patricia
On 6/29/2011 1:56 PM, Patricia Shanahan wr
something! Fingers cross on the QA
tests. I'm just about to sign off now, but please check the deletions
into the trunk if/when you're happy with them and I'll create some new
RCs.
If only all fixes were as simple.
On Wed, Jun 29, 2011 at 9:56 PM, Patricia Shanahan wrote:
I&#
I'm signing off for the night. Sill one failure.
Patricia
On 6/29/2011 8:56 PM, Patricia Shanahan wrote:
I got a QA test failure,
com/sun/jini/test/impl/reggie/MultihomedClientTest.td. The failure is
due to the missing
com.sun.jini.test.impl.reggie.NameServiceDescriptorImpl class.
ge -
I'm signing off for the night. Sill one failure.
Patricia
On 6/29/2011 8:56 PM, Patricia Shanahan wrote:
I got a QA test failure,
com/sun/jini/test/impl/reggie/MultihomedClientTest.td. The failure is
due to the missing
com.sun.jini.test.impl.reggie.NameServiceDescriptorImpl cla
On 6/30/2011 1:42 AM, Sim IJskes - QCG wrote:
On 30-06-11 10:12, Tom Hobbs wrote:
Actually, lets have a proper vote thread.
Release the artifacts 2.2.0 which can be found in
http://river.apache.org/~thobbs/river?
+1 Peter Firmstone
+1 Tom Hobbs
Grammar and spelling have been sacrificed on t
0 Jun 2011 14:12, "Patricia Shanahan" wrote:
On 6/30/2011 1:42 AM, Sim IJskes - QCG wrote:
On 30-06-11 10:12, Tom Hobbs wrote:
Actually, lets have a proper vote thread.
Release the artifacts 2.2.0 which can be found in
http://river.apache.org/~thobbs/river?
+1 Peter Firmstone
+1 Tom H
ends.
Patricia
On 6/30/2011 6:54 AM, Patricia Shanahan wrote:
The build is clean if the classes are removed. At least one QA test
fails. That is why I suggested as an alternative fix removing the two
classes and skipping the failing test.
Patricia
On 6/30/2011 6:32 AM, Tom Hobbs wrote:
In what sense does the qa suite require jdk1.6?
With the modification to change NameServiceImpl back to the 1.5
NameService interface, I just did a successful JDK1.5 "ant all.build".
Patricia
On 6/30/2011 12:25 AM, Peter wrote:
The qa suite needs to be considered separately from the main bui
I'm having trouble squaring this with the description of
ThreadPoolExecutor. If I'm reading it right, it *can* be initialized to
set a low limit on the maximum number of threads, but can equally well
be set to have up to Integer.MAX_VALUE threads, effectively unlimited.
There are two forms of Tas
On 6/30/2011 11:38 PM, Dan Creswell wrote:
On 1 July 2011 03:22, Gregg Wonderly wrote:
On 6/30/2011 9:02 PM, Patricia Shanahan wrote:
...
loadLevel permits specification of a ratio between threads and tasks, so
that threads are only created up to e.g. one third of the number of
tasks. I&#
ries and having a top
level release, and then produce 2.2.1 ASAP to clean up the loose ends.
Patricia
On 6/30/2011 6:54 AM, Patricia Shanahan wrote:
The build is clean if the classes are removed. At least one QA test
fails. That is why I suggested as an alternative fix removing the two
classes an
I've seen some discussion of using a separate JVM for security. Does it
also provide a solution to the problem of JVM migration in a
continuously operating River-based system?
Suppose the objective is to migrate from 1.5 to 1.6.
The first step would be to get each client and server into a stat
On 7/1/2011 1:14 PM, Gregg Wonderly wrote:
...
If the system throughput is not meeting my needs, I'll apply admission
controls, or "add hardware" to manage the issue. Anything else done by
river only serves as a "limit" that can be very frustrating to debug and
deal with.
I would like to make a
f not implementation) but allow users to swap in their own
task execution implementations that may or may not throttle in some way.
Just a thought.
Grammar and spelling have been sacrificed on the altar of messaging via
mobile device.
On 1 Jul 2011 21:29, "Patricia Shanahan" wrote:
On 7
Generally, tasks in the same TaskManager instance were all created by
the same object, and their class is, or could be, an inner class in that
object, and therefore they *could* talk to each through methods in that
object.
I'm not sure the current runAfter mechanism is right for all the uses to
w
On 7/7/2011 2:26 PM, Mike Sobolewski wrote:
I'm curious about why the load factor option is desirable. Suppose
you have 30 tasks waiting, and you have could afford 30 threads for
the function, then why not allow 30 threads? The load factor has
the effect of limiting the throughput even when you
I've read the document, and am thinking about its implications.
I am not a trademark enforcer. I have no training as a trademark
enforcer, and no interest in learning to be one. I did not understand
that joining the PMC meant becoming a trademark enforcer.
Patricia
On 7/19/2011 1:28 PM, Tom
On 7/31/2011 1:43 AM, Peter Firmstone wrote:
...
* TaskManager - improve concurrency and remove the dependency on
Task.runAfter() in River code.
...
I'm playing with implementing a subclass of ThreadPoolExecutor that
modifies the number of threads based on the mean number of tasks over
some r
I'm investigating extended ThreadPoolExecutor to get an Executor that
bases the number of threads on the mean number of tasks over an
interval. If successful, that would flatten out sudden peaks in the task
load, using the queue as a buffer, but would make the number of threads
match a sustaine
On 8/9/2011 1:44 PM, Greg Trasuk wrote:
On Tue, 2011-08-09 at 15:36, Patricia Shanahan wrote:
3. Use a dedicated thread that sleeps until it is time to reconsider the
number of tasks, processes the queue of log messages, does any
adjustment, and then goes back to sleep. This is the most
1 - 100 of 356 matches
Mail list logo
