Author |
Message
|
nelson |
Posted: Wed Nov 11, 2015 4:51 am Post subject: Identify message flow instance thread |
|
|
 Partisan
Joined: 02 Oct 2012 Posts: 313
|
Hi All,
Is there a way to identify which message flow instance is processing a message?
Any inputs are very appreciated. |
|
Back to top |
|
 |
nelson |
Posted: Wed Nov 11, 2015 4:52 am Post subject: |
|
|
 Partisan
Joined: 02 Oct 2012 Posts: 313
|
Posted to the wrong section...  |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Nov 11, 2015 5:32 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Moved _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Nov 11, 2015 4:55 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
AFAIK Java will allow you to access the current thread and get some information from it. Don't think you can do that with esql  _________________ MQ & Broker admin |
|
Back to top |
|
 |
timber |
Posted: Thu Nov 12, 2015 2:37 am Post subject: |
|
|
 Grand Master
Joined: 25 Aug 2015 Posts: 1292
|
Monitoring events contain the thread id of the message flow instance that emitted the event. |
|
Back to top |
|
 |
inMo |
Posted: Wed Nov 18, 2015 6:33 am Post subject: |
|
|
 Master
Joined: 27 Jun 2009 Posts: 216 Location: NY
|
From a slightly different perspective, is there anyway to see the total number of threads in use for a specific flow? Rather then looking for a specific active thread, I'd like to see all currently active threads. If total allowed is 20, I'd like to know if n are currently being used. |
|
Back to top |
|
 |
smdavies99 |
Posted: Wed Nov 18, 2015 8:05 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Why do you need to know this sort of detail? Some of us have worked with the product for well over 10 years and never felt the need to aquire this data. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Nov 18, 2015 8:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Message flow statistics should show you this. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
inMo |
Posted: Wed Nov 18, 2015 8:28 am Post subject: |
|
|
 Master
Joined: 27 Jun 2009 Posts: 216 Location: NY
|
smdavies99 wrote: |
Some of us have worked with the product for well over 10 years and never felt the need to aquire this data. |
Yes. I'm one of them, until now. We are simply trying to do some modeling where we want to purposefully allocate threads today and use that allocation to predict/estimate growth tomorrow. A great starting point would be our current actual usage vs. our current allowed. (A lot of the allowed seems to be randomly assigned rounded numbers) If a developer allowed additional 100 but the flow only really ever uses 5, and stress tests cause it to spike to 9, I'd rather not account for 100.
I'm all ears if you have differing opinions. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Nov 18, 2015 9:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
The one thing to remember is that additional instances are only used when they're needed.
So if your stress testing only ever goes up to nine instance/threads, then you would likely never seem more than 20 of those 100 active ever. And even then, under extreme circumstances.
So in terms of allocation of resources, you only have to worry about high numbers of additional instances when something is behaving very very very badly. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
inMo |
Posted: Wed Nov 18, 2015 11:20 am Post subject: |
|
|
 Master
Joined: 27 Jun 2009 Posts: 216 Location: NY
|
mqjeff wrote: |
So if your stress testing only ever goes up to nine instance/threads, then you would likely never seem more than 20 of those 100 active ever. |
Exactly. So we just want to run a normal load test against a specific flow and observe/capture threads used, do the same for a stress test vs. assuming that 100 is an accurate, well thought out number.
The underlying assumption is that adding threads at will to an EG will eventually reach a number that causes a problem. If the upper threshold is not ever a concern, then we don't really have too much to worry about. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Nov 18, 2015 12:00 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
There is an upper limit - it's constrained by all of the same rules as any other multi threaded environment. Just remember that EGs use more memory - and flows use more memory - than something like a Java app might.
And remember to count the total number of additional instances across all flows in all EGs on a given machine.
There are good numbers in the perf reports...
Again, I believe you can get the data you want from accounting/statistics. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
|