| Author |
Message
|
| srinivas07438 |
 Posted: Wed Jul 08, 2015 1:30 am Post subject: syncrequest http error returned message broker, HTTP/1.1 404 |
 |
|
Apprentice
Joined: 26 Jun 2013
Posts: 28
|
Hi,
I have created a web service message flow to call the web service. they have HTTPS, three levels of security 1. username Token, Encryption and Signing. I have set up policy set and policy set binding for encryption and signing.
For Username token, password digest and nonce are added in the soap header as follows.... here user name is token generated from the service.
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Header.wsse:Security.(XMLNSC.Attribute)soapenv:mustUnderstand=true;
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Header.wsse:Security.wsse:UsernameToken.wsse:Username='vdkznrxWwbjYf9ln90ijyJRlVyQHBILzx6TsxbtKNUKafRkNOsHKnJOCzUDVnRpdQweDmwMBZKAmPxyT9CHXdUCj7yDuc01jnqwhGeTZ2UXYYbEHcYdE2lyYBQDcqoMAeRGgrllyNN8GjBi7uJuALoJt9HsRN7B4ts8xyMSd0TDHHP0Y7R0JayDdvWu93Bclun0t1uwA';
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Header.wsse:Security.wsse:UsernameToken.wsse:Password.(XMLNSC.Attribute)Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest';
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Header.wsse:Security.wsse:UsernameToken.wsse:Password='RVJmVqHOxwtl0YNTVcd43SkNWPk=';
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Header.wsse:Security.wsse:UsernameToken.wsse:Nonce ='MTQzNjMzODYzMDY1NQ==';
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Header.wsse:Security.wsse:UsernameToken.wsse:Created = '1436338630659';
I am able to get response when i hit from the soap ui but broker I am getting the error
"syncrequest http error returned message broker, HTTP/1.1 404"
Please suggest where I made mistake |
|
| Back to top |
|
 |
