Cannot Connect to JMX monitor Performance Security Server

[phavira]

Hello Xroad Team,

i got the error from service xroad-monitor. i cannot connect to JMX monitor. i got the response error like this.

so what I should to do ?

Thanks.

2024-08-21T08:06:04.795Z [taskScheduler-2] INFO  org.hibernate.Version - HHH000412: Hibernate ORM core version [WORKING]
2024-08-21T08:06:04.797Z [taskScheduler-2] INFO  org.hibernate.cfg.Environment - HHH000406: Using bytecode reflection optimizer
2024-08-21T08:06:05.711Z [taskScheduler-2] WARN  org.hibernate.orm.deprecation - HHH90000028: Support for `<hibernate-mappings/>` is deprecated [RESOURCE : serverconf.hbm.xml]; migrate to orm.xml or mapping.xml, or enable `hibernate.transform_hbm_xml.enabled` for on the fly transformation
2024-08-21T08:06:05.717Z [taskScheduler-2] WARN  org.hibernate.orm.deprecation - HHH90000028: Support for `<hibernate-mappings/>` is deprecated [RESOURCE : identifiers.hbm.xml]; migrate to orm.xml or mapping.xml, or enable `hibernate.transform_hbm_xml.enabled` for on the fly transformation
2024-08-21T08:06:05.738Z [taskScheduler-2] INFO  o.h.e.j.c.i.ConnectionProviderInitiator - HHH000130: Instantiating explicit connection provider: org.hibernate.hikaricp.internal.HikariCPConnectionProvider
2024-08-21T08:06:05.751Z [taskScheduler-2] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2024-08-21T08:06:05.846Z [taskScheduler-2] INFO  com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.postgresql.jdbc.PgConnection@2253e325
2024-08-21T08:06:05.848Z [taskScheduler-2] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2024-08-21T08:06:05.900Z [taskScheduler-2] WARN  org.hibernate.orm.deprecation - HHH90000026: CustomPostgreSQLDialect has been deprecated; use org.hibernate.dialect.PostgreSQLDialect instead
2024-08-21T08:06:06.066Z [taskScheduler-2] WARN  org.hibernate.orm.incubating - HHH90006001: Encountered incubating setting [hibernate.id.db_structure_naming_strategy].  See javadoc on corresponding `org.hibernate.cfg.AvailableSettings` constant for details.
2024-08-21T08:06:06.072Z [taskScheduler-2] WARN  org.hibernate.orm.incubating - HHH90006001: Encountered incubating setting [hibernate.id.db_structure_naming_strategy].  See javadoc on corresponding `org.hibernate.cfg.AvailableSettings` constant for details.
2024-08-21T08:06:06.072Z [taskScheduler-2] WARN  org.hibernate.orm.incubating - HHH90006001: Encountered incubating setting [hibernate.id.db_structure_naming_strategy].  See javadoc on corresponding `org.hibernate.cfg.AvailableSettings` constant for details.
2024-08-21T08:06:06.072Z [taskScheduler-2] WARN  org.hibernate.orm.incubating - HHH90006001: Encountered incubating setting [hibernate.id.db_structure_naming_strategy].  See javadoc on corresponding `org.hibernate.cfg.AvailableSettings` constant for details.
2024-08-21T08:06:06.072Z [taskScheduler-2] WARN  org.hibernate.orm.incubating - HHH90006001: Encountered incubating setting [hibernate.id.db_structure_naming_strategy].  See javadoc on corresponding `org.hibernate.cfg.AvailableSettings` constant for details.
2024-08-21T08:06:06.073Z [taskScheduler-2] WARN  org.hibernate.orm.incubating - HHH90006001: Encountered incubating setting [hibernate.id.db_structure_naming_strategy].  See javadoc on corresponding `org.hibernate.cfg.AvailableSettings` constant for details.
"monitor.log" 413L, 75259B ```                   

[raits]

Hello @phavira,

Sorry for some reason this issue has gone unnoticed until now. Have you managed to resolve the problem on your own already?

[phavira]

I not yet to resolve on this issue. I just use other way to monitor like zabbix agent or snmp.

[raits]

Ok, would you still like to try and resolve the issue or are you happy with the current approach?

If you would like to resolve it, could you please check if there are any errors in the log. Currently, they seem to be regular log entries. Also, please share in that case the error you are getting when connecting and the settings you are using to connect.

[phavira]

it good with the current approach. Thank you for your support.