Have you tried using IE to hit the page (using both ports) http://LB:80/arsys/WSDL/ ... http://LB:8102/arsys/WSDL/ ...
This way you could verify the results of what they are getting -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Campbell, Paul (Paul) Sent: Friday, April 25, 2014 3:55 PM To: arslist@ARSLIST.ORG Subject: Re: Strange behavior of a Remedy WebService WSDL requests I am thinking so, but I suspect I'm going to have to get my load balancer admin to grab packets so I can see what they are actually requesting -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Friday, April 25, 2014 4:50 PM To: arslist@ARSLIST.ORG Subject: Re: Strange behavior of a Remedy WebService WSDL requests The difference appears to be the web server part (and port). One thing to remember is that everything is dynamically generated. The web server returned in the location is basically exactly what the web server sees itself as in that transaction instance. Is that app calling the web server by a different name? (or if they are calling the same load balancer, is the LB doing something different because of the port 80 vs 8102 ?) Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Campbell, Paul (Paul) Sent: Friday, April 25, 2014 3:00 PM To: arslist@ARSLIST.ORG Subject: Strange behavior of a Remedy WebService WSDL requests ** I have several different applications that are using the same Remedy hosted Custom Web Service and when these applications request the WSDL to get the endpoint, all of these applications but one are getting a correct endpoint as shown in the midtier log snippet below (I've replaced parts of the hostnames with a 1 for 1 character replacement with a * for security purposes) Correct Endpoint: <wsdl:service name="A2R_QS_CreateReferal_NewService"> <wsdl:port binding="s0:A2R_QS_CreateReferal_NewSoapBinding" name="A2R_QS_CreateReferal_NewSoap"> <soap:address location="http://p****a.e**.*****.com:80/arsys/services/ARService?server=p*****a&webService=A2R_QS_CreateReferal_New"/> </wsdl:port> </wsdl:service> But one application is getting the following endpoint returned, and for the life of me, I can't figure out why, the one bad one is getting this: <wsdl:service name="A2R_QS_CreateReferal_NewService"> <wsdl:port binding="s0:A2R_QS_CreateReferal_NewSoapBinding" name="A2R_QS_CreateReferal_NewSoap"> <soap:address location="http://f**p**c3.****.com:8102/arsys/services/ARService?server=p*****a&webService=A2R_QS_CreateReferal_New"/> </wsdl:port> </wsdl:service> All of these are calling our Mid-Tiers via a loadbalancer, the first example is the correct hostname for our loadbalancer, but the second is what I believe is the hostname of the calling application. When I load the WSDL in SoapUI, I get the correct endpoint. Our environment is a pair of midtiers version 7.6.04 ( no SP) hosted on Weblogic 11g, our remedy app servers are Remedy 7.6.04, all are running on RHEL6 Here is the whole request from the log for the app that is failing Apr 23, 2014 12:23:16 PM - FINE (com.remedy.log.WEBSERVICES) : WSDL Request:: server: p*****a webService: A2R_QS_CreateReferal_New Apr 23, 2014 12:23:16 PM - FINE (com.remedy.log.WEBSERVICES) : WSDL Content: <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions targetNamespace="urn:A2R_QS_CreateReferal_New" xmlns:s0="urn:A2R_QS_CreateReferal_New" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> . . . . <wsdl:service name="A2R_QS_CreateReferal_NewService"> <wsdl:port binding="s0:A2R_QS_CreateReferal_NewSoapBinding" name="A2R_QS_CreateReferal_NewSoap"> <soap:address location="http://f**p**c3.****.com:8102/arsys/services/ARService?server=p*****a&webService=A2R_QS_CreateReferal_New"/> </wsdl:port> </wsdl:service> </wsdl:definitions> Log file from a WSDL get request from SoapUI Apr 25, 2014 7:50:01 PM - FINE (com.remedy.log.WEBSERVICES) : WSDL Request:: server: p*****a webService: A2R_QS_CreateReferal_New Apr 25, 2014 7:50:01 PM - FINE (com.remedy.log.WEBSERVICES) : No security policy or security actions! Security filter processing skipped Apr 25, 2014 7:50:01 PM - FINE (com.remedy.log.WEBSERVICES) : WSDL Content: <?xml version="1.0" encoding="UTF-8"?>^M <wsdl:definitions targetNamespace="urn:A2R_QS_CreateReferal_New" xmlns:s0="urn:A2R_QS_CreateReferal_New" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";>^M . . . . <wsdl:service name="A2R_QS_CreateReferal_NewService">^M <wsdl:port binding="s0:A2R_QS_CreateReferal_NewSoapBinding" name="A2R_QS_CreateReferal_NewSoap">^M <soap:address location="http://p*****.e**.*****.com:80/arsys/services/ARService?server=p*****a&webService=A2R_QS_CreateReferal_New"/>^M </wsdl:port>^M </wsdl:service>^M </wsdl:definitions>^M Paul Campbell | Development Team Lead | TS&D SSBL, A2R WFE, and ESP Remedy Team | Avaya Client Services | | 678-421-5342 | Web Conference | Audio Conference +1-513-228-8888 |code: 4215342 Everyone needs deadlines. Even the beavers. They loaf around all summer, but when they are faced with the winter deadline, they work like fury. If we didn't have deadlines, we'd stagnate. Walt Disney _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
