This week's giveaway is in the Java in General forum.
We're giving away four copies of Java Challengers and have Rafael del Nero on-line!
See this thread for details.
Win a copy of Java Challengers this week in the Java in General forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

OutOfMemoryException on multiple deploys of Spring application

 
Ranch Hand
Posts: 281
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This seems to be common error:

I see OutOfMemoryError when I deploy a spring based application in an app server. AspectJ type classes are not getting garbage collected. By looking at other postings, it seems ore like the way application is coded/configured. Some of the postings talk about the problem with having static member variables. Shutdownhook is registered in the code.

Following seems like an interesting article:

http://blogs.sun.com/fkieviet/entry/...e_dreaded_java

That being said, did not notice similar problem with non spring app in the same app server with multiple deploys.

Any suggestion, or advice will be appreciated.
 
ranger
Posts: 17346
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The link doesn't work. ;)

Most of these errors are because some App Servers hot deploy doesn't clean things up as nicely with the way the deal with ClassLoaders. So, it really isn't a Spring issue as much a ClassLoader/App Server issue.

What I tend to do is restart the App Server to deploy my apps rather than hot deploy them.

Mark
 
reply
    Bookmark Topic Watch Topic
  • New Topic