Custom Query (2765 matches)

Sometimes RasJ crashes, returning an exception that references an internal error.

For example, for the query

<wcs:GetCoverage xmlns:wcs="http://www.opengis.net/wcs/2.0"
    xmlns:gml="http://www.opengis.net/gml/3.2"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    service="WCS" version="2.0.0">
    <wcs:id gml:id="rgb"/>
    <wcs:trimDimension>
        <wcs:dimension>x</wcs:dimension>
        <wcs:trimLow>200</wcs:trimLow>
        <wcs:trimHigh>202</wcs:trimHigh>
    </wcs:trimDimension>
    <wcs:trimDimension>
        <wcs:dimension>y</wcs:dimension>
        <wcs:trimLow>250</wcs:trimLow>
        <wcs:trimHigh>259</wcs:trimHigh>
    </wcs:trimDimension>
</wcs:GetCoverage>

sometimes gives the following error in the tomcat logs:

rasj[0] rasj: rasdaman Java API. rasdaman 6.1test -- generated Thu Feb 22 19:50:39 CET 2007.
rasj[0]  Using server http://kahlua.eecs.jacobs-university.de:9001
rasj[0] RnpBaseClientComm.communicate: error: rcv io exception: null
[11:07:29] ERROR: [PetascopeInterface] Runtime error : Internal client exception in class RnpBaseClientComm, method communicate(): (none).

...
...
[11:07:29] ERROR: [PetascopeInterface] Runtime error : Internal client exception in class RnpBaseClientComm, method communicate(): (none).

Caused by: rasj.RasClientInternalException: Internal client exception in class RnpBaseClientComm, method communicate(): (none).
        at rasj.rnp.RnpBaseClientComm.communicate(RnpBaseClientComm.java:184)
        at rasj.rnp.RnpBaseClientComm.sendRequestGetAnswer(RnpBaseClientComm.java:105)
        at rasj.rnp.RasRNPImplementation.executeQueryRequest(RasRNPImplementation.java:848)
        at rasj.rnp.RasRNPImplementation.queryRequest(RasRNPImplementation.java:389)
        at rasj.odmg.RasOQLQuery.execute(RasOQLQuery.java:233)
        at petascope.wcs2.server.ops.GetCoverage.executeRasqlQuery(GetCoverage.java:368)
....
....

Cannot fully reproduce this bug, even though I have encountered it several times while working with petascope and rasj. It seems to occur intermitently, once in a while. I have no work-around at the moment.

• make rasmgr give sign of life less frequently
• make sign of life not appear in the log

the systemtest/ test suite needs to be reactivated by adding a comprehensive set of integration tests, in addition to the unit tests which are already available per module directory. This should run with "make check".