How do I know if UVM limit is approaching? (Java crash)

[tentimes]

Hi,

EDIT: This is in reference to the Attack Blocker, sorry I should have said so.

In this post it is mentioned that allowing P2P to proceed will eventually hit the limit of the Java virtual machine.

I want to allow as much P2P as possible but not to the extent I crash the virtual machine. Is there any way of seeing how close to the edge it is? I have looked in the interface but cannot see it.

I have a fibre connection and bandwidth is not an issue. I also do a lot of P2P from ONE machine. I have added an unlimited exception, but I have no idea how many connection to limit bittorrent to.

The machine running Untangle is a Core2@2Ghz with 2Gig RAM and pretty modern, so it has room to stretch itself. Is there any way to signal to Untangle that it has more room to manoeuvre or is there some guidance you can give me on the maximum connections it can manage?

Many thanks for any help in advance,

Kevin

[dmorris]

It will say "Hit session limit" in console.log, but you won't see it because you arent.

I'd take everything in that post with a large grain of salt.
He almost certainly has some other issue.

[sky-knight]

P2P has the potential of overloading Untangle, however, in my experience it ends up DOS'ing the LAN interface right off the LAN long before the UVM is tracking 10k sessions.

[tentimes]

Ok - thanks I've let it free and no problems whatsoever. I have 200 connection limit (utorrent standard) for reference.