Details
-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
4.0
-
Websphere 7.0.0.0
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxi3260sr2-20080818_01(SR2))
Ubuntu 9.04
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260-20080816_22093 (JIT enabled, AOT enabled)
J9VM - 20080816_022093_lHdSMr
JIT - r9_20080721_1330ifx2
GC - 20080724_AA)
JCL - 20080808_02Websphere 7.0.0.0 java version "1.6.0" Java(TM) SE Runtime Environment (build pxi3260sr2-20080818_01(SR2)) Ubuntu 9.04 IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260-20080816_22093 (JIT enabled, AOT enabled) J9VM - 20080816_022093_lHdSMr JIT - r9_20080721_1330ifx2 GC - 20080724_AA) JCL - 20080808_02
-
4
-
Description
I was unable to get JIRA 4.0 running on Websphere 7.0 (WAS 7.0). There are two main problems:
- Plugins do not start. It looks like there are some problems with either scanning packages or exporting them:
[13/10/09 11:29:03:996 EST] 0000000a OsgiPlugin W com.atlassian.plugin.impl.AbstractPlugin enable Unable to enable plugin 'com.atlassian.jira.rest' com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: com.atlassian.jira.rest at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:385) at com.atlassian.plugin.impl.AbstractPlugin.enable(AbstractPlugin.java:212) at com.atlassian.plugin.impl.AbstractDelegatingPlugin.enable(AbstractDelegatingPlugin.java:213) at com.atlassian.plugin.manager.PluginEnabler.enable(PluginEnabler.java:65) at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:544) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:151) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1275) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:224) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:210) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:63) at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42) at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1588) at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:350) at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:292) at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:99) at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:167) at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:722) at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:607) at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376) at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1162) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1313) at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:611) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:938) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:740) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2092) at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:437) at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:122) at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:380) at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$300(CompositionUnitMgrImpl.java:105) at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:928) at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527) Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle 33: package; (package=com.atlassian.jira.plugin.util) at org.apache.felix.framework.Felix._resolveBundle(Felix.java:1725) at org.apache.felix.framework.Felix._startBundle(Felix.java:1588) at org.apache.felix.framework.Felix.startBundle(Felix.java:1541)
- The worker threads cannot access the transaction manager. It appears that Websphere does not export the same JNDI namespace to our threads (e.g. services) that it does to its HTTP threads. Speak to Peter Z and/or Anton about this, it may just be problems with our instructions. We may need to use a special JNDI name that is consistent across both types of threads.
Attachments
Issue Links
- is duplicated by
-
JRASERVER-19980 JIRA v4.0.1 does not start on WebSphere v7.0: The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symb name...
- Closed
- is related to
-
JRASERVER-19421 JIRA 4.0 does not work under WebSphere 6.1
- Closed
-
JRASERVER-19389 The startup log causes an exception in WAS 7.0
- Closed
- relates to
-
JRASERVER-19379 JIRA 4 doesn't work with IBM JVM
- Closed