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

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Can you see if this happens with current CVS HEAD?  There have been some 
changes since 4.2.2 that were intended as "feature adds", but they may 
have acutally fixed these problems you're seeing because they dealt with 
the same code.

Snapshots of CVS HEAD are available on the ftp site.

In any case, I am unable to reproduce this problem with current CVS HEAD.

Thanks,

Lee.


Jordan Kojouharov wrote:

> Hi,
>
> I upgraded from HylaFAX 4.2.1 to 4.2.2 a few days ago, and since the 
> upgrade I have had the following strange problem:
>
> Sometimes, when a fax is sent to the same destination number more than 
> once, it never attempts to dial, but both jobs go straight into 
> 'Blocked by concurrent call', and seem to lock each other out. My 
> 'MaxConcurrentCalls' parameter is set to '1'.
>
> for example, the command used to submit the fax is (N=NUMBER):
>
> sendfax -d <N1> -d <N1> -d <N2> -d <N3> -d <N3> <filename>
>
> there are 3 unique numbers there, with two of them repeated (double 
> destination).
>
> The first job for N1, and N2 start sending, the second job for N1 goes 
> into 'Blocked by concurrent' (so far so good), but BOTH jobs for N3 go 
> directly into 'Blocked by concurrent call' and never actually attempt 
> to send. After the send for N1 finishes, the second send to N1 
> unblocks as it should, and then it sends). Afterwards, the only thing 
> left is two blocked jobs to N3, without an attempt to dial N3 ever 
> been made, and there are no other active current jobs to N3 anywhere 
> in the queue... The blocked jobs are always the ones to the 4th and 
> 5th destination, never to the 1st and 2nd, even though those numbers 
> are also identical.
>
> It seems that it is not really a problem with sending to 2 identical 
> destination numbers, as a send to 'N1 N2 N1 N3 N3 N2 N4', for example, 
> works, as I found out with some testing. From the patterns, my random 
> guess would be that this only appears to happen when there is more 
> than one group of consecutive identical destinations specified.
>
> The destination numbers have not changed, so I definitely know that 
> this did NOT exist in 4.2.1. Any ideas if anything has changed in the 
> scheduling of concurrent jobs from version 4.2.1 to 4.2.2?
>
> regards,
> Jordan
>
>
>
> ____________________ 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 expensive HylaFAX(tm) support, mail sales@xxxxxxxxx*


____________________ 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*