Collaborator client error (CollabClientInvalidInputException)

[bkambach]

Upgraded Collaborator server to 11.3 (build 11301).

With both client versions 11301 and 11000, get the following error trying to create a new review:

!ENTRY com.smartbear.collaborator.ui 4 0 2018-07-11 16:24:34.643
!MESSAGE Could not finish Review Job
!STACK 0
com.smartbear.ccollab.client.CollabClientInvalidInputException:
JSON API Error: Permission denied (Code: IOError )
at com.smartbear.ccollab.client.commands.Command.sendBatch(Command.java:519)
at com.smartbear.ccollab.client.commands.AbstractAddChangelistCommand.executeJson(AbstractAddChangelistCommand.java:261)
at com.smartbear.ccollab.client.commands.admin.review.AbstractReviewCommand.executeJson(AbstractReviewCommand.java:208)
at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:433)
at com.smartbear.collaborator.Collaborator.executeJson(Collaborator.java:219)
at com.smartbear.collaborator.jobs.AddToReviewJob.processChanges(AddToReviewJob.java:223)
at com.smartbear.collaborator.jobs.AddToReviewJob.run(AddToReviewJob.java:134)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

[bkambach]

One additional detail: When I log into Collaborator (in the browser), a new review was created but none of the files were added. 

So, even though the error indicates "Permission denied", the client authenticated enough to create the review.

[AlexeyKryuchkov]

Hi,

May I request the whole log from Eclipse?

Thanks!

[bkambach]

I've attached the full log (which was actually split into 5 separate files).

In each of those files, I've sanitized file names, file content, etc., which you'll see as a note of the form "<BK Sanitized ...>".

[alwaysonnet]

I am also getting this error? Is there any resolution?

[bkambach]

We traced this down to some of the files/folders in the collaborator content cache (<Collaborator root>/tomcat/collaborator-content-cache) being owned by root insted of the lower-priviledged user normally used to run the server.

Recursively resetting the ownership of this directory remedied the problem.

[alwaysonnet]

Hi,

I don't see the folder collaborator content cache in our setup. Are there any other places to look for this folder?

[bkambach]

My installation just uses the default location, but the Collaborator documentation has some details about alternate locations:

https://support.smartbear.com/collaborator/docs/server/admin-tasks/content-storage.html

"If you decide to use the non-default content cache location, you can change it by editing the XML file: <Collaborator server installation>/tomcat/conf/Catalina/localhost/ROOT.xml. Find the Parameter element with the content-cache name attribute. The value attribute of this element should be the path to the content cache. Relative paths are interpreted relative to the installation directory."

[alwaysonnet]

You are right. File specifies an alternative location for content-cache. I see there is lot of disk space available too (close to 8GB) and permissions look good too. all the CC users have read and execute permissions.

[alwaysonnet]

I have restarted the services and everything is back to normal.