activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "pfid (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-156) Client excepction when sending messages
Date Thu, 06 Dec 2007 15:06:27 GMT

    [ https://issues.apache.org/activemq/browse/AMQCPP-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40800
] 

pfid commented on AMQCPP-156:
-----------------------------

yes thats right. but the messages in the example are real short, should be at most 40 characters.
i don't know how much memory the broker needs for a 40byte message, but even 30.000 messages
of those should not block the whole broker app?
plus the problem won't occur when using topics. as described above, i notice a memory usage
going from 41 to 71 after 29000 messsages. when using topics instead of queues with the same
code, the memory usage goes from 41mb to 43mb after 40.000 messages. 

anyway, even if the broker runs out of (ram-)memory, shouldn't it write its  cache to disk/database
somehow and continue working?

> Client excepction when sending messages
> ---------------------------------------
>
>                 Key: AMQCPP-156
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-156
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 2.1.1
>         Environment: redhat 2.4.12
>            Reporter: pfid
>            Assignee: Nathan Mittler
>         Attachments: example.tar.gz
>
>
> Using the example code from the website (only modification: use queues, number of messages
= 20000, only create producer, no consumer. see attached file), i'll get the following error
message:
> No valid response received for command: Begin Class = ActiveMQTextMessage
> Begin Class = ActiveMQMessageBase
>  Value of ackHandler = 0
>  Value of redeliveryCount = 0
>  Value of properties = Begin Class PrimitiveMap:
> map[Integer] = 9
> Begin Class PrimitiveMap:
> Begin Class = Message
>  Value of Message::ID_MESSAGE = 0
>  Value of ProducerId is Below:
> Begin Class = ProducerId
>  Value of ProducerId::ID_PRODUCERID = 123
>  Value of ConnectionId = e41c6cc2-2542-4577-bde0-7011ffd6ea5f
>  Value of Value = 0
>  Value of SessionId = 0
> No Data for Class BaseDataStructure
> End Class = ProducerId
>  Value of Destination is Below:
> Begin Class = ActiveMQQueue
> Begin Class = ActiveMQDestination
>  Value of exclusive = false
>  Value of ordered = false
>  Value of advisory = false
>  Value of orderedTarget = coordinator
>  Value of physicalName = TEST.FOO
>  Value of options = Begin Class activemq::util::Properties:
> End Class activemq::util::Properties:
> No Data for Class BaseDataStructure
> End Class = ActiveMQDestination
> End Class = ActiveMQQueue
>  Value of TransactionId is Below:
>    Object is NULL
>  Value of OriginalDestination is Below:
>    Object is NULL
>  Value of MessageId is Below:
> Begin Class = MessageId
>  Value of MessageId::ID_MESSAGEID = 110
>  Value of ProducerId is Below:
> Begin Class = ProducerId
>  Value of ProducerId::ID_PRODUCERID = 123
>  Value of ConnectionId = e41c6cc2-2542-4577-bde0-7011ffd6ea5f
>  Value of Value = 0
>  Value of SessionId = 0
> No Data for Class BaseDataStructure
> End Class = ProducerId
>  Value of ProducerSequenceId = 9
>  Value of BrokerSequenceId = 0
> No Data for Class BaseDataStructure
> End Class = MessageId
>  Value of OriginalTransactionId is Below:
>    Object is NULL
>  Value of GroupID =
>  Value of GroupSequence = 0
>  Value of CorrelationId =
>  Value of Persistent = 0
>  Value of Expiration = 0
>  Value of Priority = 4
>  Value of ReplyTo is Below:
>    Object is NULL
>  Value of Timestamp = 1195642676866
>  Value of Type =
>  Value of Content[0] = , check broker.
>         FILE: activemq/transport/filters/ResponseCorrelator.cpp, LINE: 146
>         FILE: activemq/transport/filters/ResponseCorrelator.cpp, LINE: 154
>         FILE: activemq/connector/openwire/OpenWireFormatNegotiator.cpp, LINE: 105
>         FILE: activemq/connector/openwire/OpenWireConnector.cpp, LINE: 1370
>         FILE: activemq/connector/openwire/OpenWireConnector.cpp, LINE: 847
>         FILE: activemq/core/ActiveMQSession.cpp, LINE: 675
>         FILE: activemq/core/ActiveMQProducer.cpp, LINE: 194
>         FILE: activemq/core/ActiveMQProducer.cpp, LINE: 149
>         FILE: activemq/core/ActiveMQProducer.cpp, LINE: 108
> i'm using a 4.1.1 broker (re-downloaded, unedited original config files) and activemq-cpp
2.1.1. 
> when running the program for the first time, it will successfully write 20.000 messages
to the queue "TEST.FOO". when starting the program again, the program will stop at message
#9291 with the above mentioned exception error. any further tries of running the program will
fail, no more messages can be send to this queue. at this point, the broker's ram usage increased
from initial 41mb to 71mb. memory leak?
> using topics instead of queues will work without problems, and the broker's ram usage
will barely increase. however this isn't an option, since we need to use queues.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message