Code Collaborator won't Start
After successfully installing mysql and code collaborator and mysql, the code collaborator well not start properly. Any attempt to connect to the WebGUI just returns a completely blank page. Unfortunately the error below is not very descriptive. engswadm@app-lvn-bvg-47:/export/coco$ cat ./tomcat/logs/collab.log 2024-10-07 13:42:28,786 INFO localhost-startStop-1 org.jboss.weld.environment.servletWeldServlet - WELD-ENV-001008: Initialize Weld using ServletContainerInitializer 2024-10-07 13:42:28,806 INFO localhost-startStop-1 org.jboss.weld.Version - WELD-000900: 2.4.5 (Final) 2024-10-07 13:42:29,008 INFO localhost-startStop-1 org.jboss.weld.Bootstrap - WELD-000101: Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously. 2024-10-07 13:42:29,777 INFO localhost-startStop-1 org.jboss.weld.environment.servletTomcat - WELD-ENV-001100: Tomcat 7+ detected, CDI injection will be available in Servlets, Filters and Listeners. 2024-10-07 13:42:30,230 INFO localhost-startStop-1 com.smartbear.ccollab.auth.UserAuthenticators - Using authenticator type: com.smartbear.ccollab.auth.TomcatUserAuthenticator 2024-10-07 13:42:30,230 INFO localhost-startStop-1 com.smartbear.ccollab.auth.UserAuthenticators - Instantiating authenticator: com.smartbear.ccollab.auth.TomcatUserAuthenticator 2024-10-07 13:42:34,291 ERROR localhost-startStop-1 com.smartbear.ccollab.CollabReusable - Could not acquire engine object because the application is not started properly. javax.naming.NamingException: Could not create connection to database server. Attempted reconnect 3 times. Giving up. at org.apache.naming.NamingContext.lookup(NamingContext.java:856) at org.apache.naming.NamingContext.lookup(NamingContext.java:159) at org.apache.naming.NamingContext.lookup(NamingContext.java:827) at org.apache.naming.NamingContext.lookup(NamingContext.java:173) at com.smartbear.ccollab.CollabReusable.getDatabaseConnection(CollabReusable.java:521) at com.smartbear.ccollab.CollabReusable$1.createEngine(CollabReusable.java:267) at com.smartbear.ccollab.datamodel.manager.EngineManagerTrivial.acquire(EngineManagerTrivial.java:26) at com.smartbear.ccollab.CollabReusable.getEngine(CollabReusable.java:174) at com.smartbear.ccollab.CodeCollaborator.start(CodeCollaborator.java:205) at com.smartbear.ccollab.CollaboratorInitializationListener.contextInitialized(CollaboratorInitializationListener.java:85)19Views0likes1CommentDocument not uploading
HI all, I'm very new to Collaborator, but I was asked to quickly create a new Collaborator server a few weeks ago. I put it on a Rhel 8 VM, it's licensed and has been working normally for a few weeks. It is still using the internal database though, as I haven't had time to migrate it yet. Yesterday, I was notified that oone of the Devs couldn't upload a new document. He gets the "upload successful" message, but it doesn't actually get uploaded. I"ve tried the normal stuff, restarted the service, I rebooted the server, but the issue continues. I feel like it's something simple and to do with the internal database possibly, but I'm not sure what to try next to get the devs working again. Is anyone able to point me in the right direction to get this working? Edit: Not a diskspace issue. Users are accessing Collaborator through a web browser.This is on an air-gapped network and using LDAP in case it matters.... TIA298Views0likes1CommentCollaborator displays an HTTP 404 error
Hello, We've been using collaborator community 11.5.11500, and it works well. The collaborator server is upgrade to 14.3.14303 in 15th Jul, and now it shows 404 error. I'm not sure if the reason is that collaborator server is no longer community version anymore, and it has a 30-day limitation?😂 If so, can we back to the community version? I've tried the solution in this page:https://support.smartbear.com/collaborator/faq/collaborator-is-displaying-an-http-404-error/ It doesn't work. Thanks684Views0likes2CommentsScan Error meassage (submitted this question yesterday
Getting this error message in scan logs for groovy script: Error occurred while executing external script, returning null - MissingPropertyException: No such property: jiraCreds for class: Script1 I'm using the Checkmarx SAST tool442Views0likes0CommentsOption to not re-open review after comment
Hello, is there a way (admin option?) to not re-open a review after it's been completed, if someone puts a comment after the fact? Often times, the reviewer has already approved a review, and some other observer will put a comment to ask a question or propose a future modification. It would be nice for the author to be notified that such a comment has been added to the review. But right now this action will put the review from "completed" to back in "inspection". Meaning everyone is notified and all the reviewers will have to approve the review again!! that is the most annoying flow ever. Is there a way to disable that feature? I haven't found the option in the documentation. thanks, JMT528Views0likes1CommentHow to get Azure Boards work item info for recent GitHub PRs in a given repo?
have Git repos in GitHub and work items in Azure DevOps (Azure Boards). We are using the "Azure Boards" GitHub app, and thus when we addto a PR comment, it links to the right work item in Azure DevOps? We would like to create a list of recent GitHub pull requests that show the Azure Boards work item that is associatedand its parent work item. We could do this when our PRs were in Azure DevOps Git, but it seems tough to do so with PRs ion GitHub.587Views0likes0CommentsCollaborator Server 14.0.14001 excessive memory usage
My Collaborator server instance seems like it's got a memory leak. It was consuming 10 gigs of ram. Our peak usage in the last 30 days has been 6 users, probably not more than 3 or 4 simultaneously. After a restart, the Collaborator server process is sitting around 2 gigs of ram. 1) Is this expected/typical memory usage? 2) Is there a way to set a "max memory usage" parameter for the Collaborator server process?612Views0likes0Comments