[hylafax-users] Problems with hylafax regarding job files without number and/or gnu.hylafax class

["Ulf Zimmermann" <ulf@xxxxxxxxxxxxxxxxxxx>]

We are currently running 4.1.8 (I can't upgrade right now as both
servers are production and I don't have a spare PRI card and PRI). In
the last days we have been encountering problems with Hylafax
complaining about "Null or missing number". We submit jobs from our java
application using the java class gnu.hylafax.HylaFAXClient (version
0.0.7).

One thing I am seeing in our tomcat log is that this class connects to
the server, submits a job with just a document:

-> user fax_status_prod@xxxxxxxxxxx
230 User fax_status_prod@xxxxxxxxxxx logged in.
-> noop
200 NOOP command successful.
-> tzone LOCAL
200 Using time values in PST.
-> jnew
200 New job created: jobid: 18598 groupid: 18598.
-> port 10,21,130,17,154,6 (10.21.130.17:39430)
200 PORT command successful.
-> stot
150 FILE: /tmp/doc9425.ps (Opening new data connection).
<... here comes the file ...>
226 Transfer complete (FILE: /tmp/doc9425.ps).

Now it goes on and creates a new job:

-> jnew
200 New job created: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm FROMUSER AutoTradeCenter Corporation
213 FROMUSER set to "AutoTradeCenter Corporation".
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm NOTIFYADDR fax_status_prod@xxxxxxxxxxx
213 NOTIFYADDR set to "fax_status_prod@xxxxxxxxxxx".
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm MAXDIALS 3
213 MAXDIALS set to 3.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm MAXTRIES 3
213 MAXTRIES set to 3.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm SCHEDPRI 127
213 SCHEDPRI set to 127.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm DIALSTRING XXX-XXX-XXX (real number taken out)
213 DIALSTRING set to "XXX-XXX-XXXX".
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm VRES 196
213 VRES set to 196.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm PAGEWIDTH 215
213 PAGEWIDTH set to 215.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm PAGELENGTH 279
213 PAGELENGTH set to 279.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm PAGECHOP default
213 PAGECHOP set to "default".
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm CHOPTHRESHOLD 3
213 CHOPTHRESHOLD set to 3.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm NOTIFY done
213 NOTIFY set to "done".
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm LASTTIME 000259
213 LASTTIME set to 000259.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> job
200 Current job: jobid: 18599 groupid: 18598.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jparm DOCUMENT /tmp/doc9425.ps
200 Added document /tmp/doc9425.ps as docq/doc9425.ps.18599.
-> job 18599
200 Current job: jobid: 18599 groupid: 18598.
-> jsubm 18599
200 Job 18599 submitted.

So basically it seems to submit a job for the document, then creates a
new job and uses the document from the previous job. Job id 18599 got
sent good as far I can tell, but 18598 gets complains about missing
number.

And today Hylafax Queuer seemed to have tried it about 2,924 times:

Feb  9 14:17:34 faxfrmt01 HylaFAX[16412]: sendq/q18598: line 51: Null or
missing number in job request 
Feb  9 14:17:40 faxfrmt01 HylaFAX[16434]: sendq/q18598: line 51: Null or
missing number in job request 
Feb  9 14:17:44 faxfrmt01 HylaFAX[16436]: sendq/q18598: line 51: Null or
missing number in job request 
Feb  9 14:18:09 faxfrmt01 HylaFAX[16464]: sendq/q18598: line 51: Null or
missing number in job request

I got 2,924 of those lines, together with other jobs it created a very
large messages file and filled up 1GB of /var file system.

Now my questions are:

Is this java class doing it the right way? 2 jobs, etc?

Secondly why this repeated tries from Hylafax seconds apart and no
reject until hours later?




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