| Author |
Message
|
| Esa |
 Posted: Mon Feb 20, 2012 5:12 am Post subject: |
 |
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| mqjeff wrote: |
| Esa wrote: |
You are right, MQ is out of question. This is a 'SOA Project'  |
So SOAP over JMS is out of the question because? |
mainly because it's a Microsoft endpoint |
|
| Back to top |
|
 |
| prasadpav |
| Posted: Mon Feb 20, 2012 5:15 am Post subject: |
|
|
Centurion
Joined: 03 Oct 2004
Posts: 142
|
fjb_saper wrote:
| Quote: |
| Don't quite agree... think SOAP over JMS where MQ just happens to be the JMS provider... |
If the service provider (which "Esa" is trying to call using SOAPRequest node) is aiming for WS-I Basic profile 1.0 compliance then SOAP/JMS may not be an option. |
|
| Back to top |
|
|
| mgk |
| Posted: Mon Feb 20, 2012 5:40 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1644
|
| Quote: |
| I would like to know if there is a way to make SOAPRequest node keep the connection alive so that it doesn't have to shake hands each time. |
I do not believe it should shake hands each time, unless your remote server is sending some form of "Connection: close" header on the reponse. Therefore, you may want to raise a PMR...
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| Esa |
| Posted: Mon Feb 20, 2012 6:04 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| mgk wrote: |
| Quote: |
| I would like to know if there is a way to make SOAPRequest node keep the connection alive so that it doesn't have to shake hands each time. |
I do not believe it should shake hands each time, unless your remote server is sending some form of "Connection: close" header on the reponse. Therefore, you may want to raise a PMR... |
Done already |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Mon Feb 20, 2012 10:03 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| Esa wrote: |
| I would like to know if there is a way to make SOAPRequest node keep the connection alive so that it doesn't have to shake hands each time. |
Which version of HTTP does the SOAPRequest node use? HTTP/1.0 does not enable persistent connections by default, and some HTTP/1.0 implementations may not handle them correctly. HTTP/1.1 is preferable for persistent connections. |
|
| Back to top |
|
|
| Esa |
| Posted: Tue Feb 21, 2012 4:47 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| rekarm01 wrote: |
| Esa wrote: |
| I would like to know if there is a way to make SOAPRequest node keep the connection alive so that it doesn't have to shake hands each time. |
Which version of HTTP does the SOAPRequest node use? HTTP/1.0 does not enable persistent connections by default, and some HTTP/1.0 implementations may not handle them correctly. HTTP/1.1 is preferable for persistent connections. |
With HTTPRequest node you can select which version to use, and also switch keepalive on for HTTP 1.1, but with SOAPRequest node you cannot. |
|
| Back to top |
|
|
| mgk |
| Posted: Tue Feb 21, 2012 5:16 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1644
|
| Quote: |
| With HTTPRequest node you can select which version to use, and also switch keepalive on for HTTP 1.1, but with SOAPRequest node you cannot. |
That's because HTTP/1.1 and KeepAlive are automatically "on" for the SOAPRequest node...
Kind Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Tue Feb 21, 2012 8:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| Esa wrote: |
| With HTTPRequest node you can select which version to use, and also switch keepalive on for HTTP 1.1, but with SOAPRequest node you cannot. |
The broker does allow for overriding HTTPVersion through the LocalEnvironment.
For HTTP/1.1, 'Connection' and 'Keep-Alive' are not the same thing.
| mgk wrote: |
| That's because HTTP/1.1 and KeepAlive are automatically "on" for the SOAPRequest node... |
Ok. It might still be worthwhile to examine the HTTP headers for both the request and response, to confirm the HTTP Version, and to determine if either the request or response message includes a "Connection: close" header. |
|
| Back to top |
|
|
| Esa |
| Posted: Tue Feb 28, 2012 7:36 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| rekarm01 wrote: |
| Ok. It might still be worthwhile to examine the HTTP headers for both the request and response, to confirm the HTTP Version, and to determine if either the request or response message includes a "Connection: close" header. |
The HTTP Response does not contain Connection: close header. But it confirms that HTTP 1.1. was used. The debugger does not show the HTTPRequest header that was sent. Neither does iptrace, because the traffic is SSL and the header is encrypted, too. |
|
| Back to top |
|
|
| rsr007 |
| Posted: Fri Aug 10, 2012 6:26 am Post subject: SOAPRequest node slowness |
|
|
Newbie
Joined: 10 Aug 2012
Posts: 2
|
I am a brand new user of this forum. I have the same issue that was reported by Esa and I see that the SOAPRequest Node is taking over 100 ms's more than the time taken by SOAP UI.
Just wanted to to check if there was any resolution that came out of Esa's PMR.
Thanks,
Ravi |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Aug 10, 2012 7:24 am Post subject: Re: SOAPRequest node slowness |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| rsr007 wrote: |
I am a brand new user of this forum. I have the same issue that was reported by Esa and I see that the SOAPRequest Node is taking over 100 ms's more than the time taken by SOAP UI.
Just wanted to to check if there was any resolution that came out of Esa's PMR.
Thanks,
Ravi |
There is something wrong with your configuration. You should be able to process 200 messages in 100 milliseconds.
See ftp://public.dhe.ibm.com/software/integration/support/supportpacs/individual/ip6p.pdf
page 21
| Quote: |
| The SOAPInput and SOAPReply nodes are are used in a message flow which implements a provider web service. The SOAPInput node is configured to enable validation ("Content and value"; SOAP Parser Options select "Build tree using XML schema data types"). A SOAP message is received by the broker via the SOAPInput node. A Compute node then copies the unmodified SOAP request message across to a SOAP response message, which is then sent via the SOAPReply node. |
Millisecond per message is measured in this performance test at 0.5 milliseconds.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| McueMart |
| Posted: Fri Aug 10, 2012 7:37 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
rsr007 mentioned he his having the same problems as reported by Esa. Esa was having issues using SOAP over https. The performance reports are using http. Therefore saying that rsr007 should be able to achieve 200 messages in 100 milliseconds isnt very helpful.
I would also be interested in the outcome of this PMR (purely for interests sake...). Was it due to SSL handshaking each time? Was the HTTP 1.1 Keep-alive not functioning correctly? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Aug 10, 2012 7:41 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| McueMart wrote: |
rsr007 mentioned he his having the same problems as reported by Esa. Esa was having issues using SOAP over https. The performance reports are using http. Therefore saying that rsr007 should be able to achieve 200 messages in 100 milliseconds isnt very helpful.
I would also be interested in the outcome of this PMR (purely for interests sake...). Was it due to SSL handshaking each time? Was the HTTP 1.1 Keep-alive not functioning correctly? |
I agree that the results of the PMR would be of interest.
I disagree with your statement that the performance report is not helpful. SSL handshake would not be 12,000 percent of the transaction time if the system were configured correctly.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| rsr007 |
| Posted: Fri Aug 10, 2012 9:06 am Post subject: SOAPRequest node slowness |
|
|
Newbie
Joined: 10 Aug 2012
Posts: 2
|
I forgot to mention earlier that I was just using plain http. I am not using SSL.
At this time I am more interested in the response time rather than the throughput and wanted to know why the SOAP Request node is performing much slower than invocation using SOAP UI.
Also, I tried the same webservice using the HTTPRequest node and it has the same delay, taking 100 to 150 millisecond more than the time taken by SOAPUI client.
I am planning to test the request thru HTTPRequest mode after changing broker properties to tcpNoDelay.
Not sure if that is also applicable to SOAPRequest Node. |
|
| Back to top |
|
|
| mgk |
| Posted: Fri Aug 10, 2012 9:26 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1644
|
| Quote: |
I am planning to test the request thru HTTPRequest mode after changing broker properties to tcpNoDelay.
Not sure if that is also applicable to SOAPRequest Node. |
Yes it does as the same setting applies to both nodes. Hopefully this do the trick for you.
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
|
|
