[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1359) JBM is not able to work with MSSQL

Tue Jun 10 21:44:16 EDT 2008

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1359?page=comments#action_12416378 ] 

Len DiMaggio commented on JBMESSAGING-1359:
-------------------------------------------

Adding a piece of an email from Martin - providing background on the test and problem:

JBM_MSG table is used just as a persistent storage of undelivered 
messages. Once the message is delivered, it is removed from the table. It 
behaves like queue in fact. After sending 500,000 there are around 5,000 
messages in that table and the table takes over 2GB. How many KB the table 
takes can be easily revealed by this script: 
http://www.databasejournal.com/scripts/article.php/1450801

Oracle doesn't grow in size, but slows down. This "could" be the same problem.

> JBM is not able to work with MSSQL
> ----------------------------------
>
>                 Key: JBMESSAGING-1359
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1359
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core Persistence
>    Affects Versions: 1.4.0.SP3.CP02
>         Environment: SOA-P 4.2 CP02, RHEL5, MSSQL
>            Reporter: Martin Vecera
>         Assigned To: Tim Fox
>            Priority: Critical
>         Attachments: dbstat.csv.gz, jbm_msg.csv.gz, soaesb1_dbstat.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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira