Author: spadkins
Date: Mon Nov 12 10:32:48 2007
New Revision: 10231
Modified:
p5ee/trunk/App-WorkQueue/lib/App/WorkQueue.pm
Log:
more logging to catch yet another case where async_events and num_workers
gets out of whack, this time in _release_in_mem
Modified: p5ee/trunk/App-WorkQueue/lib/App/WorkQueue.pm
==============================================================================
--- p5ee/trunk/App-WorkQueue/lib/App/WorkQueue.pm (original)
+++ p5ee/trunk/App-WorkQueue/lib/App/WorkQueue.pm Mon Nov 12 10:32:48 2007
@[EMAIL PROTECTED]
-637,9 +637,13 @[EMAIL PROTECTED]
for ($e = 0; $e <= $#$data; $e++) {
$ent = $data->[$e];
if ($self->_hash_to_key($ent) eq $entry_key) {
+ ### TODO: Rare occasions we get here, and have not called
_release_resources, why?
if ($ent->{$status_attrib} eq $STATUS_ACQUIRED) {
$self->_release_resources($ent);
}
+ else {
+ $context->log("NOTE: _release_in_mem NO
_release_resources : STATUS_ACQUIRED[$STATUS_ACQUIRED] : entry[" .
join("|",@[EMAIL PROTECTED]
) . "]\n");
+ }
$self->update($ent,\@[EMAIL PROTECTED]
);
splice(@[EMAIL PROTECTED]
$e, 1);
print "RELEASED[M]: {", join("|",%$entry), "}\n" if
($verbose);


|