[
https://issues.apache.org/jira/browse/QPID-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814402#comment-16814402
]
ASF subversion and git services commented on QPID-8297:
-------------------------------------------------------
Commit 3df0648436ec30e53444c08368828acd2da5b0df in qpid-broker-j's branch
refs/heads/7.1.x from overmeulen
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=3df0648 ]
QPID-8297: [Broker-J][Oracle Message Store] QPID_MESSAGE_CONTENT reserved space
keeps growing
This closes #24
(cherry picked from commit 9eb98551eb923430405e409b239cc52563b32f99)
> [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
> Assignee: Alex Rudyy
> Priority: Critical
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
