[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-673) Add support for multiple routes in JSESSIONID

[Jean-Frederic Clere (Jira)]

    [ https://issues.jboss.org/browse/MODCLUSTER-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698914#comment-13698914 ] 

Jean-Frederic Clere commented on MODCLUSTER-673:
------------------------------------------------

[~rhusar] to do that look in get_route_balancer() it look to first . (if ((route = strchr(sessionid, '.')) != NULL )) we need a clever logic there.... 
Note that the route is stored via apr_table_setn(r->subprocess_env, "BALANCER_SESSION_ROUTE", route); etc... we need a list... It don't remember how to handle a list in apr...
the failover logic is find_best_byrequests()... find_best_byrequests() is going to be called for each tries, picking the next node/worker shouldn't be too difficult.
See find_best_roundrobin() in modules/proxy/examples/mod_lbmethod_rr.c



> Add support for multiple routes in JSESSIONID
> ---------------------------------------------
>
>                 Key: MODCLUSTER-673
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-673
>             Project: mod_cluster
>          Issue Type: Enhancement
>          Components: Native (httpd modules)
>    Affects Versions: 1.4.0.Final
>            Reporter: Paul Ferraro
>            Assignee: Radoslav Husar
>            Priority: Major
>
> WildFly will soon be able to annotate the JSESSIONID using multiple routes.  Thus the route should be parsed as a list of targets (instead of a single target).  When the target route contains multiple entries, the reverse proxy should attempt to direct requests to the 1st active worker in the list.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)