[ http://jira.jboss.com/jira/browse/JBAS-1336?page=history ]
Scott M Stark moved JBMQ-2 to JBAS-1336:
----------------------------------------
Project: JBoss Application Server (was: JBoss MQ)
Key: JBAS-1336 (was: JBMQ-2)
Issue Type: Task (was: Patch)
Component: JMS service
(was: Persistence)
Version: JBossAS-4.0.1 Final
JBossAS-3.2.7 Final
(was: JBossAS-3.2.5)
> Need better control over the pm memory usage during destination recovery
> ------------------------------------------------------------------------
>
> Key: JBAS-1336
> URL: http://jira.jboss.com/jira/browse/JBAS-1336
> Project: JBoss Application Server
> Type: Task
> Components: JMS service
> Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
> Reporter: Scott M Stark
> Assignee: Adrian Brock
>
>
> When starting up jboss with a destination with either a large number or very
> large persistent messages, the jdbc pm may run out of memory if the select *
> from the db results in the jdbc driver pulling in all of the records. We need
> to either write the pm with this expectation or allow for some configuration
> to avoid this.
--
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
