| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Mapping Problems after Upgrading to WMB 7.0.0.6 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Frik |
 Posted: Tue Jun 17, 2014 1:38 pm Post subject: Mapping Problems after Upgrading to WMB 7.0.0.6 |
 |
|
Acolyte
Joined: 25 Nov 2009
Posts: 69
|
Hello,
We have upgraded the WMB version (on AIX) today from 7.0.0.4 to 7.0.0.6.
After upgrading it seems that all the Mapping node have a great problem:
every field that is mapped suddenly became of type CHAR(!!!), even its type is "int" or "short" in the MRM!
I even tried to cast it (although the source and the target fields are of type "xs:int") to int' but nothing!
WTF?!
Is it a known problem?
Is there a way to downgrade?! |
|
| Back to top |
|
 |
| Frik |
| Posted: Tue Jun 17, 2014 8:56 pm Post subject: Re: Mapping Problems after Upgrading to WMB 7.0.0.6 |
|
|
Acolyte
Joined: 25 Nov 2009
Posts: 69
|
| Frik wrote: |
Hello,
We have upgraded the WMB version (on AIX) today from 7.0.0.4 to 7.0.0.6.
After upgrading it seems that all the Mapping node have a great problem:
every field that is mapped suddenly became of type CHAR(!!!), even its type is "int" or "short" in the MRM!
I even tried to cast it (although the source and the target fields are of type "xs:int") to int' but nothing!
WTF?!
Is it a known problem?
Is there a way to downgrade?! |
Seems that is not the fix, but something else - The parsing of XMLNSC.
Still weird |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jun 18, 2014 2:36 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I suggest that you diagnose the problem before posting again.
First, find out where the *first* difference in behaviour occurs.
Secondly, check that you have not made a mistake, and caused the change accidentally while migrating.
Only then should you post and ask for help here. And when you do, please provide a lot more information. Sentences like 'Seems that is not the fix, but something else - The parsing of XMLNSC. Still weird' belong on your Twitter feed, not on this forum.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| Frik |
| Posted: Wed Jun 18, 2014 2:54 am Post subject: |
|
|
Acolyte
Joined: 25 Nov 2009
Posts: 69
|
| kimbert wrote: |
I suggest that you diagnose the problem before posting again.
First, find out where the *first* difference in behaviour occurs.
Secondly, check that you have not made a mistake, and caused the change accidentally while migrating.
Only then should you post and ask for help here. And when you do, please provide a lot more information. Sentences like 'Seems that is not the fix, but something else - The parsing of XMLNSC. Still weird' belong on your Twitter feed, not on this forum. |
Allright.
If then, I would open a twitter account just for phrames like this:
- "Seems that is not the fix, but something else - The parsing of XMLNSC. Still weird"
- "Mapping on WMB7 can't count children of Root element LOLz!!!"
- "My broker just had an upgrade and all I got is this lousy post"
- "got an WMB error: "CWF mismatch Message is too large, well... Thats what she said!!!" |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 18, 2014 4:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Frik wrote: |
| If then, I would open a twitter account just for phrames like this |
Be sure and post the details so we can all follow you and tweet helpful suggestions. Some of them technical (or at least medical).
In terms of getting help here with your problem, then try actually providing details (in sentances) describing what's going on, the change of behaviour and why you think it should work. One of the changes with all the WMBv7 fix packs is that as part of the improvement process things which shouldn't really have been allowed but squeeked through on earlier version are fixed even through they're not "defects"; or sometimes as a consequence of other fixes.
Bleating half formed sentances and abbreviations that "it doesn't work and it's just not fair!" are not going to yield much progress.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jun 18, 2014 2:43 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
OK - I apologize for that reply. It was not helpful and it was not respectful. I do understand that you are probably in the middle of a difficult migration, and this error is the last thing that you need.
The thing is, I really wanted to help. But I was not able to help based on the information that was provided. I know that there is a setting on the XMLNSC parser that controls whether the types in the xsd are actually used when building the message tree. Maybe that setting got accidentally changed during the migration? But I think it is unlikely that the migration has corrupted that setting ( it has been in the product since v6.1 ).
Bottom line: We still want to help. If you still want help, you will need to provide accurate info about your problem.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
