StringUtils not found when testing JIRA Salesforce Connection

  • 1
  • Problem
  • Updated 2 years ago
I am running JIRA 5.0.6 and was running Salesforce connector 5.3.2. Some one had changed the password in SF, so I had to re-authenticate. While I was int eh system, I updated the Core Connector and JIRA connector plugins to 1.4.18 which was fine, but I received an error when I tried to update the Saleforce Connector plugin to 5.3.9. 

At this point, I was not able to display the details section on issues. I spent some time and uninstalled all the plugins and tried to re-install 5.3.9, still get an error. I also got an error on 5.3.8. I was able to install 5.3.6 with success and it installed 1.4.10 of the core and JIRA connectors. 

I still cannot display the details section of the issue and now when I go to the connector config page and click Test connection, I get an error:

Cause: 

java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils

Stack Trace: [hide]

java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils
	at net.customware.plugins.connector.salesforce.manager.impl.DefaultSalesforceManager.<init>(DefaultSalesforceManager.java:80)
	at net.customware.plugins.connector.salesforce.manager.impl.CachingSalesforceManager.<init>(CachingSalesforceManager.java:80)
	at net.customware.plugins.connector.salesforce.manager.impl.SalesforceIntegrationManager.createManagerForConfig(SalesforceIntegrationManager.java:39)
	at net.customware.plugins.connector.salesforce.manager.impl.SalesforceIntegrationManager.createManagerForConfig(SalesforceIntegrationManager.java:21)
	at net.customware.plugins.connector.core.servlet.ConfigurationServlet.handleTestRequest(ConfigurationServlet.java:278)
	at net.customware.plugins.connector.core.servlet.ConfigurationServlet.handleRequestInternal(ConfigurationServlet.java:171)
	at net.customware.plugins.connector.core.servlet.ServletBase.handleRequest(ServletBase.java:288)
	at net.customware.plugins.connector.core.servlet.ServletBase.doGet(ServletBase.java:235)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:42)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at com.atlassian.plugin.servlet.ServletModuleContainerServlet.service(ServletModuleContainerServlet.java:52)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

Any ideas how to get an old version to run again. I really don't have the time to move to the latest JIRA version, but it may be required. Ughh.
Photo of George Spatz

George Spatz

  • 7 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Kheng Jin Leow

Kheng Jin Leow

  • 21 Posts
  • 0 Reply Likes
Hi George,

It seems like the JIRA instance that you're using is no longer supported by Atlassian and since we are following the End of Life support policy provided by Atlassian

What you can do is, upgrade your current JIRA instance to at least version 6.1 and we will help to solve the issue if the issue still persists.

Thank you.