Failure receiving payment capture notification

Bug #684042 reported by Michael Nelson on 2010-12-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Software Center Agent
Michael Nelson

Bug Description

Since bug 656533 was released, we are not seeing the huge number of payment_notification errors for other statuses, but we are still seeing oopses during CAPTURE notifications.

There was one example of this at 2010-11-30T12:53:59.881324+00:00

There is no corresponding traceback in the webapp log at this time :/
2010-11-30 12:16:48,625 - sca.models - INFO - subscription (id: 2233) by******** for Vendetta Online ($0.00): New -> PaymentNotificationReceived: Skipping payment process for free app.
2010-11-30 12:59:52,960 - sca.models - INFO - subscription (id: 2240) by******* for Vendetta Online ($0.00): New -> PaymentNotificationReceived: Skipping payment process for free app.

description: updated
tags: added: oops
Changed in software-center-agent:
status: New → In Progress
assignee: nobody → Michael Nelson (michael.nelson)
importance: Undecided → Medium
Changed in software-center-agent:
status: In Progress → Fix Committed
Michael Nelson (michael.nelson) wrote :

Although it doesn't affect the purchase process (as we don't trust the insecure notifications received from pay and instead query pay via the API), we are still seeing 500 errors when receiving the captured payment notification, like:

so I've put this back to confirmed and may take a quick look.

Changed in software-center-agent:
status: Fix Committed → Confirmed
Michael Nelson (michael.nelson) wrote :

Here's a dump of what I found out in case anyone else has ideas:

   * There are plenty of subscriptions where the CAPTURED notification is handled without error in the logs, so either something about the state of the subscription or the server different.
   * I can even post to the notification url given in the above oops and it works just fine
   * The fact that there is no log message before the oops suggests that we're not getting to the
 subscription._set_state() call.

So I'm left thinking something temporal (a transaction rollback on the view? or something related to the timestamp used during _set_state?) is causing these few remaining notification 500s.

Of course, if we had tracebacks in the related oopses, things would be a lot simpler. At first I thought it was to do with the:
    2011-04-17 14:37:46,144 - root - ERROR - Error when dumping OOPS 1933rangpur3
messages we were seeing in the log, but then, it's hard to tell, as we currently have r54 installed on the production server [1], and it was r56 that stopped this (incorrect) error message being printed for each oops [2].


Dave Morley (davmor2) on 2012-11-16
Changed in software-center-agent:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers