integration logs

RE: integration logs

michaelr0003 — Wed, 14 Aug 2019 02:35:14 GMT

Did you resolve this issue? I'm having the same problem.

RE: integration logs

rishis — Tue, 21 Aug 2018 19:15:28 GMT

can i enable more trace and see whats going on?

RE: integration logs

rishis — Tue, 21 Aug 2018 19:14:54 GMT

same error

19:14:02,634 INFO [stdout] (ajp-/0.0.0.0:8009-1) 2018-08-21 19:14:02,633 [ajp-/0.0.0.0:8009-1] ERROR com.appiancorp.connectedsystems.http.execution.AppianHttpRequestExecutor - ConnectorRuntimeException [title=Something went wrong, Failed to connect to https://xxxxxxreference/v1/country]

RE: integration logs

Sumeet Khare — Tue, 21 Aug 2018 19:05:42 GMT

yes please

RE: integration logs

rishis — Tue, 21 Aug 2018 19:03:34 GMT

its in my qa box, should i re-import it from dev?

RE: integration logs

Sumeet Khare — Tue, 21 Aug 2018 19:01:18 GMT

Can you delete that integration and create new one and then check the logs please

RE: integration logs

rishis — Tue, 21 Aug 2018 18:36:58 GMT

This is fresh restart from jboss, this is only thing output once started.

18:07:53,713 INFO [com.sun.jersey.server.impl.application.WebApplicationImpl] (ajp-/0.0.0.0:8009-1) Initiating Jersey application, version 'Jersey: 1.8-atlassian-6 03/12/2012 02:59 PM'
18:13:18,153 INFO [stdout] (ajp-/0.0.0.0:8009-1) 2018-08-21 18:13:18,153 [ajp-/0.0.0.0:8009-1] ERROR com.appiancorp.connectedsystems.http.execution.AppianHttpRequestExecutor - ConnectorRuntimeException [title=Something went wrong, Failed to connect to https://xxxxxxreference/v1/country]

RE: integration logs

Sumeet Khare — Tue, 21 Aug 2018 18:35:18 GMT

If possible please attach the log file.

RE: integration logs

rishis — Tue, 21 Aug 2018 16:19:55 GMT

the api is fine, something is wrong with the integration object/jboss call. where can i see the logs to see whats going on. This is not a network or server issue or an issue from api which we are trying to make the get call on. Its not a authorization issue either.
I get a failed to connect and connection reset error from appian. This get should take seconds. So something is blocking the request.

RE: integration logs

Abhay Giri — Tue, 21 Aug 2018 11:31:02 GMT

Hi Rishi,

1->
If your service was working till yesterday in QA and not working today it means something configuration has been changed which you need to implement in your Appian or if it is using any kind of authentication then it may be authentication details changed.

2-> try to connect the service from SOAP UI or POSTMAN and check weather you are able to connect the service or not?

Regards
Abhay Giri

RE: integration logs

aloks0189 — Tue, 21 Aug 2018 07:48:27 GMT

Hi rishis a quick question here:

What do you mean by "browser on the appian box"?

Did you try clearing the browser history, cache and the cookies before accessing this URL via web browser. Also I believe, if you are trying to access this service directly via browser url, it must ask for authentication details.

Also, may I know what's the Http status code you are getting in response while accessing this service using integration object? E.g. is that 404, 500 etc...

Sometimes, irrespective of whether your service is working or not, browser will return the result using the cache/history.

Also, can you try accessing this service using SOAPUI or any other Third party client. And check whether it's being accessed or not.

Also, as this API is exposed via Appian hence don't forget to pass basic authentication details and preemptive as true while accessing it via third party client tool/browser plugins.

If your SOAPUI is able to access this service then their must be something wrong in your integration object configuration but if not, then you need to cross check your API configuration.

Hope this will help you in debugging this issue.

RE: integration logs

Shanmukha — Tue, 21 Aug 2018 03:48:08 GMT

Hi Rishi,
I would like to ask few things for better understanding of the scenario so that it may help other folks to provide right pointers for the problem.

1) If you say it is internal web service call which means is ti implemented in Appian itself? if it is out side service hen did you check the firewall setting (that might have modified) if any?
2) What kind of web service call is it?