Error communicating with server
Brought to you by:
cyberfox
Hi!
I have successfully used Jbidwatcher (version 0.9.3.1) with
www.ebay.de to snipe some items. After the update to 0.9.5 I only
get "Error communicating with Server" upon startup. Since I am
behind a firewall, I tested the searching for an updated version
whcih works, so I guess, the proxy that I have set in the settings
is found and used. Even the going back to version 0.9.3.1 wont
work since I am unable to add an auction, but in this version the
communication with the server works.
my system:
- Linux Mandrake 10.1
- java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)
- jBidwatcher 0.9.5
Cheers Juergen
Logged In: YES
user_id=741109
It seems the app can connect to the server after like 5/10 minutes if you
just give it some time. After that even resyncing time and searching
works flawlessly.
J.
Logged In: NO
I am experiencing the same issue to a lesser degree. 0.9.3
worked perfectly, then I upgraded to 0.9.5. Now upon
launching the .jar, the dynamic status "wording" area in the
upper right corner states my ebay user name then "Error
communicating with Server". After about 15-30 seconds, the
time synchronizes and then all My Ebay items update. After
that sniping and updating works fine.
My system:
Windows XP Pro SP2
Sun Java RE 1.4.2_06
jbidwatcher 0.9.5
I am behind a router and software firewall...I have tried
disabling the software firewall and connecting directly to my
modem, no affect...same error message regardless of
connection configuration.
I also turned off the "Registered Adult" setting as stated on
the website, but this made no difference. All my
configuration settings work fine, the new build works fine
after the initial launch of the .jar.
Thank you for a wonderful app, truly appreciated.
Logged In: NO
I've just installed 0.9.5 on my Windows XP SP1 laptop and
I'm getting this error too when I load the app. I have no
prior experience with this app, so it could be user error
for all i know. I get the "error communicating with server"
error as soon as I launch the app. I've entered my ebay
username and password, selected ebay.co.uk option, and
that's all. I did try "start firefox" for the Browser
"Windows Command" but whatever I tried it gave "Failed to
launch browser". Looks like a promising app but I've got
nowhere with it yet...
my setup:
- Windows XP Service Pack 1
- java 2 Runtime 1.4.2_03 (and also 1.3.1_01).
- Router with firewall. No software firewall.
Logged In: NO
I have this problem too.
I think this one may be related to bug 1108973.
Logged In: YES
user_id=19745
Greetings,
I have just completed a move to Seattle, and finally have my
primary development systems up and running again, just today.
Coming up to speed at my new job, and situating myself in my new
apartment, with fiancee and cat, all has eaten up every available
cycle of my time until just recently. With my primary dev
environment back up (and not rebooting every 5 minutes!), I'm
able to start to address some of the problems people have been
reporting.
I've been trying to debug with one hand tied behind my back,
effectively, recently. Hopefully with the new setup, and
everything coming live, I'll be better able to respond and fix
problems.
I apologize for my awful response time, recently. Ever since
mid-February, I've been effectively offline. I barely managed
the 0.9.6 release due to eBay's change at one of the worst times
for me in terms of net access, and it looks like I overlooked a
few things in the process. I intend to try and fix those up, and
start on older bugs.
-- Morgan Schweers, CyberFOX!
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!