Clarity

It has been a recuring problem when employees report for WIP adjustments being slow. We do flush the cache which resolves the issues for time being. But next day the same issue reappers. Do we have a permanent solution for this concern? Also we found some errors in bg logs..do not know if they are of any importance here .....

ERROR 2010-07-09 09:59:44,350 [http-443-Processor6] [niku].[Niku Web Control] (USX21879:6816172__9ffa855:createWipAdjustmentSearchReturn) Servlet.service() for servlet Niku Web Control threw exception

java.lang.IllegalStateException: Current state = FLUSHED, new state = CODING_END

at java.nio.charset.CharsetEncoder.throwIllegalStateException(CharsetEncoder.java:941)

at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:537)

at sun.nio.cs.StreamEncoder$CharsetSE.flushLeftoverChar(StreamEncoder.java:358)

at sun.nio.cs.StreamEncoder$CharsetSE.implClose(StreamEncoder.java:414)

at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:160)

at java.io.OutputStreamWriter.close(OutputStreamWriter.java:222)

Thanks.

could you suggest any further info, such as what v of clariy? db type and version? which screen / function is it particular to? what is the size of your implementation? eg 000s of users? 000,000s of transactions?

samos wrote:

could you suggest any further info, such as what v of clariy? db type and version? which screen / function is it particular to? what is the size of your implementation? eg 000s of users? 000,000s of transactions?

Hello Samos,

We are on Clarity v8.1 SP2 , MSQL server 2005. This problems starts occuring mainly durin WIP adjustments. approximately 100+ users use this functionality.

Do let me know if you need any further information.

Thanks