The JIRA suggests this is fixed, is that the case?

And for release notes, does the user have to add that code? And if so, where does it go?

I guess we need to add the patch to the next ER.
https://github.com/modcluster/mod_cluster/commit/08be77c8c393d421ca9c1abb7145fd006165df70

Well, yes, it is fixed in master. Target release being mod_cluster 1.2.5.Final.
It is not fixed in 1.2.4.Final though. This means this bug is present in EAP 6.1.0.ER6.

One has to add that code only if one is using "CreateBalancers 1" (mod_cluster.conf in conf.d, httpd configuration). User might want to have something like:

CreateBalancers 1
ProxyPass / balancer://qacluster

and it won't work. Workaround would be to have:

CreateBalancers 1
ProxyPass / balancer://qacluster stickysession=JSESSIONID|jsessionid

Of course, "qacluster" is an arbitrary name. Default value for ManagerBalancerName directive is "mycluster".

(In reply to comment #2)
> I guess we need to add the patch to the next ER.
> https://github.com/modcluster/mod_cluster/commit/
> 08be77c8c393d421ca9c1abb7145fd006165df70

Yes, if we can, it would be nice. At the moment, it is not fixed in EAP 6.1.0.ER6.

Jean-Frederic, do you have the tag 1.2.5.Final ready if we can get this in?

I asked on the AS mailing list and we're in blocker only mode, so it looks like we'll get this in EAP 6.2.0.

Jean-Frederic, please include this fix in the tag for EAP 6.2.0 and assign it to us when the new tag is ready. Thanks!

Michal Babacek <mbabacek@redhat.com> made a comment on jira MODCLUSTER-334

Verified on
[modcluster/mod_cluster/tree/1.2.x|https://github.com/modcluster/mod_cluster/tree/1.2.x].
Closing.

Michal Babacek <mbabacek@redhat.com> updated the status of jira MODCLUSTER-334 to Closed

Added draft release notes text to the top of the Doc Text field above (retained original content below it). Setting NEEDINFO for technical verification of draft.

To clarify, this is a Known Issue for the 6.1 Release Notes?

Removing the original info from the Doc Text field so it doesn't get picked up in auto-builds.

#######
Cause: 
   Having:
   ProxyPass / balancer://qacluster
   and CreateBalancers 1
   without any stickysession=JSESSIONID|jsessionid
   
Consequence: 
   Segmentation fault 
   [notice] child pid 7787 exit signal Segmentation fault (11)
   
Workaround (if any): 
   Add stickysession=JSESSIONID|jsessionid, so as to have:
   ProxyPass / balancer://qacluster stickysession=JSESSIONID|jsessionid


Result:

Verified with m_c 1.2.6, EAP 6.2.ER4 :-)

Added Doc Text draft based on the 'Known Issue' text in bug 958990. 

The above draft assumes that the workaround was adopted in this release as a default.

Please comment with information if this is incorrect.

"In previous versions" in fact that is no correct that was regression.