Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1083

Enable profiling in SecurityServerClientImpl to capture Crowd profiling information from JIRA or Confluence

    • 6
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

          [CWD-1083] Enable profiling in SecurityServerClientImpl to capture Crowd profiling information from JIRA or Confluence

          DonnaA added a comment -

          Attaching new profiling JAR for Crowd 1.5.

          DonnaA added a comment - Attaching new profiling JAR for Crowd 1.5.

          DonnaA added a comment -

          This functionality will not be available in 1.5 but I will continue to add new JAR files for new releases until this is available.

          DonnaA added a comment - This functionality will not be available in 1.5 but I will continue to add new JAR files for new releases until this is available.

          DonnaA added a comment -

          Attaching a client JAR for 1.4.3 profiling.

          DonnaA added a comment - Attaching a client JAR for 1.4.3 profiling.

          The reason why this currently isn't in the release is because we need to have the "UBER" jar in place.

          I am trying to limit the direct dependencies on the integration client as much as possible to make it easier for our users who are integrating with no atlassian systems.

          This is why I trimmed back the client and was able to remove the dependency on atlassian-core, adding atlassian-profiling as it is now will just cause us more pain (support wise) than I am willing to accept at the moment.

          So once we go 'uber', we can add the profiling

          Jus.

          Justin Koke added a comment - The reason why this currently isn't in the release is because we need to have the "UBER" jar in place. I am trying to limit the direct dependencies on the integration client as much as possible to make it easier for our users who are integrating with no atlassian systems. This is why I trimmed back the client and was able to remove the dependency on atlassian-core, adding atlassian-profiling as it is now will just cause us more pain (support wise) than I am willing to accept at the moment. So once we go 'uber', we can add the profiling Jus.

          DonnaA added a comment -

          Until this functionality is added to the crowd-integration-client JAR permanently, you can TEMPORARILY replace the crowd-integration-client JAR file in either JIRA or Confluence's WEB-INF/lib directory with one of the attached. Use the 1.4.1 JAR if using Crowd 1.4.x. Use the 1.3.2 JAR if using Crowd 1.3.x.

          Once the JAR is in place, restart the client application (e.g. JIRA or Confluence) and enable profiling in the client application (Admin -> Logging & Profiling). The resulting logs should contain additional profiling information about Crowd performance.

          Once testing is complete, restore the original crowd-integration-client JAR file and restart your client app.

          DonnaA added a comment - Until this functionality is added to the crowd-integration-client JAR permanently, you can TEMPORARILY replace the crowd-integration-client JAR file in either JIRA or Confluence's WEB-INF/lib directory with one of the attached. Use the 1.4.1 JAR if using Crowd 1.4.x. Use the 1.3.2 JAR if using Crowd 1.3.x. Once the JAR is in place, restart the client application (e.g. JIRA or Confluence) and enable profiling in the client application (Admin -> Logging & Profiling). The resulting logs should contain additional profiling information about Crowd performance. Once testing is complete, restore the original crowd-integration-client JAR file and restart your client app.

            Unassigned Unassigned
            donna@atlassian.com DonnaA
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: