It wasn’t JBoss’s fault

I saved my changes to jboss-log4j.xml and waited for JBoss to notice the new file… but it never seemed to notice it, and my advice.log kept not showing up in the log directory.  I immediately suspected JBoss.  “Why isn’t it watching server/default/conf/jboss-log4j.xml like it’s supposed to be?”

Then I remembered that I was editing a copy of jboss-log4j.xml in my Eclipse workspace, so I’d have the benefit of Eclipse’s local history feature.  Oops!

I copied jboss-log4j.xml from my Eclipse workspace out to JBoss’s server/default/conf directory, and sure enough… JBoss noticed the changes.  : )

Advertisements

, ,

  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s