NAVTEQ_Support_1
Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Mock sending extra characters after header
Hi, We have defined this response to be delivered by our mock: <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <getChargePointInfoResponse xmlns="urn://Vas/Cs/2010/12/"></getChargePointInfoResponse> </s:Body> </s:Envelope> And this is what we see as raw response when querying that mock from SoapUI: HTTP/1.1 200 OK Content-Type: application/soap+xml;charset=UTF-8 Content-Encoding: gzip Transfer-Encoding: chunked Server: Jetty(6.1.x) <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <getChargePointInfoResponse xmlns="urn://Vas/Cs/2010/12/"></getChargePointInfoResponse> </s:Body> </s:Envelope> So far so good... But our system which was running against that mock was seeing some extra characters there which caused problems so I investigated inside SoapUI with http log and this is what I saw: Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "POST /mockVasPublisherServiceSoap HTTP/1.1[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "Accept-Encoding: gzip,deflate[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "Content-Type: application/soap+xml;charset=UTF-8;action="/GetChargePointInfo"[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "User-Agent: Jakarta Commons-HttpClient/3.1[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "Host: 127.0.0.1:8088[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "Content-Length: 282[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="urn://Vas/Cs/2010/12/">[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " <soap:Header>[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " <ns:subscriberIdentity>navteq</ns:subscriberIdentity>[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " </soap:Header>[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " <soap:Body>[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " <ns:getChargePointInfoRequest/>[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " </soap:Body>[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "</soap:Envelope>" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "HTTP/1.1 200 OK[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "HTTP/1.1 200 OK[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "Content-Type: application/soap+xml;charset=UTF-8[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "Content-Encoding: gzip[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "Transfer-Encoding: chunked[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "Server: Jetty(6.1.x)[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "B" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "B" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[0x1f][0x8b][0x8][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x85][0x90]A[0xb][0x82]0[0x18][0x86][0xef]A[0xff]a[0xec][0xae][0xdf]T[0xba][0xc][0xf5][0x90]t[0x8][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[0xa2] [0xba][0xe]]*[0xe8]6[0xfc]V[0xb3] [0x9f][0xd2][0xea]&[0xdd][0xbe][0xf7][0xf0]</[0xef][0x97]"[0xdf][0xa9][0xa7][0xec][0xb4][0x91]d[0xec];[0x85][0x1c]3[0xda]Xk8[0x80]s.tI[0xa8][0x87][0x1a]b[0xc6][0x12]`[0x1b]@-L =@[0xf3][0xf5][0x8a][0x10][0x92]"[0xdf][0xea][0xea][0xe5][0xf1][0x11][0xdb][0x5]A[0x4][0xb7][0xe3][0xe1]R6[0xb2][0x17]A[0xab][0xd0][\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "UJ[0xfa][0xa3][0xaa][0xff][0x94][0xef][0x9b]+ki[0x8b]F[0xc][0xb5]<[0xe9]V[0xd9][0xbd][0xba][0xeb][0xb3]D[0xa3][0x15][0xfa][0x15][0x19]}[0xc]jr][0x5]B[0x81][0x93]'b[0x10][0xc5]@[0xf3][0x14][0x96]Q?[0x7]>{[0xa6]4[0x9f][0xdf][0xef][0xe4]oc[0x1b][0xf4]d*[0x1][0x0][0x0]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "0" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\n]" Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r][\n]" Note those two lines with "B" in them, after the header, right before XML code starts. Where are those coming from? I can see that they depend on the actual size of message being sent and is most probably hexadecimal number. So what can we do about this??? Thanks, roman4KViews0likes5CommentsRe: Decreasing memory usage
Hi Ole, yes, things I found there and at http://www.soapui.org/Working-with-soap ... usage.html helped with our issues. I was also passing that information to some other teams here who were struggling and it saved them a lot of time and frustration. roman1.3KViews0likes0CommentsRe: Decreasing memory usage
hmmm, posting reply to myself but right after posting the original question i tried searching the forum and found this: viewtopic.php?f=2&t=8259&p=23957&hilit=memory#p23957 so we are gonna try that first and see if it helps. sorry for the noise roman1.3KViews0likes0CommentsDecreasing memory usage
Hi, we have projects with large amount of tests where fairly long responses are being processed. To give you some idea - one project has over 700 tests and majority of them end up with responses longer than 300kb which are then asserted with various groovy scripts. Running the whole project is a tough nut then - we are hitting memory limit of SoapUI/Java and tests are then failing or even if we manage to run all of them, SoapUI is not able to generate report. I know that splitting project into smaller ones would help but those tests are really logically connected and we would like to keep them together. I was thinking about possibility to clear periodically results of tests which were already completed, something like special test step that would discard those large responses. Is there something you can recommend to help with this? Thanks, roman2.8KViews0likes3CommentsTestrunner sets property after loadscript execution
Hi, I'm not sure if this is intentional feature or a bug but apparently if I specify project property while executing testrunner with -P[property setup], this is actually done only after project loadscript is executed. Seems really wrong (at least for me) since my loadscript uses the one property I'm modifying through the -P parameter. Any thoughts? Thanks, roman1.8KViews0likes1CommentExecute from here
Hi, suggestion for a small feature - sometimes my test case contains many steps (20+) and if it fails somewhere in the middle, there are situations when I want to continue with execution so what I need to do is open subsequent steps one-by-one and manually execute every one of them. It would be nice to have something like "Execute from here" which would start with that particular step, no matter what the circumstances are. Thanks, roman3.5KViews0likes2Comments