We have seen this issue on v3 and are now getting it on v4. Basically, FAXLOGADD notifications stop arriving, usually after sending 200 or so faxes. My application simply stops getting these messages and I have resorted to a clumsy scheme where a thread uses FaxLogFind to see which log a pending fax has been moved to.
I would prefer to use the proper notification system, so how can I go about getting this problem debugged? My application is doing nothing special here and it only requests the notifications once, at startup. The application is multi-threaded, and each thread gets it's own PAPPINFO pointer.
Here is the sequence of events.
- The main application thread calls FaxRegisterApp, passing it the handle to a window owned by the thread. It then calls FaxSubscribe, passing it SUBSCRIBE_LOG_COMPLETE|SUBSCRIBE_LOG_FAILED.
- Faxes are sent from separate threads. Each thread calls FaxRegisterApp but a window handle is not passed.
- Faxes send fine and notifications arrive to the main window as WM_FAXMSG messages.
- After 200 or so faxes are sent, the WM_FAXMSG messages simply stop arriving. Restarting the application doesn't fix it - only a restart of FaxMan itself will get the messages arriving again.
- I have littered my code with debug messages and am confident that it is behaving correctly.
I could change each thread's call to FaxRegisterApp to also pass the main threads window handle but I don't think this matters, else notifications wouldn't ever be received.
I rely on these notifications so I can send email messages when faxes send successfully and would love a solution to this issue. When I first reported this issue I was told to upgrade the customers to v4, but have run out of things to try. I would be happy to install a special debug version of FaxMan if it would help, but the customer(s) are losing patience with us.
Any advice would be welcome.