| Author |
Message
|
| Deeksha |
 Posted: Mon May 23, 2011 11:34 pm Post subject: How to remove phantom or duplicate message flows? |
 |
|
Newbie
Joined: 23 May 2011
Posts: 4
|
A EG in solaris environment has around 45 message flows and hence it is very difficult to remove all of them completely and redeploy to get rid of duplicate message flows.
The problem with the duplicate message flow is that it has a old version functionality and hence incoming http messages get randomly processed by the old duplicate flow as well.
Not sure how it got created!
Any ways to identify the RESOURCETYPE,RESOURCENAME of duplicate flows so that corresponding row can be removed from BROKERRESOURCES TABLE?
Any other suggestions to remove this rogue message flow? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue May 24, 2011 2:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
presumably you're at 6.1, or perhaps 6.0...
this shouldn't be possible in v7.
It should be entirely possible and easy to redeploy your 45 message flows - you should have the current BAR files under change control somewhere and be able to retrieve them as needed?
If the difficulty is finding the time to schedule an outage of the flows... there's no reason to do that, either. Just create a NEW EG and deploy all the flows there. Then delete the other EG. |
|
| Back to top |
|
|
| Deeksha |
| Posted: Tue May 24, 2011 3:34 am Post subject: |
|
|
Newbie
Joined: 23 May 2011
Posts: 4
|
Broker version is 6.0.0.9.
I can get the message flows path from MB toolkit. Not an issue.
But it is not that easy to fix this if it happens in production environment.
Any possible workarounds to fix this? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 24, 2011 4:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Deeksha wrote: |
| Broker version is 6.0.0.9. |
Do you know how old & out of support that is? It's even 2 levels behind the most recent 6.0.
| Deeksha wrote: |
| I can get the message flows path from MB toolkit. Not an issue. |
My most worthy associate was talking about the BAR files. Unless you're utterly confident the source you have matches the production flows.
| Deeksha wrote: |
| But it is not that easy to fix this if it happens in production environment |
Yes it is. Create a new EG as my most worthy associate suggests and take an outage to switch them over. When management whines that you can't have an outage in production, point out that if they'd allowed enough downtime for you to keep up to date on software versions previously, you'd be using v7 & wouldn't be having this problem.
Any possible workarounds to fix this?[/quote]
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Deeksha |
| Posted: Tue May 24, 2011 4:12 am Post subject: |
|
|
Newbie
Joined: 23 May 2011
Posts: 4
|
I agree that recreation is not an impossible thing.
As 6.0 is out of support, We are in the process of MB version upgrade.
I have posted this issue to know if this could be sorted out by any other means to avert lot of manual efforts. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue May 24, 2011 4:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The mqsibrowse command will show you the relevant tables in a readable form, and should allow you to find what you're looking for.
But again, creating a new EG with all the correct flows and starting that FIRST means that you don't actually have to have an 'outage' when you remove the OLD eg. You temporarily have, actually, a greater capacity than before - in that there are now at least 2 instances of every flow rather than 1. And at no point do you have any flows that have 0 instances running. |
|
| Back to top |
|
|
| Deeksha |
| Posted: Tue May 24, 2011 9:13 pm Post subject: |
|
|
Newbie
Joined: 23 May 2011
Posts: 4
|
|
| Back to top |
|
|
|
|
