AMS not detecting exported beans

[mSX]

Have you seen this link? You are trying to have metrics for your custom component, so you are responsible for creating metrics you are going to see.

To be able to have performance metrics automatically you have to use stereotype annotations i.e. @Service, @Component, @Controller, etc., but as I mentioned we were unable to make spring dm server community edition export such metrics, and the 1.0.2 version of spring dm server enterprise edition has a bug, that does not allow to export performance metrics correctly without patching internal spring dm server bundles.

[pa7751]

Thanks for this useful information. So we cannot have these metrics exported with the dm server that I am using..okay..but I am not sure if the dm-server-1.0.2.SR02 that I am using is community or an evaluation version of the enterprise version. Any clue on that please?

spring dm server enterprise edition has a bug, that does not allow to export performance metrics correctly without patching internal spring dm server bundles.

So what are those specific bundles for which we will need the patches? Are these patches only available with the enterprise version?

[mSX]

Spring DM EE contains instrumented version of spring jars, so you don't need to replace ones.

So what are those specific bundles for which we will need the patches? Are these patches only available with the enterprise version?

There is no patch for Enterprise and community versions. The problem jar is "repository\bundles\subsystems\com.springsource.se rver.management\com.springsource.server.management .core-1.0.2.RELEASE.jar" - it depends on obsolete version of instrumented spring and does not allow to replace spring jars with the new ones. The main problem is that AMS creates autogroups for the resources of the same type, and all the resources in one autogroup must have the same metrics and control options.

[pa7751]

So then what is the workaround for this problem in the EE?

[mSX]

We have implemented an osgi fragment for the com.springsource.management.adapter.jmx bundle. This fragment uses custom BeanFactoryPostProcessor that replaces jmxManagedResourceExporter in the context of the bundle with the ours exporter. Out exporter overrides managedResourceAdded method replacing the first paramter of type ManagedResourceName with the new one that can uniquely identify managed resource of the certain type (class).

[pa7751]

Okay so that's your own custom implementation then. Is there a jira logged for the bug yet?

Regards

[mSX]

I emailed to spring support more than month ago. There is no reply by the moment.