Archived Data Techniques Forums

Hi,

We have problem with FAXMAN4 running on quad core CPU computer, the problem is FAXLOGADD did NOT be fired.

When we submit a fax by "FAXMAN1.SENDFAX", we also keep check the fax to ensure it has be put into FAXMAN database .  Because  we found that the "FaxMan1_FaxLogAdd" event did not be fired sometimes. Even we re-submit the fax again, FAXMAN4 could not respone anymore. We have to reboot the computer to resume normal.

The problem quite often happens on quad core CPU computer, any suggestions?

Regards,

KC

Private Sub Timer_Queue_Msg_Timer() ' Send Message
  :
  :
  
  FaxMan1.SendFax
  'This loop is to wait for FAXMAN complete his job before we submit another one.

  My_Integer = 0

    Do Until MSG_STAMP = Verify_FaxManUserData

      WRITElog "Message send and waiting for FAXMAN process "
      My_Integer = My_Integer + 1
      If My_Integer > 100 Then
        WRITElog "ERROR : Waiting FAXMAN TIME OUT!" 
        Exit Do
      End If

      DoEvents
    Loop
                   
  :
  :
End Sub

Private Sub FaxMan1_FaxLogAdd(ByVal LogType As Integer, ByVal FaxID As Long, ByVal LogIndex As Long)

  Dim Item As Object

  On Error GoTo Error_Handler

  Set Item = FaxMan1.FindFax(FaxID)
  If LogType = 0 Then Verify_FaxManUserData = Item.LogUserData
  :
  :
End Sub

An Example  Log file

2/27/2009 4:55:30 PM C:\MEGAMAIN\HST06343.A3311 WILL BE SENT!

2/27/2009 4:55:30 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:31 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:31 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:32 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:32 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:33 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:33 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:34 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:34 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:35 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:35 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:36 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:36 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:37 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:37 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
2/27/2009 4:55:38 PM MESSAGE SEND AND WAITING FOR FAXMAN PROCESS  (TIMER_QUENE_MSG/FRMFAX_MAIN)
   :

2/27/2009 4:58:11 PM ERROR : WAITING FAXMAN TIME OUT! (TIMER_QUENE_MSG/FRMFAX_MAIN)

 Hi,

A couple of questions:

1. What version of Faxman4.exe are you running ?

2. So does this same app work  fine on a single or dual core processor ? Are you sure its the quad core issue thats causing the event issue ?

Hi,

We are using Faxman4 V4.4.4. & VB6.

We haven't get any the above error from other computer, in addition the error was happened not just once in a while. From our log, it was clearly shown the "FaxMan1_FaxLogAdd" event did not be fired.

 Regard

KC

Hi,

What OS was the quad core box running ?

Hi,

The OS is Windows Server 2003.

HI,

Thanks for the addtl info, one other question,  how long does it take for this to occur ?

Is your app multithreaded ? How many FaxMan fax controls are you using ?

Hi,

We're trying to gather additional information on this so we can duplicate it here, so far we have been unable to. This poster seems to think the issue only occurs in their apps on a particular machine which is quad core and Win 2003. How does this correspond to what you have seen ?

We have been getting this problem for a few years - on Windows NT4, 2000, XP and 2003.  Our support team will restart our app and FaxMan to get notifications working again, and they do this quite often (and don't always tell me).  I *think* that all the machines that exhibit this are multi-processor/dual-core, but I would need to check with our support guys.

FWIW our app runs as a Windows service and creates a hidden window that we use for the FaxMan notifications.  Is there any chance that the method you are using to send notifications (PostMessage?) is failing?  Could we try a debug version 4 that adds some logging to your message posting code?

I have recently added a fall-back scheme where a separate thread checks for fax IDs in the log using FaxFind - this is clunky and not terribly efficient but it means we spot when faxes are sent/fail and can send out email notifications.  These email notifications are very important for our customers, but we would prefer to use the 'proper' FaxMan message notifications.

We also have an administrator app that runs as a normal process which also registers for FaxMan log messages and I don't think we have ever seen this issue.  Perhaps the fact our main app is a Windows service is key here?

We had one customer recently send thousands of faxes before notifications stopped, yet another only managed a couple of hundred.  Hence this issue is almost impossible to reproduce in-house,

 Any new findings regarding multi-core/multi-processor CPUs? 

Wendell