Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Request Processor Spam

pmdw
2008-02-26
2013-03-07
  • pmdw
    pmdw
    2008-02-26

    Hi All

    Cross posting Alert!
    I am doing a bit of cross posting here as I think it would be nifty to have the Request Processor say something like “ Escalated Request Updated” or “Alert Request Updated”  etc  in its emails instead of just “Request Updated”. this way the spam makes some sense.

    Heres why
    We are currently running Adempiere Release 3.2.0 - 2007-05-01  on a postgres database

    We originally had a problem sending emails manually, like emailing purchase orders or invoices from within Adempiere. but we seem to have sorted it out.

    However we are still having a problem with the request process. We have set up the request processor to be reminded of outstanding requests.

    We originally set up 2 request processes ( client support and technical) as follows.
    Frequency type is day
    Frequency is 1 (ie every day)
    Reminder days 2
    Alert after days due 2
    Escalate after days due 3
    Inactivity Alert days  3

    We also have 9 request types set up these are still active, but do not have email request on.
    email when due       not checked
    email when overdue  not checked

    We have however deactivated both the request processes but we still get emails

    No previously set up request processor should still be working, right?. Also, we make sure that when setting up new requests, we "de-activate" the update notifications (user). And yet, we literally receive hundreds of Request Updated: emails, each time we turn on our computers in the morning. 
    ( yea I know sort out the request and you don't get the emails) but we get at least 2 emails for each request sometimes 3 or 4.

    The Adempiere Server Monitor lists the following which does not make any sense at all

    Thuthuka Ltd - Accounting Processor (Running)
    Thuthuka Ltd - Accounting Processor (Running)
    GardenWorld Request Processor (Running)
    GardenWorld Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    GardenWorld Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    Thuthuka Ltd - Request Processor (Running)
    System Workflow Processor (Running)
    System Alert Processor (Running)
    Delete Old Notes (Running)
    Adempiere LDAP Server (Running)

    At current, I am thinking that the request processor does not check if the process is active or not and still processes according to the settings.

    The problem is that the “Request Updated” email does not say the reason it is updated. 
    its a “Reminder” or  “Alert” or “Escalate” or “Inactivity Alert”  after days due 3
    So each email looks identical.

    I am now setting the request processor to
    Frequency type is day
    Frequency is 1 (ie every day)
    Reminder days 0
    Alert after days due 0
    Escalate after days due 0
    Inactivity Alert days  0

    And will see what happens.
    More to follow
    Pete