Web Request - Workflw Error
/customer/servlet/servlet.FileDownload?file=00P6000000em1GsEAI
Can anyone help me get this Workflow Error popup NOT to display?
I am submitting a Web Request, which returns a byte array. I don't care about the output. As soon as I submit the request, it hits an SOE that runs a QC on the version submitted, and the output from that is an email. I realize a Web Request is 'requesting' something from the url in the activity. I tried doing a "Post" as one of the Web Request params, which also did not help.
Additionally, I have I tried to a bunch of Try Catch activity options where the Catch was the arguments exception and other exceptions with no luck. The SOE can run for ten minutes and am wondering if this is timing out. Either way, I don't want to extent the timeout to that long on the server just because of this one situation.
-
Ryan,
Are y our WebRequest to the SOE Webservice requiring to take a input param with XML format?
If then, have you configured the Headers in InArguments with New WebHeaderCollection() which may need to have two configurations "Content_Type" and "application/x-www-form-urlencoded"?
Munhwan
0 -
Hi Munwhan,
I am using the Web Request with a similar SOE to return lists without issue, just using a few string parameters... avoiding any In Arguments other than the Uri. So, I thought it would be similar.
Can you elaborate a little on how to set up the "two configurations "Content_Type" and "application/x-www-form-urlencoded" for the collection? I set up a new collection (iCollection1) with variable type System.Net.WebHeaderCollection. iCollection1 is now the header in the In Arguments. I added New System.Collections.Generic.Dictionary(Of String, String) From { { "Content_Type", "application/x-www/form-urlencoded" }} as the Parameters. This did not work for me either. I get my email as a success via the SOE, but the same error is returned.
thank you!
Ryan
0 -
Munwhan,
I missed the first part of your question. No, they are not taking XML as an input param.
Any other ideas?
0 -
What you do on the Header part looks ok.
I have no experience to get the Email from Email before so I am afraid to help you more.
However, I would like to suggest to use 'Fiddler' to investigate more what WebRequest content to the SOE looks like and also what Response from the SOE with that request to check.
It looks like there is an issue between Gcx Web server and SOE server. So with the help from the Fiddler, you may find what it happends that WebRequest to the SOE.
Munhwan
0 -
Munwhan,
I am really looking for a way to just kick off a request where the GeoCortex server is not looking for a response. Therefore I am using the Web Request. Maybe there's a better option. When using the Web Request activity in the past, I always needed something returned, in which it only took a few seconds...
Fiddler did not tell me much other than my error is a 500 error.
I think I am going to submit a ticket on this one as I need as answer asap.
thanks for your help as always,
Ryan
0 -
ok. Ryan.
> The SOE can run for ten minutes and am wondering if this is timing out
GVS will be time-out after few minutes if there is no any other activity is happening.
To resolve this time-out issue, you may put your WebRequest to SOE to the WorkflowAsyn (if you don't have any further activity with that response from SOE on your original workflow),
or you can wake-up the original workflow with a timer (and workflowContainer) every few seconds or so to tell GVS your original workflow is running.
But it is a good idea to use the Support ticket to get the thorough help.
Munhwan
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
6 Kommentare