Closed surachai-tep closed 3 years ago
Hi
Can you test with GelfUdpAppender
?
I'm going to create a load tester with siege during the weekend and try to find the issue
Hi jjchiew, We try GelfUdpAppender today and found it's working fine with no hang for 8 hours. We'll keep monitoring for week to make sure that it'll not get the same issue like the async one.
Thanks.
Great!
I'll take a look to all the Async*Appenders
Hi, We've found our web application hang after started using gelf4net on some of our production server. The problem comes a few hour after application start. We decided to dump memory while it hang for analysis and here is what we found.
------Type of Analysis Performed Hang Analysis------------ Machine Name
Operating System Windows Server 2008 R2Service Pack 1 Number Of Processors:
Process ID 9856 Process Image
Command Line
System Up-Time 100 day(s) 14:55:06 Process Up-Time 02:54:09 Processor Type X64 Process Bitness 64-Bit
------------- .NET Threads Summary -------------- Total Threads: 569 Running Threads: 569 Idle Threads: 0 Max Threads: 32767 Min Threads: 120
82.32% of threads blocked (568 threads) Look at the callstack of thread 143 to see why that thread id waiting on and why it is not releasing the lock.
--------- Stacktrace of thread no. 143 ---------------
----------- Many threads that were blocked by 143 were on Enter lock state ----------------
---------- Here is our appender configuration -------
Is there anything wrong on our configuration that cause thread block? Any idea or suggestion would be appreciated.
Thank you