Hi Forum I've had a strange error occur where a particular webser

lincolnf454 over 10 years ago

Hi Forum

I've had a strange error occur where a particular webservice fails after working perfectly for 6 months. It seems to be a problem with the endpoint, even though it has been working fine up until now. We have changed the endpoint from Soap12 to soap and this worked, but this was quite cumbersome throughout every instance in the process and may seriously affect any active process instances.

Is there a way to stop this from occurring again?

Discussion posts and replies are publicly visible

0 Aleksi White
Appian Employee
over 10 years ago

Did you make any changes in the environment recently? Upgrade appian version or apply a hotfix? Set up a VPN tunnel?
Could you also attach the application-server.log?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lincolnf454 over 10 years ago

Hi Aleksi

Thank you for your response. to answer your questions, we have not made any recent changes to the environment. Please see the attached server log
application-server.log
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Aleksi White
Appian Employee
over 10 years ago

According to the logs the read timed out. This could indicate something on the network level preventing the connection. Can you confirm if this works properly over SOAPUI when the endpoint is set to Soap12? Are you able to get a telnet connection from the appian server to the endpoint? Are there any firewalls or other appliances between the appian server and the endpoint?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lincolnf454 over 10 years ago

Hi Aleksi

It appears that this is not a time out issue, as I can edit process, change the endpoint to SOAP and the webservice will work correctly. We need urgent advise on this as it is effecting a live environment
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Aleksi White
Appian Employee
over 10 years ago

What is the latest status on this issue?
Are you seeing the same error as originally reported?
Please also try the following:

1) In appian_log4j.properties add the following line:
log4j.logger.com.appiancorp.ws=DEBUG
2) Wait a few minutes, and then test to recreate the error
3) Modify the node as you mentioned so it works properly, and then test that
4) Attach application-server.log

This way I will have a successful attempt to compare against the failed attempt.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel