[ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
