I've never encountered any problem like that with JiBX. My guess is that
there is some buffering bug in a lower layer of your I/O pipeline.

-Archie

On Fri, Apr 27, 2018 at 1:46 PM, Vadheraju, Rajeshwar <Rajeshwar.Vadheraju@
fisglobal.com> wrote:

> When we do marshalling of object into XML, the name spaces are being
> truncated intermittently. We could not reproduce the issue consistently all
> the time but it is happening pretty much every day in the production. And
> the issue goes away when we recycle JVMs. We checked code and there is
> nothing we changed recently and we also checked production load which did
> not change much. We have been encountering the issue since 4/6 and very
> consistently every day this week.
>
>
>
> The good marshalled XML looks like below:
>
>
>
> *<dataRepositoryModel xmlns="http://xyz.com/dxModel/bdm/common
> <http://xyz.com/dxModel/bdm/common>"
> xmlns:cst="http://xyz.com/dxModel/bdm/customer
> <http://xyz.com/dxModel/bdm/customer>"
> xmlns:act="http://xyz.com/dxModel/bdm/account
> <http://xyz.com/dxModel/bdm/account>"
> xmlns:ast="http://xyz.com/dxModel/bdm/asset
> <http://xyz.com/dxModel/bdm/asset>"
> xmlns:lia="http://xyz.com/dxModel/bdm/liability
> <http://xyz.com/dxModel/bdm/liability>"
> xmlns:rel="http://xyz.com/dxModel/bdm/relationship
> <http://xyz.com/dxModel/bdm/relationship>"
> xmlns:col="http://xyz.com/dxModel/bdm/collateral
> <http://xyz.com/dxModel/bdm/collateral>"
> xmlns:gua="http://xyz.com/dxModel/bdm/guarantee
> <http://xyz.com/dxModel/bdm/guarantee>"
> xmlns:ses="http://xyz.com/dxModel/bdm/activity
> <http://xyz.com/dxModel/bdm/activity>"
> xmlns:esg="http://xyz.com/dxModel/bdm/esignature
> <http://xyz.com/dxModel/bdm/esignature>"
> xmlns:ath="http://xyz.com/dxModel/bdm/attachment
> <http://xyz.com/dxModel/bdm/attachment>">*
>
>
>
> The bad one looks like below:
>
> *<dataRepositoryModel xmlns="http://xyz.com/dxModel/bdm/common
> <http://xyz.com/dxModel/bdm/common>"
> xmlns:ses="http://xyz.com/dxModel/bdm/activity
> <http://xyz.com/dxModel/bdm/activity>">*
>
>
>
> So when we unMarshall bad document/XML, jib is throwing error(which is
> obvious) that
>
>
>
> org.xmlpull.v1.XmlPullParserException: could not determine namespace
> bound to element prefix cst (position: END_TAG seen
> ...</adtnl_phones><cst:branch_nbr>... @1:19189)
>
>                at org.xmlpull.mxp1.MXParser.pars
> eStartTag(MXParser.java:1816)
>
>                at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1259)
>
>                at org.xmlpull.mxp1.MXParser.nextToken(MXParser.java:1100)
>
>                at org.jibx.runtime.impl.XMLPullR
> eaderFactory$XMLPullReader.nextToken(Unknown Source)
>
>                at org.jibx.runtime.impl.UnmarshallingContext.advance(Unknown
> Source)
>
>                at org.jibx.runtime.impl.Unmarsha
> llingContext.parsePastCurrentEndTag(Unknown Source)
>
>                at com.xyz.dxModel.bdm.customer.J
> iBX_bdm_services_binding_2AdtnlPhonesType_access.unmarshal()
>
>                at com.xyz.dxModel.bdm.customer.C
> ustomerEntity.JiBX_bdm_services_binding_2_unmarshal_1_1(
> CustomerEntity.java)
>
>                at com.xyz.dxModel.bdm.customer.C
> ustomerEntity.JiBX_bdm_services_binding_2_unmarshal_1_2(
> CustomerEntity.java)
>
>                at com.xyz.dxModel.bdm.account.Ji
> BX_MungeAdapter.JiBX_bdm_services_binding_2_unmarshal_1_95()
>
>                at com.xyz.dxModel.bdm.common.Dat
> aRepositoryModelType.JiBX_bdm_services_binding_2_unmarshal_
> 1_0(DataRepositoryModelType.java)
>
>                at com.xyz.dxModel.bdm.common.JiB
> X_bdm_services_binding_2DataRepositoryModelType_access.unmarshal()
>
>                at org.jibx.runtime.impl.Unmarsha
> llingContext.unmarshalElement(Unknown Source)
>
>                at org.jibx.runtime.impl.Unmarsha
> llingContext.unmarshalDocument(Unknown Source)
>
>
>
>
> *Raj Vadheraju *IT Architect Specialist
> Corporate CIO Office
>
>
>
> T: 414.815.2613
> C: 414.551.6410
> rajeshwar.vadher...@fisglobal.com
>
> *FIS | Empowering the Financial World* [image:
> cid:image001.png@01D112FA.C4A77D90] <https://www.facebook.com/FIStoday>[image:
> cid:image002.png@01D112FA.C4A77D90] <https://twitter.com/FISGlobal>[image:
> cid:image003.png@01D112FA.C4A77D90] <https://www.linkedin.com/company/fis>
>
>
>
> [image: cid:image009.jpg@01D1810B.6E815C90]
>
>
> The information contained in this message is proprietary and/or
> confidential. If you are not the intended recipient, please: (i) delete the
> message and all copies; (ii) do not disclose, distribute or use the message
> in any manner; and (iii) notify the sender immediately. In addition, please
> be aware that any message addressed to our domain is subject to archiving
> and review by persons other than the intended recipient. Thank you.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> jibx-users mailing list
> jibx-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jibx-users
>
>


-- 
Archie L. Cobbs
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users

Reply via email to