Your message dated Sun, 11 Nov 2018 10:23:34 +0100
with message-id <b430ad0d-1660-fb52-eeb5-1df71f218...@xs4all.nl>
and subject line Re: Bug#913458: osmosis --rri download slowdown with 
openjdk-11-jre
has caused the Debian Bug report #913458,
regarding osmosis --rri download slowdown with openjdk-11-jre
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
913458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: osmosis
Version: 0.47-3
Severity: normal

Dear Maintainer,

After installing openjdk-11-jre I'm experiencing significant slowdown
when downloading OSM replication files (--rri). What used to take
minutes now takes hours. Like 6 hours compared to 10 or 15 minutes.

I've experienced this problem with osmosis version 0.47-2 and 0.47-3.
It appears that this problem is osmosis specific.

Using JRE 10 for osmosis solves the problem.
For example providing /etc/osmosis/osmosis.conf with content
JAVACMD=/usr/lib/jvm/java-10-openjdk-amd64/bin/java


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (510, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages osmosis depends on:
ii  default-jre-headless [java8-runtime-headless]     2:1.11-70
ii  libbatik-java                                     1.10-1
ii  libcommons-codec-java                             1.11-1
ii  libcommons-compress-java                          1.18-1
ii  libcommons-dbcp-java                              1.4-5
ii  libcommons-pool-java                              1.6-3
ii  libjpf-java                                       1.5.1+dfsg-4
ii  libmariadb-java                                   2.3.0-1
ii  libosmpbf-java                                    1.3.3-11
ii  libplexus-classworlds2-java                       2.5.2-2
ii  libpostgis-java                                   1:2.2.1-9
ii  libpostgresql-jdbc-java                           42.2.5-1
ii  libprotobuf-java                                  3.6.1-4
ii  libspring-beans-java                              4.3.19-1
ii  libspring-context-java                            4.3.19-1
ii  libspring-core-java                               4.3.19-1
ii  libspring-jdbc-java                               4.3.19-1
ii  libspring-transaction-java                        4.3.19-1
ii  libxerces2-java                                   2.11.0-9
ii  libxz-java                                        1.8-2
ii  openjdk-10-jre-headless [java8-runtime-headless]  10.0.2+13-2
ii  openjdk-11-jre-headless [java8-runtime-headless]  11.0.1+13-2
ii  openjdk-9-jre-headless [java8-runtime-headless]   9.0.4+12-4

osmosis recommends no packages.

osmosis suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Control: tags -1 upstream wontfix

On 11/11/18 9:14 AM, Blaž Lorger wrote:
> After installing openjdk-11-jre I'm experiencing significant slowdown
> when downloading OSM replication files (--rri). What used to take
> minutes now takes hours. Like 6 hours compared to 10 or 15 minutes.
> 
> I've experienced this problem with osmosis version 0.47-2 and 0.47-3.
> It appears that this problem is osmosis specific.
> 
> Using JRE 10 for osmosis solves the problem.
> For example providing /etc/osmosis/osmosis.conf with content
> JAVACMD=/usr/lib/jvm/java-10-openjdk-amd64/bin/java

osmosis is not actively developed any more, see:

 https://lists.openstreetmap.org/pipermail/osmosis-dev/2018-October/001847.html

This issue is unlikely to get fixed unless someone resumes upstream
development.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

--- End Message ---

Reply via email to