Re: [hylafax-users] Blocked by concurrent call problem since upgrade to 4.2.2

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Jordan Kojouharov wrote:

> Lee, thank you for the quick and detailed response.
>
> As a follow up to this, some more testing suggests that this only 
> happens for me when the following conditions are true:
>
> 1. there are two or more jobs to the same destination already in the 
> outgoing queue, with one of them sending, and the others 'blocked by 
> concurrent'.
>
> 2. then, a few more jobs for that destination get submitted, and 
> HylaFAX attemps to batch them, however, resulting in two or more of 
> them going into 'blocked by concurrent', and never unblocking, even 
> after the current sends to that destination get completed.


I cannot reproduce this on my machine with current CVS HEAD.  This is 
what I do:

 echo test | sendfax -n -d 400
 (wait a second as faxq pulls that in)
 echo test | sendfax -n -d 400
 echo test | sendfax -n -d 400
 (these last two are blocked, as expected)
 (wait about 30 seconds)
 echo test | sendfax -n -d 400 -d 400 -d 400
 (these three are blocked, as expected)
 (the first job finishes)
 (faxq then queues-up all of the other jobs in one batch)

All of this is as expected.  Again, some of this changed between 4.2.2 
and now in CVS, and I suspect that whatever error there was it is now 
fixed.  So you could help by testing current CVS HEAD.  Does my 
procedure produce the problem for you?  (400 is a local number on my PBX.)

> 'man hylafax-config' does seem to indicate that the default value for 
> MaxBatchJobs is 1. Not sure if the man page is wrong, or I'm reading 
> it wrong:
>
> MaxBatchJobs   integer   1   max jobs in a batch
>
> The maximum number of jobs to batch together.  Fax  Batching  is an 
> advanced  feature that has some rough edges.  It is not currently 
> considered fully supported,  but  in  limited  situations works  well. 
>  Enabling  this  on  a server where you don't have total faith in your 
> users could have serious undesired  affects. 


Oh my.  Well, it looks like some of that person's bias against batching 
still slipped in to the 4.2.2 release documentation, now didn't it?

For the whole story see:

 http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=667

I'll get that documentation fixed for the next release.

Lee.


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*