#696 ✓resolved
Therese Telepski

JBW 2.01-825 not cancelling multisnipe groups after won snipe

Reported by Therese Telepski | February 17th, 2009 @ 03:58 AM | in 2.1 Release

Ooouuups -- now it has happened. I've won 13 (!) items of a multisnipe group. Noe is realized as won in the 'completed' tab. Other members of that multisnipe group aren't cancelled out.

I probably will be able to resell them, however such a thing is serious.

A few numbers:

150326816754 end time 17.02.09 07:49:43 MEZ

150326816672 end time 17.02.09 07:48:26 MEZ

150326816558 end time 17.02.09 07:46:43 MEZ

150326816497 end time 17.02.09 07:45:58 MEZ

Yes, they are close together, admittedly. but 45 seconds to 1½ minutes basically should be enough to retrieve at least one winning auction and cancel out the other ones.

A look into the error log reveals JBW apparently has noticed these items as successful bids, even says that other members of that group havn't been updated and thus other snipes of that group are going to be cancelled -- however it does not do so ... :-((

Sincerely,

Therese

Comments and changes to this ticket

  • Morgan Schweers

    Morgan Schweers February 17th, 2009 @ 05:14 AM

    • Tag changed from bug, multisnipe, serious to acknowledged, bug, multisnipe, serious
    • State changed from “new” to “open”

    Greetings,

    Hmmmm; interesting. Looks like problems started around 5pm on the 15th; it appears to be attempting to double-snipe on items. I'm guessing that it's double-registering a snipe; one with the internal server to handle ebay.com and one with the internal server to handle ebay.co.uk.

    I'm looking into it now; that's beyond serious, that's downright dangerous.

    -- Morgan Schweers, CyberFOX!

  • Morgan Schweers

    Morgan Schweers February 17th, 2009 @ 06:38 AM

    Greetings,

    So far I've been able to confirm that snipes are handled wrong; they end up being 'owned' by both the default server (that handles ebay.com) and the secondary server (that handles ebay.co.uk) if they exist only on the ebay.co.uk site. I can fix that easily, but I can't confirm that that problem causes the multisnipe to fire for multiple entries. Specifically, the snipe that is on the ebay.com site shouldn't successfully fire, because ebay.com doesn't accept bids for items that aren't visible on that site. :(

    I also don't understand why suddenly, 10 hours into it, it starts 'postponing' messages to the internal server. Messages like 'cancel snipe', and 'do seller search'.

    Argh; one bug down (losing items in between sessions), another two or more bugs up (too-long load times, this multisnipe failure).

    You can get what I've done so far at:

    http://next.jbidwatcher.com/down...

    It should fix the problem I described above, where snipes end up being handled by both the ebay.com and ebay.co.uk server handlers, but I can't promise it'll fix the multisniping problem entirely. (It also should fix the 'lost auction' problems. You might get a 'recovered' tab, the first time you start it up again with items that got orphaned.)

    -- Morgan Schweers, CyberFOX!

    p.s. That log is amazing. It's got just about everything I could want to understand the behavior of JBidwatcher in a large scale use. There are HTML pages that it didn't recognize, snipes firing and snipes failing, JBidwatcher behaving very well, and very badly. I'm going to be mining that log for a while yet...once I wake up again, at least.

  • Therese Telepski

    Therese Telepski February 17th, 2009 @ 01:51 PM

    Dear Morgan,

    alright, just downloaded that 'hidden' file.

    Some lost ended items I didn't even notice actually were recovered (usually I deleted them after a short while to avoid blowing up the database with information that never will be needed anyway.

    The 'Selling' tab is filled again.

    Re multisnipes I can tell more when the next one goes through.

    Sincerely,

    Therese

  • Morgan Schweers

    Morgan Schweers February 17th, 2009 @ 06:43 PM

    (from [811]) If the username or password changed for the eBay server, the underlying hash code changed, which broke the Message Queueing system by not finding the correct server anymore, so critical server messages (like cancel snipe) weren't being received anymore. Should help address [#696] at least.

  • duncanSF

    duncanSF February 21st, 2009 @ 03:45 AM

    Ticket #709 may be a simpler case tickling the same bug. A single auction successfully sniped is also not flagged as having been won in the completed tab's list of auctions.

  • RT

    RT March 6th, 2009 @ 02:53 PM

    The same thing happened to me today. I multisniped 10 items and won 3 of them! Luckily, I caught it before the last 4 auctions ended and changed my ebay password, or I would've wound up with 5! I'm attaching screenshots with the items highlighted that I multisniped, and the error and activity logs. Please let me know if any other info would be helpful for troubleshooting.

  • RT

    RT March 6th, 2009 @ 03:01 PM

    One more thing... the first item that I won was under my maximum bid amount ($26.03 w/ shipping). The second and third came out to $29.27 and $26.09, respectively, so not only were the bid on after I won a similar item in a single multisnipe, but the program wound up bidding over my maximum amount as well.

  • Nils Philippsen

    Nils Philippsen March 8th, 2009 @ 05:33 AM

    Same here with 2.0.1-825 on Linux. I'm attaching all files in ~/.jbidwatcher with a current timestamp (from today when the error happened), sans password of course.

  • jmccabe

    jmccabe March 9th, 2009 @ 04:07 AM

    Just thought I'd add that I've had a similar problem to this, but fortunately only won one item. The item I won though has the following in the "show information" box:

    
    Sun Mar 08 18:57:40 GMT 2009: Preparing snipe.
    Sun Mar 08 18:57:42 GMT 2009: Loading bid request... 
    Sun Mar 08 18:57:43 GMT 2009: Done loading bid request, got form... 
    Sun Mar 08 18:59:39 GMT 2009: Firing actual snipe. 
    Sun Mar 08 18:59:40 GMT 2009: Submitting bid form. 
    Sun Mar 08 18:59:41 GMT 2009: Successfully sniped a high bid on Alesis Microverb 3! 
    Sun Mar 08 18:59:41 GMT 2009: Done loading post-bid data. 
    Sun Mar 08 18:59:41 GMT 2009: Loading post-bid data. 
    Sun Mar 08 18:59:41 GMT 2009: Done submitting bid form. 
    Sun Mar 08 18:59:42 GMT 2009: Preparing snipe. 
    Sun Mar 08 18:59:45 GMT 2009: Loading bid request... 
    Sun Mar 08 18:59:46 GMT 2009: Cancelling snipe. 
    Sun Mar 08 18:59:46 GMT 2009: Snipe was too low, and was not accepted. 
    

    I've attached a log of the session (with my user name in some of the http requests changed). Perhaps the "Bad input tag" stuff is significant. Is there something I've missed (like should I be using the new MyEbay format?).

  • Therese Telepski

    Therese Telepski March 9th, 2009 @ 11:30 AM

    @jmccabe: The last one looks like JBW firing two snipes at the same item directly after one another.

    I remember to have read about this issue marked as harmless.

    So far for me JBW2.01-825 hasn't done anything seriously wrong on multisnipes (VISTA32, JAVA 6.12). At least for this Windows platform the multisnipe issue seemes to be handled.

    Sincerely,

    Therese

  • jmccabe

    jmccabe March 9th, 2009 @ 02:17 PM

    @Therese

    Hi,

    Yes, you're right it does look like JBW has tried two snipes on the same item at the same time. It may be harmless, but it's strange and unexpected behaviour. In the log file that I posted though you can see that JBW then has difficulty finding out who won the item and as a result the other snipes that were part of this multisnipe remained active. Fortunately for me, these other snipes were a couple of days later.

    I also have had the issue someone else mentioned with snipes where, if you get JBW to automatically subtract shipping it gets it wrong.

    John

  • Rob Frohne

    Rob Frohne March 10th, 2009 @ 07:26 PM

    This seems to apply to JBW 2.0.1 as well. I just had it purchase two items (only $4.00 for me). I canceled the rest of the multi snipe.

    Rob

  • Joop

    Joop March 11th, 2009 @ 01:31 AM

    Same here. I use JBidwatcher (2.0.1-825) Overnight I won 2 items of about 14 Euro, but had multisniped on 8 items, phew... Still lucky I guess.

    The log of the won bids states: "Wed Mar 11 05:56:24 CET 2009: Your bid was below or equal to your previous high bid, and was not accepted."

    But when looking at the screen this morning the programs shows a "won checkmark" at the articles???

    Joop

  • Dave Burton

    Dave Burton March 11th, 2009 @ 02:12 PM

    • Tag changed from acknowledged, bug, multisnipe, serious to bug, multisnipe, serious

    I'm using the current version of JBidWatcher (2.0.1-825). This happened to me, too.

    I had a multisnipe set to buy one of several old m100 and m105 Palm Pilots. I won one of them, but jbidwatcher did not cancel the rest of the multisnipe group.

    Fortunately, I noticed it before the next snipe happened, and I manually cancelled the rest of the snipes. So I didn't have any accidental purchases.

    Here's what happened, to the best of my recollection:

    I'd set the general multisnipe amount for the whole group of PDAs to $7.00 total, including shipping. The first item had an opening bid price of $.99, and a shipping cost of $6.00, so my initial snipe amount for it was set to $7.01.

    However, I had sent a question to the seller, and she replied promptly. I liked the answer, so I right-clicked on that item in jbidwatcher, and increased my snipe amount (for that item, only) to $11 including shipping. That changed my maximum bid amount from $1.01 to $5.01. I left the snipe amounts for the other auctions unchanged.

    After the auction close, I noticed that only three PDAs were still shown on the "current" tab of JBidWatcher. They were still highlighted in the multisnipe group, so I assumed that I'd not won the first auction. Out of curiosity I clicked on the "complete" tab to see what the final price was. To my surprise, it showed "$0.99 (1)" and there was a big green checkmark in the "status" column!

    My snipe had been successful, yet the rest of the snipes in the multisnipe group had not been cancelled.

    The auction that I won was: 260372853087

    The log file shows a few errors:

    During startup: Error setting up scripting: java.lang.NoClassDefFoundError: org/jruby/runtime/builtin/IRubyObject Also at startup, 14 long-expired auctions show these errors: We appear to be waking from sleep; networking may not be up yet. The computer may have slept through the snipe time!

    Later (at 44 different times) we get this error: eBay says my max bid is a different type of currency than I have stored! Cannot compare different currencies. at com.jbidwatcher.util.Currency.less(Currency.java:610) at com.jbidwatcher.auction.server.ebay.ebayAuction.setMaxBidFromServer(ebayAuction.java:642) at com.jbidwatcher.auction.server.ebay.ebayAuction.parseAuction(ebayAuction.java:425) at com.jbidwatcher.auction.server.AuctionServer.doParse(AuctionServer.java:264) at com.jbidwatcher.auction.server.AuctionServer.loadAuction(AuctionServer.java:212) at com.jbidwatcher.auction.server.AuctionServer.reload(AuctionServer.java:182) at com.jbidwatcher.auction.AuctionEntry.update(AuctionEntry.java:1135) at com.jbidwatcher.auction.Auctions.doUpdate(Auctions.java:158) at com.jbidwatcher.auction.Auctions.doNextUpdate(Auctions.java:188) at com.jbidwatcher.auction.Auctions.check(Auctions.java:210) at com.jbidwatcher.ui.ListManager.checkEachList(ListManager.java:152) at com.jbidwatcher.ui.AuctionsManager.check(AuctionsManager.java:93) at com.jbidwatcher.util.queue.TimerHandler.run(TimerHandler.java:56)

    Then this legitimate failed snipe: Tue Mar 10 17:46:03 GMT-05:00 2009: 180333720661 (Palm M100 with Nice Carrying Case) - Preparing snipe. Tue Mar 10 17:48:03 GMT-05:00 2009: 180333720661 (Palm M100 with Nice Carrying Case) - Firing actual snipe. Tue Mar 10 17:48:04 GMT-05:00 2009: 180333720661 (Palm M100 with Nice Carrying Case) - You have been outbid in your snipe on Palm M100 with Nice Carrying Case Tue Mar 10 17:48:05 GMT-05:00 2009: 180333720661 (Palm M100 with Nice Carrying Case) - Preparing snipe. Tue Mar 10 17:48:07 GMT-05:00 2009: 180333720661 (Palm M100 with Nice Carrying Case) - Snipe was too low, and was not accepted. Tue Mar 10 17:48:07 GMT-05:00 2009: 180333720661 (Palm M100 with Nice Carrying Case) - Cancelling snipe. Tue Mar 10 17:48:08 GMT-05:00 2009: 180333720661 (Palm M100 with Nice Carrying Case) - Preparing snipe. Tue Mar 10 17:48:09 GMT-05:00 2009: 180333720661 (Palm M100 with Nice Carrying Case) - Snipe was too low, and was not accepted. Tue Mar 10 17:48:09 GMT-05:00 2009: 180333720661 (Palm M100 with Nice Carrying Case) - Cancelling snipe.

    Note that it appears that jbidwatcher tried twice more after the initial snipe failed. That seems strange, though perhaps innocuous.

    Then this is the snipe which won the auction. Note that the snipe worked, but then jbidwatcher tried twice more to snipe, and those (of course) failed: Wed Mar 11 11:38:36 GMT-05:00 2009: 260372853087 (PALM M105 PDA with Palm Leather Case) - Preparing snipe. Wed Mar 11 11:40:36 GMT-05:00 2009: 260372853087 (PALM M105 PDA with Palm Leather Case) - Firing actual snipe. Wed Mar 11 11:40:37 GMT-05:00 2009: 260372853087 (PALM M105 PDA with Palm Leather Case) - Successfully sniped a high bid on PALM M105 PDA with Palm Leather Case! Wed Mar 11 11:40:39 GMT-05:00 2009: 260372853087 (PALM M105 PDA with Palm Leather Case) - Preparing snipe. Wed Mar 11 11:40:41 GMT-05:00 2009: 260372853087 (PALM M105 PDA with Palm Leather Case) - Your bid was below or equal to your previous high bid, and was not accepted. Wed Mar 11 11:40:41 GMT-05:00 2009: 260372853087 (PALM M105 PDA with Palm Leather Case) - Cancelling snipe. Wed Mar 11 11:40:43 GMT-05:00 2009: Wed Mar 11 11:40:42 GMT-05:00 2009: 260372853087 (PALM M105 PDA with Palm Leather Case) - Preparing snipe. Wed Mar 11 11:40:45 GMT-05:00 2009: 260372853087 (PALM M105 PDA with Palm Leather Case) - Your bid was below or equal to your previous high bid, and was not accepted. Wed Mar 11 11:40:45 GMT-05:00 2009: 260372853087 (PALM M105 PDA with Palm Leather Case) - Cancelling snipe.

    A few hours later I manually cancelled the other snipes in the multisnipe group, and shut down jbidwatcher: Wed Mar 11 14:48:58 GMT-05:00 2009: 230329392551 (Palm M100 - PDA, includes case - FREE SHIPPING!!) - Cancelling snipe. Wed Mar 11 14:49:01 GMT-05:00 2009: 110361441622 (Palm M100 PDA, Serial cable, Software and Carrying Case) - Cancelling snipe. Wed Mar 11 14:49:03 GMT-05:00 2009: 230330457250 (Palm M100) - Cancelling snipe. Wed Mar 11 15:37:58 GMT-05:00 2009: Shutting down JBidwatcher.

    I hope this helps!

    Dave

  • Dave Burton

    Dave Burton March 11th, 2009 @ 03:20 PM

    Typo correction:

    "so my initial snipe amount for it was set to $7.01."

    Should have said:

    "so my initial snipe amount for it was set to $1.01."

  • Rod Smith

    Rod Smith March 13th, 2009 @ 12:02 PM

    FWIW, I ran into this recently, too, although fortunately I didn't win anything beyond my initial winning auction. I noticed the following in the auction information screen for the auction that won:

    Fri Mar 13 12:21:41 EDT 2009: Preparing snipe. Fri Mar 13 12:23:41 EDT 2009: Firing actual snipe. Fri Mar 13 12:23:42 EDT 2009: Successfully sniped a high bid on Mamiya TLR 80mm f2.8 lens 80/2.8 C-330 C330! Fri Mar 13 12:23:43 EDT 2009: Preparing snipe. Fri Mar 13 12:23:45 EDT 2009: Cancelling snipe. Fri Mar 13 12:23:45 EDT 2009: Your bid was below or equal to your previous high bid, and was not accepted.

    So it looks as if JBW tried to snipe twice. (I did change my snipe amount prior to any bids being placed; I don't know if this is relevant.)

  • Dave Burton

    Dave Burton March 25th, 2009 @ 02:24 AM

    Morgan, if this is hard to fix, maybe you should temporarily disable multisnipes altogether, so that someone doesn't accidentally buy five automobiles.

  • Dave Burton

    Dave Burton March 25th, 2009 @ 04:08 AM

    BTW, it appears that tickets 726, 746 & 760 are all duplicates of ticket #696.

  • Dave Burton

    Dave Burton March 27th, 2009 @ 06:28 AM

    Unfortunately, I've now seen another variant of this problem.

    As before, jbidwatcher logs that it "Successfully sniped a high bid" but then it immediately (2 seconds later, in this case) prepares another (erroneous) snipe for the same auction.

    But what happens next is different. The log records:

    Failure to get the bid key! BID FAILURE! Read timed out

    Then:

    Cancelling snipe, auction is reported as ended. Cancelling snipe. Cancelling snipe, auction is reported as ended. Cancelling snipe.

    Also, at every step jbidwatcher is reporting:

    eBay says my max bid is a different type of currency than I have stored! Cannot compare different currencies.

    When the dust settles, the result is the same as before: I won the first auction in the multisnipe group, but the rest of the snipes didn't get cancelled.

    However, my emailed suggestion to simply cancel the multisnipe whenever you see a snipe result of "Your bid was below or equal to your previous high bid and was not accepted" will not solve the problem with this new scenario.

    The log file is attached; I'll also email you a few more files (auctions.xml, .htm captures of the auction and bid history pages, derby.log).

    Dave

  • Therese Telepski

    Therese Telepski April 1st, 2009 @ 06:43 AM

    • Title changed from “JBW 2.0-800 not cancelling multisnipe groups after won snipe” to “JBW 2.01-825 not cancelling multisnipe groups after won snipe”

    And yet another instance of the initial problem even with the latest version of JBW.

    The same as the initial problem -- won an item of a multisnipe group, the other items weren't cancelled out.

    VISTA32, Java 6.12, JBW 2.01-825.

    Sincerely,

    Therese

  • Therese Telepski

    Therese Telepski April 1st, 2009 @ 02:27 PM

    Two other one auctions from bid groups. In one case the other multisnipes were cancelled out, in the other case not.

    Error log is attached.

    Sincerely,

    Therese

  • Kirby Files

    Kirby Files May 11th, 2009 @ 08:07 AM

    I have my own experience with this bug now. Also using 2.01-825 (on Linux). Attached are the auction datafiles from auctionsave/, and the error and derby logs. Both auctions have the check mark in the Completed auctions, despite the log saying that "bid was too low" for both successful snipes.

    In my case, I only ended up buying two $30 items. I'm hoping I can relist the second for minimal loss, but overbuying kinda defeats the purpose of sniping.

    I'm going to revert to 2.0beta11, as others have reported better luck with that version. This bug is too serious to continue beta testing 2.0.1.

  • Morgan Schweers

    Morgan Schweers May 16th, 2009 @ 03:58 AM

    • Tag changed from bug, multisnipe, serious to @moved, bug, multisnipe, serious
    • Milestone changed from 2.0 Full Release to 2.1 Release

    [milestone:ID#38598 tagged:"@moved" bulk edit command]

  • Morgan Schweers

    Morgan Schweers July 9th, 2009 @ 04:47 AM

    • Tag changed from @moved, bug, multisnipe, serious to @moved, bug, committed, multisnipe, serious
    • State changed from “open” to “resolved”

    (from [975]) Don't re-establish snipes if the snipe has been cleared but the multisnipe data is still in place (i.e. the snipe has fired successfully, but the auction hasn't ended yet). The re-established snipe fails, which causes a snipe cancellation, which removes the item from the multisnipe list even if the user is the high bidder.

    Should fix [#696 state:resolved tagged:committed]

  • Dave Burton

    Dave Burton July 15th, 2010 @ 11:53 PM

    • Tag changed from @moved, bug, committed, multisnipe, serious to @moved, bug, committed, multisnipe
    • Milestone order changed from “0” to “0”

    Morgan, this problem is still happening in 2.1pre8, It is very discouraging that this serious problem has been happening for about 1.5 years. See:

    https://jbidwatcher.lighthouseapp.com/projects/8037/tickets/1025-mu...

    and

    https://jbidwatcher.lighthouseapp.com/projects/8037/tickets/1133-fa...

    Dave

  • Morgan Schweers

    Morgan Schweers August 2nd, 2010 @ 02:16 AM

    Greetings,
    Check out #1133; I believe I've found and fixed @Dave Burton's issue with 2.1pre8. Bid retractions would fubar multisnipes because it wouldn't recognize the current user as the high bidder, and therefore wouldn't cancel subsequent multisnipes.

    Different problem, same manifestation.

    -- Morgan Schweers, CyberFOX!

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Shared Ticket Bins

Referenced by

Pages