search

ajrockefeller / openfpc

Automatically exported from code.google.com/p/openfpc
0 stars 0 forks source link

Thread Creation Fails in openfpc-queued after an arbitrary period of time running #26

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.run openfpc for a long time, sending requests to the queue daemon
2.wait
3.

What is the expected output? What do you see instead?

Should continue creating threads to process requests. Instead I see pthread 
creation failed at line 180 in /usr/bin/openfpc-queued errors in the 
/var/log/messages and as stdout when running openfpc-queued in --debug mode

What version of the product are you using? On what operating system?

0.6-314 Ubuntu Server 10.04

Please provide any additional information below.

I dont seem to be doing anything unusual, as you know I'm running a setup where 
requests are made constantly on signatures firing so there is quite a number of 
requests at a time if a signature is aggressive. This causes me issues as the 
openfpc-client requests stay as active processes and consume system resources. 
I am finding it difficult to debug this as there is no real logging that could 
explain why threads are not being created.

Original issue reported on code.google.com by matt.new...@gmail.com on 9 Sep 2011 at 4:21

GoogleCodeExporter commented 8 years ago 
How big is the queue when it dies?

-L

Original comment by leon.j.w...@gmail.com on 20 Feb 2012 at 2:25

GoogleCodeExporter commented 8 years ago 
Im not really sure, the system is constantly queueing up requests until it 
stops, throwing the error above. It seems to have improved slightly on the 
newer releases. Have you done any performance testing with heavy loads? I may 
have some more time over the next few weeks to push openfpc hard and monitor 
for the effects. I will feed them back to you offline mate.

Original comment by matt.new...@gmail.com on 20 Feb 2012 at 2:28

GoogleCodeExporter commented 8 years ago 
I've never had a chance to try any capacity testing, I've no idea where it will 
break.
Perhaps there is a maximum count of threads or array limit that's being hit.

IIRC an "openfpc -a status" will show the current queue length.

-L

Original comment by leon.j.w...@gmail.com on 20 Feb 2012 at 3:14