Bug 911117

pm-ack assuming it does not impact the scheudle.  Otherwise no.

Will be this change available only by using management APIs [1] or are there plans to include these metrics in GWT based WebUI? 

[1] CLI, HTTP API, JAVA API

For the console a separate issue must be created.

If Carlo's patch I just merged into upstream master goes into EAP, a commit bumping the minor or micro version of the EJB subsystem management API *must* be included. That wasn't necessary with the upstream patch because an earlier patch had already bumped the AS 8 subsystem's major version.

The management API versions in the 7.2.0 tag are fixed, so any post-tag changes in EAP require a management API version bump.

https://github.com/jbossas/jboss-eap/pull/28

Hi Carlo, I see that the changes are present in 6.1.0.ER4, but I only see method invocation metrics - execution time, invocation count and waiting time for each method. Nothing like cache size, passivated count, min/max invocation times, etc., as you specified in the first comment. Are you planning to add these? I am setting this to VERIFIED for now, so this should be considered just a reminder|question|whatever. Should you plan to add the mentioned metrics, feel free to reopen it. Thanks

I am not sure why this is marked VERIFIED. If the missing metrics are still missing then doesn't that mean we may have missed something?

Carlo, can you please let us know where we should be looking for these metrics as it related to comment 6?

We are still missing the cache statistics. These were never ported over from the deprecated StatefulCache interface.

As for the other ones, they don't make sense.

The statistics are meant to be used in a round-robin database. Where the RRD dictates the interval. So for EAP the interval should be an external variable.

In EAP 5 you could reset the statistics, but the time-series between last query and reset would be lost. Essentially it is a very crude hammer to notify EAP of the interval.
This also makes it an unstable piece of EJB3 code.

I choose to ditch that, which makes min, max and average non-existent. There is no interval known to EAP. This makes for stable data point queries.

Ultimately I still want to be able to have a performance ui as I drafted ~4 years ago, wherein the pressure on each EJB is properly visualized.
I'm not sure whether it needs a re-introduction of the interval notion.
It would need some additional means to provide data points to the histogram though.

Created attachment 739089 [details]
Perfomance UI drawing

Chao Wang <chaowan> updated the status of jira WFLY-1590 to Resolved

Chao Wang <chaowan> made a comment on jira WFLY-1590

merged Pull Request at https://github.com/wildfly/wildfly/pull/4701

@Larry,
the new metrics are available in EAP 6.1.1.ER3. I briefly checked them and they seem to work fine. Can you have a look and tell if you are satisfied? 
If yes, we will mark this as VERIFIED.
Thanks

@Jan
Looks like everything is there (of course this was a stateful-session-bean): 

/deployment=jboss-as-ejb-in-war.war/subsystem=ejb3/stateful-session-bean=GreeterEJB:read-resource(include-runtime=true)
{
    "outcome" => "success",
    "result" => {
        "cache-size" => 1,
        "component-class-name" => "GreeterEJB",
        "declared-roles" => [],
        "execution-time" => 1L,
        "invocations" => 7L,
        "methods" => {"sayHello" => {
            "execution-time" => 1L,
            "invocations" => 7L,
            "wait-time" => 0L
        }},
        "passivated-count" => 0,
        "peak-concurrent-invocations" => 1L,
        "run-as-role" => undefined,
        "security-domain" => "other",
        "total-size" => 1,
        "wait-time" => 0L
    }
}

Verified in EAP 6.1.1.ER3

I've added a draft release note text to this bug for possible inclusion in the 6.1.1 Release Notes document.

Please review for accuracy and comment on any problems.

Marking for exclusion from the 6.1.1 Release Notes document as an entry for this bug could not be completed or verified in time.