3 Replies Latest reply on Dec 7, 2004 6:32 AM by starksm64

    MDB Timing Stats

    greydeath

      Hi,

      I was wondering if the timings on the onMessage are really correct. (J22 Management) I have a MDB that calls a Session EJB. The overall time in the Session EJB adds up to the overall time of my test (enqueue,process), but the MDB timings don't.

      According to the MDB timings, the overall time should be more then double the EJB time, which it is not:

      Overall : 10:28:24 - 10:32:17 = 233s 6.16 msg/s
      MDB Proxy (5): 2697518ms = 2697.518s 0.53 msg/s
      Session EJB(5): 1150457ms = 1150.457s 1.2 msg/s

      As you see the EJB times multipled by 5 (number of instances) roughly add up to the overall time. the MDB only calls the Session EJB, nothing more, but its time does not add up anywhere.

      Could somebody explain why the MDB times differ so much or if this really is a bug.

      Thanks
      Mike

        • 1. Re: MDB Timing Stats
          starksm64

          These stats look fine to me for a similar configuration. Exactly where are you getting the stats from and what version of jboss are you talking about.

          • 2. Re: MDB Timing Stats
            greydeath

            I'm using 4.0.1RC1 and I use the jboss.management.local mbean for the MDB:
            EJBModule=ftisoft.core-ejb.jar,J2EEApplication=ftisoft.app.ear,J2EEServer=Local,j2eeType=MessageDrivenBean,name=local/TPSProxy

            To gather the stats

            • 3. Re: MDB Timing Stats
              starksm64

              An mdb invoking a session bean which takes 10 seconds produces the following stats which look good to me with the 4.0.1RC2 release.

              org.jboss.management.j2ee.statistics.MessageDrivenBeanStatsImpl [ {onMessage=[ Count: 3, Min. Time: 10016, Max. Time: 10047, Total Time: 30079, Request Rate: 10026.0, onMessage(description: The timing information for the given method, units: MILLISECOND, startTime: 1102419035640, lastSampleTime: 0) ], CreateCount=[ 0:CreateCount(description: Number of creates, units: 1, startTime: 1102418835859, lastSampleTime: 1102419035625) ], RemoveCount=[ 0:RemoveCount(description: Number of removes, units: 1, startTime: 1102418835859, lastSampleTime: 1102419035625) ], MessageCount=[ 3:MessageCount(description: The count of messages received, units: 1, startTime: 1102418835859, lastSampleTime: 1102419035640) ]} ]
              


              Create a bug report with an example that illustrates the erroneous stats:
              http://jira.jboss.com/jira/browse/JBAS