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

ArrayIndexOutOfBoundsException when adding issue type scheme.

    • Icon: Support Request Support Request
    • Resolution: Resolved Locally
    • Icon: Medium Medium (View bug fix roadmap)
    • None
    • 3.4.2
    • None
    • JBoss 3.2.6 / Tomcat 5.0.28
      mysql 4.0.12
      JIRA compiled from source code (w/o modifications)

      When trying to confirm changes, using save button, on "Add Issue Types Scheme" screen, server has logged following problem, blocking flow control on that screen:

      java.lang.ArrayIndexOutOfBoundsException: 4096
      at org.apache.coyote.http11.InternalOutputBuffer.write(InternalOutputBuffer.java:688)
      at org.apache.coyote.http11.InternalOutputBuffer.sendStatus(InternalOutputBuffer.java:428)
      at org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processor.java:1531)
      at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:892)
      at org.apache.coyote.Response.action(Response.java:180)
      at org.apache.coyote.http11.InternalOutputBuffer.endRequest(InternalOutputBuffer.java:388)
      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:836)
      at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
      at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
      at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
      at java.lang.Thread.run(Thread.java:534)

      This happens only on JBoss 3.2.6 / Tomcat 5.0.28. With JBoss 4.0.2 / Tomcat 5.5 everything is fine.
      My problems is that production environment is still JBoss 3.2.6 and upgrading is unpredicted effort... first thing that comes to mind is to upgrade tomcat sar
      to newer version. Did you noticed problem mentioned above and have any workarounds?

      regards,
      andy

            [JRASERVER-8843] ArrayIndexOutOfBoundsException when adding issue type scheme.

            BrianH added a comment -

            Hi Andrew,

            Thanks for the update, great to hear that you have resolved you issue.

            The problem with the common-collections jar is a known issue with JBOSS, and we plan to add this to our online docuemtation.

            Thanks,
            Brian

            BrianH added a comment - Hi Andrew, Thanks for the update, great to hear that you have resolved you issue. The problem with the common-collections jar is a known issue with JBOSS, and we plan to add this to our online docuemtation. Thanks, Brian

            You are right. I have put JIRA 3.4.2 on vanilla plain Tomcat 5.0.28 and after few moments of fighting (yeah, do not put jira into webapps directory...) it shows that this issue has no place.
            Then I have once again run JBoss 3.2.6 and analysed logs. Then I found that before series of ArrayIndexOutOfBoundsExceptions there is also another error report:
            java.lang.NoSuchMethodError: org.apache.commons.collections.CollectionUtils.exists(Ljava/util/Collection;Lorg/apache/commons/collections/Predicate;)Z

            Now it is appranet to me, that embeded Tomcat is using older version of apache commons (v2.1) that is loaded before JIRA's required commons (v3.1). Putting "commons-collections-3.1.jar" in server "lib" directory resolved this particular problem.

            Sorry for raising alarm prematurely, but maybe this note will save somebody's time

            regards,
            andy

            Andrew Michalec added a comment - You are right. I have put JIRA 3.4.2 on vanilla plain Tomcat 5.0.28 and after few moments of fighting (yeah, do not put jira into webapps directory...) it shows that this issue has no place. Then I have once again run JBoss 3.2.6 and analysed logs. Then I found that before series of ArrayIndexOutOfBoundsExceptions there is also another error report: java.lang.NoSuchMethodError: org.apache.commons.collections.CollectionUtils.exists(Ljava/util/Collection;Lorg/apache/commons/collections/Predicate;)Z Now it is appranet to me, that embeded Tomcat is using older version of apache commons (v2.1) that is loaded before JIRA's required commons (v3.1). Putting "commons-collections-3.1.jar" in server "lib" directory resolved this particular problem. Sorry for raising alarm prematurely, but maybe this note will save somebody's time regards, andy

            Andy,

            This is almost certainly a JBoss / Tomcat issue.

            JIRA has been successfully tested on Tomcat 5.0.28, so this looks like it may be a problem with the integration with JBoss.

            Seeing as JIRA doesn't require anything from JBoss, could you just install the standalone version of JIRA?

            Let me know what your options are.

            Cheers,
            Scott

            Scott Farquhar added a comment - Andy, This is almost certainly a JBoss / Tomcat issue. JIRA has been successfully tested on Tomcat 5.0.28, so this looks like it may be a problem with the integration with JBoss. Seeing as JIRA doesn't require anything from JBoss, could you just install the standalone version of JIRA? Let me know what your options are. Cheers, Scott

              Unassigned Unassigned
              5914e883b450 Andrew Michalec
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: