ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » [solved] XMLNSC types

Post new topic  Reply to topic
 [solved] XMLNSC types « View previous topic :: View next topic » 
Author Message
Esa
PostPosted: Thu Mar 12, 2015 6:10 am    Post subject: [solved] XMLNSC types Reply with quote

Grand Master

Joined: 22 May 2008
Posts: 1387
Location: Finland

What is the difference between these two trace file entries:

Code:
(0x01000000:Folder)http://a:b = ( ['xmlnsc' : 0x7fd28477f200]


Code:
(0x01000000:Folder)http://a:b = ( ['xmlnsc' : 0x7fd284737a50]



I cannot find these XMLNSC type codes in the documentation.


Last edited by Esa on Thu Mar 12, 2015 6:59 am; edited 1 time in total
Back to top
View user's profile Send private message
Esa
PostPosted: Thu Mar 12, 2015 6:15 am    Post subject: Reply with quote

Grand Master

Joined: 22 May 2008
Posts: 1387
Location: Finland

Not type codes but runtime object id's?
Back to top
View user's profile Send private message
mgk
PostPosted: Thu Mar 12, 2015 7:11 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

Quote:
Not type codes but runtime object id's?


Correct. This allows you to determine which parts of the tree are owned by the same (or different) parsers even when the parser name is the same, but the parser instances may not be. To put it another way, we output the parser name (and id) in a trace node when the element is owned by a different parser to it's parent - even if that parser has the same name, the id can be different. This allows you to catch parser "overuse" where you create elements in a loop, all with new parsers for example which is unnecessary and very inefficient. Of course, ResourceStats for parsers will also show you the number of parsers created, but not their ids.

I hope this has made things clearer

Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » [solved] XMLNSC types
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.