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
Exposing additional ports from the droplet is a bit tricky, so JMX support wouldn't be trivial to add. Of course the buildpack supports Newrelic and it should simply be a matter of defining a Newrelic service locally and then binding the service to an application. The buildpack will then run the Newrelic agent. We recently added support to the buildpack so that it would recognise a user-provided Newrelic service - see the Newrelic framework for details.
@soudmaijer At the moment, the buildpack can't assign ports arbitrarily, that can only be done by the core Cloud Foundry runtime. If a JMX port is really important to you, I'd recommend that you open an issue (for more than just an HTTP/S port) with them and we'll support it as soon as it's available.
In the meantime, has the zero-touch New Relic support worked for you?
As a workaround can we use the websockets approach as explained here to tunnel JMX over the existing inbound port ... ?
Create a tunnel servlet TunnelServlet.java and bind this to /debug/mytunnelservlet in
your webapp.
– On your client machine, you have a separate application that accepts your application
url and port you want to connect to
– This will allow developers to connect to Liberty using Jconsole or Visualvm
Since there has been no response on this issue for a fortnight, I'm going to close this. If you find that you are still having trouble, please feel free to open another issue.
Activity
glyn commentedon Nov 15, 2013
Exposing additional ports from the droplet is a bit tricky, so JMX support wouldn't be trivial to add. Of course the buildpack supports Newrelic and it should simply be a matter of defining a Newrelic service locally and then binding the service to an application. The buildpack will then run the Newrelic agent. We recently added support to the buildpack so that it would recognise a user-provided Newrelic service - see the Newrelic framework for details.
nebhale commentedon Nov 18, 2013
@soudmaijer At the moment, the buildpack can't assign ports arbitrarily, that can only be done by the core Cloud Foundry runtime. If a JMX port is really important to you, I'd recommend that you open an issue (for more than just an HTTP/S port) with them and we'll support it as soon as it's available.
In the meantime, has the zero-touch New Relic support worked for you?
kelapure commentedon Nov 18, 2013
As a workaround can we use the websockets approach as explained here to tunnel JMX over the existing inbound port ... ?
your webapp.
– On your client machine, you have a separate application that accepts your application
url and port you want to connect to
– This will allow developers to connect to Liberty using Jconsole or Visualvm
see
https://github.com/sstur/node-websocket-tunnel
http://grokbase.com/p/cloudfoundry.org/vcap-dev/1385efw28y/one-app-withmultiple-
ports
nebhale commentedon Dec 4, 2013
Since there has been no response on this issue for a fortnight, I'm going to close this. If you find that you are still having trouble, please feel free to open another issue.