Thanks for your reply
I remember seeing this tag in the past but I couldn't find it in the
reference page http://caucho.com/resin-4.0/reference.xtp and I also
thought it was default true for Resin 4.
But anyway it seems as it is default false now and I added it to the
configuration. This resulted in the following behavior.
1. Two nodes up, A and B. Active browser sessions (sticky sessions)
against each of them.
2. Shut down of node A results in active sessions on A is transferred to B.
3. Start of A again (with bind-ports-after-start set to true) results
in A sessions is transferred back to node A immediately at start (the
same as without the new tag).
4. But when accessing with an A session it now doesn't wait for the
servlet to start, instead I get a timeout since the port isn't bound
So it seems as the <bind-ports-after-start> doesn't affect the srun ports.
2011/11/8 Alex Rojkov <a...@caucho.com>:
>> I have a problem with clustering in Resin 4.0.23 that I hope someone
>> can help me with.
> Can you try adding <bind-ports-after-start>true</> to server-default?
>> When I bring a cluster node back online after it has been shut down
>> the cluster recognizes it as "up and functioning" too soon (this can
>> be monitored on the caucho-status page). My problem is that I have a
>> servlet that is really heavy to start and it has <load-on-startup>
>> set. As it is set up now requests goes to this new node trying to
>> access the servlet prior too its startup and they are left waiting. I
>> would like to have the cluster node off line until all the
>> <load-on-startup> servlets has started. Is there an existing setting
>> that can make this work?
>> What I am looking for is something like <load-balance-grace-time> or
>> <cluster-off-line-until-load-on-startup-done> :)
>> Best regards
>> Mathias Lagerwall
>> resin-interest mailing list
> resin-interest mailing list
resin-interest mailing list