Topic: 2.1pre6 problems: Java loading, changing seller name

Greetings,
I believe 2.1pre7 fixed this, but this should definitely be resolved in the most recent version (2.1pre8 at this time).

— Morgan Schweers, CyberFOX!

Topic: 2.1pre6 problems: Java loading, changing seller name

Greetings,
I’m just letting folks know, I’ve pushed up a 2.1pre7-28-gcd0e285 version to the same download spot described above and will be releasing it as a 2.1pre7 officially tomorrow evening, unless some showstoppers come up.

So…please try it out and let me know if there are any showstoppers! :)

It fixes…snipes failing, bad seller names, bad bidder names, auctions seen as fixed price, unable to retrieve prices, selection color customization, private listing recognition, some sticky search and update infinite loops, and it reduces the amount of derby.log data dumped out when debugging is set to true. There’s also a bunch of improvements internally, and some work towards a new feature that a bunch of users have been asking about.

Yeah…there’s a lot of code in there.

It’s about as tested as I can manage personally, so I’d love some more eyes on it! Feedback is all I ask…!

Best of luck with your auctions!

— Morgan Schweers, CyberFOX!

Topic: 2.1pre6 problems: Java loading, changing seller name

Just reporting in: pre7 fixed the seller name issue for me on XP SP3.
Cheers, Matt

Topic: 2.1pre6 problems: Java loading, changing seller name

I just found this, after I posted in the Beta forum – http://forum.jbidwatcher.com/forums/8/topics/2227

I’m getting the seller name issue in JBidwatcher (2.1pre7-8-g61363f2) on MacOS 10.6.3. Also getting auctions showing in JB as Buy it Now, so can’t set a snipe. Details, with pointers to specific auctions, in the post I link to above.

Cheers, Liam

Topic: 2.1pre6 problems: Java loading, changing seller name

Hi Morgan,

just to inform you that the “seller name” problem is also solved on Linux/Opensuse 11.1 with pre7. regards,

Charles

Topic: 2.1pre6 problems: Java loading, changing seller name

Hi Morgan.
First of all, I apologize for my mistake: it’s XP’s Startup, not Autostart like I stated before.
Let me put it this way:
Added to Startup – there it follows the first entry: Logitech Setpoint, the trackball software – Jbidwatcher seems to get its memory management right.
BUT:
If I later need to close it for some reason, the next time I try to start it I will get the dreaded warning window informing me that it ‘Could not create the Java virtual machine’. This latter is the ‘on-its-own situation’.

Topic: 2.1pre6 problems: Java loading, changing seller name

Greetings,
Erf; drastic, but understandable.

Wait…‘Added it to Autostart’? Tell me more about this; what did you do? I’m not familiar with that.

What happens if you don’t add it to Autostart, just run it on its own?

— Morgan Schweers, CyberFOX!

Topic: 2.1pre6 problems: Java loading, changing seller name

Many thanks Morgan.
I have finally managed to make 2.1pre7 work again, but it took some (cold) sweat & tears before I saw it start.
Since my PC is indeed public-facing, it wasn’t possible go for the radical solution you kindly provided.
Instead, I chose a milder version of the same method:

1. I uninstalled ALL Java components, from within and outside of Firefox. For that I also needed to do the somewhat risky job of fiddling with Firefox’s config.
2. I uninstalled eMule, SoulSeek and every other application I don’t need ‘to survive’.
After very single step that involved deleting files and/or folders I ran TuneUp 1-Click Mainenance until it showed ZERO issues.
3. after being Absolutely Sure I left no traces of Java software, I TuneUp-defragged the registry, which of course implied a reboot.
4. now, having a ‘system free of Java software’, I went to java.com and downloaded the complete environment again.
5. finally, I added 2.1pre7 to Autostart and rebooted again.

It is under these circumstances ONLY does it agree to work: closing and restarting it after the Autostart sequence further triggers the error window.

