Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Verified Answer
+1
person also asked this
people also asked this
Replies
3 replies
Subscribers
5 subscribers
Views
1755 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Seeing the below error in logs and WS smart service hangs up but was able to loa
abhinavg
over 9 years ago
Seeing the below error in logs and WS smart service hangs up but was able to load the service operations and input and output are getting initialized properly, only while calling WS endpoint it hangs up.
WS operation works fins when called from SOAP UI
Logs: ERROR com.appiancorp.process.runtime.activities.WebServiceActivity2
******************
16:13:16,768 INFO [stdout] (Appian Work Item - 442653 - ProcessExec00 : UnattendedJavaActivityRequest) 2015-05-12 16:13:16,764 [Appian Work Item - 442653 - ProcessExec00 : UnattendedJavaActivityRequest] ERROR com.appiancorp.process.runtime.activities.WebServiceActivity2 - An error occurred while reading the WSDL
168.110.18.121/.../ErrorLoggingService.svc
to create WSInvoker for the service {
tempuri.org/}DamageInspectionService
and the endpoint BasicHttpBinding_DamageInspectionService.
16:13:16,768 INFO [stdout] (Appian Work Item - 442653 - ProcessExec00 : UnattendedJa...
OriginalPostID-148771
OriginalPostID-148771
Discussion posts and replies are publicly visible
0
abhinavg
over 9 years ago
...vaActivityRequest) com.appiancorp.ws.WSClientException: The WSDL cannot be processed. It contains invalid or unsupported elements. Details: Service {
tempuri.org/}DamageInspectionService
was not found in the WSDL (APNX-1-4043-001)
16:13:16,768 INFO [stdout] (Appian Work Item - 442653 - ProcessExec00 : UnattendedJavaActivityRequest) at com.appiancorp.ws.WSClient.createWSInvoker(WSClient.java:180)
16:13:16,769 INFO [stdout] (Appian Work Item - 442653 - ProcessExec00 : UnattendedJavaActivityRequest) at com.appiancorp.ws.WSClientUtils.createWSInvoker(WSClientUtils.java:33)
16:13:16,769 INFO [stdout] (Appian Work Item - 442653 - ProcessExec00 : UnattendedJavaActivityRequest) at com.appiancorp.process.runtime.activities.WebServiceActivity3.getWSInvoker(WebServiceActivity3.java:158)
*******************************
We have cloud environment ans ws was working fine till yesterday
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Maybe a WSDL cache issue that a restart of the application server can fix.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
+1
abhinavg
over 9 years ago
Yes it worked after restart for App Server and Engines
Cancel
Vote Up
0
Vote Down
Sign in to reply
Reject Answer
Cancel