What web.xml options add most to stability of NXT server? The stability problems could simply be from suboptimal web.xml settings.
Does the 0.5.3 install use the most stable options in web.xml?
Are there any other files that need to be tweaked?
I am thinking that a lot of the problems in the field could be related to having a wrong set of settings. We are so close to a stable NXT server. I updated my peers list and now it is not going brain dead. Still need more time, but looking good so far.
The only thing that was changed was the list of peers, but I remember seeing a bunch of different tweaks. Has anybody tested the effect of the different tweaks on NXT server stability. So much work has been put into NXT, it would be a shame if a new NXT'er gets a bad experience due to suboptimal settings.
James
Does the 0.5.3 install use the most stable options in web.xml?
Are there any other files that need to be tweaked?
I am thinking that a lot of the problems in the field could be related to having a wrong set of settings. We are so close to a stable NXT server. I updated my peers list and now it is not going brain dead. Still need more time, but looking good so far.
The only thing that was changed was the list of peers, but I remember seeing a bunch of different tweaks. Has anybody tested the effect of the different tweaks on NXT server stability. So much work has been put into NXT, it would be a shame if a new NXT'er gets a bad experience due to suboptimal settings.
James
The problems we have been seeing were mostly due to one specific type of attack combined with a ddos. These attacks seem to have stopped now that they don't have the "desired" effect anymore.
The parameters are fine as they are, no need to adjust them. As are the peers, as soon as you see one peer, it will send you all it's other peers and you're good to go