Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-19732

Websphere 6.1 classloader preferences documentation for com.atlassian.jira.plugin.JiraOsgiContainerManager

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      The current WebSphere 6.x documentation at http://confluence.atlassian.com/display/JIRA/Installing+JIRA+on+IBM+Websphere+6.x does not mention the requirement to amend the default classloader policy. If the classloaded is not changed from the default the following is logged in the WebSphere System.out:

      [11/15/09 19:40:11:139 CST] 00000035 SystemOut     O 2009-11-15 19:40:11,138 WebContainer : 5 ERROR     [plugin.event.impl.DefaultPluginEventManager] Plugin Event Listener 'com.atlassian.jira.plugin.JiraOsgiContainerManager@5cb25cb2' th
      rew an error on event 'com.atlassian.plugin.event.events.PluginFrameworkStartingEvent@31e031e': Detected older version (4.0 or earlier) of OSGi.  If using WebSphere 6.1, please enable application-first (parent-last) classloading and the
       'Single classloader for application' WAR classloader policy.
      

      Full stack trace is attached as 406.txt

      Having this documented before starting JIRA will reduce the frustration a user would experience when installing JIRA under WebSphere 6.1.

      Attachments

        Issue Links

          Activity

            People

              rosie@atlassian.com Rosie Jameson [Atlassian] (Inactive)
              pdzwart PdZ (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: