D
dbeavon
Guest
It is primarily all about memory and cpu activity (garbage collection?) of the Java broker process for the state-free appserver. Our state-free broker uses over 1 GB of resident memory on HP-UX and 3 GB of virtual memory. This consists of over 1000 client connections from about 24 different remote I.P. addresses, and probably around 200-300 separate remote processes (.Net ). Also, there is a max client connections number (sum of all client apps * sessions used by those apps) which we have run into on a couple occasions (most recently at the 1000 mark). When no more client connections can be made, we are forced to double this max client connections property in the ubroker.config and have to restart the broker, thereby dumping all client connections in the middle of the work day.
Continue reading...
Continue reading...