[
https://issues.apache.org/jira/browse/ARTEMIS-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700978#comment-16700978
]
Justin Bertram commented on ARTEMIS-2185:
-----------------------------------------
[~jschmied], can you elaborate on the use-case where this is seen? In general
connections should live awhile and not be opened/closed frequently. If your
application is closing 200 connections that's almost certainly an anti-pattern.
The stack-trace in the attached screenshot indicates you're using an in-vm
connection which would almost never need to be closed (since it doesn't have to
deal with network problems).
> High allocation pressure due to pre generated ActiveMQExceptionMessage
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-2185
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2185
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.6.3
> Reporter: juergen schmied
> Priority: Minor
> Labels: ChannelImpl, Memory, collection, garbage
> Attachments: tempsnip.png
>
>
> In org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl there is
> {code:java}
> public void returnBlocking(Throwable cause) {
> lock.lock();
> try {
> response = new
> ActiveMQExceptionMessage(ActiveMQClientMessageBundle.BUNDLE.unblockingACall(cause));
> sendCondition.signal();
> } finally {
> lock.unlock();
> }
> }
> {code}
> The response is created but not used normally.
> For every get/close connection there is the a ActiveMQExceptionMessage incl.
> stacktrace created and abandoned.
> This shows a high allocation pressure in jmc (8 MB garbage/200 calls).
> please don't precreate the unused exception (maybe use a producer producing
> exception when really needed)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
