openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Woods <dwo...@apache.org>
Subject Re: openjpa-integration test failures.
Date Tue, 18 Aug 2009 20:32:02 GMT
Only thing I can think of, is to try using a copy of the Sun 1.6.0 JDK 
that isn't distributed with WebLogic....  The latest is 1.6.0_16.


-Donald


Ravi P Palacherla wrote:
> Hi Donald,
> 
> Thanks for your input.
> I have 4GB ( effective 3.25GB) RAM.
> I do not know why I am unable to run a java process with perm512m and 1gb
> heap.
> (unless it is reaching  2GB process size limitation.)
> 
> I am currently de-fragmenting, but I have a question though.
> Why does I need to have 512M contiguous heap ?
>  
> Regarding if other process are taking up most of my RAM. Here is what I did
> :
> 
> Mvn is failing at a java initialization and the java that is failing is :
> C:\bea\WLS103\JDK160~1\jre\bin\java -Xmx1024m -XX:MaxPermSize=512m -jar
> C:\TEMP\surefirebooter38008.jar C:\TEMP\surefire38006tmp
> C:\TEMP\surefire38007tmp
> 
> So I ran it outside mvn at command prompt and I got the same problem.
> 
> C:\bea\WLS103\JDK160~1\jre\bin\java -Xmx1024m -XX:MaxPermSize=512m -jar
> C:\TEMP\surefirebooter38008.jar C:\TEMP\surefire38006tmp
> C:\TEMP\surefire38007tmp
> 
> Error occurred during initialization of VM
> Could not reserve enough space for object heap
> Could not create the Java virtual machine.
> 
> Immediately, in the same command window, ran java on a different class with
> same memory parameters and I can run it 
> 
> C:\>C:\bea\WLS103\JDK160~1\jre\bin\java -Xmx1024m -XX:MaxPermSize=512m
> weblogic.Server
> <Aug 18, 2009 1:54:58 PM MDT> <Info> <WebLogicServer> <BEA-000377>
<Starting
> WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun
> Microsystems Inc.>
> 
> I am unable to understand what I am doing wrong here.
> I am going to try couple of options:
> 1) Try with same settings on another machine.
> 2) Try to increase process size on my current machine to 3GB and see if it
> will help.
> 
> Regards,
> Ravi.
> 
> 
> DWoods wrote:
>> The default settings work fine for me on my 32bit WinXP machine w/ 2GB 
>> RAM and Sun 1.6.0_15.
>>
>> I'm guessing you either have less than 2GB in your system or there have 
>> been other apps started and maybe shutdown which has caused the memory 
>> to become fragmented and a contiguous 512MB heap cannot be created....
>>
>> I have the following set in my cmdline before running "mvn clean 
>> install", as the values set in pom.xml are only used by the JVM that 
>> gets spawned off by surefire for running the tests -
>>
>> MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=512m
>>
>>
>> -Donald
>>
>>
>> Ravi P Palacherla wrote:
>>> Hi ,
>>>
>>> Iam using jdk 1.6.
>>>
>>> The default values in pom.xml are permsize 512m and heap of 1gb.
>>> I get the following error if I run with above values:
>>> "Error occurred during initialization of VM
>>> Could not reserve enough space for object heap
>>> Could not create the Java virtual machine."
>>>
>>> On a 32 bit windows machine the process size limit is 2GB and hence
>>> openjpa
>>> tests with default values can not be run on a windows machine. So, the
>>> only
>>> change I did is to change permsize in pom.xml to 256m.
>>>
>>> With above change, Here is the error that I see :
>>>
>>> testNullUpdateConstraint(org.apache.openjpa.integration.validation.TestConstraints)

>>> Time elapsed: 7
>>> .734 sec  <<< ERROR!
>>> <openjpa-2.0.0-SNAPSHOT-r422266:805138M fatal user error>
>>> org.apache.openjpa.persistence.ArgumentExc
>>> eption: Errors encountered while resolving metadata.  See nested
>>> exceptions
>>> for details.
>>>         at
>>> org.apache.openjpa.meta.MetaDataRepository.resolve(MetaDataRepository.java:578)
>>>         at
>>> org.apache.openjpa.meta.MetaDataRepository.getMetaData(MetaDataRepository.java:323)
>>>         at
>>> org.apache.openjpa.jdbc.meta.MappingRepository.getMapping(MappingRepository.java:289)
>>>
>>>
>>> Caused by: <openjpa-2.0.0-SNAPSHOT-r422266:805138M fatal user error>
>>> org.apache.openjpa.persistence.
>>> ArgumentException: No table was given for persistent type
>>> "org.apache.openjpa.integration.validation
>>> .ConstraintDates".
>>>         at
>>> org.apache.openjpa.jdbc.meta.MappingInfo.createTable(MappingInfo.java:478)
>>>         at
>>> org.apache.openjpa.jdbc.meta.ClassMappingInfo.getTable(ClassMappingInfo.java:245)
>>>         at
>>> org.apache.openjpa.jdbc.meta.ClassMappingInfo.getTable(ClassMappingInfo.java:263)
>>>
>>> Complete error stacks : 
>>> http://n2.nabble.com/file/n3467520/openjpatestresult.txt
>>> openjpatestresult.txt 
>>>
>>> Regards,
>>> Ravi.
>>>
>>>
>>>
>>> Michael Dick wrote:
>>>> FWIW these tests are passing for me too.
>>>> Are you using Sun JDK6? I've increased the perm gen size to 512m
>>>> (probably
>>>> overkill) when I use Sun JDK6 on Linux. Not sure whether this applies to
>>>> other plaftorms though.
>>>> -mike
>>>>
>>>> On Tue, Aug 18, 2009 at 9:46 AM, Jeremy Bauer <techhusky@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Ravi,
>>>>>
>>>>> What type of failure(s) are you seeing?  I just ran these tests with
a
>>>>> slightly newer rev (805429) and these tests were successful.
>>>>>
>>>>> -Jeremy
>>>>>
>>>>> On Tue, Aug 18, 2009 at 8:47 AM, Ravi P Palacherla <
>>>>> ravi.palacherla@oracle.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The following tests are failing at revision 805409, while running
"mvn
>>>>>> clean
>>>>>> test -Dtest="
>>>>>>
>>>>>> TestConstraints
>>>>>> TestValidationGroups and
>>>>>> TestValidatingLEM.
>>>>>>
>>>>>> All 3 are under openjpa-integration, am I doing anything wrong ?
>>>>>>
>>>>>> Regards,
>>>>>> Ravi.
>>>>>> --
>>>>>> View this message in context:
>>>>>>
>>>>> http://n2.nabble.com/openjpa-integration-test-failures.-tp3466133p3466133.html
>>>>>> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
>>>>>>
>>
> 

Mime
View raw message