Selection Key Context Task.call(Selection Key Context Task.java:59) at grizzly. Abstract Thread Pool$Work(Abstract Thread Pool.java:532) at Edit: I have found form the stacktrace that exception is coming on this line Workbook workbook = new Workbook(Path, load Options);.Abstract Thread Pool$Worker.run(Abstract Thread Pool.java:513) at Utility.convert Excel(Utility.java:132) at com.delta. Native Method Accessor Impl.invoke0(Native Method) at sun.reflect.

Application Filter Filter(Application Filter Chain.java:217) at org.primefaces.webapp.filter.

File Upload Filter(File Upload Filter.java:77) at org.apache.

It's probably either JDK 1.6 default implementation (Sun's SJSXP), or Woodstox; or if you are unlucky, stax reference implementation...

(unlucky since it is buggy) These are also most common reasons why naive java testing benchmarks give useless results: if you do not account for both (i.e. Validating Stream Reader) are used in my code unintentionally.

As you have stated, I believe that the behaviour of the inconsitent results in the intial runs should be due to JIT.

Yes, it should be sufficient as jar contains META-INF/services entries to 'register' woodstox as a stax impl.

So now I am stuck here and unable to find why this is happening?

Note: In search of this problem, I found this answer on aspose forum but it is not helpful and feasible(to check all the classes present in jars placed in lib). aspose.com/community/forums/aspose.cells-product-family/19/… We recommend you to kindly try our latest version of the product (e.g v7.7.x (JAVA)) as we did remove some inter dependencies jars and have written/included our own custom XML parsers to perform some XML operations in the product.

Http Protocol Chain.execute(Http Protocol Chain.java:79) at grizzly.