Yeah. WAS 5.0 is not particularly friendly to commons-logging because it uses it internally. Hence, it wants to use its own configuration. There are work arounds (none good) of course... IBM's documentation:
http://www-1.ibm.com/support/docview.wss?uid=swg27004610 David Hibbs, ACS Staff Programmer / Analyst American National Insurance Company > -----Original Message----- > From: Pingili, Madhupal [mailto:[EMAIL PROTECTED] > Sent: Friday, June 18, 2004 9:50 AM > To: 'Struts Users Mailing List' > Subject: Struts 1.1 / WebSphere 5.1 logging > > > > I have a web application developed with Struts 1.1 running on > WebSphere > 4.0.4 successfully. > Now, if I deploy the same app on WebSphere 5.1, there is no log file > created. > I am using commons-logging.properties: > org.apache.commons.logging.Log=org.apache.commons.logging.impl > .Log4JLogger > > and log4j.properties with 2 rolling file appenders to create > 2 log files. > > Has anyone come across the logging issues when porting the web app to > WebSphere 5.1? > > Any help or links to resources is appreciated. > > > Reddy Pingili > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
