Error encountered merging CanVec data layer to OSM layer

[longiaru@…]

What steps will reproduce the problem?

1. ?? Haven't sen this issue before. Have used this importing 195 previous files and have not experienced this error.

What is the expected result? Layers merged.

What happens instead?

Please provide any additional information below. Attach a screenshot if
possible.

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2011-04-26 01:31:34
Last Changed Author: bastiK
Revision: 4064
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2011-04-25 20:32:26 +0200 (Mon, 25 Apr 2011)
Last Changed Rev: 4064

Identification: JOSM/1.5 (4064 en)
Memory Usage: 202 MB / 494 MB (80 MB allocated, but free)
Java version: 1.6.0_22, Sun Microsystems Inc., OpenJDK Client VM
Operating system: Linux
Dataset consistency test: No problems found

Plugin: buildings_tools (25905)
Plugin: turnrestrictions (25845)

java.lang.IndexOutOfBoundsException: Index: 2, Size: 2
	at java.util.ArrayList.rangeCheck(ArrayList.java:571)
	at java.util.ArrayList.get(ArrayList.java:349)
	at java.util.Collections$UnmodifiableList.get(Collections.java:1170)
	at org.openstreetmap.josm.gui.dialogs.LayerListDialog$LayerListModel.setValueAt(LayerListDialog.java:1303)
	at javax.swing.JTable.setValueAt(JTable.java:2743)
	at javax.swing.JTable.editingStopped(JTable.java:4728)
	at javax.swing.AbstractCellEditor.fireEditingStopped(AbstractCellEditor.java:142)
	at javax.swing.DefaultCellEditor$EditorDelegate.stopCellEditing(DefaultCellEditor.java:366)
	at javax.swing.DefaultCellEditor.stopCellEditing(DefaultCellEditor.java:231)
	at javax.swing.JTable$CellEditorRemover.propertyChange(JTable.java:5970)
	at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:298)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:292)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:229)
	at java.awt.KeyboardFocusManager.firePropertyChange(KeyboardFocusManager.java:1420)
	at java.awt.KeyboardFocusManager.setGlobalPermanentFocusOwner(KeyboardFocusManager.java:712)
	at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:536)
	at java.awt.Component.dispatchEventImpl(Component.java:4499)
	at java.awt.Container.dispatchEventImpl(Container.java:2103)
	at java.awt.Component.dispatchEvent(Component.java:4455)
	at sun.awt.X11.XWindow$1.run(XWindow.java:401)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
	at java.awt.EventQueue.access$000(EventQueue.java:96)
	at java.awt.EventQueue$1.run(EventQueue.java:608)
	at java.awt.EventQueue$1.run(EventQueue.java:606)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

[stoecker]

Can you reproduce this?

[longiaru@…]

Tried responding twice to trac@… and a request for further information but it was bounced back.

No. I had not seen this error before and this is one of my standard operations with JOSM. I'm running on a Dual-Core P4, under Ubuntu 11.04 with 4Gb memory. I did notice, however, that when closing the error notification window, another would just pop up in its place. I eventually wound up killing JOSM as it was the only way to get out.

Upon restarting JOSM, there was a notice that JOSM had crashed previously and asked if I wanted to restore the data. I said yes and the complete merged layer was restored. So the merge actually did successfully complete... it just threw the error notifications while attempting to do it the first time.

Anything else I can yell you? I'll certainly pass a bug report if I see it again.

Thanks

[stoecker]

The e-mail is send-only. You can't reply to it.