Dear Basex Team, Basex server instance consuming more money,That instance is not releasing the memory ,to resolve this issue every time we are doing manually stopping the basex server instance and again starting.
We are using the Basex7.9 version.
We found the leak suspect.Please find in below
986,394,064 bytes (41.11 %) of Java heap is used by 4,062,161 instances of org/basex/query/path/IterStep$1 480,109,832 bytes (20.01 %) of Java heap is used by 100,000 instances of org/basex/query/value/node/FElem 206,334,096 bytes (8.6 %) of Java heap is used by 633,122 instances of org/basex/query/iter/NodeSeqBuilder 178,523,080 bytes (7.44 %) of Java heap is used by 37,245 instances of org/basex/query/value/node/FElem 103,703,288 bytes (4.32 %) of Java heap is used by 1,069,602 instances of org/basex/query/value/node/DBNode
What may be causing this problem and what are some possible solutions?
Regards, Chandrasekhar
Hi Chandra,
Does this also happen with the latest version of BaseX?
Best, Christian
chandra sekhar n vcsred@gmail.com schrieb am Mi., 29. Juli 2020, 07:58:
Dear Basex Team, Basex server instance consuming more money,That instance is not releasing the memory ,to resolve this issue every time we are doing manually stopping the basex server instance and again starting.
We are using the Basex7.9 version.
We found the leak suspect.Please find in below
986,394,064 bytes (41.11 %) of Java heap is used by 4,062,161 instances of org/basex/query/path/IterStep$1 480,109,832 bytes (20.01 %) of Java heap is used by 100,000 instances of org/basex/query/value/node/FElem 206,334,096 bytes (8.6 %) of Java heap is used by 633,122 instances of org/basex/query/iter/NodeSeqBuilder 178,523,080 bytes (7.44 %) of Java heap is used by 37,245 instances of org/basex/query/value/node/FElem 103,703,288 bytes (4.32 %) of Java heap is used by 1,069,602 instances of org/basex/query/value/node/DBNode
What may be causing this problem and what are some possible solutions?
Regards, Chandrasekhar
Dear Team, Actually it is happening in production ,So we can not test this scenario with the latest version.
Regards, Chandrasekhar
On Wed, Jul 29, 2020 at 12:00 PM Christian Grün christian.gruen@gmail.com wrote:
Hi Chandra,
Does this also happen with the latest version of BaseX?
Best, Christian
chandra sekhar n vcsred@gmail.com schrieb am Mi., 29. Juli 2020, 07:58:
Dear Basex Team, Basex server instance consuming more money,That instance is not releasing the memory ,to resolve this issue every time we are doing manually stopping the basex server instance and again starting.
We are using the Basex7.9 version.
We found the leak suspect.Please find in below
986,394,064 bytes (41.11 %) of Java heap is used by 4,062,161 instances of org/basex/query/path/IterStep$1 480,109,832 bytes (20.01 %) of Java heap is used by 100,000 instances of org/basex/query/value/node/FElem 206,334,096 bytes (8.6 %) of Java heap is used by 633,122 instances of org/basex/query/iter/NodeSeqBuilder 178,523,080 bytes (7.44 %) of Java heap is used by 37,245 instances of org/basex/query/value/node/FElem 103,703,288 bytes (4.32 %) of Java heap is used by 1,069,602 instances of org/basex/query/value/node/DBNode
What may be causing this problem and what are some possible solutions?
Regards, Chandrasekhar
Hi Chandra,
As BaseX 7.9 is more than 6 years old now, we definitely recommend you to switch to the latest version in the near future.
Best, Christian
On Wed, Jul 29, 2020 at 8:36 AM chandra sekhar n vcsred@gmail.com wrote:
Dear Team, Actually it is happening in production ,So we can not test this scenario with the latest version.
Regards, Chandrasekhar
On Wed, Jul 29, 2020 at 12:00 PM Christian Grün christian.gruen@gmail.com wrote:
Hi Chandra,
Does this also happen with the latest version of BaseX?
Best, Christian
chandra sekhar n vcsred@gmail.com schrieb am Mi., 29. Juli 2020, 07:58:
Dear Basex Team, Basex server instance consuming more money,That instance is not releasing the memory ,to resolve this issue every time we are doing manually stopping the basex server instance and again starting.
We are using the Basex7.9 version.
We found the leak suspect.Please find in below
986,394,064 bytes (41.11 %) of Java heap is used by 4,062,161 instances of org/basex/query/path/IterStep$1 480,109,832 bytes (20.01 %) of Java heap is used by 100,000 instances of org/basex/query/value/node/FElem 206,334,096 bytes (8.6 %) of Java heap is used by 633,122 instances of org/basex/query/iter/NodeSeqBuilder 178,523,080 bytes (7.44 %) of Java heap is used by 37,245 instances of org/basex/query/value/node/FElem 103,703,288 bytes (4.32 %) of Java heap is used by 1,069,602 instances of org/basex/query/value/node/DBNode
What may be causing this problem and what are some possible solutions?
Regards, Chandrasekhar
thank you veru much
On Wed, Jul 29, 2020 at 12:30 PM Christian Grün christian.gruen@gmail.com wrote:
Hi Chandra,
As BaseX 7.9 is more than 6 years old now, we definitely recommend you to switch to the latest version in the near future.
Best, Christian
On Wed, Jul 29, 2020 at 8:36 AM chandra sekhar n vcsred@gmail.com wrote:
Dear Team, Actually it is happening in production ,So we can not test this scenario
with the latest version.
Regards, Chandrasekhar
On Wed, Jul 29, 2020 at 12:00 PM Christian Grün <
christian.gruen@gmail.com> wrote:
Hi Chandra,
Does this also happen with the latest version of BaseX?
Best, Christian
chandra sekhar n vcsred@gmail.com schrieb am Mi., 29. Juli 2020,
07:58:
Dear Basex Team, Basex server instance consuming more money,That instance is not
releasing the memory ,to resolve this issue every time we are doing manually stopping the basex server instance and again starting.
We are using the Basex7.9 version.
We found the leak suspect.Please find in below
986,394,064 bytes (41.11 %) of Java heap is used by 4,062,161
instances of org/basex/query/path/IterStep$1
480,109,832 bytes (20.01 %) of Java heap is used by 100,000 instances
of org/basex/query/value/node/FElem
206,334,096 bytes (8.6 %) of Java heap is used by 633,122 instances of
org/basex/query/iter/NodeSeqBuilder
178,523,080 bytes (7.44 %) of Java heap is used by 37,245 instances of
org/basex/query/value/node/FElem
103,703,288 bytes (4.32 %) of Java heap is used by 1,069,602 instances
of org/basex/query/value/node/DBNode
What may be causing this problem and what are some possible solutions?
Regards, Chandrasekhar
basex-talk@mailman.uni-konstanz.de
-
chandra sekhar n -
Christian Grün