Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-438

DataGravitatorInterceptor logs ERROR when alone in cluster

XMLWordPrintable

    • Release Notes

      See JBCACHE-1220.

      Logging after making 1 request for a static page in a distributable webapp when the node was the only cluster member:

      11:45:04,122 ERROR [DataGravitatorInterceptor] No replies to call _gravitateData; id:35(/JSESSION/localhost/ROOT/FC5F1D24DE0C89413E2D633331C6F030, true, false). Perhaps we're alone in the cluster?
      11:45:04,128 ERROR [DataGravitatorInterceptor] No replies to call _gravitateData; id:35(/JSESSION/localhost/ROOT/FC5F1D24DE0C89413E2D633331C6F030, true, false). Perhaps we're alone in the cluster?
      11:47:35,104 ERROR [DataGravitatorInterceptor] No replies to call _gravitateData; id:35(/JSESSION/localhost/ROOT/FC5F1D24DE0C89413E2D633331C6F030, true, false). Perhaps we're alone in the cluster?
      11:47:35,107 ERROR [DataGravitatorInterceptor] No replies to call _gravitateData; id:35(/JSESSION/localhost/ROOT/FC5F1D24DE0C89413E2D633331C6F030, true, false). Perhaps we're alone in the cluster?
      11:47:35,195 ERROR [DataGravitatorInterceptor] No replies to call _gravitateData; id:35(/JSESSION/localhost/ROOT/FC5F1D24DE0C89413E2D633331C6F030, true, false). Perhaps we're alone in the cluster?
      11:47:35,198 ERROR [DataGravitatorInterceptor] No replies to call _gravitateData; id:35(/JSESSION/localhost/ROOT/FC5F1D24DE0C89413E2D633331C6F030, true, false). Perhaps we're alone in the cluster?
      11:47:35,328 ERROR [DataGravitatorInterceptor] No replies to call _gravitateData; id:35(/JSESSION/localhost/ROOT/FC5F1D24DE0C89413E2D633331C6F030, true, false). Perhaps we're alone in the cluster?
      11:47:35,331 ERROR [DataGravitatorInterceptor] No replies to call _gravitateData; id:35(/JSESSION/localhost/ROOT/FC5F1D24DE0C89413E2D633331C6F030, true, false). Perhaps we're alone in the cluster?

      Need to decide how to get this fixed in the EAP; probably by moving to JBC 1.4.1.SP7.

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: