Open Source Document Management System | OpenKM

Got it...


Made the changes.. I did not understand your previous post well enough.

I did get

Sourced file: inline evaluation of: ``import org.slf4j.Logger; import org.slf4j.LoggerFactory; import com.openkm.api . . . '' : Undefined argument: level : at Line: 16 : in file: inline evaluation of: ``import org.slf4j.Logger; import org.slf4j.LoggerFactory; import com.openkm.api . . . '' : ( "Folder: {}" , level )

So I changed it to:

log.info("Folder: {}", fld.getPath());

and it seems to run now..

Hopefully it will complete and not run out or memory or stack space.

THANKS!

Keep us updated, if it fails we can try another solution.

I ran it for three days and started to get an error message in the catalina.out about day three.
Thousands of times in the logs..

Any ideas?

It restarted fine...

better if you add other post for this warning, because has no relation with initial post

At first the script wouldn't run due to a JDBC issue. I was able to resolve that by changing the connection string.

Then then the script wouldn't complete due to unknown issues but you offered a slight change to the script.

Then the script doesn't complete due to whatever the issue is now as related to the previous post I made and the error message.

Now you tell me I need start a new thread due to the subject not being proper although the underlying issue is not being solved.

So every time I get a new error message due to this horrible bug in 6.2.5 and the recursive directory issue I must start a new thread with a different subject?

What subject thread do you suggest? I only need to resolve this issue but I am no closer at this point and now I guess semantics are more important than the resolution huh?

I supposed has no relation with the script execution. I do not know the reason why it happens, take in mind when you start the script there's a session alive several hours and seems days, here could be some problem on it, but I suspect could be something with crontab tool name "Refresh User Items" or "User Items Serialize". Try stopping it while you're executing the process.

From database query you can check if the nodes are being deleted ( value should decrease on time ): Finally I understand your problem and how are you feeling, but also understand us. At the end of day we expend time answering and trying to help community users as well as we can. Unfortunatelly you have been affected by a tedious bug, sorry for it, although version 6.2.X is a very stable version and it has been passed all of our quality test we had not detected ( on customers scenario we can directly solve it on server, but is not your case and are some rules what can not be break down ).

On next newsletter we will include an alert about this issue recommending al 6.2.x version upgrade to 6.3.x