Re: Problem reserving enough space for Java object heap since stretch upgrade

On 7/1/2017 10:37 AM, David Wright wrote: I have been unable to execute Java with >=2048M memory allocation since upgrading to stretch. I've changed nothing in my configuration otherwise. I have plenty of RAM: # free totalusedfree shared buff/cache

Re: Problem reserving enough space for Java object heap since stretch upgrade

Hi, On Mon, Jul 03, 2017 at 04:16:53PM +0100, Joe wrote: > The amd64 software versions were not all identical to the i386 ones, but > I got away with it. The major configurations, samba and exim4, went in Shouldn't happen on stable. > without a hitch, and this was a server, so no faffing about

Re: Problem reserving enough space for Java object heap since stretch upgrade

On Mon, 3 Jul 2017 10:36:56 -0400 Adam Rosi-Kessel wrote: > On 7/3/2017 6:52 AM, Rene Engelhard wrote: > >>> On 01-07-2017 10:47, Adam Rosi-Kessel wrote: > I have been unable to execute Java with >=2048M memory allocation > since upgrading to stretch. I've

Re: Problem reserving enough space for Java object heap since stretch upgrade

On 7/3/2017 10:56 AM, Henrique de Moraes Holschuh wrote: On Mon, 03 Jul 2017, Adam Rosi-Kessel wrote: This isn't on purpose and not something I've ever thought about it. It looks like migrating an existing system from i386 to amd64 is a cumbersome and potentially glitchy process. Is it still

Re: Problem reserving enough space for Java object heap since stretch upgrade

On Mon, 03 Jul 2017, Adam Rosi-Kessel wrote: > This isn't on purpose and not something I've ever thought about it. It looks > like migrating an existing system from i386 to amd64 is a cumbersome and > potentially glitchy process. Is it still true that there is no foolproof and > easy way to

Re: Problem reserving enough space for Java object heap since stretch upgrade

On Monday, July 03, 2017 10:36:56 AM Adam Rosi-Kessel wrote: > This isn't on purpose and not something I've ever thought about it. It > looks like migrating an existing system from i386 to amd64 is a > cumbersome and potentially glitchy process. Is it still true that there > is no foolproof and

Re: Problem reserving enough space for Java object heap since stretch upgrade

On 7/3/2017 6:52 AM, Rene Engelhard wrote: On 01-07-2017 10:47, Adam Rosi-Kessel wrote: I have been unable to execute Java with >=2048M memory allocation since upgrading to stretch. I've changed nothing in my configuration otherwise. Might be related to this:

Re: Problem reserving enough space for Java object heap since stretch upgrade

Hi, On Sat, Jul 01, 2017 at 10:49:53AM -0400, Adam Rosi-Kessel wrote: > On 7/1/2017 9:50 AM, Eduardo M KALINOWSKI wrote: > >On 01-07-2017 10:47, Adam Rosi-Kessel wrote: > >>I have been unable to execute Java with >=2048M memory allocation > >>since upgrading to stretch. I've changed nothing in my

Re: Problem reserving enough space for Java object heap since stretch upgrade

On 7/1/2017 9:50 AM, Eduardo M KALINOWSKI wrote: On 01-07-2017 10:47, Adam Rosi-Kessel wrote: I have been unable to execute Java with >=2048M memory allocation since upgrading to stretch. I've changed nothing in my configuration otherwise. Might be related to this:

Re: Problem reserving enough space for Java object heap since stretch upgrade

On 7/1/2017 10:37 AM, David Wright wrote: On Sat 01 Jul 2017 at 09:47:38 (-0400), Adam Rosi-Kessel wrote: I have been unable to execute Java with >=2048M memory allocation since upgrading to stretch. I've changed nothing in my configuration otherwise. # ulimit -v unlimited What does #

Re: Problem reserving enough space for Java object heap since stretch upgrade

On Sat 01 Jul 2017 at 09:47:38 (-0400), Adam Rosi-Kessel wrote: > I have been unable to execute Java with >=2048M memory allocation > since upgrading to stretch. I've changed nothing in my configuration > otherwise. > > I have plenty of RAM: > > # free > totalused

Re: Problem reserving enough space for Java object heap since stretch upgrade

On 01-07-2017 10:47, Adam Rosi-Kessel wrote: > I have been unable to execute Java with >=2048M memory allocation > since upgrading to stretch. I've changed nothing in my configuration > otherwise. Might be related to this: https://lists.debian.org/debian-security-announce/2017/msg00160.html --

Problem reserving enough space for Java object heap since stretch upgrade

I have been unable to execute Java with >=2048M memory allocation since upgrading to stretch. I've changed nothing in my configuration otherwise. I have plenty of RAM: # free totalusedfree shared buff/cache available Mem:5168396 3326140