|
From: Davis, B. [DAS] <Bil...@io...> - 2008-07-08 17:47:59
|
We are having problems with logging just simply "stopping" occasionally. We use Wrapper (v. 3.2.3) to run a Mule ESB server that processing incoming XML files from various state agencies and prepares them for our main system here. The system will be running along fine but it just stops writing to the log. The program is still running and processing files...but nothing shows up in the log file. Anybody ever hear of a problem like this? I've poked around the web site and searched the mailing list and stuff (still am searching, actually) and haven't found anything yet that quite sounds like this problem, though apparently there have been some "issues" with logging that have been fixed in more recent version of Wrapper. We're also apparently using the following logging-related jar files in this project: commons-logging-1.0.4.jar log4j-1.2.9jar log4j-all-1.3alpha-8.jar (which is most odd, as development of version 1.3 was abandoned in favor of 2.0) We're probably going to start upgrading logging-related components one at a time, starting with Wrapper (easiest) and then Mule and the logging-related jar files, but of course since we can't reproduce the problem on demand, fixing this will be a pain unless someone has run across something like this before. We may also just change the log4j properties to write elsewhere than the Wrapper log, I ran across a suggestion about that in the Wrapper mailing list archives today. Note: I did not develop this app - I just "inherited" it after the previous programmer left, so I'm not terribly familiar with Wrapper, Mule, or even Java. I've had some courses in Java, and programmed in C and many other languages for many years (decades, really). But an expert in Java, Mule, Wrapper, etc I am not (yet.) I'm just getting started and am having something of a baptism by fire, so please be patient with the noob! ;-) Thanks! Bill Davis |