SMB exceptions with jcifs in the trace tell us that JCIFS couldn't talk to
your windows share server. That's all we can tell though.
Karl
On Mon, Nov 15, 2021 at 7:24 AM ritika jain
wrote:
> Hi,
>
> Raising the concern above again, to process only 60k of document (when
> clock issue is fixed
Hi,
Raising the concern above again, to process only 60k of document (when
clock issue is fixed too), job process is not progressing , its being stuck
for like days. So had to restart the docker container every time for it to
process.
This time now we are getting this :- Timeout Exception. What
One hour is quite a lot and will wreak havoc on the document queue.
Karl
On Tue, Nov 9, 2021 at 7:08 AM ritika jain wrote:
> I have checked, there is only one hour time difference between docker
> container and docker host
>
> On Tue, Nov 9, 2021 at 4:41 PM Karl Wright wrote:
>
>> If your
I have checked, there is only one hour time difference between docker
container and docker host
On Tue, Nov 9, 2021 at 4:41 PM Karl Wright wrote:
> If your docker image's clock is out of sync badly with the real world,
> then System.currentTimeMillis() may give bogus values, and ManifoldCF uses
If your docker image's clock is out of sync badly with the real world, then
System.currentTimeMillis() may give bogus values, and ManifoldCF uses that
to manage throttling etc. I don't know if that is the correct explanation
but it's the only thing I can think of.
Karl
On Tue, Nov 9, 2021 at
