Thank you for the additional information. If you only have 910MB ram available for the JVM heap size than a memoryUsage of 680MB would be appropriate. Setting the prefetch memoryLimit to 100MB would be reasonable.
This all being said, perhaps you could update your broker to a more recent version? http://activemq.apache.org/download.html The configuration of the latest broker is mostly the same, however the memoryUsage is set as a percentage. If possible, please increase your JVM heap size to something larger (4GB to 8GB would be great if you have the available ram). With the above memory concerns addressed, now you can start in on the client side issue of priorities. There is documentation on Broker priority queues here: http://activemq.apache.org/how-can-i-support-priority-queues.html Consumer priority documentation here: http://activemq.apache.org/consumer-priority.html Cheers, Jamie On Mon, Oct 12, 2015 at 3:04 PM, AnnaKuranda <[email protected]> wrote: > Hi, > Thanks for the answer. > My jvm 910mb > Activemq version 5.8.0 > Run on windows vm > Use java 7 - jdk1.7.0_55-64bit > Jms client org.springframework.jms.core.JmsTemplate > > According to your mail should change > If my jvm 910 mb the proper configuration should be like: > memoryLimit=100 > memoryUsage limit=600 mb ? > > Thanks > Anna > > From: jgoodyear [via ActiveMQ] > [mailto:[email protected]] > Sent: יום ב, 12 אוקטובר 2015 19:23 > To: Anna Kuranda > Subject: Re: When send to Q big amount of prioritrized messages they done by > wrong priority on consumer side. > > Hi, > > A couple of questions, and a few configuration notes. > > Which version of ActiveMQ, Java, host platform, and type of JMS client? > > Configuration notes: > > The brokers' memory configuration is 3900 MB, this suggests that you > should have a JVM heap size of ~5250 MB set (As a rule of thumb you'll > want 70 to 75% of memory available to the Broker, with the remainder > for house keeping - you can pass the Xmx setting via the activemq.sh > or wrapper.conf). > > The memoryLimit set on myQueue is larger than the available memory to > the broker (see MemoryUsage). This being said, setting PFC will stem > the flow of messages into myQueue until consumers can reduce its size. > If PFC is engaged than you'll want to increase your consumer speed, > and/or quantity. You may also want to review your message payload size > (best to pass along a URI to a resource instead of passing around > multi-megabyte messages). > > Depending on your version of ActiveMQ, you may want to experiment with > using the NIO transport instead of TCP. > > Hope the above helps. > > Cheers, > Jamie > > On Mon, Oct 12, 2015 at 5:04 AM, AnnaKuranda <[hidden > email]</user/SendEmail.jtp?type=node&node=4702841&i=0>> wrote: > >> When send to Q big amount of prioritrized messages they done by wrong >> priority on consumer side. >> >> * The issue not happen when in Q about 60-100 sent messages.Used >> activemq.xml for Q configuration.Tried to increase cache and disk size , but >> looks like it not help >> If you have any idea how to solve this bug ,please let me know >> Defined : >> >> <policyEntry queue="MyQueue" producerFlowControl="true" >> memoryLimit="4096mb" >> prioritizedMessages="true" >> queuePrefetch="1" >> useCache="false" expireMessagesPeriod="0" >> strictOrderDispatch="true"> >> <pendingQueuePolicy> >> <vmQueueCursor/> >> </pendingQueuePolicy> >> </policyEntry> >> >> <persistenceAdapter> >> <kahaDB directory="${activemq.data}/kahadb" >> ignoreMissingJournalfiles="true" >> checkForCorruptJournalFiles="true" >> checksumJournalFiles="true"/> >> </persistenceAdapter> >> >> <systemUsage> >> <systemUsage> >> <memoryUsage> >> <memoryUsage limit="3900 mb"/> >> </memoryUsage> >> <storeUsage> >> <storeUsage limit="25 gb"/> >> </storeUsage> >> <tempUsage> >> <tempUsage limit="0 mb"/> >> </tempUsage> >> </systemUsage> >> </systemUsage> >> >> http://activemq.apache.org/configuring-transports.html >> --> >> <transportConnectors> >> >> <transportConnector name="openwire" >> uri="tcp://0.0.0.0:1414?maximumConnections=1000&wireformat.maxFrameSize=104857600"/> >> </transportConnectors> >> >> >> <shutdownHooks> >> <bean xmlns="http://www.springframework.org/schema/beans"; >> class="org.apache.activemq.hooks.SpringContextHook" /> >> </shutdownHooks> >> >> </broker> >> >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/When-send-to-Q-big-amount-of-prioritrized-messages-they-done-by-wrong-priority-on-consumer-side-tp4702831.html >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > http://activemq.2283324.n4.nabble.com/When-send-to-Q-big-amount-of-prioritrized-messages-they-done-by-wrong-priority-on-consumer-side-tp4702831p4702841.html > To unsubscribe from When send to Q big amount of prioritrized messages they > done by wrong priority on consumer side., click > here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4702831&code=QW5uYS5LdXJhbmRhQG5pY2UuY29tfDQ3MDI4MzF8LTY0NTM4MTY0OA==>. > NAML<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/When-send-to-Q-big-amount-of-prioritrized-messages-they-done-by-wrong-priority-on-consumer-side-tp4702831p4702850.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
