IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 4.5.0, 4.6.0, 4.7.0
    • Code reviews
    • None

      Problem Definition

      As described on the Email Notifications Not Being Sent article, Fisheye/Crucible may lose the connection to the network and when trying to send an email, the default settings allow it to wait indefinitely for a connection to the SMTP server. This connection then sits open and does not allow any new emails to be sent until the application is restarted.

      This can be resolved by applying the Connection timeout and Timeout in the user interface (from the Administration >> Global Settings >> Server >> Mail Server >> Edit config user interface).

      If the timeouts are set, the following can be found in config.xml, otherwise the parameters are omitted.

      <smtp ... connectionTimeout="1200" timeout="1200"
      

      Suggested Solution

      Apply the suggested timeouts by default.

      Workaround

      Manually apply the timeouts.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • Icon: Bug Bug
              • Resolution: Unresolved
              • Icon: Low Low
              • None
              • 4.5.0, 4.6.0, 4.7.0
              • Code reviews
              • None

                Problem Definition

                As described on the Email Notifications Not Being Sent article, Fisheye/Crucible may lose the connection to the network and when trying to send an email, the default settings allow it to wait indefinitely for a connection to the SMTP server. This connection then sits open and does not allow any new emails to be sent until the application is restarted.

                This can be resolved by applying the Connection timeout and Timeout in the user interface (from the Administration >> Global Settings >> Server >> Mail Server >> Edit config user interface).

                If the timeouts are set, the following can be found in config.xml, otherwise the parameters are omitted.

                <smtp ... connectionTimeout="1200" timeout="1200"
                

                Suggested Solution

                Apply the suggested timeouts by default.

                Workaround

                Manually apply the timeouts.

                        Unassigned Unassigned
                        lpater Lukasz Pater
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        6 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            lpater Lukasz Pater
                            Affected customers:
                            1 This affects my team
                            Watchers:
                            6 Start watching this issue

                              Created:
                              Updated: