Very interesting, I didn't know about the negative value being an
option; don't replace all occurrences though as in some cases
System.currentTimeMillis() is more appropriate, you can find some
interesting discussions here:
http://lists.jboss.org/pipermail/infinispan-dev/2011-October/009277.html
I
On 10/09/14 13:58, Alan Field wrote:
> Hey Bela,
>
>> Just a quick heads up. I'm currently working on
>> https://issues.jboss.org/browse/JGRP-1877, which it critical as it
>> may: - cause RPCs to return prematurely (possibly with a
>> TimeoutException), or - cause RPCs to blocks for a long time (
Yep - meanwhile I just search for System.currentTimeMillis() and
System.nanoTime().
On 10/09/14 14:45, Romain Pelisse wrote:
> Given the pattern of it, I might be able to produce a PMD checks for
> this. This way, you could run it across the code base and check for all
> occurences of it.
>
> On
Given the pattern of it, I might be able to produce a PMD checks for this.
This way, you could run it across the code base and check for all
occurences of it.
On 10 September 2014 13:58, Alan Field wrote:
> Hey Bela,
>
> > Just a quick heads up. I'm currently working on
> > https://issues.jboss.
Hey Bela,
> Just a quick heads up. I'm currently working on
> https://issues.jboss.org/browse/JGRP-1877, which it critical as it may:
> - cause RPCs to return prematurely (possibly with a TimeoutException), or
> - cause RPCs to blocks for a long time (pick which one is worse :-))
How frequently c
Just a quick heads up. I'm currently working on
https://issues.jboss.org/browse/JGRP-1877, which it critical as it may:
- cause RPCs to return prematurely (possibly with a TimeoutException), or
- cause RPCs to blocks for a long time (pick which one is worse :-))
This is due to my misunderstanding
