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

JIRA 4.0 does not work under WebSphere 6.1

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High (View bug fix roadmap)
    • 4.0.1
    • 4.0
    • Installation

    • WAS 6.1.0.0
      J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20060504 (JIT enabled)
      J9VM - 20060501_06428_lHdSMR
      JIT - 20060428_1800_r8
      GC - 20060501_AA
      Ubuntu 9.04

      The plugin system has trouble starting under WebSphere 6.1. The plugin system just seems to start failing. I tested with the ServletContext patch but this just brought more errors to the front. I have attached the log files for your viewing pleasure.

      I have the VM if you are interested.

        1. ag-refimpl-websphere.txt
          12 kB
        2. atlassian-jira-8thDEC.txt
          134 kB
        3. Gadget error-8Dec.jpg
          Gadget error-8Dec.jpg
          24 kB
        4. log.tar.bz2
          23 kB
        5. websphere.jpg
          websphere.jpg
          52 kB
        6. websphere.txt
          40 kB

            [JRASERVER-19421] JIRA 4.0 does not work under WebSphere 6.1

            JoachimA added a comment -

            It seems that this issue has resurfaced again in JIRA 4.1.2 in WAS 6.1 with the exact stack trace. The problem will be solved by adding the following to web.xml which is located in <JIRA_install>/atlassian-jira/WEB-INF/ directory:

            ...
<!-- This is a dummy servlet mapping to trick WebSphere 6.1.0.x to push the request through the filter chain,
	         so that the REST servlet filter plugin can be properly mapped to and intercept the rest URLs
    -->
    <servlet-mapping>
        <servlet-name>noopservlet</servlet-name>
        <url-pattern>/rest/*</url-pattern>
    </servlet-mapping>
...

            Please restart JIRA after that. Considering re-open this bug again?

            JoachimA added a comment - It seems that this issue has resurfaced again in JIRA 4.1.2 in WAS 6.1 with the exact stack trace. The problem will be solved by adding the following to web.xml which is located in <JIRA_install>/atlassian-jira/WEB-INF/ directory: ... <!-- This is a dummy servlet mapping to trick WebSphere 6.1.0.x to push the request through the filter chain, so that the REST servlet filter plugin can be properly mapped to and intercept the rest URLs --> <servlet-mapping> <servlet-name>noopservlet</servlet-name> <url-pattern>/rest/*</url-pattern> </servlet-mapping> ... Please restart JIRA after that. Considering re-open this bug again?

            sladey added a comment -

            As indicated in comments above we have had success running JIRA 4.0.1 on WebSphere 6.1.0.27. The version of WebSphere is important as we have seen issues running with WebSphere 6.1.0.3.

            sladey added a comment - As indicated in comments above we have had success running JIRA 4.0.1 on WebSphere 6.1.0.27. The version of WebSphere is important as we have seen issues running with WebSphere 6.1.0.3.

            Veenu Bharara (Inactive) added a comment -

            Verified the issue with JIRA 4.0.1 and Websphere 6.1.0.27. JIRA is working fine without any issues.

            Veenu Bharara (Inactive) added a comment - Verified the issue with JIRA 4.0.1 and Websphere 6.1.0.27. JIRA is working fine without any issues.

            Chris Mountford added a comment -

            juggling into QR from Verified

            Chris Mountford added a comment - juggling into QR from Verified

            Jed Wesley-Smith (Inactive) added a comment -

            A relevant APAR can be found here

            Jed Wesley-Smith (Inactive) added a comment - A relevant APAR can be found here

            Brian Lane added a comment -

            Hello,

            As we continue to work this issue, we are going to need to push this issue over to 4.02.

            As part of 4.02 this is one of the highest priority issues to resolve for that version. We continue to work on this issue, but the solution will probably not be fully realized in a release until 4.02 is shipped.

            Regards,

            Brian Lane
            JIRA Product Manager

            Brian Lane added a comment - Hello, As we continue to work this issue, we are going to need to push this issue over to 4.02. As part of 4.02 this is one of the highest priority issues to resolve for that version. We continue to work on this issue, but the solution will probably not be fully realized in a release until 4.02 is shipped. Regards, Brian Lane JIRA Product Manager

            Tim Moore [Atlassian] added a comment -

            I can reproduce this with the base refapp, without gadgets installed.

            Tim Moore [Atlassian] added a comment - I can reproduce this with the base refapp, without gadgets installed.

            sladey added a comment -

            Linking in the corresponding AG issue - https://studio.atlassian.com/browse/AG-1178

            sladey added a comment - Linking in the corresponding AG issue - https://studio.atlassian.com/browse/AG-1178

            Tim Moore [Atlassian] added a comment -

            That error happens with both AG 1.1.2 and 2.0.0.rc2

            Tim Moore [Atlassian] added a comment - That error happens with both AG 1.1.2 and 2.0.0.rc2

            Tim Moore [Atlassian] added a comment -

            When I start up the AG refimpl in WebSphere I get an error immediately that prevents it from starting: ag-refimpl-websphere.txt

            Tim Moore [Atlassian] added a comment - When I start up the AG refimpl in WebSphere I get an error immediately that prevents it from starting: ag-refimpl-websphere.txt

              jed Jed Wesley-Smith (Inactive)
              bbain bain
              Affected customers:
              8 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: