BPCOR-6130: Activity Name is Invoke ERROR

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

BPCOR-6130: Activity Name is Invoke ERROR

marcelo.moscoso
This post has NOT been accepted by the mailing list yet.
Hello friends, invoking an external web service presents the following error: Caused by: Not in GZIP format ,Do I have to trasformat or compress the sending message?

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode>SOAP-ENV:Server</faultcode>
         <faultstring>
<![CDATA[BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;El servidor ha enviado el código de estado HTTP 200: OK&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance]]>
</faultstring>
         <faultactor>sun-bpel-engine</faultactor>
         <detail>
            <detailText>
<![CDATA[BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;El servidor ha enviado el código de estado HTTP 200: OK&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance
   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=paymetServiceATCPnk, portType={http://tempuri.org/}IPaymentService, operation=AcceptPayment)
BPCOR-6129: Line Number is 66
BPCOR-6130: Activity Name is Invoke1
   Caused by: El servidor ha enviado el código de estado HTTP 200: OK
   Caused by: Not in GZIP format]]>
</detailText>
         </detail>
      </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

thanks and regards
Reply | Threaded
Open this post in threaded view
|

Re: BPCOR-6130: Activity Name is Invoke ERROR

Paul Perez
Administrator
Hello Marcelo

Could you provide more detail on that Case.
What do you try to invoke
There is no need to compress any message.
could we get more information on the WSDL you try to invoke and the project you develop ?

regards

Paul
www.pymma.com The best services on OpenESB
Reply | Threaded
Open this post in threaded view
|

Re: BPCOR-6130: Activity Name is Invoke ERROR

marcelo.moscoso
This post has NOT been accepted by the mailing list yet.

Thanks Paul, Inhave in production openesb 3.0.5.   when invoking
an external web service  on the header has to Content-Encoding = gzip

Consult where I have to configure for that type of support?


Apparently I already saw this topic in, I do not understand: gzip compression support in HTTP BC?
http://openesb-community-forum.794670.n2.nabble.com/gzip-compression-support-in-HTTP-BC-td5366301.html


regards
Reply | Threaded
Open this post in threaded view
|

Re: BPCOR-6130: Activity Name is Invoke ERROR

Paul Perez
Administrator
Marcelo,

I send your request to the OpenESB HTTP BC manager and come back to you

Paul
www.pymma.com The best services on OpenESB