wsaman deploy issues - Connect error 10901

Please let me know if you have any advice - I'm trying to deploy a new web service in a Linux environment, but get an error message "An error occurred connecting to the Web Service application. (10901)

It appears to be deployed correctly - I can access the WSDL - but when I attempt to send a message request with SoapUI, I get an error message "An error occurred connecting to the Web Service application. (10901)".

The web service's name is xxsfptexp, the wsa instance is wsa1, and when I point to the wsa in a web browser, I get a status of 111.

I deploy the web service with the command wsaman -i wsa1 -appname xxsfptexp -wsm /apps/wsmloc/xxsfptexp.wsm

The server returns a message saying that the service is deployed but disabled. I then enable the webservice with the command wsaman -i wsa1 -appname xxsfptexp -enable, which reports that the web service is enabled. If I run wsaman -i wsa1 -appname xxsfptexp -q, the system reports that the web service is enabled.

The full log entry is pasted below - if there's anything that you can think of that I missed - please let me know.



[19/11/27@15:39:15.469-0800] P-015698 T-http-8080-1 1 --- --- Log entry types activated: WSADefault,
[19/11/27@15:40:24.147-0800] P-015698 T-http-8080-3 2 wsa1 Admin-Provider Enabling Web Service application xxsfptexp
[19/11/27@15:41:12.989-0800] P-015698 T-http-8080-2 2 xxsfptexp 4GL-Provider Error in SOAP request execution: Connect Failure: Application Service xxsfptexp Unknown at NameServer at Host localhost Port 5162. (8234) (10926)
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
Do you have more than one nameserver running on this box? Is it possible that the nameserver listening on port 5162 is unrelated to this web service, e.g. it's from a different DLC version?
 

Stefan

Active Member
Additionally, do you have an AppServer that is named (or has a service name) xxsfptexp? Which coincidentally happens to be the name of your web service. We generally have one AppServer which services all web services, the AppServer to use for a web service can be configured in the web service properties (I think you do need to disable the web service to able to edit the properties).
 
Stefan - Thanks for the quick reply. I believe that the only Appserver is called "test_ws" (nsman -q output pasted below), which is what I'm expecting.

I'm trying to deploy my own web service with a service name of xxsfptexp, and hoping it can run under test_ws. Is it an issue with how I'm deploying or enabling the web service?

[danp@linuxserver scripts]$ nsman -name NS1 -q
OpenEdge Release 10.1C04 as of Fri May 29 21:51:17 EDT 2009
\

Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for NS1 (8288)
Connecting to NS1 (8276)

NameServer NS1 running on Host blalinux06.barksdale.cranecn.com Port 5162 Timeout 30 seconds.
Application Service UUID Name Host Port Weight Timeout

WS.test_WS
3ffc2085cb20f69b:-4098b40c:16586e31f7c:-8000 WS.test_WS linuxserver.domainsomewhere.com/172.25.0.238 20000 0 30

[danp@linuxserver scripts]$ \
 

Stefan

Active Member
A broker with WS prefix is a WebSpeed broker - you need an AppServer broker (prefix = AS)
 
Stefan - Thanks - (Again) - It turns out that there is an Appserver broker with the AS prefix, and it appears to be running. Is the issue with how I'm deploying and enabling the code? (Pasted below)

I'm deploying the web service using the command wsaman -i wsa1 -wsm /home/dpacker/xxsfptexp.wsm -deploy
I'm enabling the web service using the command wsaman -i wsa1 -appname xxsfptexp -enable

The web service appears to be enabled when I run wsaman -name wsa1 -list:

[dpacker@server ~]$ wsaman -name wsa1 -list
OpenEdge Release 10.1C04 as of Fri May 29 21:51:17 EDT 2009

Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for wsa1 (8288)
List of Web Services at wsa1:
xxsfptexp
Target NameSpace: urn:services-progress-com:sfptexp
Status : ENABLED

[dpacker@server ~]$ nsman -i NS1 -q
OpenEdge Release 10.1C04 as of Fri May 29 21:51:17 EDT 2009

Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for NS1 (8288)
Connecting to NS1 (8276)
NameServer NS1 running on Host server.company.com Port 5162 Timeout 30 seconds.
Application Service UUID Name Host Port Weight Timeout
WS.test_WS
3ffc2085cb20f69b:-4098b40c:16586e31f7c:-8000 WS.test_WS server.company.com/172.25.0.238 20000 0 30
AS.test_AS
3ffc2085cb20f69b:50121a0a:16586e31ff5:-8000 AS.test_AS server.company.com/172.25.0.238 1300 0 30
[dpacker@server ~]$
 
Last edited:

Stefan

Active Member
Your initial error:

xxsfptexp 4GL-Provider Error in SOAP request execution: Connect Failure: Application Service xxsfptexp Unknown at NameServer at Host localhost Port 5162. (8234) (10926)

indicates that the NameServer is fine, but that it does not know which AppServer should be handling xxsfptexp - this /may/ be the default when deploying how you are deploying - this /may/ be contained in your wsm file - this /may/ also be ignored due to some bug.

There are two options:

1. add xxsfptexp to the application service names (on the broker properties of your AppServer - this defaults to the name of your AppServer)
2. adjust the properties of your web service to point to your AppServer
 
Thank you - I'll try it out this afternoon.
 
#2 didn't work :(
For #1 - are you talking about adding it in ubroker.properties? Or somewhere else?

Thanks!
 
Stefan - I resolved the issue - I didn't correctly implement your second suggestion.

Thank you again for all of your assistance. I really appreciate it!
 

Stefan

Active Member
For #1 - are you talking about adding it in ubroker.properties? Or somewhere else?
Yes, but since I always use the OpenEdge Explorer GUI, I do not have the property name in the ubroker.properties file handy - its OpenEdge 11.7 Documentation

But since you got the web service pointing to the correct appserver, it's moot.
 
Top