You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Dan Richelson (Created) (JIRA)" <ji...@apache.org> on 2012/03/14 17:54:40 UTC
[jira] [Created] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
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
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
[jira] [Commented] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233239#comment-13233239 ]
Claus Ibsen commented on CAMEL-5086:
------------------------------------
I am trying with the 2.9-SNAPSHOT to see how it goes there.
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Labels: leak, memory, memory_leak, permgen, spring, tomcat, war, webapp
> Fix For: 2.10.0
>
> Attachments: tomcat.png, tomcat2.png
>
>
> 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
[jira] [Updated] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Assigned] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-5086:
----------------------------------
Assignee: Claus Ibsen
> 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
> Assignee: Claus Ibsen
> 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
[jira] [Commented] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233237#comment-13233237 ]
Claus Ibsen commented on CAMEL-5086:
------------------------------------
And my permgen, was not leaking, and getting down to 31mb - see tomcat2
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Labels: leak, memory, memory_leak, permgen, spring, tomcat, war, webapp
> Attachments: tomcat.png, tomcat2.png
>
>
> 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
[jira] [Updated] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-5086:
-------------------------------
Fix Version/s: 2.9.2
Looks fine with the 2.9-SNAPSHOT (to be 2.9.2 release).
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Labels: leak, memory, memory_leak, permgen, spring, tomcat, war, webapp
> Fix For: 2.10.0, 2.9.2
>
> Attachments: tomcat.png, tomcat2.png
>
>
> 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
[jira] [Commented] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233236#comment-13233236 ]
Claus Ibsen commented on CAMEL-5086:
------------------------------------
We have fixed a number of leaks on trunk. I suggest to try the upcoming 2.10 release. Or the 2.9.2 release.
I just tried with 2.10 and could not detect any leaks. I touched the web app 5 times
{code}
davsclaus:/opt/apache-tomcat-7.0.26/webapps$ touch bar-1.0-SNAPSHOT.war
davsclaus:/opt/apache-tomcat-7.0.26/webapps$ touch bar-1.0-SNAPSHOT.war
davsclaus:/opt/apache-tomcat-7.0.26/webapps$ touch bar-1.0-SNAPSHOT.war
davsclaus:/opt/apache-tomcat-7.0.26/webapps$ touch bar-1.0-SNAPSHOT.war
davsclaus:/opt/apache-tomcat-7.0.26/webapps$ touch bar-1.0-SNAPSHOT.war
{code}
And memory usage was low. When performing a GC I get down to 7-8mb.
> 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
> Assignee: Claus Ibsen
> 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
[jira] [Commented] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233229#comment-13233229 ]
Claus Ibsen commented on CAMEL-5086:
------------------------------------
I suggest to attach jvisualvm to the tomcat container and try to see if you can spot any leaks?
> 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
[jira] [Commented] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233227#comment-13233227 ]
Claus Ibsen commented on CAMEL-5086:
------------------------------------
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
[jira] [Updated] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Dan Richelson (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Richelson updated CAMEL-5086:
---------------------------------
Description:
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.
was:
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.
> 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
[jira] [Resolved] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5086.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.10.0
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Labels: leak, memory, memory_leak, permgen, spring, tomcat, war, webapp
> Fix For: 2.10.0
>
> Attachments: tomcat.png, tomcat2.png
>
>
> 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
[jira] [Updated] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-5086:
-------------------------------
Attachment: tomcat2.png
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Labels: leak, memory, memory_leak, permgen, spring, tomcat, war, webapp
> Attachments: tomcat.png, tomcat2.png
>
>
> 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
[jira] [Updated] (CAMEL-5086) Archetype: camel-archetype-web
retains loaded classes after redeployment, causing permgen space to fill
up.
Posted by "Claus Ibsen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-5086:
-------------------------------
Attachment: tomcat.png
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Labels: leak, memory, memory_leak, permgen, spring, tomcat, war, webapp
> Attachments: tomcat.png
>
>
> 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