| nelson |
| Posted: Wed Jul 08, 2015 5:29 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| Code: |
| syncrequest http error returned message broker, HTTP/1.1 404 |
404 means you were unable to communicate with the server. I should check that the Web Service URL is reachable from broker.. |
|
| Back to top |
|
|
| srinivas07438 |
| Posted: Wed Jul 08, 2015 11:46 pm Post subject: syncrequest http error returned message broker, HTTP/1.1 404 |
|
|
Apprentice
Joined: 26 Jun 2013
Posts: 28
|
Thanks for the reply Nelson,
Before I got SSl socket exception but after setting the sll configuration it was cleared, and now its giving the syncrequest http error returned message broker, HTTP/1.1 404.
That means successfully handshake is done so I think web service url is reachable by broker.
Updated message header construction is
SET Nonce=common.GetNonce();
SET PasswordDigest=common.GetPasswordDigest(password);
SET OutputRoot.XMLNSC.soap:Envelope.(XMLNSC.NamespaceDecl)xmlns:soap = 'http://www.w3.org/2003/05/soap-envelope';
SET OutputRoot.XMLNSC.soap:Envelope.(XMLNSC.NamespaceDecl)xmlns:v2 = 'http://sita.aero/iborders/aras/TelephoneEventManagementServiceWSDLType/V2';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.(XMLNSC.Attribute)soap:mustUnderstand=true;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.(XMLNSC.NamespaceDecl)xmlns:wsse = 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.(XMLNSC.NamespaceDecl)xmlns:wsu = 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.(XMLNSC.Attribute) wsu:Id = 'UsernameToken-116';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsse:Username='t0lRu1CKPcqQx5Z0f1bgU4k7UcSAtFjE9i8VJoYcP5byOZPO8MBLodV4TIuzb0jQzibESOyXNXluRQgbVDf5EaLj3CRyw8jtW1jzVXDq5VnT02pxKGcoOwoYtnl0pIiMaamE3lMrKUo9gkqMiURKMcXK2sKk14ro3E6wddJuoqJOKWWDSI6Gcn2I1d0Vmdhc4AFuHOIN';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsse:Password.(XMLNSC.Attribute)Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsse:Password=PasswordDigest;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsse:Nonce.(XMLNSC.Attribute)EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsse:Nonce =Nonce;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsu:Created = CAST(CURRENT_TIMESTAMP AS CHARACTER FORMAT 'yyyy-MM-dd'||'''T'''||'HH:mm:ss.SSS'||'''z''');
I set the policy set and policy set binding for message encryption and signing |
|
| Back to top |
|
|
| srinivas07438 |
| Posted: Thu Jul 09, 2015 12:26 am Post subject: |
|
|
Apprentice
Joined: 26 Jun 2013
Posts: 28
|
|
| Back to top |
|
|
| srinivas07438 |
| Posted: Mon Jul 13, 2015 1:48 am Post subject: syncrequest http error returned message broker, HTTP/1.1 404 |
|
|
Apprentice
Joined: 26 Jun 2013
Posts: 28
|
My flow is like
soapinputnode-->computenode-->soapreq node-->soap replynode
I giving input using soapui and in the compute node i constructed a message and also set the token security in soap header. the esql is as follows
[DECLARE Token, PasswordDigest, Nonce CHARACTER;
DECLARE password CHARACTER 'S1ta@123';
SET Environment.Variables.Request.OT_EAI_HEADER = InputRoot.XMLNSC.*:*[<].OT_EAI_HEADER;
SET Environment.Variables.Request.MESSAGE = InputRoot.XMLNSC.*:*[<].Request;
SET Nonce=common.GetNonce();
SET PasswordDigest=common.GetPasswordDigest(password);
SET OutputRoot.XMLNSC.soap:Envelope.(XMLNSC.NamespaceDecl)xmlns:soap = 'http://www.w3.org/2003/05/soap-envelope';
SET OutputRoot.XMLNSC.soap:Envelope.(XMLNSC.NamespaceDecl)xmlns:v2 = 'http://sita.aero/iborders/aras/TelephoneEventManagementServiceWSDLType/V2';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.(XMLNSC.Attribute)soap:mustUnderstand=true;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.(XMLNSC.NamespaceDecl)xmlns:wsse = 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.(XMLNSC.NamespaceDecl)xmlns:wsu = 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.(XMLNSC.Attribute) wsu:Id = 'UsernameToken-116';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsse:Username='vAyawXD2DdSjIIcSf5EP1n1DDrnX6m9G1E8Js5TkkZsEkkRFuB6aNqML4pQHHF6GlTX2tRuivjZmUHOC0xe9sJnzXFmcF5WhtDoNkmUm3GnYEvSsdyY5rJ8PL1VX1R2TOwg0aUWUL2vF4hxAZCqAV7pVsOzWaJ59xTT739znyilBopgAzWP6MkD5ijVev0jW718SJU1V';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsse:Password.(XMLNSC.Attribute)Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsse:Password=PasswordDigest;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsse:Nonce.(XMLNSC.Attribute)EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary';
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsse:Nonce =Nonce;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Header.wsse:Security.wsse:UsernameToken.wsu:Created = CAST(CURRENT_TIMESTAMP AS CHARACTER FORMAT 'yyyy-MM-dd'||'''T'''||'HH:mm:ss.SSS'||'''z''');
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.PhoneNumber = Environment.Variables.Request.MESSAGE.eventData.SubscriberNumber;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.IssueDate = Environment.Variables.Request.MESSAGE.eventData.IssueDate;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.Type = Environment.Variables.Request.MESSAGE.eventData.Type;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.SimSerialNumber = Environment.Variables.Request.MESSAGE.eventData.SimSerialNumber;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.CardType = Environment.Variables.Request.MESSAGE.eventData.CardType;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.PaymentDetail.PaymentMethod = Environment.Variables.Request.MESSAGE.eventData.PaymentDetail.PaymentMethod;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.LocationofIssue = Environment.Variables.Request.MESSAGE.eventData.LocationofIssue;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.ContactNumber1 = Environment.Variables.Request.MESSAGE.eventData.ContactNumber1;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.ContactNumber2 = Environment.Variables.Request.MESSAGE.eventData.ContactNumber2;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.Email = Environment.Variables.Request.MESSAGE.eventData.Email;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.OrganisationName = Environment.Variables.Request.MESSAGE.eventData.OrganisationName;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.JobTitle =Environment.Variables.Request.MESSAGE.eventData.JobTitle;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.EventData.OrganisationNumber =Environment.Variables.Request.MESSAGE.eventData.OrganisationNumber;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.FamilyName =Environment.Variables.Request.MESSAGE.personData.FamilyName;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.GivenName = Environment.Variables.Request.MESSAGE.personData.GivenName;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.Birth.Date = Environment.Variables.Request.MESSAGE.personData.Birth.Date;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.Birth.Place = Environment.Variables.Request.MESSAGE.personData.Birth.Place;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.Nationality = Environment.Variables.Request.MESSAGE.personData.Nationality;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.Gender = Environment.Variables.Request.MESSAGE.personData.Gender;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.IdDocumentData.(XMLNSC.Attribute)IsEndorsee = Environment.Variables.Request.MESSAGE.personData.IdDocumentData.IsEndorsee;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.IdDocumentData.DocumentType = Environment.Variables.Request.MESSAGE.personData.IdDocumentData.DocumentType;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.IdDocumentData.DocumentNumber = Environment.Variables.Request.MESSAGE.personData.IdDocumentData.DocumentNumber;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.IdDocumentData.DocumentIssueDate = Environment.Variables.Request.MESSAGE.personData.IdDocumentData.DocumentIssueDate;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.IdDocumentData.DocumentIssueCountry = Environment.Variables.Request.MESSAGE.personData.IdDocumentData.DocumentIssueCountry;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.IdDocumentData.DocumentExpiryDate = Environment.Variables.Request.MESSAGE.personData.IdDocumentData.DocumentExpiryDate;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.IdDocumentData.DocumentIssueAuthority = Environment.Variables.Request.MESSAGE.personData.IdDocumentData.DocumentIssueAuthority;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.PersonData.IdDocumentData.DocumentIssuePlace = Environment.Variables.Request.MESSAGE.personData.IdDocumentData.DocumentIssuePlace;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.ProviderData.ProviderId = Environment.Variables.Request.MESSAGE.providerData.ProviderId;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.ProviderData.OutletId = Environment.Variables.Request.MESSAGE.providerData.OutletId;
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.ProviderData.UserId = Environment.Variables.Request.MESSAGE.providerData.UserId;]
I use policy set and policy set binding for signing and encryption. For configuration i used the following link
[http://www-01.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.samples.wssecsamp.doc/doc/setup_extend_ws_security.htm?cp=SSMKHH_9.0.0%2F2-5-1-8-2-4-1-0]
and also setup the keystore and trustatore also.
But I am getting the exception "syncrequest http error returned message broker, HTTP/1.1 404" after Soaprequest node where it catches in failure terminal.
And I want to know how to see what request message going to webservice, because I use policy set and policy set binding for signing and excryption. So I dont know wether it working or not
[/url][/code] |
|
| Back to top |
|
|
| srinivas07438 |
| Posted: Mon Jul 13, 2015 2:07 am Post subject: syncrequest http error returned message broker, HTTP/1.1 404 |
|
|
Apprentice
Joined: 26 Jun 2013
Posts: 28
|
Can any one please provide links or document to setup policy set and policy set binding for signing and encryption, I followed the info center for webservice consumer setup but getting an exception
Thanks in advance |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Jul 13, 2015 2:50 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
If you followed the instructions detailed in the documentation and it is still failing then...
1) you did script all the commands used didn't you?
2) It is repeatable on a newly created broker (using scripts)?
Then
It might be time to raise a PMR.
As for your code, I really do hope that you don't use this
| Code: |
SET OutputRoot.XMLNSC.soap:Envelope.soap:Body.v2:SubmitTelephoneEventRequest.v2:TelephoneNumberIssued.ProviderData.
|
in every line. This sort of construct went out of fashion oh, around 10 years ago when references became available.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| srinivas07438 |
| Posted: Mon Jul 13, 2015 3:11 am Post subject: syncrequest http error returned message broker, HTTP/1.1 404 |
|
|
Apprentice
Joined: 26 Jun 2013
Posts: 28
|
Thanks for the reply smdavies99
As I used the steps given in infocenter to implement my requirement, So If you ever done ws-security (signing and encryption) share your knowledge.
As this is the first time I am doing ws-security (signing encryption), may be I am missing some steps when configuring, I am unable to find the mistake...
Thanks for your suggestion regarding the ESQL code as this implementation is for testing so kept like that with out using references... |
|
| Back to top |
|
|
| ganesh |
| Posted: Mon Jul 13, 2015 10:40 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| Take a service trace that might have more information than the exception tree also what node are you using to make a call to external web service? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jul 13, 2015 11:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ganesh wrote: |
| Take a service trace that might have more information than the exception tree |
I think you mean user trace. While a service trace does have more information, the extra information is only usable is you can see the broker source code. Which means you only need to do this when IBM asks for it in a PMR.
But you're right - a user trace will have much more potentially useful information than the exception tree.
| ganesh wrote: |
| also what node are you using to make a call to external web service? |
| srinivas07438 wrote: |
My flow is like
soapinputnode-->computenode-->soapreq node-->soap replynode |
I'm guessing the SOAP Request node is the one making the call to the external web service.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jul 13, 2015 11:10 am Post subject: Re: syncrequest http error returned message broker, HTTP/1.1 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| srinivas07438 wrote: |
| As this is the first time I am doing ws-security (signing encryption), may be I am missing some steps when configuring, I am unable to find the mistake... |
How have you attempted to verify the configuration?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| srinivas07438 |
| Posted: Mon Jul 13, 2015 11:45 am Post subject: 404 |
|
|
Apprentice
Joined: 26 Jun 2013
Posts: 28
|
Hi Vitor and ganesh,
Thanks for the response, I enable the user trace and service trace as well but it is not clear. it is also giving info which giving in exception tree.
Ganesh I am using soap request node to hit the webservice.
service trace o/p
| Code: |
RecoverableException BIP3691S: A SOAP request encountered an HTTP error while making an HTTP request. The HTTP request was made to the destination ''https://82.178.125.245/TelephoneEventManagementV2/TelephoneEventManagementServiceV2.wsdl''. The HTTP status line that was returned was: ''HTTP/1.1 404 Not Found''.
An error occurred during an HTTP request.
Check that the remote server is responding and that the request is specified correctly. See subsequent messages for information pertinent to this error. |
|
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jul 13, 2015 12:35 pm Post subject: Re: 404 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| srinivas07438 wrote: |
| it is not clear. |
| srinivas07438 wrote: |
| Code: |
| See subsequent messages for information pertinent to this error. |
|
What do the subsequent messages say?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ganesh |
| Posted: Tue Jul 14, 2015 1:54 pm Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
HTTP 404 error -
1) Check if the end point url is correct ( I see a .wsdl in your url, do you really need that ?)
2) If URL is correct check if the service is available.
3) Try to get the wsdl using a browser. |
|
| Back to top |
|
|
| psyconic |
| Posted: Tue Jul 14, 2015 5:31 pm Post subject: |
|
|
Novice
Joined: 17 Jun 2015
Posts: 11
|
I am not sure if this helps : -
Make sure you are sending your tests to the correct port.
IIB9 was sending my tests to broker wide http listener , port 7080
when at execution group level I needed to be testing against port 7800.
I had to use something other than IIB9 broker to run my tests as I couldn't tell it to stop using port 7080 (Broker wide httpListener).
In my system at one stage I had another http node that was intercepting my test and trying to process the call and generating errors of course, as the criteria I set for the restful service also satisfied the restful url call I was making. So it was infact being processed by another webservice and not the one I was thinking it was. That is probably not your case but it was a silly thing I once did that snuck up on me. |
|
| Back to top |
|
|
|
|
