]
Radoslav Husar updated AS7-6137:
--------------------------------
Affects Version/s: No Release
(was: 7.1.3.Final (EAP))
Correct overlap in clustering logging id ranges
-----------------------------------------------
Key: AS7-6137
URL:
https://issues.jboss.org/browse/AS7-6137
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: No Release
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.2.0.Alpha1
The following ranges are used for logging ids in the clustering subsystem:
{noformat}
clustering range: 10200 - 10399 (199 message ids)
ClusteringApiLogger: 10200 range = 10, used = 2
ClusteringApiMessages: 10210 range = 10, used = 10 (full range)
ClusteringImplLogger: 10220 range = 20, used = 19 (almost full range)
ClusteringImplMessages: 10240 range = 20, used = 9
JGroupsLogger: 10260 range = 10, used = 6
JGroupsMessages: 10270 range = 10, used = 8
InfinispanLogger: 10280 range = 10, used = 7
InfinispanMessages: 10290 range = 10, used = 15 (over full)
ClusteringWebLogger: 10300 range = 10, used = 1
ClusteringWebMessages: 10310 range = 10, used = 5
InfinispanWebLogger: 10320 range = 10, used = 6
InfinispanWebMessages: 10330 range = 10, used = 7
SingletonLogger: 10340 range = 10, used = 4
SingletonMessages: 10350 range = 10, used = 2
EJBLogger: not assigned range = ?, used = 0
EJBMessages: 10360 range = 10, used = 4
-- free 10370 - 10399 --
{noformat}
The overlapping range between InfinispanMessages and ClusteringWebLogger needs to be
rectified, as GSS uses message ids for distinct topics in knowledge databases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: