|
Home > Archive > BizTalk Server Orchestration > November 2005 > strange soap adapter error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
strange soap adapter error
|
|
|
| Hi!
I have an orchestration that calls a web service method. The behavior of the
soap receive adapter seems very unstable. Sometimes I manage to receive an
answer, sometimes I don't....
When sending a request to the web service I encounter the following warnings
in the application log:
EventID: 5740 The adapter "SOAP" raised an error message. Details "Exception
has been thrown by the target of an invocation.".
EventID: 5740 The adapter "SOAP" raised an error message. Details "The
operation has timed-out.".
EventID: 5743 The adapter failed to transmit message going to send port "my
web service port". It will be retransmitted after the retry interval
specified for this Send Port. Details:"The operation has timed-out.".
The state of the orchestration remains "Active", that is the request has not
event been sent to the method (I assume).
As I said, sometimes I manage to get an answer without any problems and
without any warnings in the log.
Has anybody encountered this strange behavior?
Gratefull for feedback!
//theo
| |
| anand kumar 2005-10-05, 9:01 pm |
| Hi,
In your orchestration before invoking the web service set the SOAP time out
property as follows
MessageType(SOAP.ClientConnectionTimeout) = 10000
(10000 is an arbitrary number in this example) and MessageType is your
Message that is being sent to the web service.
Good Luck.
--
Anand
"Theo" wrote:
> Hi!
>
> I have an orchestration that calls a web service method. The behavior of the
> soap receive adapter seems very unstable. Sometimes I manage to receive an
> answer, sometimes I don't....
>
> When sending a request to the web service I encounter the following warnings
> in the application log:
>
> EventID: 5740 The adapter "SOAP" raised an error message. Details "Exception
> has been thrown by the target of an invocation.".
>
> EventID: 5740 The adapter "SOAP" raised an error message. Details "The
> operation has timed-out.".
>
> EventID: 5743 The adapter failed to transmit message going to send port "my
> web service port". It will be retransmitted after the retry interval
> specified for this Send Port. Details:"The operation has timed-out.".
>
> The state of the orchestration remains "Active", that is the request has not
> event been sent to the method (I assume).
>
> As I said, sometimes I manage to get an answer without any problems and
> without any warnings in the log.
>
> Has anybody encountered this strange behavior?
>
> Gratefull for feedback!
>
> //theo
>
>
| |
| Kekilie 2005-11-15, 7:53 am |
| Hi,
I also have an orchestration that calls webservice methods, 3 different
methods. All of them receive one xml as a parameter. The xml's are populated
from database tables, three different tables. 2 of the webservice calls works
fine, 1 results in a timeout. The xml's in the 2 calls that succeeds contains
data from database tables with 500 and 900 rows. These 2 calls returns back
to the orchestration with a response. The call that fails contains a xml with
data from 13500 database table rows! I thought that maybe the webservice
needed more time, so I added the following code in the Assignment shape just
before the webservice call in my orchestration :
Msg_SOAPRequest(SOAP.ClientConnectionTimeout) = 12000;
Msg_SOAPRequest(HTTP.RequestTimeout) = 12000;
This code had no effect! Still get timeout, and I get it immediately after
the request is sent. It doesnt wait for 3 minutes before it times out (if
12000 milliseconds is like 3 minutes...)
Any ideas to fix this timeout?
Or to troubleshoot? Is there anything else than my orchestration that can
cause this error? In that case what?
Regards,
Kekilie
"anand kumar" wrote:
[vbcol=seagreen]
> Hi,
> In your orchestration before invoking the web service set the SOAP time out
> property as follows
>
> MessageType(SOAP.ClientConnectionTimeout) = 10000
> (10000 is an arbitrary number in this example) and MessageType is your
> Message that is being sent to the web service.
>
> Good Luck.
> --
> Anand
>
>
> "Theo" wrote:
>
|
|
|
|
|