camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5086) Archetype: camel-archetype-web retains loaded classes after redeployment, causing permgen space to fill up.
Date Tue, 20 Mar 2012 05:41:52 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated CAMEL-5086:
-------------------------------

    Comment: was deleted

(was: Why do you want to use the Camel web console embedded with your application?
You drag in the web console, that uses scala, scalete, jersey, and whatnot. All libraries
that may have a leak somewhere.
The Camel web console is not really ment for production usage, but a developer consoler for
trying out stuff with Camel.

I suggest to use this tutorial, and just use a plain war project
http://camel.apache.org/tutorial-on-using-camel-in-a-web-application.html

)
    
> Archetype: camel-archetype-web retains loaded classes after redeployment, causing permgen
space to fill up.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5086
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5086
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-spring
>    Affects Versions: 2.9.1
>         Environment: Apache Tomcat 7.0.26
> jdk 1.6.0_26
> CentOS:
> Linux version 2.6.18-238.el5
>            Reporter: Dan Richelson
>            Priority: Minor
>              Labels: leak, memory, memory_leak, permgen, spring, tomcat, war, webapp
>
> Steps to reproduce:
> 1. Create a new camel web project (based on instructions here: http://camel.apache.org/camel-maven-archetypes.html
):
> mvn archetype:generate -DarchetypeGroupId=org.apache.camel.archetypes -DarchetypeArtifactId=camel-archetype-web
-DarchetypeVersion=2.9.1 -DarchetypeRepository=https://repository.apache.org/content/groups/snapshots-group
> 2. Build the new project:
> mvn clean install
> 3. Copy .war file in target/ to tomcat's webapps directory.
> 4. Reload webapp (easiest way is to touch the .war file)
> 5. If you are using a profiler, you will see that the permgen space increases on every
reload (the previous webapp's classes don't get unloaded)
> 6. Eventually the webapp container will crash with a permgen out of memory error.
> Workaround: restarting the webapp container will reset the permgen space.
> Removing the Spring nature of the project makes this go away, so it could be a problem
with Spring itself.
> This also happens when using Jetty7, so I don't think it is a problem with the container.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message