Hide Forgot
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000004UaFc project_key: JBEPP JBoss AS / EAP supports an easy switch to change clustering communication from UDP to TCP: -Djboss.default.jgroups.stack=tcp EPP should leverage this by adding a jgroups stack based on TCP and by using the jboss.default.jgroups.stack parameter to control which stack is being used.
Link: Added: This issue related JBEPP-772
Link: Added: This issue is related to JBEPP-778
Link: Added: This issue is related to JBEPP-779
Link: Added: This issue is related to JBEPP-780
Link: Added: This issue is a dependency of JBEPP-735
Would be better to not close them until the dependent or related ones are not closed. Here it seems like the feature describe by the JIRA is fixed but it is not.
Link: Added: This issue relates to JBEPP-935
Link: Added: This issue is related to GTNPORTAL-2234
Release Notes Text: Added: We are using parameter -Dgatein.default.jgroups.stack=tcp to switch EPP clusters (JCR, IDM, MOPSessionManager, NavigationService, DescriptionService) to TCP. So that we are independent on "jboss.default.jgroups.stack" parameter, which is good for portability (same fix is applied in GateIn trunk where it need to work for all servers). Another thing is that EAP supports more valid values for parameter jboss.default.jgroups.stack (udp, udp-async, udp-sync, tcp, tcp-sync...) where we have only two for parameters gatein.default.jgroups.stack (udp, tcp). However it's not problem to add more JGroups configurations. JGroups configs are under gatein.ear/02portal.war/WEB-INF/classes/jgroups directory and there are two files gatein-udp.xml and gatein-tcp.xml. You can add more files or change existing if needed.
Link: Added: This issue relates to JBEPP-1210
This JIRA is fixed with JBEPP-1210 (rev 7870)
Release Notes Docs Status: Added: Not Yet Documented
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Feature Request Release Notes Text: Removed: We are using parameter -Dgatein.default.jgroups.stack=tcp to switch EPP clusters (JCR, IDM, MOPSessionManager, NavigationService, DescriptionService) to TCP. So that we are independent on "jboss.default.jgroups.stack" parameter, which is good for portability (same fix is applied in GateIn trunk where it need to work for all servers). Another thing is that EAP supports more valid values for parameter jboss.default.jgroups.stack (udp, udp-async, udp-sync, tcp, tcp-sync...) where we have only two for parameters gatein.default.jgroups.stack (udp, tcp). However it's not problem to add more JGroups configurations. JGroups configs are under gatein.ear/02portal.war/WEB-INF/classes/jgroups directory and there are two files gatein-udp.xml and gatein-tcp.xml. You can add more files or change existing if needed. Added: It is possible to switch portal clusters between UDP and TCP communication modes using a command-line parameter. The -Dgatein.default.jgroups.stack=[tcp | udp] parameter switches EPP clusters (JCR, IDM, MOPSessionManager, NavigationService, DescriptionService) between the two protocols. The functionality is implemented using an adapted, and mutually exclusive implementation of jboss.default.jgroups.stack. <note><para>This enhancement is based on, but deliberately independent of, the JBoss Enterprise Application Platform parameter. "jboss.default.jgroups.stack" which supports more values by default than Enterprise Portal Platform currently does. The decision to keep the two parameters separate was for upstream compatibility.</para></note>