| Author |
Message
|
| m.schneider |
 Posted: Tue Sep 02, 2008 8:02 am Post subject: Issue with MCD by migration from 6.0 to 6.1 |
 |
|
Centurion
Joined: 10 Apr 2007
Posts: 132
Location: Germany
|
Hi,
I'm testing a migration from 6.0 to 6.1. I have some flows that work under 6.0 but not with 6.1. It seems like 6.1 always fills the MCD that overwrites the settings in my inputnodes.
In one node I used the blob input parser, because I didn't know what kind of messages would arrive. Now they arrive as MRM or other types, this results in an error with the following process where I use ASBITSTREAM on the inputbody, ...
The other problem is an input node which has a parser, msgset, ... defined but receives an empty MCD and doesn't get recognized like before, ...
Has anyone simular problems? Is there an option to ignore the MCD?
Thanks for the help! |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Sep 03, 2008 12:43 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Just checking that I understand the problem; you are receiving messages from a v6.1 message flow, and getting the mcd folder populated unexpectedly? |
|
| Back to top |
|
|
| m.schneider |
| Posted: Wed Sep 03, 2008 1:47 am Post subject: |
|
|
Centurion
Joined: 10 Apr 2007
Posts: 132
Location: Germany
|
Yes.
Even if I set the MCD to null within the computenode, in the outgoing message it appears again. |
|
| Back to top |
|
|
| missing_link |
| Posted: Fri Sep 12, 2008 1:44 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 60
|
hmmm....we seem to seeing this as well. it looks like that if you have an MQRFH2 on the message the broker sets the mcd and the domain. this of course overrides anything thats set on the mqinput of a receiving flow.
main impact for us is on some routing flows, but it appears that if you clear the domain on that inputnode (the routing flow doesnt use the message body at all) then although the output msg still has the mcd set it doesn't set the domain and doesnt impact the receiving flow.
of course, it proabably doesn't help if you need access to the message body in your flow 
ash. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Sep 12, 2008 2:40 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
There was a defect fix for IY94881 which may be causing thes symptoms.
If it is causing you a problem you can revert to the previous behaviour by setting environment variable MQSI_DISABLE_CREATE_RFH2_MCD ( value can be anything you like ). |
|
| Back to top |
|
|
| missing_link |
| Posted: Mon Sep 15, 2008 1:02 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 60
|
| What did IY94881 fix? Was this raised because of the mcd getting set in the rfh? |
|
| Back to top |
|
|
| m.schneider |
| Posted: Mon Sep 15, 2008 1:39 am Post subject: |
|
|
Centurion
Joined: 10 Apr 2007
Posts: 132
Location: Germany
|
|
| Back to top |
|
|
| missing_link |
| Posted: Mon Sep 15, 2008 1:53 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 60
|
Ah...at least it's in the doc's..but its still an annoying (for us) change in behaviour.
More testing.....! |
|
| Back to top |
|
|
| missing_link |
| Posted: Thu Sep 18, 2008 5:00 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 60
|
Is that MQSI_DISABLE_CREATE_RFH2_MCD env var spelt correctly? Just tried that and i still seem to get the mcd in my rfh.
running broker 6101.
thanks. |
|
| Back to top |
|
|
|
|
