Affects: Release Notes project_key: JBPAPP6 On redeplying application. This is new to me, probably related to JGroups upgrade. {noformat} ... JBossINF] 18:02:16,182 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: clusterbench-ee6.ear [JBossINF] 18:02:16,206 INFO [org.jboss.as.osgi] (MSC service thread 1-6) JBAS011941: Register module: Module "deployment.clusterbench-ee6.ear:main" from Service Module Loader [JBossINF] 18:02:16,206 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) JBAS016008: Starting weld service for deployment clusterbench-ee6.ear [JBossINF] 18:02:16,238 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011941: Register module: Module "deployment.clusterbench-ee6.ear.clusterbench-ee6-ejb.jar:main" from Service Module Loader [JBossINF] 18:02:16,260 INFO [org.jboss.as.osgi] (MSC service thread 1-13) JBAS011941: Register module: Module "deployment.clusterbench-ee6.ear.clusterbench-ee6-web.war:main" from Service Module Loader [JBossINF] 18:02:16,368 INFO [stdout] (pool-18-thread-3) [JBossINF] 18:02:16,369 INFO [stdout] (pool-18-thread-3) ------------------------------------------------------------------- [JBossINF] 18:02:16,369 INFO [stdout] (pool-18-thread-3) GMS: address=perf18/ejb, cluster=ejb, physical address=10.16.90.54:55200 [JBossINF] 18:02:16,370 INFO [stdout] (pool-18-thread-3) ------------------------------------------------------------------- [JBossINF] 18:02:16,419 INFO [stdout] (pool-13-thread-3) [JBossINF] 18:02:16,420 INFO [stdout] (pool-13-thread-3) ------------------------------------------------------------------- [JBossINF] 18:02:16,420 INFO [stdout] (pool-13-thread-3) GMS: address=perf18/web, cluster=web, physical address=10.16.90.54:55200 [JBossINF] 18:02:16,420 INFO [stdout] (pool-13-thread-3) ------------------------------------------------------------------- [JBossINF] 18:02:16,481 WARNING [org.jgroups.protocols.UNICAST2] (OOB-20,null) perf18/web: my conn_id (0) != received conn_id (4); discarding STABLE message ! [JBossINF] 18:02:16,541 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-3) ISPN000078: Starting JGroups Channel [JBossINF] 18:02:16,542 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-3) ISPN000094: Received new cluster view: [perf19/ejb|5] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb] [JBossINF] 18:02:16,543 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-3) ISPN000079: Cache local address is perf18/ejb, physical addresses are [10.16.90.54:55200] [JBossINF] 18:02:16,553 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-21-thread-3) ISPN000031: MBeans were successfully registered to the platform mbean server. [JBossINF] 18:02:16,558 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-20-thread-3) ISPN000031: MBeans were successfully registered to the platform mbean server. ... {noformat}
Link: Added: This issue is related to JBPAPP-7577
This is a spurious message and can be completely ignored. It can happen in UNICAST(2) when the unicast connection (with id=0) between A and B is torn down, but a STABLE message from A is still in transit (delayed, e.g. due to retransmissions), then the new id between A and B is 4 and the old STABLE message is received. It will be discarded by B. The warning can be safely ignored.
Thanks, Bela, that's what I suspected was going on. * The question now is then, whether its necessary to log this in AS log? * If we still want to log it, how about rephrasing it so its clearer that this message is spurious?
I could change the log level from WARN --> TRACE if you want
We can close this then - and file a jgroups jira to lower the log level. INFO is probably appropriate.
Done. Didn't file a JIRA though... will be in JGroups 3.0.10
Release Notes Docs Status: Added: Not Yet Documented Labels: Added: usability
Link: Added: This issue is a dependency of JBPAPP-9290
Link: Removed: This issue is related to JBPAPP-7577
JGroups 3.0.10 was released in mid May, so this should be in EAP 6.0.1
Changed the log statement to use TRACE instead of WARN in 3.0.10. Upgrading to 3.0.10 or later makes the warning disappear.
Upstream master and 7.1 were upgraded to JGroups 3.0.10 (or later) quite a while ago so this should be resolved.
Verified, closing.
updating for release notes
Writer: Added: tomwells
Affects: Added: Release Notes
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Release Notes Text: Added: A warning message could occur in UNICAST(2) during startup, because the unicast connection was torn down while a STABLE message was still in transit. This message could be safely ignored, and the log level has been decreased to removed the warning.
Release Notes Docs Status: Removed: Documented as Resolved Issue Writer: Removed: tomwells Release Notes Text: Removed: A warning message could occur in UNICAST(2) during startup, because the unicast connection was torn down while a STABLE message was still in transit. This message could be safely ignored, and the log level has been decreased to removed the warning. Docs QE Status: Removed: NEW