[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1359) MSSQL not cleaning deleted rows from JBM_MSG table, not reclaiming disk space

[Tim Fox (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Fox updated JBMESSAGING-1359:
---------------------------------

    Fix Version/s: 1.4.1.GA


> MSSQL not cleaning deleted rows from JBM_MSG table, not reclaiming disk space
> -----------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1359
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1359
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.SP3.CP02
>         Environment: SOA-P 4.2 CP02, RHEL5, MSSQL
>            Reporter: Martin Vecera
>            Assignee: Tim Fox
>             Fix For:  1.4.0.SP3.CP04, 1.4.1.GA
>
>         Attachments: dbstat.csv.gz, jbm_msg.csv.gz, soaesb1_dbstat.sql.gz, soaesb1_perf.sql.gz
>
>
> Reproducible: 100%
> Description: There is something that prevents MSSQL to clean deleted rows from JBM_MSG table and the disk space occupied by that table grows permanently.
> I had HelloWorld ESB service listening on JMS queue. I was constantly sending messages to that queue. JBM_MSG table contains around 1000 in average - this is balanced between sender and receiver. Consumer consumes old messages, new messages are still arriving.
> Every message has 5kB.
> The DB grows in size during this procedure until it takes the whole disk space and make the DB unusable for JBM.
> Evidence - attached files:
> dbstat.csv - status report for all the tables in DB - see RowCount, DataSpace for JBM_MSG
> jbm_msg.csv - content of JBM_MSG table when status report was generated
> soaesb1_dbstat.sql - SQL script for generating status report
> Caution: MSSQL is required in SOA-P PRD. If this cannot be solved, the requirement should be removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira