• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Jprofiler with Weblogic Issue

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I am new to JProfiler. I want to profile my code (.jar) which sits inside a war file. So I added classpath to my jar and filter to only classes in my jar in JProfiler. I have war application deployed in weblogic ManagedServer and I am starting startWebLogic_jprofiler.cmd (AdminServer) from JProfiler. After that I am starting NodeManager and ManagedServer.

But in Jprofiler 'MemoryViews' section I am not able to see my required classes when I run my application. Is it possible to profile the code in ManagedServer or Do I need to deploy my war in AdminServer itself ? or anything missing here.

Please help me regarding this. Thanks in Advance.

-cdhar
 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, it is a long time since I do not use jProfiler, however as far as I know it was a matter of changing some parameters for boot command. Typically this is done through jProfiler wizard however nothing is preventing you to it manually. This is my suggestion add the boot modifiers to the managedServer startup script.

These are the steps I would follow:

1) Have a look at the script jProfiler modified for you, and identify the lines, you may use a tool such us windiff.
2) Paste these lines in the managed server script, or just try to modify the setEnv.cmd or setWLSEnv.cmd at WLSHOME\server\bin with those lines.

Start, it should work. In case not, just send me more details about your env: OS, WLS version, and the scripts JPROFILER created for you, I will help...

Regards.
 
I have a knack for fixing things like this ... um ... sorry ... here is a consilitory tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic