Forum Discussion

DennisWCook's avatar
DennisWCook
Occasional Contributor
2 years ago

New Collaborator install fails to load page.

New Collaborator 14.3.14302 install on Ubuntu 22 - Start page fails to load. No errors reported during installation.

What did I miss?

 

Error.log contains the following error ;

SEVERE: Servlet.service() for servlet [StartPage] in context with path [] threw exception
java.lang.IllegalStateException: Cannot call sendRedirect() after the response has been committed
at org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFacade.java:488)
at com.smartbear.ccollab.CollabCleanupFilter.doFilter(CollabCleanupFilter.java:60)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:177)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
at com.smartbear.ccollab.auth.AuthTicketValve.invoke(AuthTicketValve.java:32)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:360)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:891)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1784)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:829)

 

  • Hi, 

    Are you able to log in to Collaborator server, if Yes, please follow below steps to share dump file for analysis. Or if not please share snap.

     

    1. Click the "System" link at the bottom of the page (you might have to be an administrator to see that).
    2. In the "Server Backup/Debugging Dump" box at the top of the page, select the following settings:
    a. "Server Logs" => "Include Server Logs"
    b. "File Contents" => "No file content"
    c. "Which Data" => "System configuration only - no review data"
    Then click on the "Download Dump File" button. Send me the resulting zip file.

  • srinivasraj's avatar
    srinivasraj
    2 years ago

    Hi, I noticed RTC service plugins and their dependencies are caught in the log, i.e. when Collaborator is installed since you selected it during the installation steps and which is not required (hope this is the window - pic attached).

     

    The logs you see there, are looking for the RTC configuration inside Collaborator server which is not available in Collaborator.

     

    Please choose RTC only if you're using it in Collaborator server or else you can uncheck the RTC service and install Collaborator, it's works fine.

     

    If you're using RTC then please use this link https://support.smartbear.com/collaborator/docs/source-control/rtc/index.html to know more about RTC Service in Collaborator.

     

    Hope this helps.

     

     

  • DennisWCook's avatar
    DennisWCook
    2 years ago
    Thanks - I thought that I had turned off the RTC in this last install attempt. Trying to reduce down to only the basics.

    The current error when attempting to load the page is here;

    May 25, 2023 10:38:28 AM org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet [StartPage] in context with path [] threw exception
    java.lang.IllegalStateException: Cannot call sendRedirect() after the response has been committed
    at org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFacade.java:488)
    at com.smartbear.ccollab.CollabCleanupFilter.doFilter(CollabCleanupFilter.java:60)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:177)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
    at com.smartbear.ccollab.auth.AuthTicketValve.invoke(AuthTicketValve.java:32)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:360)
    at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399)
    at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
    at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:891)
    at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1784)
    at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
    at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
    at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.base/java.lang.Thread.run(Thread.java:829)


    Thanks Again

    -Dennis
  • Did you solve this?  If so, how?

    I had same issue with "couldn't create connection to database server".

    For us, using RHEL8 java fips conflicts with selinux fips.   Try turning off fips and try restarting again.

     

    (Long term solution was to disable just java fips by editing <java_distribution>/<java_version>/conf/security/java.security and change security.useSystemPropertiesFile=false)

  • May I know the Java version you are using and is it a Linux machine? 

    If installed Collaborator server in your system, please share the error.log file (you'll get in Collab installed dir) and collab.log (<Collb insta dir>/tomcat/logs/collab.log)

    will check and let you know the update.

    • DennisWCook's avatar
      DennisWCook
      Occasional Contributor

       

      java --version
      openjdk 11.0.19 2023-04-18
      OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu120.04.1)
      OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu120.04.1, mixed mode, sharing)

       

      uname -a
      Linux engttmcocoappprd1 5.15.0-72-generic #79~20.04.1-Ubuntu SMP Thu Apr 20 22:12:07 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

      • srinivasraj's avatar
        srinivasraj
        Staff

        The log file has lot SQL errors that is the JDBC connection pool error "Could not create connection to database server". 

         

        Somewhere in the MySQL configuration (Connector/J) is not properly configured or Connector/J is not using the desired version.

         

        Please check this link for more information on MySQL with Collaborator configuration.

        https://support.smartbear.com/collaborator/docs/server/install/db/mysql.html

         

  • Hi, 

    Are you able to log in to Collaborator server, if Yes, please follow below steps to share dump file for analysis. Or if not please share snap.

     

    1. Click the "System" link at the bottom of the page (you might have to be an administrator to see that).
    2. In the "Server Backup/Debugging Dump" box at the top of the page, select the following settings:
    a. "Server Logs" => "Include Server Logs"
    b. "File Contents" => "No file content"
    c. "Which Data" => "System configuration only - no review data"
    Then click on the "Download Dump File" button. Send me the resulting zip file.

    • DennisWCook's avatar
      DennisWCook
      Occasional Contributor

      Hello - Thanks for replying. 

      No, I have no Collab page @ all. It fails to load.

      Looking into the ccollab_server/error.log, initially there are now errors when starting the collab_server. 

      But once Firefox tries to load the page I see errors in the log,
      INFO: WELD-000119: Not generating any bean definitions from com.smartbear.rtc.service.RtcClientConfigurationResource because of underlying class loading error: Type org.eclipse.core.runtime.IProgressMonitor not found. If this is unexpected, enable DEBUG logging to see the full error.
      May 25, 2023 9:09:57 AM org.jboss.weld.bootstrap.MissingDependenciesRegistry handleResourceLoadingException
      INFO: WELD-000119: Not generating any bean definitions from com.smartbear.rtc.service.RtcWorkItemResource$ApprovalState because of underlying class loading error: Type com.ibm.team.workitem.common.model.IApprovalState not found. If this is unexpected, enable DEBUG logging to see the full error.

       

      Thanks

       

      -Dennis

       

      • srinivasraj's avatar
        srinivasraj
        Staff

        Hi, I noticed RTC service plugins and their dependencies are caught in the log, i.e. when Collaborator is installed since you selected it during the installation steps and which is not required (hope this is the window - pic attached).

         

        The logs you see there, are looking for the RTC configuration inside Collaborator server which is not available in Collaborator.

         

        Please choose RTC only if you're using it in Collaborator server or else you can uncheck the RTC service and install Collaborator, it's works fine.

         

        If you're using RTC then please use this link https://support.smartbear.com/collaborator/docs/source-control/rtc/index.html to know more about RTC Service in Collaborator.

         

        Hope this helps.