XMLCoder decode invalid data typejavaioByteArrayInputStream

, ,
1

I am trying to receive PIP 2A10 from trading partner. The conversation ID and doc type is coming up as unknown…
Log shows up error like
…
2002-12-10 00:57:54 EST We are in getInputValues method [ESIPRT.000000.000006]
2002-12-10 00:57:54 EST in contenthandler: multipart/related
2002-12-10 00:57:54:765 EST XMLCoder decode invalid data type: java.io.ByteArrayInputStream
2002-12-10 00:57:54 EST BizDocTypeReg: recognize and create starting [TRNSERV.000019.000030]
2002-12-10 00:57:54 EST BizDocTypeReg: recognizing pipeline [TRNSERV.000019.000023]
2002-12-10 00:57:54 EST We are in RN11BizDocType.isType() method [ESRN11.000000.000016]
2002-12-10 00:57:54 EST Content type : multipart/related
2002-12-10 00:57:54 EST BizDocTypeReg: pipeline will not be a wm.ip.rnif11.doc.RN11BizDocType [TRNSERV.000019.000012]
2002-12-10 00:57:54 EST In method : RN20BizDocType isType [ESRN20.000010.000004]
2002-12-10 00:57:54 EST Content type : multipart/related
2002-12-10 00:57:54 EST Content type : multipart/related
2002-12-10 00:57:54 EST BizDocTypeReg: pipeline will not be a wm.ip.rnif20.doc.RN20BizDocType [TRNSERV.000019.000012]
2002-12-10 00:57:54 EST BizDocTypeReg: pipeline will not be a com.wm.app.tn.doc.XMLDocType [TRNSERV.000019.000012]
2002-12-10 00:57:54 EST We are in IPDocType.isType() method [ESIPRT.000000.000006]
2002-12-10 00:57:54 EST BizDocTypeReg: pipeline will not be a wm.ip.doc.IPDocType [TRNSERV.000019.000012]
2002-12-10 00:57:54 EST BizDocTypeReg: pipeline will not be a com.wm.app.tn.doc.RecordDocType [TRNSERV.000019.000012]
2002-12-10 00:57:54 EST BizDocTypeReg: input pipeline is UNKNOWN [TRNSERV.000019.000003]
2002-12-10 00:57:54 EST Inserting doc c0a8da19f70d7055000007e4 into datastore [TRNSERV.000016.000073]
2002-12-10 00:57:54 EST Inserting content for doc c0a8da19f70d7055000007e4 [TRNSERV.000016.000010]
2002-12-10 00:57:54 EST We are in putOutputValues method [ESIPRT.000000.000006]

Any hints!!

2

If the doc type is unknown then all atributes must be unknown because TN doesn’t know how to query the doc.

So the first thing is fixing your doc type so that the incoming doc is recognized.

Theo

3

The par file I received for this is from webMethods.
The doc type is created by this par file when I exported in TN.
Since RN receive doen’t recognize the content, I am really out of ideas to locate the problem…
Your help in this is very much appreciated

4

I work with RosettaNet and have implemented several PIPs. If some of this is redundant I apologize.

After importing a par file.

  1. Copy the conversation script you’ll be using.
  2. Double click on the conversation.
  3. Under participants tab, ensure that the correct roles are selected.
  4. Ensure the 2A10 in the To/From role has the correct identifier that you’re expecting. In my case we use the DUNS, so make sure the values in the 2A10 match your My Enterprise Profile External ID Type value and Partner Profile External ID Type value.

I’ve had several ‘unknown documents’ and it was generally attributed to one of the steps above. I hope this helps.

5

Chris,
I retried all the steps you mentioned above and double checked for the mistake… It didn’t help…

I added savepipeline to file and it shows as below
Ithink recognize is failing to map the content to bizdoc…

  multipart/related 
 
 
  http 
  RosettaNet/V02.00 
  async 
  multipart/related; boundary=RN-HTTP-Body-Boundary; type="multipart/related" 
  25641 
 
10122113

Please help…
Thanks