You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I upgraded the spring-boot-admin-server and spring-boot-admin-server-ui from 1.3.7 to 1.5.3. In our services (spring-boot-admin-starter-client) we use 1.3.x, 1.4.x. and 1.5.x. In the spring boot admin server UI we are missing the description of the parameters from all JMX operations. This happens with our JMX operations and also with the operations from java.lang and other domains. We have the issues with all services, so I think it is an issue in the spring-boot-admin-server or spring-boot-admin-server-ui. The two attached screenshots shows the JMX operations in the UI in the different UI versions.
The relevant code snippet:
@ManagedOperationParameters({
@ManagedOperationParameter(name = "accountId", description = "The id of the accountuser aggregate"),
@ManagedOperationParameter(name = "legalTermsLockReason", description = "Reason for legal terms lock (BOUNCE, CANCELLATION")
})
public void setLegalTermsLock(String accountId, String legalTermsLockReason) {
…
}
The text was updated successfully, but these errors were encountered:
@frkautz Did you have a look into the jolokia response if the description is provided by jolokia? (and made sure you didn't had an old version from browser cache)?
@joshiste somehow a strange behavior after I deleted the browser cache it didn't work, but during analyzing the jolokia request it shows the description. So ignore my request to reopen the ticket. Thanks.
I upgraded the spring-boot-admin-server and spring-boot-admin-server-ui from 1.3.7 to 1.5.3. In our services (spring-boot-admin-starter-client) we use 1.3.x, 1.4.x. and 1.5.x. In the spring boot admin server UI we are missing the description of the parameters from all JMX operations. This happens with our JMX operations and also with the operations from java.lang and other domains. We have the issues with all services, so I think it is an issue in the spring-boot-admin-server or spring-boot-admin-server-ui. The two attached screenshots shows the JMX operations in the UI in the different UI versions.
The relevant code snippet:
The text was updated successfully, but these errors were encountered: