A job with state=error produces a null pointer exception in JOC

Current Situation

When an job has the state=error, this is not reflected in JOC.
Instead of this a null pointer exception is thrown

url: /jobs
body:
{"jobschedulerId":"scheduler_joc_cockpit","compact":true,"folders":[

]}

url: /job_chain
body:

url: /job_chains
body:
{"jobschedulerId":"scheduler_joc_cockpit","compact":false,"folders":[

],"maxOrders":5}

How to reproduce:

create an order with this job

<job>
   <script  language="java:javascript">
        <![CDATA[
function spooler_process(){
    var order = spooler.create_order();
    order.id = "ń";
    var job_chain = spooler.job_chain("/job_chain1");
    job_chain.add_order(order);
   return false;
}
        ]]>
    </script>
</job>

Desired Behaviour

When a job is in error state this should be reflected by JOC.