| Author |
Message
|
| AkankshA |
 Posted: Sun Sep 17, 2006 9:14 pm Post subject: DFE takes up 100% CPU |
 |
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
Hi All,
DFE of my broker takes up 100% of cpu usage.....
details :: i was testing scenerio when a msg is still there in SYSTEM.BROKER.TIMEOUT.QUEUE and the broker goes down... in such a case the broker was forced to go down and later when i tried to get it up.. DFE is taking up 100% cpu usage...
I even tried creating a new cmgr and broker but facing the same error...
i am left with no options
Any inputs
Thanks
Akanksha |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Sun Sep 17, 2006 9:46 pm Post subject: Re: DFE takes up 100% CPU |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Akanksha,
| Akanksha wrote: |
DFE of my broker takes up 100% of cpu usage.....
details :: i was testing scenerio when a msg is still there in SYSTEM.BROKER.TIMEOUT.QUEUE and the broker goes down... in such a case the broker was forced to go down and later when i tried to get it up.. DFE is taking up 100% cpu usage... |
Most probably the logic in the flow is making it go into an infinite loop....
Can you tell us what you are trying to do in the flow...and if you have any while loops or so...
Regards. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Sun Sep 17, 2006 9:53 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
no while loop in the flow as such... i was putting a msg to time out node to send it back to me at a later time
However my major concern out here is that when i have created everything afresh(including config manager) even then my dfe(which is newly creted) is taking 100% cpu. |
|
| Back to top |
|
|
| jbanoop |
| Posted: Sun Sep 17, 2006 9:55 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
did not quite understand the scenario that cuse the error. however als elvis_gn said, it has something to do with infinite loop within your message flow code.
clear/inhibit all input queues, kill the dfe and you should be fine.
Regards,
Anoop |
|
| Back to top |
|
|
| supreeth |
| Posted: Sun Sep 17, 2006 10:01 pm Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Hi Akanksha,
Which version of MB are u using. I have never come across this SYSTEM.BROKER.TIMEOUT.QUEUE. what does tis queue do... i mean wen wud a message be put on tis queue.
please note ... a good explanation of the problem ... faster response ... early resolution.
cheerz!!!
supreeth
_________________
Supreeth Gururaj
IBM Certified WMQ Solution Expert |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sun Sep 17, 2006 10:02 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Akanksha,
| Akanksha wrote: |
| However my major concern out here is that when i have created everything afresh(including config manager) even then my dfe(which is newly creted) is taking 100% cpu. |
That only proves that the problem is not with the broker or the configMgr....
Run a broker trace...or look at the user.log.
Regards. |
|
| Back to top |
|
|
| jbanoop |
| Posted: Sun Sep 17, 2006 10:19 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
I think the SYSTEM.BROKER.TIMEOUT.QUEUE is used by the timer (timeout) nodes of version 6 which Akanksha is using. He is apparently trying to use it trigger message flows at particular times using a combination of timeout control and timeout notification nodes.
Did u check the timeout interval of the timeout notification node to see if you are triggering it far too fast ?
Honestly I have not worked with timeout nodes too much but a better explaination of the exact scenario might help.
Regards,
Anoop |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Sep 18, 2006 2:47 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| i was putting a msg to time out node to send it back to me at a later time |
Which TimeOut node? Notify or Control? I hope you're not trying to write a message to SYSTEM.BROKER.TIMEOUT.QUEUE directly.
Tell use exactly how your flow is constructed ....
_________________
-wayne |
|
| Back to top |
|
|
| supreeth |
| Posted: Mon Sep 18, 2006 3:03 am Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Hi Wayne,
Was going thro the paper put in by you in the IBM site on the usage of the timeout node(s). very informative and descriptive one.
http://www-128.ibm.com/developerworks/websphere/library/techarticles/0603_schutz/0603_schutz.html#N10296
In one of the posts in this forum, there was a mention of the message format in the queue not documented. Din quite actually get it. wont the message in this queue be in the following format?
| Code: |
<TimeoutRequest> <Action>SET | CANCEL</Action> <Identifier>String (any alphanumeric string)</Identifier> <StartDate>String (TODAY | yyyy-mm-dd)</StartDate> <StartTime>String (NOW | hh:mm:ss)</StartTime> <Interval>Integer (seconds)</Interval> <Count>Integer (greater than 0 or -1)</Count> <IgnoreMissed>TRUE | FALSE</IgnoreMissed> <AllowOverwrite>TRUE | FALSE</AllowOverwrite> </TimeoutRequest>
|
Correct me if i am wrong. Couldnt we directly construct a message in the above format and put on the TIMEOUT queue ? I happened to read somewhere that we can even point at a particular correlation in the message which contains the TimeoutRequest body.
cheerz!!!
supreeth
_________________
Supreeth Gururaj
IBM Certified WMQ Solution Expert |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Sep 18, 2006 3:37 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
No, the message in that queue is NOT in that format.... the format of the message is proprietary, and even the fact that the timeout requests are held in that queue is undocumented. (This gives the lab the flexibility to implement the nodes differently in the future). So.... you should never be putting a message directly to that queue... sorry.
_________________
-wayne |
|
| Back to top |
|
|
| supreeth |
| Posted: Mon Sep 18, 2006 3:54 am Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Yes, I happened to notice that even the functionality of the queue is not documented. Explanation for it sounds quite logical. Thanks Wayne
cheerz!!!
supreeth
_________________
Supreeth Gururaj
IBM Certified WMQ Solution Expert |
|
| Back to top |
|
|
|
|
