Hi guys,

Unfortunately, we will not be adding WebLogic 10 support to JIRA.

This is in line with our End of Support for all WebLogic application server platforms at the launch of JIRA 4.2, currently targetted for Q3, 2010.

For more details of the announcement, please refer to this page: http://confluence.atlassian.com/display/JIRA/End+of+Support+Announcements+for+JIRA.

This means that JIRA 4.1 will be the last release to support WebLogic 9.2.

We are reducing our application server platform support to reduce the amount of testing time and help us speed up our ability to deliver market-driven features. We are committed to helping our customers understand this decision and assisting them in migrating to Tomcat, our supported Application Server. You have the option of installing the JIRA Standalone version which includes our supported Tomcat application server.

If you have any concerns, please email eol-annoucement at atlassian dot com.

Regards,
Edwin
JIRA Product Management

Hi,

My company is using JIRA 3.10.2, and they're planning to move from Tomcat 5.5.23 to Weblogic 10. However, the setup instructions for JIRA 3.10.2 refer only to Weblogic 8 and 9 (although the document states that the instructions are for versions 8 and above).

Per your experience and testing, is it recommended to run JIRA 3.10.2 on Weblogic 10?

Thanks in advance for your feedback,
GERMAN

Hello!

I'm not amused about the new fix version. I'm waiting for this task since December 2008. We are paying a lot of money for the support contract, but the really important tasks will not be worked on!
It's out of the question!

Weblogic has a parameter <prefer-web-inf-classes>true</prefer-web-inf-classes> that can go in your weblogic.xml deployment descriptor. That might resolve the clash between the different versions of commons lang, but I haven't tried it In fact, Confluence recommend setting this parameter.

A couple of customers have reported an error deploying Jira 3.13.X in Weblogic 10. They get an exception like:

METHOD: "props", exception:
java.lang.NoSuchMethodError: join
at com.atlassian.jira.util.system.ExtendedSystemInfoUtilsImpl.getProps(ExtendedSystemInfoUtilsImpl.java:235)

The join method in the StringUtils library is defined in the commons-lang library since the 2.3 version. Jira is released with commons-lang 2.4. The problem is that WebLogic has another commons lang library defined, and for some reason (we are not WebLogic experts) the app server is using that jar instead of the one packed in the Jira WAR file. If you first find the process id of the application server, and then run:

lsof -p <pid> | grep commons | grep lang

There is a com.bea.core.apache.commons.lang_2.1.0.jar library loaded, and that's the jar that is being used, instead of the 2.4 packed in the WAR.

Some application servers have a setting to define whether the jar files defined in the WAR should take precedence over common libraries loaded by the application server. Presumably WebLogic will have a similar setting, but not being an expert on this app server, I cannot confirm whether this is the case.

Thank you for the updates!

We will need to at a minimum doco this as part of the support matrix for 4 as well as in the actual product docs - so just setting this to 4 so we don't forget.

Brian

Allan,

We are working on this at the moment. However setting up a reliable testing environment is taking time. We are hoping to have something in place in the next few months.

Cheers,
Anton

hey,
I'm wondering if there are any updates on this?

Thanks in Advance,

Allan

testing WebLogic 10 is currently with the X Product Team. They are very busy at the moment, and it might take a while until we have automated tests running against WebLogic 10.