Major Hi Matt, I set the max heap to 200mb and with jvm over head it seems to
be resting at 253mb. I just need to see if it stays at that level when I
get in tomorrow. If so it will be a significant improvement. So far it
looks good.
Thanks for keeping on top of it. I will let you know how it looks
tomorrow either way.
Cheers,
Mike Grandy.
Sent from my BlackBerry 10 smartphone on the Rogers network.
*From: *Matt Batterham
*Sent: *Tuesday, November 8, 2016 5:54 PM
*To: *Michael Grandy
*Cc: *Info Queuemetrix; Bill McDermond
*Subject: *Re: Question on Lamaxu windows service
Hi Mike, How did you go?
Matt Batterham
On 8 Nov 2016, at 3:23 PM, Michael Grandy <Michael_Grandy@wsib.on.ca
<Michael_Grandy@wsib.on.ca
>> wrote:
> Thanks Matt, I will give that a try.
> If it is stable at 250MB that should be good.
>
> Regards,
>
> Mike Grandy.
>
> Sent from my BlackBerry 10 smartphone on the Rogers network.
> *From: *Matt Batterham
> *Sent: *Monday, November 7, 2016 11:12 PM
> *To: *Michael Grandy
> *Cc: *Info Queuemetrix; Bill McDermond
> *Subject: *Re: Question on Lamaxu windows service
>
>
> Hi Mike,
>
> Can you please try adding the following Java memory tuning options to
> the wrapper.conf file?
>
> edit the file C:\Program Files
> (x86)\QueueMetrix\LAMAXU\bin\yajsw\conf\wrapper.conf/(if this is the
> location you installed into)
>
> Append the lines below,
> /
>
> wrapper.java.additional.2 = -Xms250M
> wrapper.java.additional.3 = -Xmx250M
>
> This will limit the memory heap usage of Lamaxu to 250Mb. NOTE, you
> can adjust this to what you like however the values for each property
> should be equal. You'll start get out of memory errors if you set it
> too low so set it as high as you can.
>
> I've attached an example file for you.
>
> Matt
>
> On 8/11/2016 1:16 PM, Michael Grandy wrote:
>> Hi Matt, I will need to get that answer from our team here. Let me
>> check and I will get you the answer tomorrow.
>>
>> Regards,
>>
>> Mike Grandy.
>>
>> Sent from my BlackBerry 10 smartphone on the Rogers network.
>> *From: *Matt Batterham
>> *Sent: *Monday, November 7, 2016 6:30 PM
>> *To: *Michael Grandy
>> *Cc: *Info Queuemetrix; Bill McDermond
>> *Subject: *Re: Question on Lamaxu windows service
>>
>>
>> Hi Mike, Do you also have the number of queues? Could I assume 50
>> queues per server?
>>
>> Matt Batterham
>>
>> On 8 Nov 2016, at 1:43 AM, Michael Grandy <Michael_Grandy@wsib.on.ca>
>> wrote:
>>
>>> Hi Matt, we are currently monitoring 10 Queue managers with a total
>>> of 50 combined channels.
>>>
>>> Regards,
>>>
>>> Mike Grandy.
>>>
>>> *From:*Matthew Batterham matt.batterham@queuemetrix.com
>>> Sent: Friday, November 04, 2016 5:06 PM
>>> To: Michael Grandy
>>> Cc: Info Queuemetrix; Bill McDermond
>>> Subject: RE: Question on Lamaxu windows service
>>>
>>> Hi Mike, do you know approx how many queues and channels you have
>>> accross all the queue managers being monitored via Lamaxu? Lamaxu
>>> needs enough permament memory to be able to store the status info
>>> for all objects.
>>>
>>> Does the memory usage go high for a period and then come down? This
>>> behaviour could be caused by the Java garbage collector.
>>>
>>> I'll have a look a see what tuning can be done on the JVM.
>>>
>>> Matt
>>>
>>> Matt Batterham
>>>
>>> www.queuemetrix.com <http://www.queuemetrix.com>
>>>
>>> Queuemetrix Ltd
>>>
>>> -------- Original message --------
>>>
>>> From: Michael Grandy <Michael_Grandy@wsib.on.ca
>>> <Michael_Grandy@wsib.on.ca>>
>>>
>>> Date: 5/11/2016 05:26 (GMT+10:00)
>>>
>>> To: Matt Batterham <matt.batterham@queuemetrix.com
>>> <matt.batterham@queuemetrix.com>>
>>>
>>> Cc: Info Queuemetrix <info@queuemetrix.com
>>> <info@queuemetrix.com>>, Bill McDermond
>>> <flyingace510@yahoo.com <flyingace510@yahoo.com>>
>>>
>>> Subject: RE: Question on Lamaxu windows service
>>>
>>> Hi Matt, I just noticed that the Lamaxu service was consuming 341MB
>>> as opposed to the 180MB that it started with when we first looked at
>>> this. It seems something is building up in memory in a bulk way.
>>> Such as it will stay at 180MB for a good while then shoot up to 340MB
>>>
>>> I have disabled Stats and Events collection so not sure what it is
>>> keeping in memory. I would like to try some additional approaches.
>>>
>>> 1)You mentioned that we could reduce the in memory cache sizes – (I
>>> Would need instruction of how to do this)
>>>
>>> 2)You mentioned there is a web service component. We do not in any
>>> way use the web interface of Lamaxu at this time. Is there a way to
>>> disable this as well? It occurs to me that this could have some
>>> significant overhead.
>>>
>>> Any advice here would be appreciated.
>>>
>>> Thanks a lot.
>>>
>>> Regards,
>>>
>>> Mike Grandy.
>>>
>>> *From:*Matt Batterham matt.batterham@queuemetrix.com
>>> Sent: Tuesday, November 01, 2016 5:20 PM
>>> To: Michael Grandy
>>> Cc: Info Queuemetrix; Bill McDermond
>>> Subject: Re: Question on Lamaxu windows service
>>>
>>> Hi Mike,
>>>
>>> Memory should remain stable without the stats and events as only the
>>> instantaneous status values are stored.
>>>
>>> Thanks for getting back to me.
>>>
>>> Matt Batterham
>>>
>>>
>>> On 2 Nov 2016, at 4:35 AM, Michael Grandy
>>> <Michael_Grandy@wsib.on.ca> wrote:
>>>
>>> Hi Matt, I removed the stat and event collection (Set to False)
>>> in the config.xml for each queue manager. It seems to be a
>>> little better but I need to let it run for a while to see how it
>>> behaves. If it is steady at its current memory usage then it
>>> will be good for us until we can migrate to new server.
>>>
>>> Regards,
>>>
>>> Mike Grandy.
>>>
>>> *From:*Info Queuemetrix info@queuemetrix.com
>>> Sent: Thursday, October 27, 2016 7:24 PM
>>> To: Michael Grandy
>>> Cc: Matt Batterham; Bill McDermond
>>> Subject: Re: Question on Lamaxu windows service
>>>
>>> Hi Mike, in that case it's best you disable statistics and
>>> events in the config.xml if it's not already. We have a new
>>> version that contains a web GUI to assist with updating the
>>> config as well. I'll send you a link to the download.
>>>
>>> The GUI is not completely finished and still in test however the
>>> base Lamaxu functionality is stable.
>>>
>>> Matt Batterham
>>>
>>>
>>> On 27 Oct 2016, at 11:43 PM, Michael Grandy
>>> <Michael_Grandy@wsib.on.ca> wrote:
>>>
>>> Hi Matt, thanks for the quick reply. We are using Lamaxu
>>> exclusively for Solarwinds monitoring. Our Solarwinds
>>> polling of MQ stats is every 5 minutes. We collect a variety
>>> of stats for about 10 queue managers currently and a couple
>>> of additional to be added. The typical stats we poll are as
>>> per the below screen shot:
>>>
>>> <image001.png>
>>>
>>> We do not require Lamaxu to maintain any history as
>>> Solarwinds logs and retains the stats as they are collected.
>>> Solarwinds uses it’s JMX bridge to talk to the Lamaxu
>>> service and no other interface to Lamaxu is required. I am
>>> not sure if this makes sense but is it possible to configure
>>> Lamaxu to only retain the most recent statistic for each stat?
>>>
>>> Please let me know if you need more info.
>>>
>>> Regards,
>>>
>>> Mike Grandy.
>>>
>>> *From:*Matt Batterham matt.batterham@queuemetrix.com
>>> Sent: Wednesday, October 26, 2016 10:20 PM
>>> To: Michael Grandy
>>> Cc: Bill McDermond; info@queuemetrix.com
>>> Subject: Re: Question on Lamaxu windows service
>>>
>>> Hi Mike,
>>>
>>> What features of Lamaxu are you using? I mean do you use the
>>> Web interface at all to view statistics. One thing the could
>>> cause an increase in memory usage is that Lamaxu stores MQ
>>> statistics, in memory, for use with the web service. If
>>> you're not using this feature it would be worth disabling
>>> the statistics collection. You'd need to restart the service
>>> afterwards. We can also look at tuning down the in memory
>>> cache sizes as well to limit their use.
>>>
>>> Also, how many queues in total across all the queue managers
>>> might you have. Ballpark figure is ok.
>>>
>>>
>>> Matt Batterham
>>>
>>>
>>> On 27 Oct 2016, at 5:27 AM, Michael Grandy
>>> <Michael_Grandy@wsib.on.ca
>>> <Michael_Grandy@wsib.on.ca>> wrote:
>>>
>>> Hi Matt, I have a general question on this specifically
>>> dealing with memory consumption. I am seeing that on
>>> average Lamaxu deployed as a windows service uses a
>>> significant amount of memory (Lamaxu Service= approx.
>>> 360MB, Windows Service Wrapper= approx. 30MB).
>>>
>>> Can you let me know if this sounds normal to you and
>>> either way are there any options for reducing this
>>> requirement in any significant way?
>>>
>>> I appreciate any advice you can give.
>>>
>>> Regards,
>>>
>>> **
>>>
>>> Michael Grandy
>>>
>>> Incident Manager | Environments Group
>>>
>>> <image001.jpg>416-802-8195 <image002.jpg> 416-344-3888
>>> *www.wsib.on.ca
>>> <http://www.wsib.on.ca/wsib/wsibsite.nsf/public/homepage>*
>>>
>>> <image003.jpg>
>>>
>>> /<image004.jpg> Please consider the environment before
>>> printing this e-mail./
>>>
>>> *********************************************************************
>>>
>>> The information in this e-mail is intended solely for
>>> the addressee(s) named, and is confidential. Any other
>>> distribution, disclosure or copying is strictly
>>> prohibited. If you have received this communication in
>>> error, please reply by e-mail to the sender and delete
>>> or destroy all copies of this message.
>>>
>>> Les renseignements contenus dans le présent message
>>> électronique sont confidentiels et concernent
>>> exclusivement le(s) destinataire(s) désigné(s). Il est
>>> strictement interdit de distribuer ou de copier ce
>>> message. Si vous avez reçu ce message par erreur,
>>> veuillez répondre par courriel à l'expéditeur et effacer
>>> ou détruire toutes les copies du présent message.
>>>
>>> *********************************************************************
>>>
>>> The information in this e-mail is intended solely for the
>>> addressee(s) named, and is confidential. Any other
>>> distribution, disclosure or copying is strictly prohibited.
>>> If you have received this communication in error, please
>>> reply by e-mail to the sender and delete or destroy all
>>> copies of this message.
>>>
>>> Les renseignements contenus dans le présent message
>>> électronique sont confidentiels et concernent exclusivement
>>> le(s) destinataire(s) désigné(s). Il est strictement
>>> interdit de distribuer ou de copier ce message. Si vous
>>> avez reçu ce message par erreur, veuillez répondre par
>>> courriel à l'expéditeur et effacer ou détruire toutes les
>>> copies du présent message.
>>>
>>> *********************************************************************
>>>
>>> The information in this e-mail is intended solely for the
>>> addressee(s) named, and is confidential. Any other distribution,
>>> disclosure or copying is strictly prohibited. If you have
>>> received this communication in error, please reply by e-mail to
>>> the sender and delete or destroy all copies of this message.
>>>
>>> Les renseignements contenus dans le présent message électronique
>>> sont confidentiels et concernent exclusivement le(s)
>>> destinataire(s) désigné(s). Il est strictement interdit de
>>> distribuer ou de copier ce message. Si vous avez reçu ce message
>>> par erreur, veuillez répondre par courriel à l'expéditeur et
>>> effacer ou détruire toutes les copies du présent message.
>>>
>>> *********************************************************************
>>>
>>> The information in this e-mail is intended solely for the
>>> addressee(s) named, and is confidential. Any other distribution,
>>> disclosure or copying is strictly prohibited. If you have received
>>> this communication in error, please reply by e-mail to the sender
>>> and delete or destroy all copies of this message.
>>>
>>> Les renseignements contenus dans le présent message électronique
>>> sont confidentiels et concernent exclusivement le(s) destinataire(s)
>>> désigné(s). Il est strictement interdit de distribuer ou de copier
>>> ce message. Si vous avez reçu ce message par erreur, veuillez
>>> répondre par courriel à l'expéditeur et effacer ou détruire toutes
>>> les copies du présent message.
>>>
>>> *********************************************************************
>>>
>>> The information in this e-mail is intended solely for the
>>> addressee(s) named, and is confidential. Any other distribution,
>>> disclosure or copying is strictly prohibited. If you have received
>>> this communication in error, please reply by e-mail to the sender
>>> and delete or destroy all copies of this message.
>>>
>>> Les renseignements contenus dans le présent message électronique
>>> sont confidentiels et concernent exclusivement le(s) destinataire(s)
>>> désigné(s). Il est strictement interdit de distribuer ou de copier
>>> ce message. Si vous avez reçu ce message par erreur, veuillez
>>> répondre par courriel à l'expéditeur et effacer ou détruire toutes
>>> les copies du présent message.
>> *********************************************************************
>>
>> The information in this e-mail is intended solely for the
>> addressee(s) named, and is confidential. Any other distribution,
>> disclosure or copying is strictly prohibited. If you have received
>> this communication in error, please reply by e-mail to the sender and
>> delete or destroy all copies of this message.
>>
>> Les renseignements contenus dans le présent message électronique sont
>> confidentiels et concernent exclusivement le(s) destinataire(s)
>> désigné(s). Il est strictement interdit de distribuer ou de copier ce
>> message. Si vous avez reçu ce message par erreur, veuillez répondre
>> par courriel à l'expéditeur et effacer ou détruire toutes les copies
>> du présent message.
>
> *********************************************************************
>
> The information in this e-mail is intended solely for the addressee(s)
> named, and is confidential. Any other distribution, disclosure or
> copying is strictly prohibited. If you have received this
> communication in error, please reply by e-mail to the sender and
> delete or destroy all copies of this message.
>
> Les renseignements contenus dans le présent message électronique sont
> confidentiels et concernent exclusivement le(s) destinataire(s)
> désigné(s). Il est strictement interdit de distribuer ou de copier ce
> message. Si vous avez reçu ce message par erreur, veuillez répondre
> par courriel à l'expéditeur et effacer ou détruire toutes les copies
> du présent message.
*********************************************************************
The information in this e-mail is intended solely for the addressee(s)
named, and is confidential. Any other distribution, disclosure or
copying is strictly prohibited. If you have received this communication
in error, please reply by e-mail to the sender and delete or destroy all
copies of this message.
Les renseignements contenus dans le présent message électronique sont
confidentiels et concernent exclusivement le(s) destinataire(s)
désigné(s). Il est strictement interdit de distribuer ou de copier ce
message. Si vous avez reçu ce message par erreur, veuillez répondre par
courriel à l'expéditeur et effacer ou détruire toutes les copies du
présent message.