Interpreting Error message

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Interpreting Error message

yannick
Hi,
can anybody help me with interpreting this error message?

<ows:Exception exceptionCode="NoApplicableCode">
    <ows:ExceptionText>Error while executing the embedded process for: i.group</ows:ExceptionText>
  </ows:Exception>
  <ows:Exception exceptionCode="JAVA_StackTrace">
    <ows:ExceptionText>org.n52.wps.server.ExceptionReport: Error while executing the embedded process for: i.group
        at org.n52.wps.server.request.ExecuteRequest.call(ExecuteRequest.java:716)
        at org.n52.wps.server.request.Request.call(Request.java:1)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 0
        at java.util.Arrays$ArrayList.get(Arrays.java:2866)
        at java.util.Collections$UnmodifiableList.get(Collections.java:1211)
        at org.n52.wps.server.grass.GrassProcessDelegator.run(GrassProcessDelegator.java:192)
        at org.n52.wps.server.request.ExecuteRequest.call(ExecuteRequest.java:685)
        ... 5 more</ows:ExceptionText>
  </ows:Exception>
  <ows:Exception exceptionCode="JAVA_RootCause">
    <ows:ExceptionText>0</ows:ExceptionText>
    <ows:ExceptionText>java.lang.ArrayIndexOutOfBoundsException: 0
        at java.util.Arrays$ArrayList.get(Arrays.java:2866)
        at java.util.Collections$UnmodifiableList.get(Collections.java:1211)
        at org.n52.wps.server.grass.GrassProcessDelegator.run(GrassProcessDelegator.java:192)
        at org.n52.wps.server.request.ExecuteRequest.call(ExecuteRequest.java:685)
        at org.n52.wps.server.request.Request.call(Request.java:1)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)</ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>

I get it when sending an execute-request for a GRASS-module (i.group). Since I am not experienced with the xml encoding, there might be a mistake which I am not able to find:

<wps:Execute service="WPS" ...>

  <ows:Identifier>i.group</ows:Identifier>

  <wps:DataInputs>
    <Input>
      <ows:Identifier>group</ows:Identifier>
      <wps:LiteralData dataType="xs:string">gruppe</wps:LiteralData>
    </Input>

    <Input>
      <ows:Identifier>subgroup</ows:Identifier>
      <wps:LiteralData dataType="xs:string">subgruppe</wps:LiteralData>
    </Input>

    <wps:Input>
      <ows:Identifier>input</ows:Identifier>
      <wps:Reference mimeType="image/tiff" xlink:href="http://yannick-tylle.de/wps/ls46_sub2_geo.tif"/>
    </wps:Input>

  </wps:DataInputs>

  <ProcessOutputs>
    <Output>
      <ows:Identifier>stdout</ows:Identifier>
      <wps:Reference mimeType="text/plain"/>
    </Output>
  </ProcessOutputs>
</wps:Execute>


The DescribeCoverage is the same like in the demo: http://geoprocessing.demo.52north.org:8080/wps/WebProcessingService?request=DescribeProcess&Service=WPS&version=1.0.0&identifier=i.group
Reply | Threaded
Open this post in threaded view
|

Re: Interpreting Error message

BenjaminPross
Hello Yannick,

The syntax or the execute request is not correct. The WPS doesn't find the requested output because of this.
I would recommend a tool like Eclipse or the 52°North client API to create requests. I attached a syntactically correct request [1]. However, this will not bring you farther, I fear. The wps_grass_bridge doesn't support sdout outputs at the moment. Also, for each request a new workspace is created. So you will not be able to use the grouped raster. I guess that is the reason why we disabled this module in the first place.. I will see if I can find a workaround, but I can't promise anything..

Cheers,

Benjamin

[1]i..group.xml