2

I have a strange problem with my component that is a TrustAssociationInterceptor and it starts up with the Application Server, so it's not deployed.
After the upgrade to version 45 of my websphere 6.1 my log4j does not log into the file I've specified in the properties of my custom component but only into the SystemOut.log . I can change the logging level only by the WebSphere console. It seems websphere has the control of log4j. The log file of the custom component is created but not populated.

Has anyone any ideas on how to resolve this?

Thanks

maximus1927
  • 41
  • 3
  • Definitely seen this behavior in WAS 6.1 before due to JCL, but I can't think of any reason it would start just with a new Fixpack. What fixpack were you on before? http://stackoverflow.com/questions/8131529/websphere-all-logs-are-going-to-systemout-log/8138477#8138477 – dbreaux Feb 06 '13 at 18:39
  • Hi, thanks for your reply, I previously have installed the version 6.1.0.31 – maximus1927 Feb 07 '13 at 10:05
  • 1
    I done the rollback to the v.31 some days ago and the file has been created and populated without any problem... – maximus1927 Feb 07 '13 at 11:37

1 Answers1

0

Have you deployed 6.1.0-WS-WASSDK-WinX32-FP0000045.pak along with 6.1.0-WS-WAS-WinX32-FP0000045.pak, Is that to do something with SDK ?

Joachin Joseph
  • 333
  • 5
  • 18