ben short wrote:
I have altered the code to write out which webapp generated the page
to the html, so i can see where the partial responses are comming
from.
What I see is....
I stop the webapp on box 2. I make a request and I see part of the
page. The html shows that the partial page was generated by the
running webapp on box 1.
On a slightly different note, I have the mod_jk logging set to debug.
When it logs out the packets that its received from the webapps it
doesn't show all the html page. For instance I see two full packets
traced out then a half full one and that's it. But the page renders ok
in the browser. I have a example log if anyone would like to see it.
Log level debug truncates packet dump to I think 1KB, log level trace
shows all of the packets.
Maybe interesting for you: the ReplicationValve has two configurable
attributes, that allow you to detect from the app, if the request went
to the same node as the last request of the same session before, i.e. if
a failover happended.
The first attribute is primaryIndicator (Default: false), if set to
true, it will enable this feature. When the feature is enabled, there is
an additional request attribute (not: parameter), with name
"org.apache.catalina.ha.tcp.isPrimarySession" (this is a string name)
and its value is a Boolean, true if the request went to the sticky node,
false, if it switched nodes.
The name of the request attribute can be changed from the default
"org.apache.catalina.ha.tcp.isPrimarySession" to something else, by
setting the attribute primaryIndicatorName="myname" for the
ReplicationValve.
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
