Hi ,
 
Thanks.

The FAQ does say that 

"The same rules apply to Xerces-C++ DOM documents. Multiple document
instances may be concurrently accessed from different threads, but any given
document instance can only be accessed by one thread at a time"

Does that mean that even though we can pass DOM Documents between threads, 
two threads must not access them at the same time ?

That would mean that on a Single processor system the two threads would be
able to access a document (since they can never do so at the same instance)
but on a Multiprocessor System it would fail. 

Please let me know if my Inference is correct ??

Ram

********************************************
Ramkumar Iyer
Technical Architect
Wipro Technologies (T & I)
ESN���� : 6-872-8025
Tel(O)��: +91-(0)80-5538301 extn 2319
Tel(M)� : 9845195686
Mail����� : [EMAIL PROTECTED]
*********************************************
If the path be beautiful, let us not ask 
where it leads.
�


-----Original Message-----
From: Gareth Reakes [mailto:gareth@;decisionsoft.com] 
Sent: Tuesday, November 12, 2002 2:46 PM
To: [EMAIL PROTECTED]
Cc: Prasanna Kumar
Subject: Re: Application Crashes on Multiprocessor Environment

Hi,
        you cannot use multiple threads in 1 document. Check out the FAQ.

Gareth


On Tue, 12 Nov 2002, Ramkumar Iyer wrote:

> Hi All,
> 
>          
> 
> We are using Xerces 1-3 for our multithreaded application. Basically
> multiple threads are started by our application and DOM_Nodes are being
> passed from one thread to another. When we ran the application on
> Single-Processor system it works without errors.
> 
>  
> 
>  However we are seing infrequent crashes like "Bad Reference Counter" when
a
> DOM_Node is going out of scope.
> 
>  I have a couple of questions 
> 
>  
> 
> *        Is there something we need to specifically handle in our
> application vis-�-vis Xerces for this error ? 
> 
>                 (We are calling initialising the Xerces library only
once).
> 
>  
> 
> *        Is it possible that this error is non Xerces related ie due to
some
> other memory corruption ?
> 
>  
> 
> A sample trace
> 
> =>[1] ParentNode::removeChild(0x186de8, 0x1f2d18, 0xfee14364, 0x186de8,
> 0x1f2d18, 0x28), at 0xfedb880c
> 
>   [2] NodeImpl::deleteIf(0x0, 0x1f2d18, 0x186de8, 0x186740, 0x2b,
0x186778),
> at 0xfedb53e4
> 
>   [3] NamedNodeMapImpl::removeAll(0x200b38, 0x186de8, 0x1, 0x200b38,
0x7200,
> 0xfe2dceaf), at 0xfedb38a8
> 
>   [4] ElementImpl::~ElementImpl(0x186c50, 0x0, 0x9, 0xfe2dceb0,
0xfd20b5f0,
> 0x4), at 0xfedade58
> 
>   [5] __SLIP.DELETER__B(0x186c50, 0x1, 0x186c50, 0x157bc0, 0x186c50,
> 0xfe2dc3e4), at 0xfedaf524
> 
>   [6] NodeImpl::deleteIf(0x186ef0, 0x186c50, 0x157bc0, 0x2043c0, 0x157bc0,
> 0x1faed0), at 0xfedb53fc
> 
>   [7] NodeImpl::deleteIf(0x0, 0x157bc0, 0x2043c0, 0xc4f68, 0x2043c0,
> 0x5f5f0000), at 0xfedb53fc
> 
>   [8] NodeImpl::deleteIf(0x20aa90, 0x2043c0, 0xc4f68, 0x187390, 0xc4f68,
> 0xaa718), at 0xfedb53fc
> 
>   [9] NodeImpl::deleteIf(0x0, 0xc4f68, 0x187390, 0x2102c8, 0x187390,
> 0xfd20b5f0), at 0xfedb53fc
> 
>   [10] NodeImpl::deleteIf(0x0, 0x187390, 0x2102c8, 0xff1b801c, 0x4,
> 0x17c090), at 0xfedb53fc
> 
>   [11] NodeImpl::deleteIf(0x0, 0x2102c8, 0x1f9d58, 0x4, 0x7200,
0xfe2dceaf),
> at 0xfedb53fc
> 
>   [12] DOM_Node::~DOM_Node(0x1f99f0, 0x20aa90, 0x9, 0xfe2dceb0,
0xfd20b5f0,
> 0x4), at 0xfed9c4cc
> 
>  
> 
> Regards
> 
> Ram
> 
>  
> 
> p.s
> 
>  
> 
> We are in process of migrating to 1-7  in hope that it would disappear.
> 
>  
> 
>  
> 
>  
> 
> ********************************************
> Ramkumar Iyer
> 
> Technical Architect
> Wipro Technologies (T & I)
> ESN     : 6-872-8025
> 
> Tel(O)  : +91-(0)80-5538301 extn 2319
> Tel(M)  : 9845195686
> 
> Mail      : [EMAIL PROTECTED] <mailto:ramkumar.iyer@;wipro.com> 
> *********************************************
> 
> If the path be beautiful, let us not ask 
> 
> where it leads.
> 
>  
> 
>  
> 
> 

-- 
Gareth Reakes, Head of Product Development  
DecisionSoft Ltd.            http://www.decisionsoft.com
Office: +44 (0) 1865 203192



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
**************************Disclaimer************************************************** 
   
 
 Information contained in this E-MAIL being proprietary to Wipro Limited is 
'privileged' 
and 'confidential' and intended for use only by the individual or entity to which it 
is 
addressed. You are notified that any use, copying or dissemination of the information 
contained in the E-MAIL in any manner whatsoever is strictly prohibited.

****************************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to