Question
Coforge DPA private limited
AU
Last activity: 8 Jun 2016 8:45 EDT
getting Transport error: 302 Error:Found
Hi,
I am getting Transport error: 302 Error:found error when running the Connector Activity stand alone. I am just trying to check if we are able to hit the external service.
Can someone pls help me.
Thanks,
Madhusudan
Message was edited by: Lochan to add Category
Accepted Solution
PEG
PL
This error comes when the request dont go out. When you are doing it via SoapUI, you are doing it via your machine. (your network). But when you try it via PRPC, it goes out from the PRPC server. These kind of issues comes when the server is not able to make call to outside world. May be because of firewall. Could you check on that front?
Pegasystems Inc.
IN
Hello,
Have you tried using it as part of your regular use case ? is it working fine then ?
Also , have a look at this article if this helps : https://community.pega.com/support/support-articles/connect-soap-failstransport-error-302-error-moved-temporarily
Coforge DPA private limited
AU
Hi,
I saw the article but is it really something related to env configuration? because I see other Connect-Soaps are working fine.
I have created the rules using connector wizard.
Thanks,
Madhusudan
PEG
IN
Hi,
1.Which PRPC version you are in?
2. Were you able to hit the service using third party looks like SOAP UI or tcpmon?
3. Please share the PegaRules log file when issue occurred?
Coforge DPA private limited
AU
Hi,
1.)Its pega 7.1.9 version
2.) yep using SOAP UI there is no issue.
3.)
Hi,
1.)Its pega 7.1.9 version
2.) yep using SOAP UI there is no issue.
3.)
| Caught exception: com.pega.apache.axis2.AxisFault: Transport error: 302 Error: Found |
| com.pega.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:309) |
| com.pega.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:194) |
| com.pega.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75) |
| com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:411) |
| com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:233) |
| com.pega.apache.axis2.engine.AxisEngine.send(AxisEngine.java:445) |
| com.pega.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406) |
| com.pega.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229) |
| com.pega.apache.axis2.client.OperationClient.execute(OperationClient.java:165) |
| com.pegarules.generated.activity.ra_action_invokeaxis2_d7f45243222ebb1e35b38e2ce51b5995.step14_circum0(ra_action_invokeaxis2_d7f45243222ebb1e35b38e2ce51b5995.java:3899) |
| com.pegarules.generated.activity.ra_action_invokeaxis2_d7f45243222ebb1e35b38e2ce51b5995.perform(ra_action_invokeaxis2_d7f45243222ebb1e35b38e2ce51b5995.java:291) |
| com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3505) |
| com.pegarules.generated.activity.ra_action_invoke_c28ff8c27ac24045d30f5561679549d1.step8_circum0(ra_action_invoke_c28ff8c27ac24045d30f5561679549d1.java:1037) |
| com.pegarules.generated.activity.ra_action_invoke_c28ff8c27ac24045d30f5561679549d1.perform(ra_action_invoke_c28ff8c27ac24045d30f5561679549d1.java:189) |
| com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3505) |
| com.pegarules.generated.activity.sh_action_register_be365e8d105b6c6eb1dde56d37a391e8.step3_circum0(sh_action_register_be365e8d105b6c6eb1dde56d37a391e8.java:379) |
| com.pegarules.generated.activity.sh_action_register_be365e8d105b6c6eb1dde56d37a391e8.perform(sh_action_register_be365e8d105b6c6eb1dde56d37a391e8.java:111) |
| com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3505) |
| com.pega.pegarules.session.internal.mgmt.Executable.doAction(Executable.java:3238) |
PEG
IN
Could you turn on debug loggers on below class and run the scenario and share the logs?
Rule_Obj_Activity.InvokeAxis2.Rule_Connect_SOAP.Action
Accepted Solution
PEG
PL
This error comes when the request dont go out. When you are doing it via SoapUI, you are doing it via your machine. (your network). But when you try it via PRPC, it goes out from the PRPC server. These kind of issues comes when the server is not able to make call to outside world. May be because of firewall. Could you check on that front?
Coforge DPA private limited
AU
Thanks Rajeev and Gangababu for your replies.
Yes Indeed issue was with the server as there was some authentication issue. It is resolved now after talking to Admin.
Many Thanks,
Madhusudan