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
In my Micronaut application I expose the Management endpoints on a different port. The reason for this is that the API is not unknowingly available via a reverse proxy.
When I run the Micronaut application as a fatjar, everything works as expected. But when I run the native image, it seems that Netty is not listening on that port.
/ # http localhost:8090/endpoints/health
http: error: ConnectionError: HTTPConnectionPool(host='localhost', port=8090): Max retries exceeded with url: /endpoints/health (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f8572fd9c70>: Failed to establish a new connection: [Errno 111] Connection refused')) while doing a GET request to URL: http://localhost:8090/endpoints/health
Is this the separate port not supported in the native image or am I missing something?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
In my Micronaut application I expose the Management endpoints on a different port. The reason for this is that the API is not unknowingly available via a reverse proxy.
When I run the Micronaut application as a fatjar, everything works as expected. But when I run the native image, it seems that Netty is not listening on that port.
Is this the separate port not supported in the native image or am I missing something?
Beta Was this translation helpful? Give feedback.
All reactions