-
Suggestion
-
Resolution: Fixed
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.
- is related to
-
JRASERVER-19728 Update JNDI DS documentation for WebSphere from 5.1 to 6.1
- Closed
- relates to
-
JRASERVER-19729 WebSphere 6.1 JNDI DS Provider - PostgreSQL JDBC provider implementation classname needs to be stipulated
- Closed
-
JRASERVER-19731 Suspected extraneous integration step for JIRA on WebSphere 6.1
- Closed
Added the log message to the "Deploy JIRA in Websphere" section of the document http://confluence.atlassian.com/display/JIRA/Installing+JIRA+on+IBM+Websphere+6.x