qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-8297) [Broker-J][Oracle Message Store] QPID_MESSAGE_CONTENT reserved space keeps growing until it reaches the limit and crashes
Date Mon, 08 Apr 2019 10:45:00 GMT

    [ https://issues.apache.org/jira/browse/QPID-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812330#comment-16812330
] 

ASF GitHub Bot commented on QPID-8297:
--------------------------------------

overmeulen commented on pull request #24: QPID-8297: [Broker-J][Oracle Message Store] QPID_MESSAGE_CONTENT
reserved space keeps growing
URL: https://github.com/apache/qpid-broker-j/pull/24
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> [Broker-J][Oracle Message Store] QPID_MESSAGE_CONTENT reserved space keeps growing until
it reaches the limit and crashes
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-8297
>                 URL: https://issues.apache.org/jira/browse/QPID-8297
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-7.1.0
>            Reporter: Olivier VERMEULEN
>            Priority: Critical
>
> Under a continuous high load, the Oracle message store crashes because the reserved space
for the table QPID_MESSAGE_CONTENT keeps on growing (even if the table itself is empty since
we consume as fast as we produce).
> This only happens for "big" messages (over 4KB) and comes from the way Oracle handles
the LOB types (content column is declared as a BLOB). For LOB values over 4KB Oracle reserves
some space in the table to handle the value but, by default, it won't actually release it
(even if the value is removed) before a few hours.
> So when we have a high load of big messages that lasts a few hours we end up reaching
the max size of the tablespace and the database crashes...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message