Hylafax Mailing List Archives

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

[hylafax-users] JKILL and Trigger



marted=EC 17 maggio=20 2005           &n= bsp;      =20 19:45
 
 
hello,
We are using HylaFAX 4.2.1 and Fedora Core 3 with
our applicatio= n that=20 communicates
with HylaFAX server through the new client-server=20 protocol.
 
This application has a thread that starts a trigger connection
w= ith=20 HylaFAX for intercepting all job events and all work fine.
 
But when we try to kill a job that is still in send queue
and in= state=20 'S' (Sleeping) through a JKILL command (that returns success)
by this= moment=20 the trigger connection doesn't reiceve any
event and we need to resta= rt the=20 application for restarting the trigger connection.
 
This behaviour is easily reproducible also with HylaFAX utilities:<= /DIV>
 
- Run the faxwatch utility with 'faxwatch S*J*R*'.
- Sending a f= ax with=20 sendfax to a not existing phone number
  (e.g. 0000001122).
&= nbsp; At=20 this moment you can see faxwatch regular messages.
- Wait for the fir= st try=20 to sending job be completed and job become sleeping.
  At this m= oment=20 faxwatch received all regular messages and stand by.
- Then send a JK= ILL=20 command for the corresponding jobid
  (e.g. with a telnet connec= tion=20 open on port 4559):
  faxwatch trigger seems frozen.
 
 
Thanks
Paolo Bagnoli
 
 
p.bagnoli@evoluzionisof= tware.com


Home
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services