Log4j setting in RAD 6.0 - WAS 6.0 server

Hi,
I'm working on RAD 6.0 and WAS 6.0 server. I configured both WAS 5.0 and WAS 6.0 servers and published my EAR project. With WAS 5.0, everything seem to work fine as I couldn't find any error in the console. But using WAS 6.0, when I start the server, I could see an error regarding Log4j like:
0000000a SystemErr R log4j:ERROR setFile(null,true) call failed.
0000000a SystemErr R java.io.FileNotFoundException: null\WCW.log (The system cannot find the path specified)

I couldn't see this error in WAS 5.0 because I remember I gave an environment variable inside server configuration for this. The environment variable looks like this:

Name - vvv.app.log
Value - c:/app/log

I could see the log files created as WCW.log under the above c drive.

But just wondering, how can I make my WAS6.0 server recognize the Log4j path as I didn't know where I can set the environment variable. I used WAS admin console to setup the database server and other inforrmation for my EAR project.
I think its already too long, but want to give you a good idea about my problem. Thanks for any help you may give!!.

go the Server via admin console

Server >> Java process definion >> Java Virtual Machine >> here you can define custom properties or include the log4j properties/xml file in server classpath

let us know if it solvs your problems

Hi,

Thanks for your reply, I did add a name and value under 'Custom Properties' in JVM. But still have the same issue. Somewhere I read that we should have the log4j.jar file under EAR folder. But this didn't work either.

Is there anything else that I could do?

Can you confirm that you saved the changes and then saved the master configuration as well? That would appear in the top of the admin console

Are you sure your changes were accepted by the Server?

This is straight forward , all you are trying to do is start your server with VM arguements.

Can you check if you have a message like 'log4j could not be initialized properly' or something similar in your logs

It would be really nice if you can print the stack of the exception as is.That would help us debug better

[ March 19, 2007: Message edited by: Rahul Mishra ]
[ March 19, 2007: Message edited by: Rahul Mishra ]

"Phani", welcome to JavaRanch.

We're a friendly group, but we do require members to have valid display names.

Display names must contain your first name, a space, then your last name. Fictitious names are not allowed.

Please edit your profile and correct your display name since accounts with invalid display names will be deleted.

I realised that the the name that I gave is wrong, it should be vvv.app.logdir instead of vvv.app.log.

Thanks for your help.