On Dec 20, 2006, at 4:20 PM, Jason Dillon wrote:
Do you think that leak might be what is causing the random openejb
related failures I keep running into?
Still have not updated the JDK on gbuild hosts to use _10 yet...
maybe I will give that a shot.
Hi Jason,
It's possible. I had started
Do you think that leak might be what is causing the random openejb
related failures I keep running into?
Still have not updated the JDK on gbuild hosts to use _10 yet...
maybe I will give that a shot.
--jason
On Dec 20, 2006, at 12:52 PM, Kevan Miller wrote:
On Dec 20, 2006, at 10:29 A
On Dec 20, 2006, at 10:29 AM, Paul ANDERSON wrote:
Bumping up MaxPermSize works great on 1.5.
If Geronimo 1.1.1 is then stable for hot portlet deployment on
LR4.2, we'll be able to use it.
Thanks all round for the quick responses.
Hi Paul,
That's good news.
FYI -- there have been some Cla
06 15:54
À : dev@geronimo.apache.org
Objet : Re: Geronimo 1.1.1 and Liferay 4, memory problems on startup and hot
deployment
On Dec 20, 2006, at 8:46 AM, Jeff Genender wrote:
> Kevan M,
>
> Do you have any thoughts on the leaking classloaders?
Hey Jeff,
AFAIK, Geronimo 1.1.1 running on JRE
On Dec 20, 2006, at 8:46 AM, Jeff Genender wrote:
Kevan M,
Do you have any thoughts on the leaking classloaders?
Hey Jeff,
AFAIK, Geronimo 1.1.1 running on JRE 1.4.2 was clean. I ran Daytrader
through multiple deploy/undeploy cycles. Daytrader is great, in this
regard, because it hits a
Kevan M,
Do you have any thoughts on the leaking classloaders?
I have run Liferay 4.1.2 and 4.2 on Geronimo 1.1.1 setting the -Xms1G
-Xmx1G and have never run into any memory problems what-so-ever, with
the memory used at about 110M after it's up and running. I have run it
on the Mac.
Paul,
Ha
