Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-6137

Correct overlap in clustering logging id ranges

    XMLWordPrintable

Details

    Description

      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 GSS uses message ids for distinct topics in knowledge databases.

      Attachments

        Activity

          People

            rachmato@redhat.com Richard Achmatowicz
            rachmato@redhat.com Richard Achmatowicz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: