in reply to Re: ChatterBox XML Ticker randomly throwing messages away
in thread ChatterBox XML Ticker randomly throwing messages away

No, the message is not logged in the DB, at least not in the chat box portion. I can verify this because I store the PM ID numbers that come back with each message for the CB stats. When the stats service goes down and I miss it on reboot, I can see a "space" in the ID numbers. When this error is hit on my end, there is no gap.

I no longer have pmdev access here (as per my own request years ago), but I seem to recall that there is a field in the user that stores the last message that that user posted, and is used for comparison to get the whoa-cowboy rejection message. It appears to me that the message gets to the server far enough to be saved to the user record, but fails between that and actually putting it into the CB table. I'd argue that it shouldn't get saved to the user record until it has been successfully saved to the CB table (or both as part of the same transaction), but that's just arguing about error handling and doesn't solve the underlying error.

(Thanks, choroba, for posting this.)

  • Comment on Re^2: ChatterBox XML Ticker randomly throwing messages away

Replies are listed 'Best First'.
Re^3: ChatterBox XML Ticker randomly throwing messages away
by LanX (Archbishop) on Jul 08, 2019 at 06:01 UTC
    Thanks, great insight.

    > I no longer have pmdev access here

    I think the most efficient approach would be to make you pmdev again.

    > (as per my own request years ago),

    Shouldn't be a problem to leave afterwards again. :)

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

      The underlying reasoning for requesting my own removal has not changed. Well, it has, but not for the better. I have insufficient time for the projects on my to-do list, and that has gotten worse since my removal, not better. The trend line is in the wrong direction :P As much as I would love to support jdporter on this, the reality is that providing the above clues is about as much as I can do right now. Signing on as a pmdev again would imply things that would be untrue, which I consider to be a form of lying. (Which I do differentiate from "I did something once, and it's too much work to get myself removed, so I'm leaving it alone" - I had pmdev access for years after I stopped contributing in that way, too.)

      I wish I had time for that type of help again. If wishes were nickels, though, I'd be rich.

        > . I have insufficient time for the projects on my to-do list,

        Me too, I don't have the ressources to spend on this particular problem.

        And if I was, I'd bother you with so many questions that you'd rather prefer digging into it again for a day and then leaving pmdev again.

        > As much as I would love to support jdporter

        You'd support choroba it's his baby suffering for a long time now.

        To be clear: I'm only expecting a clean analysis from you hinting into the right direction.

        Not a fix nor a patch. Nothing else than at most some hours work.

        Anyway I'm fine with any decision ... just clarifying my POV! :)

        Cheers Rolf
        (addicted to the Perl Programming Language :)
        Wikisyntax for the Monastery FootballPerl is like chess, only without the dice