#910 Snipes Failing 1.0pre6

[John]

Hello Morgan, & people!

(Note: This is duplicated at your blog site!)

I first encountered jbidwatcher at the beginning of the year, release
0.9.9 and didn't have any sniping problems, but since upgrading
(necessarily so) to 1.0.6pre, I have had a very noticeable number of
sniping failures; I would say, between 15 and 20%. Literally, a failure
will occur with a successful snipe either side of it. I am running OS X
10.3.9 and, looking at my console logs, the 'doomed-to-failure' snipe
is apparent from the time that the snipe is prepared and the forms are
requested, resulting specifically in the message:

Failure to get the bid key! BID FAILURE!

Frustratingly though, this console-reported error situation isn't
reflected in the UI which, if you happen to be around when the snipe is
being processed, might allow you to notice, and then 'assume manual
mode'!

Here's a more complete example:

Sun Apr 23 20:47:38 BST 2006: Sun Apr 23 20:47:38 BST 2006:
8057327508 (Originalwerkzeug Alfa 116 Radlager) - Preparing snipe.
(1)
Sun Apr 23 20:47:40 BST 2006: Sun Apr 23 20:47:40 BST 2006:
8057327508 (Originalwerkzeug Alfa 116 Radlager) - Loading bid
request... (1)
Sun Apr 23 20:47:45 BST 2006: Failure to get the bid key! BID
FAILURE!
java.io.IOException
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURL
Connection.java:602)
at Http.receivePage(Http.java:197)
at ebayServer.getBidForm(ebayServer.java:992)
at Snipe.presnipe(Snipe.java:121)
at Snipe.fire(Snipe.java:60)
at ebayServer$SnipeListener.messageAction(ebayServer.java:2701)
at PlainMessageQueue.run(PlainMessageQueue.java:70)
at java.lang.Thread.run(Thread.java:552)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at sun.net.NetworkClient.doConnect(NetworkClient.java:137)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:402)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:618)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:306)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:267)
at sun.net.www.http.HttpClient.New(HttpClient.java:339)
at sun.net.www.http.HttpClient.New(HttpClient.java:320)
at sun.net.www.http.HttpClient.New(HttpClient.java:315)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLC
onnection.java:521)
at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnec
tion.java:498)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURL
Connection.java:626)
at
sun.net.www.protocol.http.HttpURLConnection.getHeaderFieldKey(Http
URLConnection.java:1504)
at CookieJar.getAllCookiesFromPage(CookieJar.java:195)
at CookieJar.getAllCookiesFromPage(CookieJar.java:132)
at ebayServer.getBidForm(ebayServer.java:987)
... 5 more
Sun Apr 23 20:47:45 BST 2006: Sun Apr 23 20:47:45 BST 2006:
8057327508 (Originalwerkzeug Alfa 116 Radlager) - Failed to bid.
'Show Last Error' from context menu to see the failure page from the
bid attempt. (1)
Sun Apr 23 20:48:14 BST 2006: Selection of 1 items changed out from
under 'sum'.
Sun Apr 23 20:48:22 BST 2006: Selection of 1 items changed out from
under 'sum'.
Sun Apr 23 20:48:33 BST 2006: Selection of 1 items changed out from
under 'sum'.

I have more of this kind of report if it would be helpful, but they all
seem to say very much the same. Additionally, I'm unable to select
'Show Last Error' from the contextual menu, which is greyed out.

Notwithstanding the fact that jbidwatcher is a great bit of software
and, along with many people out there, I'm hugely grateful for the work
that is put into it, I have to say that I've consequently lost out on a few
really important (ie: rare) items recently and, as a result, I've now
resorted to entering my maximum bid 'normally' which, sadly, kind of
defeats the object of the program.

I would happily sacrifice search, sort, display functionality/reliability,
for a rock solid snipe!!

I hope you can identify the problem and if I can be of any further help,
providing logs etc., please don't hesitate to ask!

Many thanks,
John

[Morgan Schweers]

Logged In: YES
user_id=19745
Originator: NO

Greetings,
Bugs filed before 1.0 and bugs without responders are being juggled in terms of priority (9 is highest priority). I'm raising bugs filed with a submitter, post-1.0 to P6. Bugs which are filed post-1.0, but without a submitter are P5. Before 1.0 bugs with a submitter are becoming P4, and pre-1.0 bugs without a submitter name become P3.

If the bug is still relevant, and has a watcher (i.e. you got notified when I changed this bug), feel free to bubble it back up again.

Email addresses in bugs are great, but I can't always respond via email. Sometimes, especially for duplicate bugs, I use automated tools (like I'm doing right now) to change status on a large number of items at once.

Thanks for your patience, while I try to pare back the bug list to what may actually still be in the program.

-- Morgan Schweers, CyberFOX!