Return to Issues Table 

Teamengine crashes while testing WMS 1.1.1

Issue ID#:
923
Category:
WMS 1.1.1
Type:
Issue
Status:
Closed (Change Required)
Priority:
High
Entered By:
Goerke, Sebastian
Created On:
2014-01-07 03:40:38
Updated By:
Bermudez, Luis
Last Update:
2014-07-24 19:03:29
Assigned To:
Goerke, Sebastian

Original Issue Details:

Testing the following WMS service leads into a complete crash of the current test run:


http://ngwd-bdnes.cits.nrcan.gc.ca/service/gin/wms/mediator/gin_en?request=GetCapabilities&version=1.1.1&service=WMS


It seems that it is just a normal test case failure which leads into that crash. TE should not crash the way it does.


18
Status: new
Assigned To: Martell, Richard

An exception occurred when trying to process viewSessionLog.jsp:

org.xml.sax.SAXParseException; lineNumber: 35; columnNumber: 38; Character reference "&#26" is an invalid XML character.

The last teamengine entry in the stack trace is com.occamlab.te.util.LogUtils.readLog(LogUtils.java:107).

Now this is a control character (Substitute, SUB). It appeared in the response entry in the log for the test wmsops-getmap-params-layers-5 (assertion: "When the layer in a GetMap request is invalid, then the response is an exception"):


<request>
  <url>http://ngwd-bdnes.cits.nrcan.gc.ca/service/gin/wms/mediator/gin_en?</url>;
  <method>get</method>
  <param name="SrS">EPSG:4326</param>
  <param name="LaYeRs">NonExistant</param>
  <param name="StYlEs"/>
  <param name="ReQuEsT">GetMap</param>
  <param name="HeIgHt">96</param>
  <param name="FoRmAt">image/png</param>
  <param name="VeRsIoN">1.1.1</param>
  <param name="BbOx">-0.0042,-0.0024,0.0042,0.0024</param>
  <param name="WiDtH">168</param>
</request>

The actual response entity is a completely transparent PNG image, not the expected ServiceExceptionReport. The media type should be checked before trying to evaluate an XPath expression against a (possibly) non-XML entity.


 

Hours Worked: 0.00
Entered By: Martell, Richard - 2014-10-23 11:54:13
18
Status: new
Assigned To: Martell, Richard

If no parser is specified an XML response entity is assumed. Perhaps try using the HTTPParser and asserting that the Content-Type header corresponds to an XML entity; the test should then fail cleanly.


<parsers:HTTPParser>
<parsers:parse>
  <parsers:NullParser/>
  </parsers:parse>
</parsers:HTTPParser>
Hours Worked: 0.00
Entered By: Martell, Richard - 2014-10-23 11:54:13
Status: Closed (Change Required)
Assigned To: Goerke, Sebastian

fixed within revision 6497

Hours Worked: 0.00
Entered By: Goerke, Sebastian - 2014-05-05 09:16:52
Status: Fixed - Requires Review
Assigned To: Goerke, Sebastian

Fixed deployed in OGC Beta Testing Facility 20140619: https://github.com/opengeospatial/cite/issues/15


 

Hours Worked: 0.00
Entered By: Bermudez, Luis - 2014-06-20 09:58:02
Status: Closed (Change Required)
Assigned To: Goerke, Sebastian

Hours Worked: 0.00
Entered By: Bermudez, Luis - 2014-07-24 19:03:29