[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1255) memory leak after 7 hours
[ http://jira.jboss.com/jira/browse/JBAS-1255?page=comments#action_12314977 ] Attila Ulbert commented on JBAS-1255: - As a result of our recent experiences we realized that our simple example application leaks in a given server directory, and does not leak in a different server directory (e.g. the default server directory of JBoss 401). I've uploaded our test server directory to the Sourceforge site. When we deployed and run our test application, it seemed to leak there, however if we used the default server, the memory consumption was stable. Strange... So please deploy your test application into our test domain. We simply cannot explain how can our test server directory turn a stable application into a memory gross feeder... memory leak after 7 hours - Key: JBAS-1255 URL: http://jira.jboss.com/jira/browse/JBAS-1255 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Alexey Loubyansky SourceForge Submitter: atomrom . Hi, I have experienced strange memory leaks under JBoss 4.0.0 after 7 hours, and under JBoss 4.0.1RC2 after 3.5 hours running my application. (In the first 7 hours my application consumes 100M of memory under 4.0.0, however after 7 hours the memory consumption raises lineraly). I used YourKit to detect the memory leak and I found that the memory is chiefly occupied by HashMap and entity bean proxies. Unfortunately I cannot provide source code, but I can give a short description of the component architecture and functioning: (a) objects are inserted into a messaging topic (b) an MDB receives the objects and: (b.i) dispaches them to a resource adapter (the RA sends the object over the network) (b.ii) creates a database entry using the String(s) returned by the RA (a tuple looks like this: [String: id, Date: date, String: st]; I'm using a CMP entity bean) (c) a timer periodically removes the overaged database entries (see date). ejbTimeout is implemented by a stateless session bean, database entries are removed by the corresponding CMP entity bean (d) whenever the RA receives an object over the network, it dispatches it to a stateless session bean, which is registered as an endpoint at the RA (e) the stateless session bean (e.i) updates the database entry (using the ), or more precisely, its st field (e.ii) inserts a new database entry (e.iii) if the st field statisfies certain conditions, removes both the inserted and updated entries Additional infos: * OS: RedHat AS (running on various hardware, e.g. simple PC and a 4 processor Xeon server) * JDK: jdk1.4.5 * I see lot of log messages regarding rolled back transactions (because of timeouts); these exceptions are thrown in the CMP entity bean in that method, which removes the overaged entries. After a findByDate I iterate over the resulting collection and when I want to access id, an exception is thrown. Not always, but strangely often. * the memory leak emerges after 7 (or 3.5) hours regardless the load, and configuration. The load influences only the gradient of the lineraly increasing (and therefore deadly) period. Merry Christmas, Mormota -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1255) memory leak after 7 hours
[ http://jira.jboss.com/jira/browse/JBAS-1255?page=comments#action_12314930 ] Alexey Loubyansky commented on JBAS-1255: - Since it is reported as a bug in CMP I would appreciate a pure CMP testcase (w/o MDBs). I wrote my own which creates and removes entity instances with commit option B: - create and remove in the same transaction - create and remove in different transactions - with the same primary key - with different primary keys So far, I don't see a leak. Pool and cache sizes are never more than 1. Memory grows for some time (several minutes) at the beginning and then stays constant. memory leak after 7 hours - Key: JBAS-1255 URL: http://jira.jboss.com/jira/browse/JBAS-1255 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Alexey Loubyansky SourceForge Submitter: atomrom . Hi, I have experienced strange memory leaks under JBoss 4.0.0 after 7 hours, and under JBoss 4.0.1RC2 after 3.5 hours running my application. (In the first 7 hours my application consumes 100M of memory under 4.0.0, however after 7 hours the memory consumption raises lineraly). I used YourKit to detect the memory leak and I found that the memory is chiefly occupied by HashMap and entity bean proxies. Unfortunately I cannot provide source code, but I can give a short description of the component architecture and functioning: (a) objects are inserted into a messaging topic (b) an MDB receives the objects and: (b.i) dispaches them to a resource adapter (the RA sends the object over the network) (b.ii) creates a database entry using the String(s) returned by the RA (a tuple looks like this: [String: id, Date: date, String: st]; I'm using a CMP entity bean) (c) a timer periodically removes the overaged database entries (see date). ejbTimeout is implemented by a stateless session bean, database entries are removed by the corresponding CMP entity bean (d) whenever the RA receives an object over the network, it dispatches it to a stateless session bean, which is registered as an endpoint at the RA (e) the stateless session bean (e.i) updates the database entry (using the ), or more precisely, its st field (e.ii) inserts a new database entry (e.iii) if the st field statisfies certain conditions, removes both the inserted and updated entries Additional infos: * OS: RedHat AS (running on various hardware, e.g. simple PC and a 4 processor Xeon server) * JDK: jdk1.4.5 * I see lot of log messages regarding rolled back transactions (because of timeouts); these exceptions are thrown in the CMP entity bean in that method, which removes the overaged entries. After a findByDate I iterate over the resulting collection and when I want to access id, an exception is thrown. Not always, but strangely often. * the memory leak emerges after 7 (or 3.5) hours regardless the load, and configuration. The load influences only the gradient of the lineraly increasing (and therefore deadly) period. Merry Christmas, Mormota -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1255) memory leak after 7 hours
[ http://jira.jboss.com/jira/browse/JBAS-1255?page=comments#action_12314698 ] Alexey Loubyansky commented on JBAS-1255: - Ok, thanks. If you can submit the testcase, please, do. I won't start looking into it until the beginning of the February though. memory leak after 7 hours - Key: JBAS-1255 URL: http://jira.jboss.com/jira/browse/JBAS-1255 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Alexey Loubyansky SourceForge Submitter: atomrom . Hi, I have experienced strange memory leaks under JBoss 4.0.0 after 7 hours, and under JBoss 4.0.1RC2 after 3.5 hours running my application. (In the first 7 hours my application consumes 100M of memory under 4.0.0, however after 7 hours the memory consumption raises lineraly). I used YourKit to detect the memory leak and I found that the memory is chiefly occupied by HashMap and entity bean proxies. Unfortunately I cannot provide source code, but I can give a short description of the component architecture and functioning: (a) objects are inserted into a messaging topic (b) an MDB receives the objects and: (b.i) dispaches them to a resource adapter (the RA sends the object over the network) (b.ii) creates a database entry using the String(s) returned by the RA (a tuple looks like this: [String: id, Date: date, String: st]; I'm using a CMP entity bean) (c) a timer periodically removes the overaged database entries (see date). ejbTimeout is implemented by a stateless session bean, database entries are removed by the corresponding CMP entity bean (d) whenever the RA receives an object over the network, it dispatches it to a stateless session bean, which is registered as an endpoint at the RA (e) the stateless session bean (e.i) updates the database entry (using the ), or more precisely, its st field (e.ii) inserts a new database entry (e.iii) if the st field statisfies certain conditions, removes both the inserted and updated entries Additional infos: * OS: RedHat AS (running on various hardware, e.g. simple PC and a 4 processor Xeon server) * JDK: jdk1.4.5 * I see lot of log messages regarding rolled back transactions (because of timeouts); these exceptions are thrown in the CMP entity bean in that method, which removes the overaged entries. After a findByDate I iterate over the resulting collection and when I want to access id, an exception is thrown. Not always, but strangely often. * the memory leak emerges after 7 (or 3.5) hours regardless the load, and configuration. The load influences only the gradient of the lineraly increasing (and therefore deadly) period. Merry Christmas, Mormota -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1255) memory leak after 7 hours
[ http://jira.jboss.com/jira/browse/JBAS-1255?page=comments#action_12314692 ] Attila Ulbert commented on JBAS-1255: - Answers to your questions: 1) In stable JBoss 4.0.1, there is no 3.5 (or 7) hours long constant-memory-use period. This means that in the previous JBoss 4.0.x releases, when I used commit option C, the memory consumption was more-or-less constant in the first few hours, however after 7 hours in the case of JB 4.0.0 (3.5 hours in the case of 4.0.1RCX), the application started to consume all the available memory. When I used the stable 4.0.1 release, I experienced the memory leak immediatlely. When I used commit option B, I experienced the leak in the case of enevry 4.0.X versions. 2) If it's really CMP related, I assume I should see the leak if I remove all the MDB stuff and just create and delete entity instances. Is there a chance you can confirm this? Yes, I can confirm. We have an example application, which simply creates and removes CMP entities in an infinite loop. And this application leaks. We have an other example application as well, which uses a timer to remove the entities. If all goes well, you will got the whole server package and the source code of this component on Monday. memory leak after 7 hours - Key: JBAS-1255 URL: http://jira.jboss.com/jira/browse/JBAS-1255 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Alexey Loubyansky SourceForge Submitter: atomrom . Hi, I have experienced strange memory leaks under JBoss 4.0.0 after 7 hours, and under JBoss 4.0.1RC2 after 3.5 hours running my application. (In the first 7 hours my application consumes 100M of memory under 4.0.0, however after 7 hours the memory consumption raises lineraly). I used YourKit to detect the memory leak and I found that the memory is chiefly occupied by HashMap and entity bean proxies. Unfortunately I cannot provide source code, but I can give a short description of the component architecture and functioning: (a) objects are inserted into a messaging topic (b) an MDB receives the objects and: (b.i) dispaches them to a resource adapter (the RA sends the object over the network) (b.ii) creates a database entry using the String(s) returned by the RA (a tuple looks like this: [String: id, Date: date, String: st]; I'm using a CMP entity bean) (c) a timer periodically removes the overaged database entries (see date). ejbTimeout is implemented by a stateless session bean, database entries are removed by the corresponding CMP entity bean (d) whenever the RA receives an object over the network, it dispatches it to a stateless session bean, which is registered as an endpoint at the RA (e) the stateless session bean (e.i) updates the database entry (using the ), or more precisely, its st field (e.ii) inserts a new database entry (e.iii) if the st field statisfies certain conditions, removes both the inserted and updated entries Additional infos: * OS: RedHat AS (running on various hardware, e.g. simple PC and a 4 processor Xeon server) * JDK: jdk1.4.5 * I see lot of log messages regarding rolled back transactions (because of timeouts); these exceptions are thrown in the CMP entity bean in that method, which removes the overaged entries. After a findByDate I iterate over the resulting collection and when I want to access id, an exception is thrown. Not always, but strangely often. * the memory leak emerges after 7 (or 3.5) hours regardless the load, and configuration. The load influences only the gradient of the lineraly increasing (and therefore deadly) period. Merry Christmas, Mormota -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1255) memory leak after 7 hours
[ http://jira.jboss.com/jira/browse/JBAS-1255?page=comments#action_12314523 ] Alex Loubyansky commented on JBAS-1255: --- What does the following mean? In stable JBoss 4.0.1, there is no 3.5 (or 7) hours long constant-memory-use period. If it's really CMP related, I assume I should see the leak if I remove all the MDB stuff and just create and delete entity instances. Is there a chance you can confirm this? Thanks. memory leak after 7 hours - Key: JBAS-1255 URL: http://jira.jboss.com/jira/browse/JBAS-1255 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Alex Loubyansky SourceForge Submitter: atomrom . Hi, I have experienced strange memory leaks under JBoss 4.0.0 after 7 hours, and under JBoss 4.0.1RC2 after 3.5 hours running my application. (In the first 7 hours my application consumes 100M of memory under 4.0.0, however after 7 hours the memory consumption raises lineraly). I used YourKit to detect the memory leak and I found that the memory is chiefly occupied by HashMap and entity bean proxies. Unfortunately I cannot provide source code, but I can give a short description of the component architecture and functioning: (a) objects are inserted into a messaging topic (b) an MDB receives the objects and: (b.i) dispaches them to a resource adapter (the RA sends the object over the network) (b.ii) creates a database entry using the String(s) returned by the RA (a tuple looks like this: [String: id, Date: date, String: st]; I'm using a CMP entity bean) (c) a timer periodically removes the overaged database entries (see date). ejbTimeout is implemented by a stateless session bean, database entries are removed by the corresponding CMP entity bean (d) whenever the RA receives an object over the network, it dispatches it to a stateless session bean, which is registered as an endpoint at the RA (e) the stateless session bean (e.i) updates the database entry (using the ), or more precisely, its st field (e.ii) inserts a new database entry (e.iii) if the st field statisfies certain conditions, removes both the inserted and updated entries Additional infos: * OS: RedHat AS (running on various hardware, e.g. simple PC and a 4 processor Xeon server) * JDK: jdk1.4.5 * I see lot of log messages regarding rolled back transactions (because of timeouts); these exceptions are thrown in the CMP entity bean in that method, which removes the overaged entries. After a findByDate I iterate over the resulting collection and when I want to access id, an exception is thrown. Not always, but strangely often. * the memory leak emerges after 7 (or 3.5) hours regardless the load, and configuration. The load influences only the gradient of the lineraly increasing (and therefore deadly) period. Merry Christmas, Mormota -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1255) memory leak after 7 hours
[ http://jira.jboss.com/jira/browse/JBAS-1255?page=comments#action_12314446 ] Scott M Stark commented on JBAS-1255: - Date: 2004-12-29 10:45 Sender: atomrom Logged In: YES user_id=1184354 Some new details: I simplified the application to the following (see new step b.iii): (a) objects are inserted into a messaging topic (b) an MDB receives the objects and: (b.i) dispaches them to a resource adapter (the RA sends the object over the network) (b.ii) creates a database entry using the String(s) returned by the RA (a tuple looks like this: [String: id, Date: date, String: st]; I'm using a CMP entity bean) (b.iii) _removes the new entry_ Despite the database entries are removed instantly after their creation (and therefore the database is empty), the memory usade increases steadyly. In stable JBoss 4.0.1, there is no 3.5 (or 7) hours long constant-memory-use period. The pace of memory consumption growth can be reduced by using C commit option (instead of the default B). Memory leak still persist when using jdk 1.5. memory leak after 7 hours - Key: JBAS-1255 URL: http://jira.jboss.com/jira/browse/JBAS-1255 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Alex Loubyansky SourceForge Submitter: atomrom . Hi, I have experienced strange memory leaks under JBoss 4.0.0 after 7 hours, and under JBoss 4.0.1RC2 after 3.5 hours running my application. (In the first 7 hours my application consumes 100M of memory under 4.0.0, however after 7 hours the memory consumption raises lineraly). I used YourKit to detect the memory leak and I found that the memory is chiefly occupied by HashMap and entity bean proxies. Unfortunately I cannot provide source code, but I can give a short description of the component architecture and functioning: (a) objects are inserted into a messaging topic (b) an MDB receives the objects and: (b.i) dispaches them to a resource adapter (the RA sends the object over the network) (b.ii) creates a database entry using the String(s) returned by the RA (a tuple looks like this: [String: id, Date: date, String: st]; I'm using a CMP entity bean) (c) a timer periodically removes the overaged database entries (see date). ejbTimeout is implemented by a stateless session bean, database entries are removed by the corresponding CMP entity bean (d) whenever the RA receives an object over the network, it dispatches it to a stateless session bean, which is registered as an endpoint at the RA (e) the stateless session bean (e.i) updates the database entry (using the ), or more precisely, its st field (e.ii) inserts a new database entry (e.iii) if the st field statisfies certain conditions, removes both the inserted and updated entries Additional infos: * OS: RedHat AS (running on various hardware, e.g. simple PC and a 4 processor Xeon server) * JDK: jdk1.4.5 * I see lot of log messages regarding rolled back transactions (because of timeouts); these exceptions are thrown in the CMP entity bean in that method, which removes the overaged entries. After a findByDate I iterate over the resulting collection and when I want to access id, an exception is thrown. Not always, but strangely often. * the memory leak emerges after 7 (or 3.5) hours regardless the load, and configuration. The load influences only the gradient of the lineraly increasing (and therefore deadly) period. Merry Christmas, Mormota -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
