Okay, the PacketSender resent-and-not-acked problem is probably caused by a
bug fixed in 1169. Unfortunately we will have to wait for most of the network
to update before this will make a big impact.
On Thursday 06 November 2008 02:43, Dennis Nezic wrote:
> > On Wed, 5 Nov 2008 22:00:52 +,
>
Okay, the PacketSender resent-and-not-acked problem is probably caused by a
bug fixed in 1169. Unfortunately we will have to wait for most of the network
to update before this will make a big impact.
On Thursday 06 November 2008 02:43, Dennis Nezic wrote:
> > On Wed, 5 Nov 2008 22:00:52 +,
>
On Wednesday 05 November 2008 02:09, Dennis Nezic wrote:
> > On Mon, 3 Nov 2008 14:58:08 +0100,
> > bqz69 wrote:
> >
> > I have almost the same problem - my freenet continues to shut down
> > several times a day, and I have to restart and get connected to open
> > net peers.
> >
> > I am using: B
> On Wed, 5 Nov 2008 22:00:52 +,
> Matthew Toseland wrote:
>
> It could very well be. Lack of memory resulting in constant garbage
> collection could easily cause a timeout.
I really don't think it's low memory. I increased
wrapper.java.maxmemory to 300, and even though only about 180MB is
be
> On Wed, 5 Nov 2008 22:00:52 +,
> Matthew Toseland <[EMAIL PROTECTED]> wrote:
>
> It could very well be. Lack of memory resulting in constant garbage
> collection could easily cause a timeout.
I really don't think it's low memory. I increased
wrapper.java.maxmemory to 300, and even though onl
On Wednesday 05 November 2008 02:09, Dennis Nezic wrote:
> > On Mon, 3 Nov 2008 14:58:08 +0100,
> > bqz69 <[EMAIL PROTECTED]> wrote:
> >
> > I have almost the same problem - my freenet continues to shut down
> > several times a day, and I have to restart and get connected to open
> > net peers.
> >
> On Mon, 3 Nov 2008 14:58:08 +0100,
> bqz69 wrote:
>
> I have almost the same problem - my freenet continues to shut down
> several times a day, and I have to restart and get connected to open
> net peers.
>
> I am using: Build #1168 r23201 and -ext Build #24 r 23199
My node also crashes many t
On Monday 03 November 2008 14:44, Jeff Isaac wrote:
> Hello all!
> I have recently stumbled across a problem with my node. I noticed that Frost
> was having trouble communicating the other day even though the node was
> running. Sure enough, the node (at the time 1167) was not connecting to any
> p
> On Mon, 3 Nov 2008 14:58:08 +0100,
> bqz69 <[EMAIL PROTECTED]> wrote:
>
> I have almost the same problem - my freenet continues to shut down
> several times a day, and I have to restart and get connected to open
> net peers.
>
> I am using: Build #1168 r23201 and -ext Build #24 r 23199
My node
On Monday 03 November 2008 14:44, Jeff Isaac wrote:
> Hello all!
> I have recently stumbled across a problem with my node. I noticed that Frost
> was having trouble communicating the other day even though the node was
> running. Sure enough, the node (at the time 1167) was not connecting to any
> p
On Monday 03 November 2008 14:44, Jeff Isaac wrote:
> Hello all!
> I have recently stumbled across a problem with my node. I noticed that Frost
> was having trouble communicating the other day even though the node was
> running. Sure enough, the node (at the time 1167) was not connecting to any
> p
On Monday 03 November 2008 15.44.10 Jeff Isaac wrote:
> Hello all!
> I have recently stumbled across a problem with my node. I noticed that
> Frost was having trouble communicating the other day even though the node
> was running. Sure enough, the node (at the time 1167) was not connecting to
> any
On Monday 03 November 2008 14:44, Jeff Isaac wrote:
> Hello all!
> I have recently stumbled across a problem with my node. I noticed that Frost
> was having trouble communicating the other day even though the node was
> running. Sure enough, the node (at the time 1167) was not connecting to any
> p
Hello all!
I have recently stumbled across a problem with my node. I noticed that Frost
was having trouble communicating the other day even though the node was
running. Sure enough, the node (at the time 1167) was not connecting to any
peers (this after running successfully for a few weeks). I foun
On Monday 03 November 2008 15.44.10 Jeff Isaac wrote:
> Hello all!
> I have recently stumbled across a problem with my node. I noticed that
> Frost was having trouble communicating the other day even though the node
> was running. Sure enough, the node (at the time 1167) was not connecting to
> any
Hello all!
I have recently stumbled across a problem with my node. I noticed that Frost
was having trouble communicating the other day even though the node was
running. Sure enough, the node (at the time 1167) was not connecting to any
peers (this after running successfully for a few weeks). I foun
16 matches
Mail list logo
