Problems with xerces on AIX 5.2

[ANIRUDDHA shevade <an...@yahoo.com>]

Hello
 We are using xerces 1.4 ( when we developed our
application this was the latest version available at
that time )

The library worked fine , until recently when we
started running out application on AIX 5.2. It apperas
that when we run on multi cpu machine, after some time
the performance degrades. When I forced a Core dump to
see the stack trace , I always found the problem in
the xerces library. It looks there are some threads
wating to lock a mutex , and one thread trying to
release it

The following is the stack trace for the thread which
is tryign to release the mutex

pth_spinlock._set_interlock(??, ??, ??) at 0xd054b0d8
pth_spinlock._unlock_wakeup(??) at 0xd054b1d8
pth_mutex.pthread_mutex_unlock(??) at 0xd0549c18
unlockMutex__16XMLPlatformUtilsFPv_45_30() at
0xd56a3544
unlock__8XMLMutexFv() at 0xd56b1ee4
__dt__12XMLMutexLockFv() at 0xd56b1f70
__nw__15DOMStringHandleFUl() at 0xd56afeb8
cloneStringHandle__15DOMStringHandleFv() at 0xd56b01d4
clone__9DOMStringCFv() at 0xd56b0bec
__ct__8AttrImplFP12DocumentImplRC9DOMString() at
0xd56abc84
__ct__10AttrNSImplFP12DocumentImplRC9DOMStringRC9DOMString()
at 0xd56ea9b8
createAttributeNS__12DocumentImplFRC9DOMStringRC9DOMString()
at 0xd56c4a34
setAttributeNS__11ElementImplFRC9DOMStringRC9DOMStringRC9DOMString()
at 0xd56e01ec
startElement__9DOMParserFRC14XMLElementDeclUiPCUsRC11RefVectorOfXT7XMLAttr_T2bT6()
at 0xd56ee44c
scanStartTagNS__10XMLScannerFRb() at 0xd5706ab0
scanContent__10XMLScannerFb() at 0xd570477c
scanDocument__10XMLScannerFRC11InputSourceb() at
0xd5703b94
parse__9DOMParserFRC11InputSourceb() at 0xd56ecde4
Parse__15AcSoapXmlParserFiPCcb() at 0xd61ada60
CheckXmlParsing__20AcSoapReceiveMessageFiPCcb() at
0xd61808ac
ParseXml__20AcSoapReceiveMessageFb() at 0xd617de00
ParseSoapBody__20AcSoapReceiveMessageFb_491_94() at
0xd618cfd0
ParseSoapBody__13AcEncycSoapMHFP13AcSoapRequest() at
0x105847bc
ProcessRequest__13AcEncycSoapMHFv() at 0x10584b04


The following is the stack trace of 2 other threads
which are trying to lock the mutex
pth_spinlock._waitlock(??, ??) at 0xd054acf8
pth_spinlock._local_lock_common(??, ??, ??) at
0xd054b310
pth_mutex.pthread_mutex_lock(??) at 0xd054a050
lockMutex__16XMLPlatformUtilsFPv_46_28() at 0xd56a35c8
lock__8XMLMutexFv() at 0xd56b1eac
__ct__12XMLMutexLockFP8XMLMutex() at 0xd56b1f28
__nw__15DOMStringHandleFUl() at 0xd56afe2c
cloneStringHandle__15DOMStringHandleFv() at 0xd56b01d4
clone__9DOMStringCFv() at 0xd56b0bec
substringData__9DOMStringCFUiT1() at 0xd56b1780
__ct__10AttrNSImplFP12DocumentImplRC9DOMStringRC9DOMString()
at 0xd56eaba4
createAttributeNS__12DocumentImplFRC9DOMStringRC9DOMString()
at 0xd56c4a34
setAttributeNS__11ElementImplFRC9DOMStringRC9DOMStringRC9DOMString()
at 0xd56e01ec
startElement__9DOMParserFRC14XMLElementDeclUiPCUsRC11RefVectorOfXT7XMLAttr_T2bT6()
at 0xd56ee44c
scanStartTagNS__10XMLScannerFRb() at 0xd5706ab0
scanContent__10XMLScannerFb() at 0xd570477c
scanDocument__10XMLScannerFRC11InputSourceb() at
0xd5703b94
parse__9DOMParserFRC11InputSourceb() at 0xd56ecde4
Parse__15AcSoapXmlParserFiPCcb() at 0xd61ada60
CheckXmlParsing__20AcSoapReceiveMessageFiPCcb() at
0xd61808ac
ParseXml__20AcSoapReceiveMessageFb() at 0xd617de00
ParseSoapBody__20AcSoapReceiveMessageFb_491_94() at
0xd618cfd0


My question is 

- Can we use xerces 1.4 on AIX 5.2 platform , which
has been compiled using Visual Age 6.0 compiler

- Are there any known issues which can occur on multi
cpu machines

Any help is appreciated

thanks 
- Aniruddha






__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org

Re: Problems with xerces on AIX 5.2

[da...@us.ibm.com]

> My question is
>
> - Can we use xerces 1.4 on AIX 5.2 platform , which
> has been compiled using Visual Age 6.0 compiler

I don't think anyone can answer that question.  You will simply have to try
to build it from source, which you can download from here:

   http://archive.apache.org/dist/xml/xerces-c/Xerces-C_1_4_0/

> - Are there any known issues which can occur on multi
> cpu machines

There were some multi-threading problems with DOMString which were fixed in
later releases.  You will have to upgrade to get them, because there was no
attempt made to retrofit them to earlier releases.  You should consider
upgrading anyway, because Xerces-C 1.4 is ancient.

Dave