Posted: Thu Oct 06, 2016 3:02 am Post subject: log4j on IIB10
Master
Joined: 05 Dec 2007 Posts: 296
Hi All,
I am exploring the different options we have with respect to logging in IIB. I am currently using IIB 10 with T24 adapters to send and receive data from T24..
I have tried to setup my logging as follows
Place the file “Logging.properties” anywhere, and give the path in JVM arguments with the below command :
I still do not have anything written to the log file.. Could I be missing something here? I am trying to track the data coming out of the T24 adapter into IIB.
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
Log4j and Broker should be consigned to the trashcan.
There are better solutions builtin to the product.
Sadly (and at the risk of becoming boring) far too many Java devs log everything including the kitchen sink using things like Log4j. They need to be weaned/detoxed off it.
Then what happens when someone fogets to disable it and the full debug level logging flow gets deployed to PROD. I've seen a PROD serve brought to its knees because of this very issue. A critical filesystem (in your case the windows C: drive could become full. Windows does not like full filesystems any more then Unix/Linux.
No, no and thrice no. Don't do it. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Use the log4j rolling log appender option to prevent the file system from filling up. _________________ Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum