Bug 900200 (JBPAPP6-900)
Summary: | WARNING on Starting JGroups Channel "[UNICAST2] (OOB-20,null) perf18/web: my conn_id (0) != received conn_id (4); discarding STABLE message !" | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Radoslav Husar <rhusar> |
Component: | Clustering | Assignee: | Bela Ban <bela> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0.0 | CC: | bela, brian.stansberry, paul.ferraro, rhusar |
Target Milestone: | --- | ||
Target Release: | EAP 6.0.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://jira.jboss.org/jira/browse/JBPAPP6-900 | ||
Whiteboard: | usability | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-10-19 06:35:46 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: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 900611 |
Description
Radoslav Husar
2012-04-12 22:23:17 UTC
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 |