Hello,

We are using Fabric 6.5 and RosettaNet Adapter 6.01 (the most recent)

Has anyone come across this particular error when using wm.ip.cm:processDocument?


com.wm.lang.flow.FlowException: ip.cm.handlers:processDocument(): Error trapped in service: wm.ip.cm:processDocument
Error: Error: Error while executing service wm.ip.cm:getConversationScript [ESIPRT.000000.000001] Suggested Action:
Level: Level:
Service Call Stack:

at wm.ip.cm.getConversationScript(cm.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
…

I have a feeling it might require a FIX to be applied as we have everything else in place (process model, recognized document, matching TPA etc.)


Thanks all!


John

This error is often thrown when the http connection to the destination (of the document) is not available. Especially if you got this error while sending the document to the Trading Partner.

~Rohit

Hi Rohit,

This error is coming from our local IS instance when it is trying to inspect the PRT for a converstation script. At this point we havent established a connection with our TP.

Our IS Box is on a different subnet from our developer client, we have ruled out if it was perhaps the firewall, by switching it off and trying a test case… unfortunently the same error persists

Hi Rohit,
When are you submitting this document to TN?
Is it the Internal Document or external PIP document.
If you are sending the PIP document to the TP. You have to submit the Internal PIP document first and then extract the TPA parameters for the external PIP to TP.

Also, Check if the TPA parameters are correct in TN.
HTH
Praveen

Praveen,

It was not I who was having the problem - it was John, the original poster of this thread.

John,

The getConversationScript is a generic error that seems be thrown by PRT when it fails to get the data to process the next step of the conversation. We in our RosettaNet environment often see this error as a result of an unavailable host (http errors). Let us know if you find the cause of this error on your side. Thanks,

~Rohit