Forum Discussion

BahamutX's avatar
BahamutX
New Contributor
2 months ago

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)

Server Administration
  • BahamutX's avatar
    BahamutX
    New Contributor
    2 months ago

    Issue resolved by reinitializing database to fresh. Unsure of the exact issue but this appears to have resolved the issue. No changes were made to the actual mysqld setup or access so this appears to be a database issue rather than server access issue.