Jboss connection pools extension with error

[MariettaAlmeida]

Hi all,

we configured connection pools Jboss extension but it shows error state:

the extension execution controller is enabled on both servers

the oneagent feature is also enabled Java Metric Extensions 2.0 (JMX)

but extension failed to connect. 

thanks in advance

[Eric_Yu]

Try checking the logs, you should get some info about the error.

https://docs.dynatrace.com/docs/shortlink/troubleshooting-extensions

[MariettaAlmeida]

There is no info, we are ingesting the logs also, maybe is there something i must check about the logs? Cause there are no logs but just for the extension

[Mizső]

Hi @Eric_Yu,

Unfortunately at many extesnions it is useless, because the result is an empty log viewer screen. It is quite annoying...

Best regards,

Mizső

[Julius_Loman · Accepted solution]

@Mizső it depends on the extension. Unfortunately, JMX has no logging. It also struggled with that for a while, to diagnose if it's activated it's best to see the OneAgent log for the particular Java process.

For JBoss connection pools it's common that you don't have connection pools of certain type in your applications, then the MBeans are missing and the extension status will show error. Yes, this is highly misleading. 

But most important information is, that you will not see the metrics in the classic screens, but in the Metrics and log analysis. So they are hidden a little bit.

[MariettaAlmeida]

thank you a lot @Julius_Loman we checked on that part and we have data. You also say that is common that certain type of applications  dont show the connection pools, what kind of apps are you refering to ? 

[Julius_Loman]

@MariettaAlmeida for example for JBoss you have connection pools and XA connection pools. your application server may have just of one those. Extension queries both MBean types.

[paolo_fumanelli]

Hi Julius, so in any case, for any possible error, the same message will be returned? Asking that because we have an automatic process that checks extensions' status and alerts us and we'd like to filter those kind of errors to avoid misleading alerting.

Thanks

[Julius_Loman]

@paolo_fumanelli  that's a question for Dynatrace PM team. @michal_nalezin are there improvements planned in terms of JMX logging ?

In the meantime, I'd recommend disabling the feature set for the JBoss database connection types you  don't use. 

[paolo_fumanelli]

Thanks for prompt reply, how can we do that? We're pretty new on this extension version 2.0. Thanks

[Julius_Loman · Accepted solution]

@MariettaAlmeida most likely the extension works as expected. Unfortunately, it will always report an error status as long there is some jmx mbean or attribute which cannot be found. There is zero logging for JMX extensions at this time.

Have you checked if the metrics are being collected? They can be found in the Metrics and log analysis menu for the process group instance.

[MariettaAlmeida]

here is where we checked.