http://livedocs.adobe.com/ Macromedia LiveDocs - online documentation with user feedback. Copyright 2009, Macromedia, Inc. 2009-11-25T15:00:36 en-us http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/jrundotxml2.htm#21269 you've made a mistake in the loggger service section. You say that error loggin should be turned off in production to minimise the amount of space used by the files. But you surely mean debug logging. Telling people to turn off error logging means nobody will ever be aware of errors in their applications. You just need to move the comment up a line. APDutch 0 0 2004-09-13T06:25:50 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/jrundotxml2.htm#13671 The minHandlerThreads is the min threads that are available to JRun at start up. After that it can get reduced if the threads are not used and timed out. That's whats missing from the docs. jrunrandy 1 0 2004-04-30T11:15:25 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/jrundotxml2.htm#13641 MinHandlerThreads has no effect?<br />only one thread remain active after timeout period ForrestNg 0 0 2004-04-30T04:21:41 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/jrundotxml2.htm#12841 In the section of the document for the 'ClusterManager' service, the UnicastPeer attribute description reads:<br /><br />"Specifies JRun servers in the cluster that are outside of the subnet. JRun automatically locates servers on the same subnet but requires a unicastPeer specification for JRun servers outside of the subnet."<br /><br />You CANNOT use the name of the JRun Server here. You MUST use the hostname of the server on which JRun is installed.<br /><br />Also, JRun by default uses IP multicasting to find other servers on the local subnet. If your network engineering team has disabled multicasting (as mine did), then you MUST specify physical hostnames in the UnicastPeer attributes. This will cause JRun to use unicast to connect to other servers to enable session replication and failover. Fuseboxer 0 0 2004-04-12T13:57:26 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/jrundotxml2.htm#1045 The SOMAXCONN value for the backlog attribute in the ProxyService config causes a NumberFormatException ! colin_froggatt 0 0 2003-05-16T06:44:00 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/jrundotxml2.htm#789 The TXDomainService under JRunTransactionService now accepts a maximum transaction timeout setting. For example:<br><br><service class="jrun.transaction.TXDomainService" name="DefaultDomain"><br> ...<br> <attribute name="maximumTimeout">600&lt;/attribute><br> ...<br></service><br><br>The default maximumTimeout attribute is 600 seconds.<br> danger42 0 0 2002-11-20T17:57:00