I appreciate you confirming what I believe.
My concern is my 9.04 productions use to work with no problem
I have not added anything except mods to code like paypal
there was a time when after a week i would have to restart the
application to be able to use the artifact.
Now even though I restart I still an not do an artifact.

so I am curious as o what is eating up the heap.
will do more investigation.

Scott Gray sent the following on 9/11/2009 9:25 PM:
> You need a bigger heap size, like I said gathering the artifact info is
> an expensive operation.  It's possible somethings going wrong in there
> but I'd try increasing your heap first.
> 
> Regards
> Scott
> 
> On 12/09/2009, at 3:24 PM, BJ Freeman wrote:
> 
>> actually that is what sent me to the demo for verification.
>> it happened on my local and production copies.
>>
>>
>> Scott Gray sent the following on 9/11/2009 7:47 PM:
>>> It doesn't really matter anyway, the ArtifactInfo screen is extremely
>>> resource intensive on its first run and the demo server simply doesn't
>>> have enough resources available to handle the request.  I would suggest
>>> that you use your local machine for browsing the artifact information.
>>>
>>> Regards
>>> Scott
>>>
>>> On 12/09/2009, at 2:11 PM, Scott Gray wrote:
>>>
>>>> Hi BJ,
>>>>
>>>> I don't see any errors of that nature in the logs, what time did it
>>>> occur and are you sure it was on 9.04?
>>>>
>>>> Thanks
>>>> Scott
>>>>
>>>> HotWax Media
>>>> http://www.hotwaxmedia.com
>>>>
>>>> On 12/09/2009, at 1:48 PM, BJ Freeman wrote:
>>>>
>>>>> I click on the artifact URL on webtools
>>>>>
>>>>> HTTP Status 500 -
>>>>> type Exception report
>>>>> message
>>>>> description The server encountered an internal error () that prevented
>>>>> it from fulfilling this request.
>>>>> exception
>>>>> javax.servlet.ServletException: Servlet execution threw an exception
>>>>> org.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:259)
>>>>>
>>>>> root cause
>>>>> java.lang.OutOfMemoryError: Java heap space
>>>>>
>>>>> note The full stack trace of the root cause is available in the Apache
>>>>> Tomcat/6.0.16 logs.
>>>>> -- 
>>>>> BJ Freeman
>>>>> http://www.businessesnetwork.com/automation
>>>>> http://bjfreeman.elance.com
>>>>> http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
>>>>>
>>>>>
>>>>> Systems Integrator.
>>>>>
>>>>
>>>
>>
>> -- 
>> BJ Freeman
>> http://www.businessesnetwork.com/automation
>> http://bjfreeman.elance.com
>> http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
>>
>> Systems Integrator.
>>
> 

-- 
BJ Freeman
http://www.businessesnetwork.com/automation
http://bjfreeman.elance.com
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
Systems Integrator.

Reply via email to