Re: [Wrapper-user] Logging randomly just "stops"

[<le...@ta...>]

Bill,
When the application is in a state where it has stopped logging, are you running a service or in console mode?
If possible can you reproduce this running in console mode?  I am assuming for now you are running on windows.

1) When in the stopped state, can you request a thread dump by pressing CTRL-BREAK?   If you see the dump, then the Wrapper process is correctly receiving and logging output from the Java process.

2) As an alternative to the thread dump, simply start the shutdown process.  If you see more log entries then once again things are working on the Wrapper side.

3) Make sure you are seeing the log entries both in the Console and the Log file.  If they are only showing up in the Console then that would point to a problem writing to the log file.

4) At the point that the logging stops, how large is the wrapper.log file?  I assume you have plenty of disk space.

5) What are your logging settings from the wrapper.conf file.

Once we have confirmed that some output from the JVM is making it to the Wrapper to be logged then the Wrapper can be ruled out and we can look into what on the Java side might be causing the problem.

All java side logging tools use System.out to print log information to the Java console.   So you can easily test that by adding some System.outs to your code.  If those show up in the Wrapper.log file, but the log4j calls do not then it is a java side logging problem of some sort.

I may have more ideas after hearing back from you.

Cheers,
Leif


On Wed, Jul 9, 2008 at 2:49 AM, Davis, Bill [DAS] <Bil...@io...> wrote:
> 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
>