There are other ways to profile without manually adding any VM parameters: You can then profile JBoss with an eclipse run configuration without adding any VM parameters. Manually adding a VM parameter to a run configuration in eclipse is not recommended for profiling with JProfiler.įor more on the eclipse IDE integration, see this screen cast and this help page. JProfiler> Could not find session with id: 117` JProfiler> Using config file C:\Users\user\.jprofiler6\config.xml (id: 117) ![]() JProfiler> Don't wait for frontend to connect. and I have set up configuration using New Server Integration, not sure what else needs to be done and how can this be fixed.Īfter adding -agentpath:C:\Users\user~1.DOS\SOFTWA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll=port=8849,nowait,id=117,config=C:\Users\user\.jprofiler6\config.xml to vm arguments under run configuration and then when i run configuration i get JProfiler> Protocol version 32 Please make sure that the remote address is correct, the remote program is started properly, and the network route allows socket connections. I am new to profiling application world and so would really appreciate if you can provide some useful pointersĬould not connect to 127.0.0.1:8849. I am tried for sometime now without any success on configuring JProfiler to work with application running on localhost, any suggestions would be highly appreciated. I have similar issue as in this question but am not able to understand the solution, any suggestions on this would be really appreciated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |