[jboss-jira] [JBoss JIRA] (AS7-6137) Correct overlap in clustering logging id ranges
Richard Achmatowicz (JIRA)
jira-events at lists.jboss.org
Tue Dec 11 14:38:17 EST 2012
[ https://issues.jboss.org/browse/AS7-6137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Achmatowicz updated AS7-6137:
-------------------------------------
Description:
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.
was:
The following ranges are used for logging ids in the clustering subsystem:
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 --
The overlapping range between InfinispanMessages and ClusteringWebLogger needs to be rectified, as CSS uses message ids for distinct topics in knowledge databases.
> 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: 7.1.3.Final (EAP)
> Reporter: Richard Achmatowicz
> Assignee: Paul Ferraro
>
> 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: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list