Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usage issue #878

Closed
mjwSilence opened this issue Jan 11, 2024 · 2 comments
Closed

Usage issue #878

mjwSilence opened this issue Jan 11, 2024 · 2 comments
Labels

Comments

@mjwSilence
Copy link

The thing is, I am using Jprofiler to analyze Java services on Linux servers. Due to network limitations, I can only set up a Windows server in the network environment where the Linux server is located, and then run Jprofiler on this Windows server to analyze Java services on Linux.
I think this process is quite complicated. If I use async profiler instead of Jprofiler, will there be any changes?

@apangin
Copy link
Collaborator

apangin commented Jan 13, 2024

A usual (and the simplest) way to use async-profiler is to start it from the command line passing PID of the target Java process. This typically requires ssh access to the host where your Java application runs.

Async-profiler can be also controlled remotely, although this is not quite secure, unless you work in a trusted private network. The options to control async-profiler over a network include:

  • HTTP API, as mentioned here;
  • JMX, as discussed here.

How would you like to run async-profiler?

@apangin
Copy link
Collaborator

apangin commented Feb 2, 2024

I assume the question is answered; closing

@apangin apangin closed this as completed Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants