title: java.util.concurrent.ExecutionException: java.lang.NullPointerException Error
body: <p>The following code snippet doesnt throw any error when executed in a standalone mode. When I deploy this into a web server [implementing a server's interface and added as JAR into classpath], I get </p>
  
  <pre><code> java.util.concurrent.ExecutionException: java.lang.NullPointerException
  at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
  at java.util.concurrent.FutureTask.get(Unknown Source)
  at com.nbis.process.JSON_2_File_Split_V004.fn_1_parserEntity(JSON_2_File_Split_V004.java:256)
  at com.nbis.process.JSON_2_File_Split_V004.fn_0_primaryCaller(JSON_2_File_Split_V004.java:177)
  at com.nbis.process.JSON_2_File_Split_V004.execute(JSON_2_File_Split_V004.java:151)
  </code></pre>
  
  <p>Code Snippet:</p>
  
  <pre><code>this.callable = new JSON_3_File_Process_V005(this.originalFileName, this.inProgressDirLoc, this.processedDirLoc, "[" + jSONRecord.toString() + "]", this.dataMDHolder, this.dataAccIDValueMap, this.dataCountryNameValueMap);
  String[] fullContent = null;    
  try {
      fullContent = executor.submit(this.callable).get();
  } catch (ExecutionException e) {
      StringWriter errors = new StringWriter();
      e.printStackTrace(new PrintWriter(errors));
      log.info("Srii: " + errors.toString());
      executor.shutdown();
      return 7;
      } 
  </code></pre>
  
  <p>Adding the get's return value to an ExecutorCompletionService would be an option, but would that not kill the concept of asynchronous processing? In other words, I collect in StringBuilder the output string from callable get and store to a disk when the get count reaches a specific number. Once data is emitted to disk, I refresh the StringBuilder. This way I push data to a disk at regular intervals without having to keep them in memory.</p>
  
  <p>Any suggestions as to what wrong am I doing here? Appreciate any inputs. Thank you.</p>