I really hope at least some of these details will come in handy for you.
Thanks A LOT for your help.

Topic: 2.1pre6 problems: Java loading, changing seller name

Greetings,
@doomkrad

Bleh.

Step back, bring your system up without anything running. No anti-virus, no extensions/services/etc., bring it up in a clean mode, so nothing is running in the background. (Caveat: Don’t do this if your system doesn’t have a hardware firewall/NAT between you and the internet. This is most likely the case if your IP address is a public-facing one (doesn’t start with 10, or 192.168.)

Try to run JBidwatcher in that clean mode, without any extraneous services running. Not because you want JBidwatcher to be running like that always, but rather because it will tell you if something else you run under normal circumstances is interfering.

It can be a real pain to get a Windows box to that state, and again, if your system faces directly into the maelstrom that is the Internet, without a NAT or hardware firewall between you and the world, then don’t do this. It’s terrifying how fast an internet-facing Windows PC gets taken over.

It really sounds like something is interfering with your JVM, though, so it’s the best test I can think of.

— Morgan Schweers, CyberFOX!

Topic: 2.1pre6 problems: Java loading, changing seller name

Hi Morgan,
2.1pre7 has now completely stopped working because of the Java virtual machine issue. I cannot even start the 2.1pre7 Installer, to try a new installation: I’m getting the same error window.
I have also googled the topic JVM tuning etc., that’s a science in itself…
I’m doomed.

Topic: 2.1pre6 problems: Java loading, changing seller name

Greetings,
@santa – I’m not seeing that; can you give me some item numbers that are failing?

Is there a possibility that you ran the wrong version…? It would have started up with the seller names correct from the last time JBidwatcher was run, and then as it walked through them, updating the seller info, it would pull the wrong data again. Use ‘About JBidwatcher’ and make sure you’re running version 2.1pre7-0-ga318f67.

— Morgan Schweers, CyberFOX!

Topic: 2.1pre6 problems: Java loading, changing seller name

Hi Morgan,
I just discovered 2.1pre7, I (monitoring this topic didn’t show any effect unfortunately), I started it and now the seller names are shown correctly again after its ‘startup initialization’. Many Thanks for 2.1pre7.
Now to the ‘Java virtual machine’ issue: with both processes closed down (the Jbidwatcher process and jqs) I still need to reboot to make the application work.
I’ll keep an eye on both matters and also keep you up-to-date with anything worth mentioning.
Thanks again for the fix to the eBay seller issue.

Topic: 2.1pre6 problems: Java loading, changing seller name

Hi,
The problem of name of ebayer seems resolute on linux/ubuntu with 2.1pre7.

Thanks

Topic: 2.1pre6 problems: Java loading, changing seller name

hi – tested windows version on Xp sp3 – problem seller name solved – have a nice day

Topic: 2.1pre6 problems: Java loading, changing seller name

Greetings,
@doomkrad – For problem #1, I’d watch out for memory issues, mainly. Check that JBidwatcher and any Java processes have completely closed down before running JBidwatcher again, and see if that helps. (Force them to quit only if absolutely necessary.) Reading around (I googled the text you quoted) suggests that there are some problems with applications that set custom environment variables, and other issues.

— Morgan Schweers, CyberFOX!

Topic: 2.1pre6 problems: Java loading, changing seller name

Greetings,
eBay changed the way things are laid out on their item pages…again.

I’m trying out a new way of getting versions out; I need folks to test them before I release them… I’d like you to try out a pre-prerelease, and let me know if it resolves your issues. (It may warn about a ‘newer version’, 2.1pre6. Ignore it.)

Standalone Windows: http://www.jbidwatcher.com/download/JBidwatcher…
Disk Image (Mac OS X): http://www.jbidwatcher.com/download/JBidwatcher…
Linux .jar: http://www.jbidwatcher.com/download/JBidwatcher…

As per usual, please let me know in as much detail as you can, about any issues you run into! This isn’t an official 2.1pre7 release, but it’s for folks who are willing to spend some extra time helping with the debugging.

— Morgan Schweers, CyberFOX!

Topic: 2.1pre6 problems: Java loading, changing seller name

I 3rd this report as to part 2

Topic: 2.1pre6 problems: Java loading, changing seller name

Hi!
I just noticed 2 issues on the freshly installed 2.1pre6:
1. closing and reopening the application causes a warning window to appear: ‘Could not create the Java virtual machine’, JBidwatcher doesn’t start, a reboot is needed to make it work again and
2. when adding new auctions the seller name is changed to (until now): ‘a question’ or ‘- opens in a new window’.
To exclude a PC infection I just updated ZoneAlarm to Extreme Security 9.1.008.000 and immediately ran a full scan, no infection is shown.

Topic: Most auctions appear as FP

I am using 2.1 pre4 on XP and ebay.co.uk and have the false FP issue – it also sets the prices to an incorrect figure.

But I have found that, if I drop JBidwatcher and restart it again, it comes back working. This seems to toggle – restart it again and it comes back broken……

Just means that in the morning you start JBid twice…

Topic: Most auctions appear as FP

Why are you not using the current version (JBW 2.1Pre4)?

Just curious…

Topic: Most auctions appear as FP

Hi Morgan,

Sorry for bad news but JBidwatcher 2.0.1-825 still has false-FPs.
Sample auction numbers are 180394658849 and 320407333795.

Topic: Most auctions appear as FP

Hi Morgan, thanks for 2.1pre4, I downloaded it roughly an hour ago.
One issue that will probably interest you:
the US item (added after moving to 2.1pre4) 220463091784 shows the seller as (unknown).
If there are any other details that I can provide about it, please let me know.
Thanks again,
Valentin

Topic: Most auctions appear as FP

Hi Morgan. Thanks for the updates….

Don’t worry about My jbw, not using it right now.

I do notice more memory being consumed. pre2 and before would sit at around 100MB of private memory (xp sp3) for the javaw process. pre3 ends up at about 100MB after the initial startup/update cycle. after about 24 hours, it’s up to 140MB-ish but I haven’t had a longer program run since I started using pre3…

Topic: Most auctions appear as FP

Greetings,
@Richard Beels – You’ve got the right idea on #6; ebay.adult was the old setting, which most people clicked because it seemed the right thing to do. :) I try to discourage it in the 2.x series, because it’s a much more complex flow, so I made folks who wanted it enabled re-enable it, by changing the configuration name.

I think I know what’s breaking with search between sessions, but it’s going to take a little bit for me to fix it.

Fixed price ‘winners’ is another thing that I’m working on; it’s similar to auction winners, but since there can be multiple buyers, it makes it a little harder.

My JBidwatcher is really, really raw right now. If you sign up for it on the web site, it’ll send you an access key (although I have to bump up your access by hand afterwards), but you can also use your web site password. (I strongly recommend against making it the same as your eBay password.) I’m too busy trying to get JBidwatcher working to spend time on the web app, but I really want to get back to it as soon as possible.

Thanks for the pointer to listings that are failing the feedback parse; I’ll try and figure out what I can do…

Glad snipes are working for you! :)

— Morgan Schweers, CyberFOX!

Topic: Most auctions appear as FP

Greetings,
@buserror – I believe you have out-of-date overrides, so your date/time parsing is broken. Overrides carry over from version to version, so it’s very possible to carry them as you upgrade. I twittered the steps to clear them out in an @ message to you.

Fundamentally, if you open the Advanced tab, type ‘override’ into the key area, it should pull up any overrides you might have defined. Select each in turn, and click ‘Delete’ to remove that key. Then, once you’re done, save the changes, exit JBidwatcher and restart it.

The overrides should be gone, and auction updates afterwards should show up correctly.

— Morgan Schweers, CyberFOX!