[Release] JBidwatcher 2.0 is out!
|
Greetings, Fixes include (in no particular order):
|
|
Hi Morgan. When I installed 2.0 on the latest Beta, all my watch items disappeared from JBidW :( And, when I try to add the items, I get a message that the item that I want to add is already on my watch list. TIa for your help. |
|
I forgot to copy the activity log. I’m under Vista Home Premium French. Sun Feb 15 09:52:12 CET 2009: Notify: Failed to load all auctions. |
|
The activity log Sun Feb 15 09:52:11 CET 2009: Error setting up scripting: java.lang.NoClassDefFoundError: org/jruby/runtime/builtin/IRubyObject |
|
Good morning Morgan. I have been using Jbidwatcher for some time, it’s really great. |
|
Greetings, @roger0621 – That’s definitely strange; the new version was supposed to be faster to start up, in fact. :( If you have more than 10 items in your My eBay page, try configuring eBay (on ebay.com) to show more than 10 at a time; it might help JBidwatcher. It might not, but some have reported success by changing their ‘per page’ viewable to around 100. @robrub – I’m not quite sure what happened there; it looks like there was some corruption. I’ll dig into it in the morning. — Morgan Schweers, Cyber*FOX*! |
|
Hi Morgan, |
|
Hi Morgan, |
|
Hi Morgan. Tnx for looking into the problem. BTW, I reinstalled Beta11 and I have all my items back. FYI, the instal of 2.0 was done under “common” (when all users can acces JBidW). I don’t know if this may be a problem. Regards. |
|
Win2K, all patches, beta11 worked fine (reverted to using that now). I used the Windows Installer version for the release V2 with a common install (all defaults taken), and javaw.exe spins with 99% of cpu. Had to kill it with task manager after a few minutes… tried several times – always fails to start up (leaves logo on screen – progress bar empty). Reverting to beta 11 and all is well again… Nick |
|
Hi, I’m running XPpro, SP3, and have just upgraded to JBW V2.0 I have hit a similar problem to robrub – before I upgraded I had put some new auctions in – after I upgraded these were not visible and I could not re-insert them – the error message was that they were already on the list. I tried rebooting but could not get them back. Eventually I had to uninstall Jbid, manually delete (actually rename) all files remaining, then reinstall as clean and re-input all my auctions. Of course that means I lose all my “complete” auction data. Morgan – can you indicate which files the ‘complete’ data is stored in? I copied this – maybe I can get it back. I looked to see if there was an ‘export/import’ feature for backing up, but I couldn’t find one. There is an ‘auction save’, but I don’t know what that is, and an ‘export’ under ‘Tab’, but I don’t know what that does either…:( |
|
Hi Morgan, Thanks for all you do with JBidWatcher! Note: I’ve installed 2.0, didn’t work, re-installed it, didn’t work. Installed 1.0.2pre5 again, didn’t work previously, now it works like a charm. Go figure. 2.0 doesn’t load auctions, loses its menus-have to quit and start again. I’m running MacOSX Leopard. -Dave |
|
Hi Morgan – Sun Feb 15 22:23:04 EST 2009: Error setting up scripting: java.lang.NoClassDefFoundError: org/jruby/runtime/builtin/IRubyObject Sun Feb 15 22:29:36 EST 2009: Loading listings from the database (28/813/816 entries, 895/964 auctions) Sun Feb 15 22:33:00 EST 2009: Done with the initial load (got 28 active entries) Sun Feb 15 22:34:13 EST 2009: Can't get row for update (id = '2167'). A lock could not be obtained within the time requested java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeQuery(Unknown Source) at com.jbidwatcher.util.db.Table.getRow(Table.java:252) at com.jbidwatcher.util.db.Table.updateMap(Table.java:208) at com.jbidwatcher.util.db.Table.insertOrUpdate(Table.java:202) at com.jbidwatcher.util.db.ActiveRecord.saveDB(ActiveRecord.java:116) at com.jbidwatcher.auction.AuctionEntry.saveDB(AuctionEntry.java:1764) at com.jbidwatcher.auction.AuctionEntry.setAuctionInfo(AuctionEntry.java:1591) at com.jbidwatcher.auction.server.AuctionServer.reload(AuctionServer.java:185) 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) Caused by: java.sql.SQLException: A lock could not be obtained within the time requested at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) ... 23 more Caused by: ERROR 40XL1: A lock could not be obtained within the time requested at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.services.locks.ConcurrentLockSet.lockObject(Unknown Source) at org.apache.derby.impl.services.locks.AbstractPool.lockObject(Unknown Source) at org.apache.derby.impl.services.locks.ConcurrentPool.lockObject(Unknown Source) at org.apache.derby.impl.store.raw.xact.RowLocking3.lockContainer(Unknown Source) at org.apache.derby.impl.store.raw.data.BaseContainerHandle.useContainer(Unknown Source) at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source) at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source) at org.apache.derby.impl.store.raw.xact.Xact.openContainer(Unknown Source) at org.apache.derby.impl.store.access.conglomerate.OpenConglomerate.init(Unknown Source) at org.apache.derby.impl.store.access.heap.Heap.open(Unknown Source) at org.apache.derby.impl.store.access.RAMTransaction.openConglomerate(Unknown Source) at org.apache.derby.impl.store.access.RAMTransaction.openCompiledConglomerate(Unknown Source) at org.apache.derby.impl.store.access.btree.index.B2IForwardScan.init(Unknown Source) at org.apache.derby.impl.store.access.btree.index.B2I.openScan(Unknown Source) at org.apache.derby.impl.store.access.RAMTransaction.openScan(Unknown Source) at org.apache.derby.impl.store.access.RAMTransaction.openCompiledScan(Unknown Source) at org.apache.derby.impl.sql.execute.TableScanResultSet.openScanController(Unknown Source) at org.apache.derby.impl.sql.execute.TableScanResultSet.openScanController(Unknown Source) at org.apache.derby.impl.sql.execute.TableScanResultSet.openCore(Unknown Source) at org.apache.derby.impl.sql.execute.IndexRowToBaseRowResultSet.openCore(Unknown Source) at org.apache.derby.impl.sql.execute.BasicNoPutResultSetImpl.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) ... 17 more Sun Feb 15 22:34:13 EST 2009: Can't store row in table. At least one parameter to the current statement is uninitialized. java.sql.SQLException: At least one parameter to the current statement is uninitialized. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source) at com.jbidwatcher.util.db.Table.storeMap(Table.java:274) at com.jbidwatcher.util.db.Table.updateMap(Table.java:211) at com.jbidwatcher.util.db.Table.insertOrUpdate(Table.java:202) at com.jbidwatcher.util.db.ActiveRecord.saveDB(ActiveRecord.java:116) at com.jbidwatcher.auction.AuctionEntry.saveDB(AuctionEntry.java:1764) at com.jbidwatcher.auction.AuctionEntry.setAuctionInfo(AuctionEntry.java:1591) at com.jbidwatcher.auction.server.AuctionServer.reload(AuctionServer.java:185) 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) Caused by: java.sql.SQLException: At least one parameter to the current statement is uninitialized. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) ... 23 more Caused by: ERROR 07000: At least one parameter to the current statement is uninitialized. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.sql.execute.BaseActivation.throwIfMissingParms(Unknown Source) at org.apache.derby.exe.acb9810038x011fx7d1bxc1b0xffffde5866421.execute(Unknown Source) at org.apache.derby.impl.sql.GenericActivationHolder.execute(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) ... 17 more Sun Feb 15 22:38:18 EST 2009: Exception during the check() operation of class com.jbidwatcher.ui.AuctionsManager null java.lang.NullPointerException at com.jbidwatcher.util.db.ActiveRecord.convertResultsToList(ActiveRecord.java:145) at com.jbidwatcher.util.db.ActiveRecord.findAllBySQL(ActiveRecord.java:138) at com.jbidwatcher.auction.AuctionEntry.findAll(AuctionEntry.java:1834) at com.jbidwatcher.auction.server.AuctionServerManager.toXML(AuctionServerManager.java:303) at com.jbidwatcher.ui.AuctionsManager.saveAuctions(AuctionsManager.java:285) at com.jbidwatcher.ui.AuctionsManager.checkSnapshot(AuctionsManager.java:78) at com.jbidwatcher.ui.AuctionsManager.check(AuctionsManager.java:95) at com.jbidwatcher.util.queue.TimerHandler.run(TimerHandler.java:56) Sun Feb 15 22:38:18 EST 2009: Shutting down JBidwatcher. |
|
Great program! Haven’t had any problems — until 2.0. I’m experiencing the same problems mentioned above with slow open/close and incomplete lists running on Windows 7 with latest Java. 2.0 seems to work fine when installed into a virgin directory, but chokes when installed into a directory with a database created by a prior release (beta11 still loads the database without any trouble). |
|
Greetings, Not completely sure why that’d be happening, but it’s very possible. I made locking more aggressive in the 2.0 version, because users were getting data consistency errors. I tested it under heavy load, and didn’t run into any lock contention, but it’s entirely possible that’s the problem. At least it gives me a direction to look… — Morgan Schweers, Cyber**FOX**! |
|
Hello Morgan, Bouuuu :-( This version is absolutely unusable for me :-( Hours for “importing complete listing” in the Derby IBM/Apache database (more bad than sqllite :-( ) All my computers are kneeling in front the “God” Jbidwatcher ;-) (XXX per cent CPU always used by Jbid). And so on :-( PS : working with Ubuntu Intrepid, using : “java version 1.6.0_10” |
|
Greetings, @silver84 – If you have a log file from when it took a long time to start up (especially if you have logging and debugging enabled) I’d appreciate it. You can email it to me, or create a ticket in my bug tracker and attach it there. — Morgan Schweers, Cyber*FOX*! |
|
Hello Morgan, Its done, sent to your email address (Top result : 99% CPU used by Java/Jbidwatcher, error.23.log and derby.log). Ask if you need more or to do some tests/debugs. Hope this help. Many thanks for your job. |
|
Hi Morgan |
|
I have the same problems on Linux and have also a very, very large old database. Already he has found some SQL problems. Just a little patience ;-) |
|
I can confirm that the 99% CPU issue is also occurring under Mac OS X 10.5.6 with all updates applied. No accurate timings are available for the program to open…. I’ve just left it an hour and it has been loaded on my return. I’ll revert to beta 11 pending Morgan’s further investigations. -Rob |
|
Just downloaded and installed 2.0.1. Thanks Morgan Mike |
|
2.0.1 seems to have fixed it for me too… Many thanks! Nick |
|
Same for me. 2.0.1. works fine and fast. Thanks. |
|
As recommended I upgraded to 2.0.1 (2.0.1-825) when it was released. However I have encountered one new problem, twice now, I have come back to JBidwatcher and found every auction in my current list has had a bid (or snipe) of £1.00 placed on it. I am based in the UK which is why it is in Pounds, I suspect if I was in the Eurozone I would return and find it had placed bids for €1.00 (one Euro). If they are snipes then it will not let me cancel them. I normally leave JBidwatcher running by itself so I can periodically look at the list of auctions I am monitoring and of course so it can Snipe for auctions if I choose. I am running JBidwatcher on a PowerMac G4 running Mac OS X 10.4.11. Quitting and relaunching and letting it refresh all the auctions does not change this. So far all the auctions had already exceeded £1.00 in value prior to JBidwatcher making this error meaning I have not been stuck with items I did not want. During the time I was running version 2.0 this did not occur. |