Bug 780255 (SOA-2652)

Summary: Running the server using the "production" profile produces discarded messages between the cluster names: udp and modeshape-cluster
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Van Halbert <vhalbert>
Component: Integration, EDSAssignee: Van Halbert <vhalbert>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.1.0.ER5CC: vhalbert
Target Milestone: ---   
Target Release: 5.1.0.ER6   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2652
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-04 20:27:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
deploy.diffs
none
conf.diffs none

Description Van Halbert 2010-12-08 18:47:50 UTC 
project_key: SOA

If running the ER5 server in the production profile, produces these warnings ever 10 secs:

2010-12-08 12:35:16,134 WARN  [org.jgroups.protocols.UDP] (OOB-5,modeshape-cluster,127.0.0.1:61508) discarded message from different group "udp" (our group is "modeshape-cluster"). Sender was 127.0.0.1:54828
2010-12-08 12:35:21,426 WARN  [org.jgroups.protocols.UDP] (OOB-5,udp,127.0.0.1:54828) discarded message from different group "modeshape-cluster" (our group is "udp"). Sender was 127.0.0.1:61508

This happens on startup and continues.

I reran ER4 and this was happening.
Comment 1 Van Halbert 2010-12-08 19:22:21 UTC 
In ER4, I don't see the following message in the log:   GMS: address is 127.0.0.1:50371 (cluster=udp)
establishing the cluster: udp.
Comment 2 Anne-Louise Tangring 2010-12-14 19:08:55 UTC 
Candidate for SOA 5.1.0. Kevin to help out.
Comment 3 Anne-Louise Tangring 2010-12-14 19:09:21 UTC 
Actually, we decided to make it a blocker.
Comment 4 Kevin Conner 2010-12-16 12:43:38 UTC 
This has been triggered by recent updates to the jBPM configuration as both jBPM and modeshape are using default values.
Comment 5 Kevin Conner 2010-12-16 12:43:38 UTC 
Link: Added: This issue is related to SOA-2365
Comment 6 Kevin Conner 2010-12-16 12:50:21 UTC 
The modeshape configuration should be updated with the following diffs
Comment 7 Kevin Conner 2010-12-16 12:50:21 UTC 
Attachment: Added: deploy.diffs
Attachment: Added: conf.diffs