You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by ramaj <ra...@gmail.com> on 2007/10/08 23:15:14 UTC
Caused by: java.lang.OutOfMemoryError: Java heap space
hi,
I have installed Jetspeed2.1.
I am doing login stress testing for multiple users using JMETER tool.
Requests are
Total requests = 8000
cun requests = 500
But stress testing reached to 5000 then
/webportal/webapps/webportal/logs/pa.log
it gives error
"Caused by: java.lang.OutOfMemoryError: Java heap space"
For to solve this error,i have increased the RAM size as follows:
webportal/bin/catalina.bat:set JAVA_OPTS=%JAVA_OPTS% -Xmx2000m
webportal/bin/catalina.sh:JAVA_OPTS="$JAVA_OPTS "-Xmx2000m
webportal/bin/catdebug.bat:set CATALINA_OPTS=-Xmx2000m
webportal/bin/startJetspeed.bat:set CATALINA_OPTS=-Xmx2000m
then application restart again........
but again it reached to 5000 requests,it gives same error..........
plz help me.........
Thanks
ramj.
--
View this message in context: http://www.nabble.com/Caused-by%3A-java.lang.OutOfMemoryError%3A-Java-heap-space-tf4590727.html#a13105025
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by Jacek Wiślicki <ja...@gmail.com>.
On 2007-10-09 19:16 Weaver, Scott wrote:
> I guess I should ask which container/app server people (who are going OOM) are running in. I have seen this in both 4.x and 5.0.x of Tomcat and Weblogic 9.2.
Tomcat 5.5.17/20.
--
best regards,
Jacek Wislicki
jacek.wislicki@gmail.com
http://www.nauka-biznes.org.pl/jetspeed/portal/
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
RE: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by "Weaver, Scott" <we...@ugs.com>.
This is an interesting theory. I do something similar but in the opposite direction. My customized Jetspeed uses an instance of my portlet application's datasource.
I guess I should ask which container/app server people (who are going OOM) are running in. I have seen this in both 4.x and 5.0.x of Tomcat and Weblogic 9.2.
-scott
> -----Original Message-----
> From: Jacek Wiślicki [mailto:jacek.wislicki@gmail.com]
> Sent: Tuesday, October 09, 2007 12:20 PM
> To: Jetspeed Users List
> Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
>
> On 2007-10-09 16:19 Weaver, Scott wrote:
>
> > Can I get anyone experiencing memory leaks to profile their portal then
> > post a list of the largest objects/large number of the same objects in
> > the heap at/near the time of the OOM error?
> We noticed this problem when I shared Jetspeed's datasource with our own
> webapp. When I returned to the previous solution (the webapp uses its
> own database connection), the issue does not seem to appear anymore.
> Maybe there is something wrong about it?
>
> --
> best regards,
> Jacek Wislicki
>
> jacek.wislicki@gmail.com
> http://www.nauka-biznes.org.pl/jetspeed/portal/
> tel.: +48 502 408 444
> gg: 2540358
> skype: jacek_wislicki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by Jacek Wiślicki <ja...@gmail.com>.
On 2007-10-09 16:19 Weaver, Scott wrote:
> Can I get anyone experiencing memory leaks to profile their portal then
> post a list of the largest objects/large number of the same objects in
> the heap at/near the time of the OOM error?
We noticed this problem when I shared Jetspeed's datasource with our own
webapp. When I returned to the previous solution (the webapp uses its
own database connection), the issue does not seem to appear anymore.
Maybe there is something wrong about it?
--
best regards,
Jacek Wislicki
jacek.wislicki@gmail.com
http://www.nauka-biznes.org.pl/jetspeed/portal/
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by David Sean Taylor <da...@bluesunrise.com>.
yup, this one:
http://people.apache.org/~taylor/large_profiler_hashmap.jpeg
On Oct 10, 2007, at 12:10 PM, Weaver, Scott wrote:
> I haven't looked at the profiler, is it also just using a map?
>
> -scott
>
>> -----Original Message-----
>> From: David Sean Taylor [mailto:david@bluesunrise.com]
>> Sent: Wednesday, October 10, 2007 2:57 PM
>> To: Jetspeed Developers List
>> Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
>>
>>
>> On Oct 10, 2007, at 10:43 AM, Weaver, Scott wrote:
>>
>>> Cool. The new cache interface is pretty well documented, I will go
>>> ahead and add the docs to the PortletWindowAccessor interface.
>>>
>>> Another quick question, do you remembered why the "windows" map in
>>> PortletWindowAccessorImpl is synchronized? I don't want to have to
>>> sync
>>> on all the cache operations if I don't have to.
>>>
>> It was synchronized because we were seeing concurrent modification
>> issues and did a sweep of all caches a while back fixing that
>> You shouldn't have to synchronize with the new ehcache impl
>> Will you be updating the Profiler cache as well?
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
RE: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by "Weaver, Scott" <we...@ugs.com>.
I haven't looked at the profiler, is it also just using a map?
-scott
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Wednesday, October 10, 2007 2:57 PM
> To: Jetspeed Developers List
> Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
>
>
> On Oct 10, 2007, at 10:43 AM, Weaver, Scott wrote:
>
> > Cool. The new cache interface is pretty well documented, I will go
> > ahead and add the docs to the PortletWindowAccessor interface.
> >
> > Another quick question, do you remembered why the "windows" map in
> > PortletWindowAccessorImpl is synchronized? I don't want to have to
> > sync
> > on all the cache operations if I don't have to.
> >
> It was synchronized because we were seeing concurrent modification
> issues and did a sweep of all caches a while back fixing that
> You shouldn't have to synchronize with the new ehcache impl
> Will you be updating the Profiler cache as well?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Oct 10, 2007, at 10:43 AM, Weaver, Scott wrote:
> Cool. The new cache interface is pretty well documented, I will go
> ahead and add the docs to the PortletWindowAccessor interface.
>
> Another quick question, do you remembered why the "windows" map in
> PortletWindowAccessorImpl is synchronized? I don't want to have to
> sync
> on all the cache operations if I don't have to.
>
It was synchronized because we were seeing concurrent modification
issues and did a sweep of all caches a while back fixing that
You shouldn't have to synchronize with the new ehcache impl
Will you be updating the Profiler cache as well?
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by "Weaver, Scott" <we...@ugs.com>.
Cool. The new cache interface is pretty well documented, I will go
ahead and add the docs to the PortletWindowAccessor interface.
Another quick question, do you remembered why the "windows" map in
PortletWindowAccessorImpl is synchronized? I don't want to have to sync
on all the cache operations if I don't have to.
Thanks,
-scott
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Wednesday, October 10, 2007 1:09 PM
> To: Jetspeed Developers List
> Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
>
>
> On Oct 9, 2007, at 1:44 PM, Weaver, Scott wrote:
>
> > Slight issue.
> >
> >
org.apache.jetspeed.container.window.PortletWindowAccessor.getPortletW
> > in
> > dows() returns a Set of HashMap.Entrys. Since this is moving to
> > cache,
> > there will no longer be a HashMap to call getEntrySet() on. I
propose
> > just changing this to return a Set of PortletWindows. The only code
> > that will need to change within Jetspeed is the
> > org.apache.jetspeed.aggregator.impl.PortletTrackingManagerImpl. It
> > has
> > three methods that call the getPortletWindows(). The three methods
> > can
> > easily be modified to expect a Set of PortletWindows as opposed to
> > a Set
> > of HashMap.Entrys.
> >
> > Does anyone have an issue with me changing this behavior?
> >
> no i don't have issue
> I think it would be better to return a set of portlet window
> The API was never properly documented, could you specify in the
> javadoc what kind of elements are in the set
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Oct 9, 2007, at 1:44 PM, Weaver, Scott wrote:
> Slight issue.
>
> org.apache.jetspeed.container.window.PortletWindowAccessor.getPortletW
> in
> dows() returns a Set of HashMap.Entrys. Since this is moving to
> cache,
> there will no longer be a HashMap to call getEntrySet() on. I propose
> just changing this to return a Set of PortletWindows. The only code
> that will need to change within Jetspeed is the
> org.apache.jetspeed.aggregator.impl.PortletTrackingManagerImpl. It
> has
> three methods that call the getPortletWindows(). The three methods
> can
> easily be modified to expect a Set of PortletWindows as opposed to
> a Set
> of HashMap.Entrys.
>
> Does anyone have an issue with me changing this behavior?
>
no i don't have issue
I think it would be better to return a set of portlet window
The API was never properly documented, could you specify in the
javadoc what kind of elements are in the set
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by "Weaver, Scott" <we...@ugs.com>.
Slight issue.
org.apache.jetspeed.container.window.PortletWindowAccessor.getPortletWin
dows() returns a Set of HashMap.Entrys. Since this is moving to cache,
there will no longer be a HashMap to call getEntrySet() on. I propose
just changing this to return a Set of PortletWindows. The only code
that will need to change within Jetspeed is the
org.apache.jetspeed.aggregator.impl.PortletTrackingManagerImpl. It has
three methods that call the getPortletWindows(). The three methods can
easily be modified to expect a Set of PortletWindows as opposed to a Set
of HashMap.Entrys.
Does anyone have an issue with me changing this behavior?
Regards,
-scott
> -----Original Message-----
> From: Weaver, Scott [mailto:weavers@ugs.com]
> Sent: Tuesday, October 09, 2007 3:43 PM
> To: Jetspeed Users List
> Subject: RE: Caused by: java.lang.OutOfMemoryError: Java heap space
>
> Working on it as we speak ;) I will log a Jira ticket here in a bit.
>
> -scott
>
> > -----Original Message-----
> > From: David Sean Taylor [mailto:david@bluesunrise.com]
> > Sent: Tuesday, October 09, 2007 3:04 PM
> > To: Jetspeed Users List
> > Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
> >
> > Here is Ethan's attachments:
> >
> > http://people.apache.org/~taylor/large_profiler_hashmap.jpeg
> > http://people.apache.org/~taylor/large_windowaccessor_hashmap.jpeg
> >
> > I agree we should cap both of these caches
> > Scott, you wanna create a jira issue and work on it? otherwise I can
> > get it, let me know
> >
> >
> > On Oct 9, 2007, at 11:40 AM, Weaver, Scott wrote:
> >
> > > My current production portal in 2.0 also but I am currently
> > > upgrading to
> > > 2.1.3.
> > >
> > >
> > >
> > > "The issues I found was with the JetspeedProfilerImpl and
> > > PortletWindowAccessorImpl. This portal is running Jetspeed 2.0,
but
> I
> > > don't think the caching method has changed since then."
> > >
> > >
> > >
> > > "most" caching has been moved to ehcache. Unfortunately,
> > > PortletWindowAccessorImpl missed the cut ;)
> > >
> > >
> > >
> > > -scott
> > >
> > >
> > >
> > > ________________________________
> > >
> > > From: Ethan Adams [mailto:ethanjadams@gmail.com]
> > > Sent: Tuesday, October 09, 2007 2:22 PM
> > > To: Jetspeed Users List
> > > Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap
space
> > >
> > >
> > >
> > > The issues I found was with the JetspeedProfilerImpl and
> > > PortletWindowAccessorImpl. This portal is running Jetspeed 2.0,
but
> I
> > > don't think the caching method has changed since then.
> > >
> > > On 10/9/07, David Sean Taylor <da...@bluesunrise.com> wrote:
> > >
> > >
> > > On Oct 9, 2007, at 7:32 AM, Ethan Adams wrote:
> > >
> > >> Oddly enough, I just came across this yesterday.
> > >>
> > >> Attached is a snapshot showing 90MB of data. Max heap is at
1GB.
> > >> This was with 25000 unique users cycling through.
> > >>
> > > I think your attachment was stripped
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
jetspeed-user-unsubscribe@portals.apache.org
> > > For additional commands, e-mail:
> jetspeed-user-help@portals.apache.org
> > >
> > >
> > >
> >
> > --
> > David Sean Taylor
> > Bluesunrise Software
> > david@bluesunrise.com
> > [office] +01 707 773-4646
> > [mobile] +01 707 529 9194
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by "Weaver, Scott" <we...@ugs.com>.
Working on it as we speak ;) I will log a Jira ticket here in a bit.
-scott
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Tuesday, October 09, 2007 3:04 PM
> To: Jetspeed Users List
> Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
>
> Here is Ethan's attachments:
>
> http://people.apache.org/~taylor/large_profiler_hashmap.jpeg
> http://people.apache.org/~taylor/large_windowaccessor_hashmap.jpeg
>
> I agree we should cap both of these caches
> Scott, you wanna create a jira issue and work on it? otherwise I can
> get it, let me know
>
>
> On Oct 9, 2007, at 11:40 AM, Weaver, Scott wrote:
>
> > My current production portal in 2.0 also but I am currently
> > upgrading to
> > 2.1.3.
> >
> >
> >
> > "The issues I found was with the JetspeedProfilerImpl and
> > PortletWindowAccessorImpl. This portal is running Jetspeed 2.0, but
I
> > don't think the caching method has changed since then."
> >
> >
> >
> > "most" caching has been moved to ehcache. Unfortunately,
> > PortletWindowAccessorImpl missed the cut ;)
> >
> >
> >
> > -scott
> >
> >
> >
> > ________________________________
> >
> > From: Ethan Adams [mailto:ethanjadams@gmail.com]
> > Sent: Tuesday, October 09, 2007 2:22 PM
> > To: Jetspeed Users List
> > Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
> >
> >
> >
> > The issues I found was with the JetspeedProfilerImpl and
> > PortletWindowAccessorImpl. This portal is running Jetspeed 2.0, but
I
> > don't think the caching method has changed since then.
> >
> > On 10/9/07, David Sean Taylor <da...@bluesunrise.com> wrote:
> >
> >
> > On Oct 9, 2007, at 7:32 AM, Ethan Adams wrote:
> >
> >> Oddly enough, I just came across this yesterday.
> >>
> >> Attached is a snapshot showing 90MB of data. Max heap is at 1GB.
> >> This was with 25000 unique users cycling through.
> >>
> > I think your attachment was stripped
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
jetspeed-user-help@portals.apache.org
> >
> >
> >
>
> --
> David Sean Taylor
> Bluesunrise Software
> david@bluesunrise.com
> [office] +01 707 773-4646
> [mobile] +01 707 529 9194
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by David Sean Taylor <da...@bluesunrise.com>.
Here is Ethan's attachments:
http://people.apache.org/~taylor/large_profiler_hashmap.jpeg
http://people.apache.org/~taylor/large_windowaccessor_hashmap.jpeg
I agree we should cap both of these caches
Scott, you wanna create a jira issue and work on it? otherwise I can
get it, let me know
On Oct 9, 2007, at 11:40 AM, Weaver, Scott wrote:
> My current production portal in 2.0 also but I am currently
> upgrading to
> 2.1.3.
>
>
>
> "The issues I found was with the JetspeedProfilerImpl and
> PortletWindowAccessorImpl. This portal is running Jetspeed 2.0, but I
> don't think the caching method has changed since then."
>
>
>
> "most" caching has been moved to ehcache. Unfortunately,
> PortletWindowAccessorImpl missed the cut ;)
>
>
>
> -scott
>
>
>
> ________________________________
>
> From: Ethan Adams [mailto:ethanjadams@gmail.com]
> Sent: Tuesday, October 09, 2007 2:22 PM
> To: Jetspeed Users List
> Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
>
>
>
> The issues I found was with the JetspeedProfilerImpl and
> PortletWindowAccessorImpl. This portal is running Jetspeed 2.0, but I
> don't think the caching method has changed since then.
>
> On 10/9/07, David Sean Taylor <da...@bluesunrise.com> wrote:
>
>
> On Oct 9, 2007, at 7:32 AM, Ethan Adams wrote:
>
>> Oddly enough, I just came across this yesterday.
>>
>> Attached is a snapshot showing 90MB of data. Max heap is at 1GB.
>> This was with 25000 unique users cycling through.
>>
> I think your attachment was stripped
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
RE: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by "Weaver, Scott" <we...@ugs.com>.
My current production portal in 2.0 also but I am currently upgrading to
2.1.3.
"The issues I found was with the JetspeedProfilerImpl and
PortletWindowAccessorImpl. This portal is running Jetspeed 2.0, but I
don't think the caching method has changed since then."
"most" caching has been moved to ehcache. Unfortunately,
PortletWindowAccessorImpl missed the cut ;)
-scott
________________________________
From: Ethan Adams [mailto:ethanjadams@gmail.com]
Sent: Tuesday, October 09, 2007 2:22 PM
To: Jetspeed Users List
Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
The issues I found was with the JetspeedProfilerImpl and
PortletWindowAccessorImpl. This portal is running Jetspeed 2.0, but I
don't think the caching method has changed since then.
On 10/9/07, David Sean Taylor <da...@bluesunrise.com> wrote:
On Oct 9, 2007, at 7:32 AM, Ethan Adams wrote:
> Oddly enough, I just came across this yesterday.
>
> Attached is a snapshot showing 90MB of data. Max heap is at 1GB.
> This was with 25000 unique users cycling through.
>
I think your attachment was stripped
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by Ethan Adams <et...@gmail.com>.
The issues I found was with the JetspeedProfilerImpl and
PortletWindowAccessorImpl. This portal is running Jetspeed 2.0, but I don't
think the caching method has changed since then.
On 10/9/07, David Sean Taylor <da...@bluesunrise.com> wrote:
>
>
> On Oct 9, 2007, at 7:32 AM, Ethan Adams wrote:
>
> > Oddly enough, I just came across this yesterday.
> >
> > Attached is a snapshot showing 90MB of data. Max heap is at 1GB.
> > This was with 25000 unique users cycling through.
> >
> I think your attachment was stripped
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
Re: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Oct 9, 2007, at 7:32 AM, Ethan Adams wrote:
> Oddly enough, I just came across this yesterday.
>
> Attached is a snapshot showing 90MB of data. Max heap is at 1GB.
> This was with 25000 unique users cycling through.
>
I think your attachment was stripped
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by Ethan Adams <et...@gmail.com>.
Oddly enough, I just came across this yesterday.
Attached is a snapshot showing 90MB of data. Max heap is at 1GB. This was
with 25000 unique users cycling through.
On 10/9/07, Weaver, Scott <we...@ugs.com> wrote:
>
> Hmmmm, and I thought I was the only one this issue. However, mine takes
> a couple days to "fall down" so to speak in. At first I thought it
> might be something in my custom pipeline but after hearing this I don't
> think this the case. I did make a point to David a while back that my
> profiling runs against my portal showed that
> org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl
> maintains an in-memory cache (Map) of
> org.apache.jetspeed.om.window.impl.PortletWindowImpls and that map was
> topping out the number of retained objects on the heap. I have been
> meaning to convert this over to using the ehcache that we use in other
> areas of Jetspeed.
>
> Can I get anyone experiencing memory leaks to profile their portal then
> post a list of the largest objects/large number of the same objects in
> the heap at/near the time of the OOM error?
>
> Regards,
> -scott
>
> > -----Original Message-----
> > From: Vitaly Baranovsky [mailto:vitaly.baranovsky.2@gmail.com]
> > Sent: Monday, October 08, 2007 6:15 PM
> > To: Jetspeed Users List
> > Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
> >
> > I have same problem.
> > Portal works about 2 hours with real users and after that falls down
> with
> > java.lang.OutOfMemoryError: Java heap space
> >
> > 2007/10/9, ramaj <ra...@gmail.com>:
> > >
> > >
> > > hi,
> > > I have installed Jetspeed2.1.
> > > I am doing login stress testing for multiple users using JMETER
> tool.
> > >
> > > Requests are
> > > Total requests = 8000
> > > cun requests = 500
> > >
> > > But stress testing reached to 5000 then
> > > /webportal/webapps/webportal/logs/pa.log
> > > it gives error
> > >
> > > "Caused by: java.lang.OutOfMemoryError: Java heap space"
> > >
> > > For to solve this error,i have increased the RAM size as follows:
> > >
> > > webportal/bin/catalina.bat:set JAVA_OPTS=%JAVA_OPTS% -Xmx2000m
> > > webportal/bin/catalina.sh:JAVA_OPTS="$JAVA_OPTS "-Xmx2000m
> > > webportal/bin/catdebug.bat:set CATALINA_OPTS=-Xmx2000m
> > > webportal/bin/startJetspeed.bat:set CATALINA_OPTS=-Xmx2000m
> > >
> > >
> > > then application restart again........
> > >
> > > but again it reached to 5000 requests,it gives same error..........
> > >
> > > plz help me.........
> > >
> > > Thanks
> > > ramj.
> > > --
> > > View this message in context:
> > >
> http://www.nabble.com/Caused-by%3A-java.lang.OutOfMemoryError%3A-Java-
> > heap-space-tf4590727.html#a13105025
> > > Sent from the Jetspeed - User mailing list archive at Nabble.com.
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > > For additional commands, e-mail:
> jetspeed-user-help@portals.apache.org
> > >
> > >
> >
> >
> > --
> > With best regards,
> > Vitaly Baranovsky
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
RE: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by "Weaver, Scott" <we...@ugs.com>.
Hmmmm, and I thought I was the only one this issue. However, mine takes
a couple days to "fall down" so to speak in. At first I thought it
might be something in my custom pipeline but after hearing this I don't
think this the case. I did make a point to David a while back that my
profiling runs against my portal showed that
org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl
maintains an in-memory cache (Map) of
org.apache.jetspeed.om.window.impl.PortletWindowImpls and that map was
topping out the number of retained objects on the heap. I have been
meaning to convert this over to using the ehcache that we use in other
areas of Jetspeed.
Can I get anyone experiencing memory leaks to profile their portal then
post a list of the largest objects/large number of the same objects in
the heap at/near the time of the OOM error?
Regards,
-scott
> -----Original Message-----
> From: Vitaly Baranovsky [mailto:vitaly.baranovsky.2@gmail.com]
> Sent: Monday, October 08, 2007 6:15 PM
> To: Jetspeed Users List
> Subject: Re: Caused by: java.lang.OutOfMemoryError: Java heap space
>
> I have same problem.
> Portal works about 2 hours with real users and after that falls down
with
> java.lang.OutOfMemoryError: Java heap space
>
> 2007/10/9, ramaj <ra...@gmail.com>:
> >
> >
> > hi,
> > I have installed Jetspeed2.1.
> > I am doing login stress testing for multiple users using JMETER
tool.
> >
> > Requests are
> > Total requests = 8000
> > cun requests = 500
> >
> > But stress testing reached to 5000 then
> > /webportal/webapps/webportal/logs/pa.log
> > it gives error
> >
> > "Caused by: java.lang.OutOfMemoryError: Java heap space"
> >
> > For to solve this error,i have increased the RAM size as follows:
> >
> > webportal/bin/catalina.bat:set JAVA_OPTS=%JAVA_OPTS% -Xmx2000m
> > webportal/bin/catalina.sh:JAVA_OPTS="$JAVA_OPTS "-Xmx2000m
> > webportal/bin/catdebug.bat:set CATALINA_OPTS=-Xmx2000m
> > webportal/bin/startJetspeed.bat:set CATALINA_OPTS=-Xmx2000m
> >
> >
> > then application restart again........
> >
> > but again it reached to 5000 requests,it gives same error..........
> >
> > plz help me.........
> >
> > Thanks
> > ramj.
> > --
> > View this message in context:
> >
http://www.nabble.com/Caused-by%3A-java.lang.OutOfMemoryError%3A-Java-
> heap-space-tf4590727.html#a13105025
> > Sent from the Jetspeed - User mailing list archive at Nabble.com.
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
jetspeed-user-help@portals.apache.org
> >
> >
>
>
> --
> With best regards,
> Vitaly Baranovsky
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Caused by: java.lang.OutOfMemoryError: Java heap space
Posted by Vitaly Baranovsky <vi...@gmail.com>.
I have same problem.
Portal works about 2 hours with real users and after that falls down with
java.lang.OutOfMemoryError: Java heap space
2007/10/9, ramaj <ra...@gmail.com>:
>
>
> hi,
> I have installed Jetspeed2.1.
> I am doing login stress testing for multiple users using JMETER tool.
>
> Requests are
> Total requests = 8000
> cun requests = 500
>
> But stress testing reached to 5000 then
> /webportal/webapps/webportal/logs/pa.log
> it gives error
>
> "Caused by: java.lang.OutOfMemoryError: Java heap space"
>
> For to solve this error,i have increased the RAM size as follows:
>
> webportal/bin/catalina.bat:set JAVA_OPTS=%JAVA_OPTS% -Xmx2000m
> webportal/bin/catalina.sh:JAVA_OPTS="$JAVA_OPTS "-Xmx2000m
> webportal/bin/catdebug.bat:set CATALINA_OPTS=-Xmx2000m
> webportal/bin/startJetspeed.bat:set CATALINA_OPTS=-Xmx2000m
>
>
> then application restart again........
>
> but again it reached to 5000 requests,it gives same error..........
>
> plz help me.........
>
> Thanks
> ramj.
> --
> View this message in context:
> http://www.nabble.com/Caused-by%3A-java.lang.OutOfMemoryError%3A-Java-heap-space-tf4590727.html#a13105025
> Sent from the Jetspeed - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
--
With best regards,
Vitaly Baranovsky