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)15Views0likes1CommentDocument 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.... TIA296Views0likes1CommentCollaborator Server operation with Java 17
The IT department has performed a Java update on the server, as it is necessary for the operation of other software on the server. Unfortunately, the operation of the CollabServer 14.4.14400 is now no longer possible. It would be nice to have a CollabServer installation that supports Java 17. Furthermore it would be desirable to know how many users are active and how many users are logged in but without activity for x minutes.141Views0likes0CommentsAWS Code Commit Support
Howdy, Please add Code Collaborator support for AWS Code Commit repository integrations to the web client. Example of this current functionality can be found here: https://support.smartbear.com/collaborator/docs/source-control/git.html https://support.smartbear.com/collaborator/docs/source-control/repo-hosting/index.html In the same way that Github, Bitbucket, and Azure can easily be integrated to the Collaborator, I would like for this process to also function with AWS Code Commit Repos. I may currently use Code Collab and AWS Code Commit via the client gui and local changes, but I would also like to have direct repo integration like the hosted repos do. Thanks.1.3KViews1like2CommentsCollaborator 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. Thanks672Views0likes2CommentsScan 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 tool442Views0likes0Comments