| Author |
Message
|
| abcnil |
 Posted: Mon Jan 23, 2017 1:34 am Post subject: IIB9 - Collector Node Issue |
 |
|
Apprentice
Joined: 29 Mar 2012
Posts: 36
|
Version - IIB 9002
This how flow is:
SOAP Input > Call 4 internal Services over SOAP JMS > Collector Node
We call 4 different services and collect the responses in Collector and process it further.
Collector node has its configuration service + queues so using different queue than bydefault system queue.
Message Flow instances are 20
Problem:
While doing load testing if we set 5 threads in 1 second. flow works fine.
If we increase it to 6 or more Threads, collector node can not process messages. I can see messages piled up in Collector and Event queues.
Message keep stuck on queue even though expiry is handled properly [Tested separately for expiry cases]
and its start throwing this error on sys logs:
IBM Integration Bus v9002 (IBD01.ISD01) [Thread 8763] (Msg 2/2) BIP2112E: Message broker internal error: diagnostic information 'SYSTEM.BROKER.EDA.CUSTDATA.COLLECTIONS', '2033'.
No new requests get processed until we clean up the queue manually. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Jan 23, 2017 4:51 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I'd raise a PMR. IMHO, there is something deep down inside the product that is getting its knickers in a twist.
_________________
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 |
|
|
| zpat |
| Posted: Mon Jan 23, 2017 5:40 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Apply IIB 9.0.0.6 fixpack and re-test.
I have seen some APARs on the collector node.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| abcnil |
| Posted: Mon Jan 23, 2017 8:34 pm Post subject: |
|
|
Apprentice
Joined: 29 Mar 2012
Posts: 36
|
| Thanks Guys, I will check with latest pack and see how it goes |
|
| Back to top |
|
|
| abcnil |
| Posted: Fri Jan 27, 2017 6:23 am Post subject: |
|
|
Apprentice
Joined: 29 Mar 2012
Posts: 36
|
| Workaround - Do not add additional instances if you have Collector Node in your flow |
|
| Back to top |
|
|
|
|
