Why DOM Parser is not thread safe? Please explain
| Newsgroups | gmane.text.xml.xerces-j.user |
|---|---|
| Message-ID | <OF83B582E6.27F628A9-ON65257A95.004007B2-65257A95.00410F53@polarisft.com> |
Apache Team,
Major concern for us with DOM parser in multi thread environment. Can you
please review this and provide your inputs? Thanks.
OS: Sun Solaris 10
Server: Websphere 6
JDK: 1.4
Xerces version: Xerces_Version_1_2_0
Number of Daemon threads per JVM: 3
Scenario:
In our Production environment when 3 daemon threads run under a JVM.
When 3 similar type of XML messages gets parsed at same second
(concurrently) under a JVM, we notice some attribute gets missed. We went
through net and found that DOM implementation is not guaranteed to be
thread safe. But question is why it is not thread safe? Which part can go
wrong? Please provide details.
Below is the piece of code:
public Document parse(InputSource inputSource, boolean isValidating) throws
SAXException,IOException {
if ( getEntityResolver() == null )
throw new IllegalStateException("EnitityResolver is not
set");
DocumentBuilder docBuilder = getDocumentBuilder(isValidating);
// parsing from input source
docBuilder.setEntityResolver(getEntityResolver());
docBuilder.setErrorHandler (getErrorHandler());
return docBuilder.parse(inputSource);
}
Sample xml passed to this code is attached: sample_message.xml
(See attached file: sample_message.xml)
Thanks,
karthik
This e-Mail may contain proprietary and confidential information and is sent for the intended recipient(s) only. If by an addressing or transmission error this mail has been misdirected to you, you are requested to delete this mail immediately. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message, contents or its attachment other than by its intended recipient/s is strictly prohibited.
Visit us at http://www.polarisFT.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
sample_message.xml
(application/octet-stream, 3.5 KB)
<?xml version="1.0"?>
<!DOCTYPE InTemplate SYSTEM "feed_dd.dtd" >
<InTemplate>
<Header>
<DataDictionary>
<element XMLName="NumberOfTxn" CFCName="NO_TRANS" CFCType="TYPE_STRING"/>
<element XMLName="ProcessingLoc" CFCName="PR_LOC" CFCType="TYPE_STRING"/>
<element XMLName="ServiceType" CFCName="FCO_TYP" CFCType="TYPE_STRING"/>
</DataDictionary>
</Header>
<Body>
<DataDictionary>
<element XMLName="TxnUID" CFCName="TRAN_NO" CFCType="TYPE_STRING"/>
<element XMLName="ServTxnUID" CFCName="SERV_REF_NO" CFCType="TYPE_STRING"/>
<element XMLName="BatchID" CFCName="DETL_BATCH_REF_NO" CFCType="TYPE_STRING"/>
<element XMLName="ProcessingActionInd" CFCName="PROC_ACTN_IND" CFCType="TYPE_STRING"/>
<collection XMLName="TxnIdentification" CFCType="TYPE_FIELDCOLLECTION">
<element XMLName="Sequence" CFCName="BSI_SEQ" CFCType="TYPE_STRING"/>
<element XMLName="TxnType" CFCName="PYMT_TYP" CFCType="TYPE_STRING"/>
<element XMLName="AcctNumber" CFCName="ACCT_NO" CFCType="TYPE_STRING"/>
<element XMLName="TxnRefNumber" CFCName="MT100_REF_NO" CFCType="TYPE_STRING"/>
<element XMLName="CitiRefNumber" CFCName="CITI_REF_NUMBER" CFCType="TYPE_STRING"/>
<element XMLName="ValueDate" CFCName="TRAN_VAL_DAT" CFCType="TYPE_DATE"/>
<element XMLName="Amount" CFCName="TRAN_AMT" CFCType="TYPE_CURRENCY"/>
<element XMLName="CCY" CFCName="ACCT_CCY_COD" CFCType="TYPE_STRING"/>
</collection>
<element XMLName="ProcessingLocCode" CFCName="PROC_LOCA" CFCType="TYPE_STRING"/>
<element XMLName="Status" CFCName="STA" CFCType="TYPE_STRING"/>
<element XMLName="SwiftSubStatus" CFCName="SUBSTATUS" CFCType="TYPE_STRING"/>
<element XMLName="Severity" CFCName="SEVERITY" CFCType="TYPE_STRING"/>
<element XMLName="TxnRespNumber" CFCName="SERV_RSP_REF_NO" CFCType="TYPE_STRING"/>
<element XMLName="AuthNumS015" CFCName="MEX_AUTH_NO" CFCType="TYPE_STRING"/>
<element XMLName="AuthNumS502" CFCName="MEX_FOLIO_NO" CFCType="TYPE_STRING"/>
<element XMLName="DigitalStamp" CFCName="MEX_DGTL_STMP" CFCType="TYPE_STRING"/>
<element XMLName="TaxInfo" CFCName="MEX_ACK_CHAIN" CFCType="TYPE_STRING"/>
<element XMLName="ErrorMessage" CFCName="ERR_MESSAGE" CFCType="TYPE_STRING"/>
<element XMLName="ErrorCode" CFCName="ERR_COD" CFCType="TYPE_STRING"/>
<element XMLName="RejReason" CFCName="ERR_DESC" CFCType="TYPE_STRING"/>
<element XMLName="RolloverDate" CFCName="ROLLOVER_DT" CFCType="TYPE_DATE"/>
<element XMLName="BoletoNumber" CFCName="TKT_NO" CFCType="TYPE_STRING"/>
<element XMLName="RejectDate" CFCName="REJ_DT" CFCType="TYPE_DATE"/>
<element XMLName="CheckWriteDate" CFCName="" CFCType="TYPE_DATE"/>
<element XMLName="CompletionDate" CFCName="CMP_DT" CFCType="TYPE_DATE"/>
<element XMLName="DiscountDate" CFCName="DISC_DT" CFCType="TYPE_DATE"/>
<element XMLName="DiscountRate" CFCName="DISC_RT" CFCType="TYPE_DOUBLE"/>
<element XMLName="DiscountStatus" CFCName="DISC_ST" CFCType="TYPE_STRING"/>
<element XMLName="CR" CFCName="CR" CFCType="TYPE_STRING"/>
<element XMLName="NextBD" CFCName="ROLLOVER_DT" CFCType="TYPE_STRING"/>
<element XMLName="NextPaymentDate" CFCName="NEXT_PYMT_DT" CFCType="TYPE_STRING"/>
<element XMLName="ISOReason" CFCName="SUB_STATUS" CFCType="TYPE_STRING"/>
<element XMLName="Reference" CFCName="MT942_REF_NO" CFCType="TYPE_STRING"/>
</DataDictionary>
</Body>
</InTemplate>