[Swift-devel] Java memory strangeness
Lorenzo Pesce
lpesce at uchicago.edu
Mon Jul 2 19:16:39 CDT 2012
David,
I have observed a similar behavior on Beagle when I was running IBM java.
The guessed diagnosis is that the JVM was in some way part 64 and part 32,
consistently with an heap analysis we did with some software.
The solution was to reinstall java and that worked.
you can try it by yourself by using the default java on Beagle and then
do module load java.
This is my 2 cents. Java is not my thing and never will be.
Lorenzo
On Jul 2, 2012, at 6:34 PM, David Kelly wrote:
> bash-3.2$ uname -a
> Linux makena.uchicago.edu 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
>
> Seems to be 64 bit
>
> ----- Original Message -----
>> From: "Justin M Wozniak" <wozniak at mcs.anl.gov>
>> To: "David Kelly" <davidk at ci.uchicago.edu>
>> Cc: "swift-devel Devel" <swift-devel at ci.uchicago.edu>
>> Sent: Monday, July 2, 2012 4:56:17 PM
>> Subject: Re: [Swift-devel] Java memory strangeness
>> Is this a 32-bit machine?
>>
>> On 07/02/2012 04:49 PM, David Kelly wrote:
>>> Hello,
>>>
>>> I installed Sun Java on a new machine I am working on. When I try to
>>> run it I see this:
>>>
>>> -bash-3.2$ java -version
>>> Error occurred during initialization of VM
>>> Could not reserve enough space for object heap
>>> Error: Could not create the Java Virtual Machine.
>>> Error: A fatal exception has occurred. Program will exit.
>>>
>>> The machine has 27G of memory free.
>>>
>>> When I specify a value of -Xmx it seems to work fine until I get
>>> somewhere around between 4 and 8 gigs. From what I've read, the
>>> default heap size is 1/4th of the total memory up to 1 gig, so I
>>> have no idea why it's failing here.
>>>
>>> I can run Swift manually from this machine because the swift shell
>>> script explicitly sets the heap size.
>>>
>>> But, I run into problems when I use ssh:pbs to the machine.
>>>
>>> How is the heap size determined when using
>>> ssh/coasters/bootstrapping? I've tried setting SWIFT_MAX_HEAP and
>>> COG_OPTS in my bashrc but that didn't seem to help. I might be able
>>> to get around this by creating some kind of java wrapper that
>>> explicitly sets heap size.. just curious how it currently gets set
>>> in this situation.
>>>
>>> Thanks,
>>> David
>>> _______________________________________________
>>> Swift-devel mailing list
>>> Swift-devel at ci.uchicago.edu
>>> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>>
>>
>> --
>> Justin M Wozniak
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
More information about the Swift-devel
mailing list