Our production servers have their maximum memory set to 2048m.
Everything is fine for a while. Eventually the java process ends up with
all 2048m allocated. At this point server load starts going up and
response time gets bad. Eventually request start timing out.
Restarting the server fixes the
On Apr 2, 2008, at 8:21 AM, Andrew Fritz wrote:
> Our production servers have their maximum memory set to 2048m.
> Everything is fine for a while. Eventually the java process ends up
> with
> all 2048m allocated. At this point server load starts going up and
> response time gets bad. Eventually
On Apr 2, 2008, at 6:22 PM, Matt Johnston wrote:
> Does the current version of resin support the @Remote functionality of
> EJB3? I looked at the documentation, but it was very sparse.
>
> I basically have an EJB3 that I want to share among all my web-apps
> within the same resin server. Each web
On Apr 2, 2008, at 2:25 PM, Knut Forkalsrud wrote:
> This was with version 3.1.4, I haven't tried 3.1.5 yet.
3.1.5 is interesting, since it should handle the null classes faster
(basically, 3.1.5 pre-analyzes all the jars). The locking in 3.1.5 is
the same as 3.1.4.
I've updated the locking
On Mar 31, 2008, at 2:58 AM, Torkil Svensgaard wrote:
> Hi list
>
> I'm playing around a bit with Amber and can't seem to get cascading
> persist to work. The attached code runs fine but doesn't persist the
> competences, only the search.
>
> Have I misunderstood something?
Based on the bug
