No announcement yet.
  • Filter
  • Time
Clear All
new posts

    "top-level exteption" in IDACall when returning bad status from export-fetch call.

    I just had a bug where i sent in some invalid data when doing an export from a grid.

    I have the DS configured to call a Spring web service, and my service behaved correctly as far as i can tell, insofar as that it returns a DSResponse with an error code.

    However, In my logs i got a nullpointer, is that normal behavior? I suppose i cant return an error code back to the client since it's exporting, but still?

    server-side log:
    2018-05-19 21:43:40.125 ERROR com.isomorphic.servlet.IDACall - com.isomorphic.servlet.IDACall top-level exception
    java.lang.NullPointerException: null
        at com.isomorphic.rpc.RPCManager.completeResponse( ~[isomorphic-core-rpc-6.0-p20171202.jar:na]
        at com.isomorphic.rpc.RPCManager.send( ~[isomorphic-core-rpc-6.0-p20171202.jar:na]
        at com.isomorphic.servlet.IDACall.processRPCTransaction( [isomorphic-core-rpc-6.0-p20171202.jar:na]
        at com.isomorphic.servlet.IDACall.processRequest( [isomorphic-core-rpc-6.0-p20171202.jar:na]
        at com.isomorphic.servlet.IDACall._processRequest( [isomorphic-core-rpc-6.0-p20171202.jar:na]
        at com.isomorphic.servlet.IDACall.doPost( [isomorphic-core-rpc-6.0-p20171202.jar:na]
    Thoughts appreciated.
    Last edited by mathias; 19 May 2018, 12:08.

    This is fixed and will be available in nightly builds since May 24 (today). This was caused by dsResponse not having data set. In case of error, in addition to status code, we normally expect error message to be set as data, but it is not required.