11

I have just upgraded to WebSphere 7 (from 6.1), and I am having new class loading conflicts which I didn't have before.

I have looked a lot over the internet but couldn't find directions on how:

1. How to enable class loading trace.
2. Where does the output go to?

Thank you very much.

User27854
  • 824
  • 1
  • 16
  • 40
user967710
  • 1,815
  • 3
  • 32
  • 58

3 Answers3

9

To enable the classloading information you need to go in application server > server_name > Java and Process Management > Process definition > Java Virtual Machine, there you will find the verbose classloading option. Enable it and restart the application server.

You should then find the classloading informations in the native_stderr.log in the <WAS_install_root>/profiles/<profile>/logs/<server> directory.

Hunter Medney
  • 381
  • 2
  • 10
Olivier.Roger
  • 4,241
  • 5
  • 40
  • 68
  • This doesn't work - I see in the log on startup the same info whether flag is on or not – user967710 Feb 21 '12 at 23:43
  • Have you also looked in the other files ? From what I see and remember I was the native_stdout.log file which was used to log. see , slide 4. – Olivier.Roger Feb 22 '12 at 07:51
4

To add to Olivier.Roger's response (I don't have the permissions to respond inline), the information is in native_stderr.log.

(late, but for anyone else who finds this thread like I did)

patstuart
  • 1,931
  • 1
  • 19
  • 29
2

I would recommend the class loader MustGather that is used by IBM support when you open a PMR. Expand the "Collecting data manually" section.

Brett Kail
  • 33,593
  • 2
  • 85
  • 90