On Sat, Feb 20, 2010 at 10:59 PM, Emmanuel Lecharny elecha...@gmail.com wrote:
is there any reason why this stupid Hudson *always* fail when we commit some
new code, and one hour later come back with again 6 useless mails telling us
that Hey, sorry, I was totally f*cked up last time I sent you
Ok, guys,
sorry for my overreaction...
Sure we have to check what's going on with the builds.
If we look at the build history, we see that we don't have that many
failures. The problem is that those failures seems to be time-dependent.
The JDK 1.6/Windows build are also in constant failure,
Opened SSHD-76 with more info.
Thanks,
Bernd
On Fri, Feb 19, 2010 at 18:05, Guillaume Nodet gno...@gmail.com wrote:
I'm not aware of any problem like that.
Are you connecting to a native ssh server or the one from SSHD ?
Also could you try to set the log level to DEBUG on the client side
On Sun, Feb 21, 2010 at 1:23 PM, Julien Vermillard
jvermill...@archean.fr wrote:
Sounds like you are pissed now, try to breath ;)
I'm agree for releasing 2.0 now.
+1
/niklas
Hi guys,
I know this will not be the perfect version, but it's not that bad. We
have some pending issues that can probably be fixed in a 2.0.1 or later,
but the base services are pretty much correctly covered.
Here are the currently pending issues :
DIRMINA-539 : Pb on TraficClass for datagram
[X] +1, yes get 2.0 out now
On Mon, Feb 22, 2010 at 4:17 AM, Emmanuel Lecharny elecha...@gmail.com wrote:
Hi guys,
I know this will not be the perfect version, but it's not that bad. We have
some pending issues that can probably be fixed in a 2.0.1 or later, but the
base services are pretty
On Mon, Feb 22, 2010 at 1:12 PM, Emmanuel Lecharny elecha...@gmail.com wrote:
Some thoughts about how to manage Idle sessions :
In order to manage idle sessions, we should use a separated thread which
will check periodically that the session has been used or not. We use a
boolean flag which
