http://livedocs.adobe.com/ Macromedia LiveDocs - online documentation with user feedback. Copyright 2009, Macromedia, Inc. 2009-11-26T04:00:30 en-us http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#38682 The connector seems to be confused by the existence of another cookie on our same domain named dcr-hrw-16000-1-PSJSESSIONID. Looking at the connector logs, once a client gets that cookie, the connector starts to try to use that value as the session ID and can never again stick to the correct server until the browser is closed and the cookies are deleted. The other cookie is set by a PeopleSoft application that many of our employees visit throughout the day. Why would the JRun connector take that cookie over its own JSESSIONID cookie that is still there? Please help! steveh1234 0 0 2005-08-15T19:15:20 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#32106 I am pretty sure that the connectors have stopped using jrunserver.store, so this shouldn't be a problem. However, I'm not sure which updater introduced this change. jrunrandy 1 1 2005-04-22T06:50:25 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#31787 It seems that apache connector deletes the contents of jrunserver.store.<br />Like below:<br />proxyservers=<br />No IP or Ports.<br />It still continues under Updater5. rio yoshida 0 0 2005-04-19T01:06:54 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#25117 When running serveral jrun severs on different ports on the same machine loadbalancing seems to spread the load unevenly over the available servers. apparently the loadbalancer (in combination with apache) does not properly apply Round Robin but gives about 35 % of the requests to the first server, 40 % to the second and about 12,5 % to the third and fourth server. Has anyone else noticed similair results? 0 0 2004-12-07T07:36:22 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#23250 Once the setup is complete for the cluster and Apache connector, if we restart apache server and not all jrun servers are running at the instance when Apache comes up. Apache does not recognize the servers in cluster which may start up later on.<br />Do we have a fix for this? mangesh@iflex 0 0 2004-11-01T15:19:28 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#23151 We have a fix for this. $ isn't supported in WML.<br /><br />Call support for this hotfix.<br /><br />Stephen Dupre<br />Macromedia QA sdupre 0 0 2004-10-29T06:00:50 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#21400 You must set different server.id at {server.root}/SERVER-INF/connector.properties on each servers. Otherwise StikySession will be Round Robin. <br />Actually, server.id will be the first four chars of jsessionid. <br />And is anyone know how to prevent using special chars(like "$") in the rest part of jsessionid? rio yoshida 0 0 2004-09-15T20:02:54 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#12840 In the jrunserver.store file, the line for proxyservers MUST use ip addresses and NOT hostnames. Fuseboxer 0 0 2004-04-12T13:53:48 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#3030 Even I added <br /><attribute name="StickySessions">true</attribute><br />in the "<service class="jrun.servlet.jrpp.JRunProxyService" name="ProxyService">" group, I still cannot see the Sticky Session.<br />The same request still be sent to the 2 servers alterlatively. songbin 0 0 2003-10-22T23:33:56 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#1243 Has anyone found problems with connector based clusting using Apache? ben pinnick 0 0 2003-08-11T03:22:05 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#1103 Not a whole lot of technical details here. Well, I would like to know if its possible to add and remove servers dynamically to the cluster.<br><br> sxm20 0 0 2003-07-15T03:48:00 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#958 Under the session management section where it states "The default is false. If your web applications use session management, you must set this attribute to true." The default for connector clustering sticky session is TRUE. You only need to specify<br><br><attribute name="StickySessions">false</attribute><br><br>If you want to disable the sticky session option. bpurcell 0 0 2003-03-05T11:21:00 http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/clustering3.htm#957 Under the session management section where it states "The default is false. If your web applications use session management, you must set this attribute to true." The default for connector clustering sticky session is TRUE. You only need to specify<br><br><attribute name="StickySessions">false</attribute><br><br>If you want to disable the sticky session option. bpurcell 0 0 2003-03-05T11:20:00