I am running a version a couple of months old and java is only using 100
megs (300megs total including paged memory).  This server has been running
for weeks and stable.

Skip

-----Original Message-----
From: Case Torres [mailto:[EMAIL PROTECTED]
Sent: Monday, December 03, 2007 3:58 PM
To: [email protected]
Subject: RE: all of a sudden, java.lang.OutOfMemoryError




ok, I defraged, uninstalled Java6, installed JDK 1.5, ran ant clean-all, ant
run-install

My java.exe is still high
Without doing anything,  not even logging in.
Mem Usage: 474,024 K, Peak Mem Usage: 478,480K, VM Size: 558,808K,
After logging in: 522,064K,  522,592K, 571,888 and climbing
5 mins later it's: 564,080K, 564, 644K, 572,748K

Physical Memory -> available= 764264
commit charge: 1285644
limit: 4033404
peak: 1312716

Any suggestions???

this is trunk, revision 588758, XP Pro

Thanks much for all your help with this.


Case Torres
[EMAIL PROTECTED]


-----Original Message-----
From: BJ Freeman [mailto:[EMAIL PROTECTED]
Sent: Monday, December 03, 2007 2:32 PM
To: [email protected]
Subject: Re: all of a sudden, java.lang.OutOfMemoryError

and what does your Performance tab show
Physical memory ->available.
commit charge:
total
limit
peak

Case Torres sent the following on 12/3/2007 12:14 PM:
> Hey BJ,
>
> Looks like the virtual memory for java.exe is the nearly the same as
> the "Mem Usage".
> 526,260K, 537,920K respectively.
>
>
> Case Torres
> [EMAIL PROTECTED]
>
>
> -----Original Message-----
> From: BJ Freeman [mailto:[EMAIL PROTECTED]
> Sent: Saturday, December 01, 2007 6:44 PM
> To: [email protected]
> Subject: Re: all of a sudden, java.lang.OutOfMemoryError
>
> have two issues here.
> one is allocated memory on startup.
> currently the max is 512. I have increased mine to 768.
> You did not say how much virutal memory you using.
> That is on the performance tab.
>
> and ver 4.0
> There have been some depreciated stuff in 1.5 and 1.6 that 4.0 may need.
> it may be not even supported in 1.6.
> however it should run in 1.5. I have not confirmed this.
> Also remember that you need to compile in 1.5 or 1.6 if you are going
> to run in it.
> That could be the problem.
>
>
> Case Torres sent the following on 12/1/2007 6:24 PM:
>> java.exe is larger than what's specified in startofbiz.bat
>>
>> Can I just increase what's in the .bat file or should I uninstall 1.6
>> and reinstall 1.5??
>>
>> I thought I read somewhere that release 4.0, at least, does not
>> support
> 1.6.
>> Thanks,
>>
>>
>> Case Torres
>> [EMAIL PROTECTED]
>>
>>
>> -----Original Message-----
>> From: BJ Freeman [mailto:[EMAIL PROTECTED]
>> Sent: Saturday, December 01, 2007 5:15 PM
>> To: [email protected]
>> Subject: Re: all of a sudden, java.lang.OutOfMemoryError
>>
>> one reason I don't allow automatic updates, especially from MS.
>> do a CTRL-ATL-DEL and look at the processes.
>> if you are using a large amount of Virtual memory then you could be
>> slow because the disk is not defraged.
>> Look at the processes you have running and see if any one of them has
>> a large amount of memory usage, like javaw you should not be larger
>> than the max specific in the startofbiz.bat
>>
>>
>> Case Torres sent the following on 12/1/2007 3:36 PM:
>>> Hi,
>>>
>>> OFBiz used to run like a champ on my XP Pro computer.
>>> Now, I'm getting the following errors from ofbiz and everything on
>>> my computer comes to a screeching halt. I think my automatic update
>>> updated jdk from 1.5 to 1.6. Could this be the problem. Anyone else
>>> have
>> this problem?
>>> Any ideas?
>>>
>>> Thanks, Case
>>>
>>>
>>> C:\ofbiz>"c:\Program Files\Java\jdk1.6.0_02\\bin\java" -Xms256M
>>> -Xmx512M -Duser.language=en -jar ofbiz.jar
>>> 1>runtime\logs\console.log Exception in thread
>>> "ContainerBackgroundProcessor[StandardEngine[default-server]]"
>>> java.lang.OutOfMemoryError: Java heap space
>>>         at org.apache.log4j.Category.forcedLog(Category.java:391)
>>>         at org.apache.log4j.Category.log(Category.java:856)
>>>         at
>>> org.apache.commons.logging.impl.Log4JLogger.error(Log4JLogger.java:251)
>>>         at
>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.
>>> p
>>> r
>>> ocessC
>>> hildren(ContainerBase.java:1572)
>>>         at
>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.
>>> p
>>> r
>>> ocessC
>>> hildren(ContainerBase.java:1579)
>>>         at
>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.
>>> p
>>> r
>>> ocessC
>>> hildren(ContainerBase.java:1579)
>>>         at
>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.
>>> p
>>> r
>>> ocessC
>>> hildren(ContainerBase.java:1579)
>>>         at
>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.
>>> r
>>> u
>>> n(Cont
>>> ainerBase.java:1559)
>>>         at java.lang.Thread.run(Thread.java:619)
>>> Exception in thread "Dispatcher-Thread-1" java.lang.OutOfMemoryError:
>>> Java heap space
>>> ---
>>> Case Torres
>>> Quantum Composers, Inc.
>>> [EMAIL PROTECTED]
>>> http://www.quantumcomposers.com
>>>
>>>
>>
>>
>>
>
>
>
>


Reply via email to