Hi,
We have had a perf issue.
Our servers have 4Gb RAM. It has just Resin and Apache installed.
The problem is, when I start Resin, the whole server uses about 2.5 Gb RAM
After that memory usage keep growing til it reachs the 4Gb RAM, use swap
and so on.
After few hours the application start
Bumping this and also bug 0002963, as we're still having memory issues in
production that we can't trace back to our application, causing PermGen to
build with every request and eventual OutOfMem/restart. Hoping issues in
this thread can be resolved and pushed into the 3.1.8 trunk. Our app is a
On Mar 20, 2009, at 9:09 AM, Ronan Lucio wrote:
Hi,
We have had a perf issue.
Our servers have 4Gb RAM. It has just Resin and Apache installed.
The problem is, when I start Resin, the whole server uses about 2.5
Gb RAM
After that memory usage keep growing til it reachs the 4Gb RAM,
We accomplish this by grabbing an instance of HttpSession from the request
via request.getSession(), casting that to resin's SessionImpl, and calling
the login() method on that impl. Your controller can lift the username and
password out of the request and pass them in to the login method, which
Scott,
Scott Ferguson escreveu:
The /resin-admin has a heap dump which will give you a general idea of
what's taking the memory (you will need to add a -agentlib:resin to
enable it.
That heap information is very important because it will very quickly
let you focus on the real issue.
On Mar 19, 2009, at 8:30 PM, Jeff Schnitzer wrote:
The problem is, j2ee automatic authentication is nearly useless.
Correct.
It doesn't allow for autologin cookies nor does it allow me to sign up
new users - they would have to then log in again. It blows my mind
that a decade later the
On Mar 19, 2009, at 4:08 PM, Riccardo Cohen wrote:
All right, thanks for the answer. I'll wait for the 4.0 stable :)
By the way, the Resin 4.0 snapshots should be usable for
experimentation (not deployment yet.) We've worked through most of
the regression failures and added the bulk of
On Mar 19, 2009, at 2:08 PM, Jeff Schnitzer wrote:
First of all, I'd just like to say wow, I'm happy to re-discover Resin
- I recall using it briefly in 2002 and I'm impressed with what you've
been doing since. It's a sharp contrast to the progress of JBoss,
which has sadly become a
On Fri, Mar 20, 2009 at 10:01 AM, Riccardo Cohen wrote:
I need someting very light, quick and safe, what do you suggest ?
I'm not familiar with JAI, so I'll leave that for others to assess.
For a server side application you may want to stick with imageio over
java.awt.Toolkit.
The Toolkit
What's the best way to lobby them? I love the new IoC stuff.
-Aaron
On Mar 19, 2009, at 2:08 PM, Jeff Schnitzer wrote:
First of all, I'd just like to say wow, I'm happy to re-discover Resin
- I recall using it briefly in 2002 and I'm impressed with what you've
been doing since. It's a
Hi Bill,
I have already done it some weeks ago, but it doesn't seem the problem.
Thanks,
Ronan
Bill Au escreveu:
I would also enable garbage collection logging (-Xloggc:filename) to
see if your application is running slow because the JVM is spending a
lot of time doing garbage collection.
11 matches
Mail list logo
