I'm seeing the same behavior as several other bug
reports, such as "[ 1102301 ] JBW regularly freezes..."
when jbidwatcher sort of still works as you can move
from tab to tab and open auctions in the browser, and
the thumbnail images works, etc. But auction updates
aren't done and just sit there - despite being expired,
snipes don't fire, and saving auctions manually doesn't
do anything and doesn't pop up the little Save Complete
popup, and jbidwatcher can't be closed, except
forcefully by killing off the process or End Task-ing
the application. After jbidwatcher is forcefully
closed, there's an auction.xml.new file (about 1KB) in
the program directory... with just skeleton xml code in
it, no data. This file is created or recreated about
the time when a manual save auctions is done, when
jbidwatcher is having the problems described above, but
it is empty until the program is closed.
I think I've narrowed down my problem to having too
large of an xml file. I notice this behavior when my
auction.xml file reaches approximately 2,650 KB. When I
notice these problems, I can then kill off jbidwatcher,
delete the auctions.xml.new file, and then restart
jbidwatcher, and then quickly delete a bunch of old
auctions and then click Save Auctions. This brings the
xml filesize down to where it doesn't have problems
anymore. I think I've noticed this in previous versions
as well... it happens to me between every 6 months to a
year, depending on how many auctions I deleted and how
many new ones i added. There doesn't seem to be any
information regarding this in the error log... unless
it's the error below... however it's not the last one,
and jbidwatcher seems to be still updating auctions
after it.
(I"m using Windows XP SP1a with a very recent Java
1.4.2_06)
Tue Feb 15 15:03:24 PST 2005: loadFromString Failed
with a null pointer!
java.lang.Exception: Updater got incorrect XML file.
at UpdaterEntry.loadFromString(UpdaterEntry.java:31)
at UpdaterEntry.<init>(UpdaterEntry.java:26)
at UpdateManager.checkUpdate(UpdateManager.java:36)
at JBidMouse.DoCheckUpdates(JBidMouse.java:1413)
at JBidMouse.DoAction(JBidMouse.java:1487)
at JTabManager.actionPerformed(JTabManager.java:125)
at
javax.swing.AbstractButton.fireActionPerformed(Unknown
Source)
at
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown
Source)
at
javax.swing.DefaultButtonModel.fireActionPerformed(Unknown
Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown
Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at
javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown
Source)
at
javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(Unknown
Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at
java.awt.LightweightDispatcher.retargetMouseEvent(Unknown
Source)
at
java.awt.LightweightDispatcher.processMouseEvent(Unknown
Source)
at
java.awt.LightweightDispatcher.dispatchEvent(Unknown
Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Logged In: YES
user_id=1104235
I sometimes have the same problem.
My assumption from what I can read from the log is that JBW
tries to save the XML file while the internal data structure
of the XML content is changed.
apple.awt.EventQueueExceptionHandler Caught Throwable :
java.util.ConcurrentModificationException
This happens especially while shutting down shortly after
starting JBW.
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=916536
No need for profuse apologies... I (and I think we,
collectively) understand that this is a free program done in
your spare time, and I/we appreciate that you created the
program in the first place, much less constantly maintain
and improve it. Thanks for your hard work.
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!
Logged In: YES
user_id=916536
Originator: YES
Actually I thought you had fixed this bug already, since I hadn't noticed any file size limit so far. My xml file is well over the previous size I had trouble with.