Hi FYI: splitter r393 dies with following error, if i try to split my DACH-extract, all other extracts are not affected java.lang.ArrayIndexOutOfBoundsException: -184650 at uk.me.parabola.splitter.O5mMapParser.setStringRefPair(O5mMapParser.java:355) at uk.me.parabola.splitter.O5mMapParser.readAuthor(O5mMapParser.java:408) at uk.me.parabola.splitter.O5mMapParser.readVersionTsAuthor(O5mMapParser.java:372) at uk.me.parabola.splitter.O5mMapParser.readNode(O5mMapParser.java:251) at uk.me.parabola.splitter.O5mMapParser.readFile(O5mMapParser.java:187) at uk.me.parabola.splitter.O5mMapParser.parse(O5mMapParser.java:133) at uk.me.parabola.splitter.Main.processOSMFiles(Main.java:1362) at uk.me.parabola.splitter.Main.processMap(Main.java:874) at uk.me.parabola.splitter.Main.genProblemLists(Main.java:697) at uk.me.parabola.splitter.Main.partitionAreasForProblemListGenerator(Main.java:729) at uk.me.parabola.splitter.Main.split(Main.java:307) at uk.me.parabola.splitter.Main.start(Main.java:181) at uk.me.parabola.splitter.Main.main(Main.java:151) here are the log files http://files.mkgmap.org.uk/download/210/20140526_0900.zip Bernd -- amarok2 now playing:
Hi Bernd, this looks like an error in the o5m file. Is osmconvert able to read it? Gerd
From: weigelt.bernd@web.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 26 May 2014 10:20:11 +0200 Subject: [mkgmap-dev] Problem with splitter r393
Hi
FYI:
splitter r393 dies with following error, if i try to split my DACH-extract, all other extracts are not affected
java.lang.ArrayIndexOutOfBoundsException: -184650 at uk.me.parabola.splitter.O5mMapParser.setStringRefPair(O5mMapParser.java:355) at uk.me.parabola.splitter.O5mMapParser.readAuthor(O5mMapParser.java:408) at uk.me.parabola.splitter.O5mMapParser.readVersionTsAuthor(O5mMapParser.java:372) at uk.me.parabola.splitter.O5mMapParser.readNode(O5mMapParser.java:251) at uk.me.parabola.splitter.O5mMapParser.readFile(O5mMapParser.java:187) at uk.me.parabola.splitter.O5mMapParser.parse(O5mMapParser.java:133) at uk.me.parabola.splitter.Main.processOSMFiles(Main.java:1362) at uk.me.parabola.splitter.Main.processMap(Main.java:874) at uk.me.parabola.splitter.Main.genProblemLists(Main.java:697) at uk.me.parabola.splitter.Main.partitionAreasForProblemListGenerator(Main.java:729) at uk.me.parabola.splitter.Main.split(Main.java:307) at uk.me.parabola.splitter.Main.start(Main.java:181) at uk.me.parabola.splitter.Main.main(Main.java:151)
here are the log files http://files.mkgmap.org.uk/download/210/20140526_0900.zip
Bernd
-- amarok2 now playing:
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Bernd, okay, so it is probably a special case :-( Please post a link to the complete o5m file. Gerd
From: weigelt.bernd@web.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 26 May 2014 10:28:33 +0200 Subject: Re: [mkgmap-dev] Problem with splitter r393
Am Montag, 26. Mai 2014, 10:21:31 schrieb Gerd Petermann:
Wow, 80 seconds to get a hint ;-)
this looks like an error in the o5m file. Is osmconvert able to read it?
What shall i do?
convert from o5m to osm and back?
No problem
Bernd
-- amarok2 now playing:
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am Montag, 26. Mai 2014, 10:31:46 schrieb Gerd Petermann: Hi Gerd
okay, so it is probably a special case Please post a link to the complete o5m file.
Sorry, my mistake Didn't check the o5m file, only ask for that, what i should do ;-) I have to test osmconvert 0.7T against the old and a new extract, then i can give you the informations, but it will take some hours. I think, osmupdate 0.3F has a problem with this large extract, ~6.3 GB, because i have to create a new extract very often. Bernd -- amarok2 now playing:
Hi Bernd, no problem. I'll try to improve the error handling for this case. Gerd
From: weigelt.bernd@web.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 26 May 2014 11:03:36 +0200 Subject: Re: [mkgmap-dev] Problem with splitter r393
Am Montag, 26. Mai 2014, 10:31:46 schrieb Gerd Petermann:
Hi Gerd
okay, so it is probably a special case Please post a link to the complete o5m file.
Sorry, my mistake
Didn't check the o5m file, only ask for that, what i should do ;-)
I have to test osmconvert 0.7T against the old and a new extract, then i can give you the informations, but it will take some hours.
I think, osmupdate 0.3F has a problem with this large extract, ~6.3 GB, because i have to create a new extract very often.
Bernd
-- amarok2 now playing:
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Bernd, I've added a check in r395. reg. osmupdate I suggest to contact Markus Weber: markus.weber@gmx.com Gerd From: gpetermann_muenchen@hotmail.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 26 May 2014 11:06:18 +0200 Subject: Re: [mkgmap-dev] Problem with splitter r393 Hi Bernd, no problem. I'll try to improve the error handling for this case. Gerd
From: weigelt.bernd@web.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 26 May 2014 11:03:36 +0200 Subject: Re: [mkgmap-dev] Problem with splitter r393
Am Montag, 26. Mai 2014, 10:31:46 schrieb Gerd Petermann:
Hi Gerd
okay, so it is probably a special case Please post a link to the complete o5m file.
Sorry, my mistake
Didn't check the o5m file, only ask for that, what i should do ;-)
I have to test osmconvert 0.7T against the old and a new extract, then i can give you the informations, but it will take some hours.
I think, osmupdate 0.3F has a problem with this large extract, ~6.3 GB, because i have to create a new extract very often.
Bernd
-- amarok2 now playing:
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am Montag, 26. Mai 2014, 11:23:51 schrieb Gerd Petermann: Hi Gerd
I've added a check in r395.
reg. osmupdate I suggest to contact Markus Weber: markus.weber@gmx.com
I don't understand, what you have done, but the error has gone with r395 ;-) I made two tests, one with a new extract, created with osmconvert and osmupdate, and then one with the old data without update from this morning. Works fine now. have to thank you one more time Bernd -- amarok2 now playing:
Hi Bernd, that sounds not good to me. The only wanted effect of the change is that splitter reports an I/O error instead of failing with an ArrayIndexOutOfBoundsException. Maybe you have a hardware problem? Gerd Bernd Weigelt wrote
Am Montag, 26. Mai 2014, 11:23:51 schrieb Gerd Petermann:
Hi Gerd
I've added a check in r395.
reg. osmupdate I suggest to contact Markus Weber:
markus.weber@
I don't understand, what you have done, but the error has gone with r395 ;-)
I made two tests, one with a new extract, created with osmconvert and osmupdate, and then one with the old data without update from this morning. Works fine now.
have to thank you one more time
Bernd
-- amarok2 now playing:
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Problem-with-splitter-r393-tp5807282p5807309.... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Am Montag, 26. Mai 2014, 04:27:13 schrieb GerdP: Hi Gerd
Maybe you have a hardware problem?
RAM? HDD? Don't think so, because then it should be more often, not only by this extract. If my HDD has a problem, the error should be the same as this morning, because i've renamed the file and didn't copy it to another place. S.M.A.R.T monitoring is enabled. But i'll test both, RAM and HDD, this night to be sure BTW: there only a few changes in the three splitter.log, the areas.list are more or less identical. Bernd -- amarok2 now playing:
Hi Bernd, if you test r393 again with same input file and it doesn't fail, you can be pretty sure that the problem is in the hardware, presuming you give enough heap so that GC is not too stressed. The areas are similar because the problem occured in a later phase. Gerd
From: weigelt.bernd@web.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 26 May 2014 14:44:26 +0200 Subject: Re: [mkgmap-dev] Problem with splitter r393
Am Montag, 26. Mai 2014, 04:27:13 schrieb GerdP:
Hi Gerd
Maybe you have a hardware problem?
RAM? HDD?
Don't think so, because then it should be more often, not only by this extract. If my HDD has a problem, the error should be the same as this morning, because i've renamed the file and didn't copy it to another place. S.M.A.R.T monitoring is enabled.
But i'll test both, RAM and HDD, this night to be sure
BTW: there only a few changes in the three splitter.log, the areas.list are more or less identical.
Bernd
-- amarok2 now playing:
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Bernd, and you may use 7zip to compress the o5m file first. Gerd
From: weigelt.bernd@web.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 26 May 2014 10:28:33 +0200 Subject: Re: [mkgmap-dev] Problem with splitter r393
Am Montag, 26. Mai 2014, 10:21:31 schrieb Gerd Petermann:
Wow, 80 seconds to get a hint ;-)
this looks like an error in the o5m file. Is osmconvert able to read it?
What shall i do?
convert from o5m to osm and back?
No problem
Bernd
-- amarok2 now playing:
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
Bernd Weigelt -
Gerd Petermann -
GerdP