You say "I try to keep some filehandles and datastructures simply on a "our" variable."
When using threads that modify shared data which is "global the the entire process", there needs to be
some kind of locking mechanism. A thread has to acquire an "exclusive write lock" versus its other "thread
peers" in order to update that commonly shared information. I don't see any locking code that would adjudicate
write/read conflicts amongst its peer threads. It is possible that one thread might read a variable during the
writing of that variable by another thread.
I don't know much about the server software that you are using, but I'm sure that some
other Monks do. However, unlocked shared variable sounds like a likely suspect to me.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|