Integration of JIRA 4.0.1 with Crowd 2.2.7 version possible problem

Petr Sobol

Dear Attlasian,

We are trying to integrate our obsolete version of Jira 4.0.1 (which we can t upgrade from bussiness reasons) with Crowd 2.2.7 and we have onlz managed to connect these two but we can't manage to have user management fully operational in terms of creation of user in JIRa if the user is added to Active directory connected to Jira via Crowd.

We were going step by step with setting up the integration but it seems that jar file is not compatible :

2012-07-24 09:48:38,654 main WARN [rest.service.util.ShutdownIgnoringMultiThreadedHttpConnectionManager] Unwanted shutdown call detected and ignored
java.lang.IllegalStateException
at com.atlassian.crowd.integration.rest.service.util.ShutdownIgnoringMultiThreadedHttpConnectionManager.shutdown(ShutdownIgnoringMultiThreadedHttpConnectionManager.java:26)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.shutdownAll(MultiThreadedHttpConnectionManager.java:120)
at com.atlassian.jirafisheyeplugin.rest.fisheye.FishEyeRestApiManagerImpl.onFrameworkShutdown(FishEyeRestApiManagerImpl.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.atlassian.plugin.event.impl.DefaultPluginEventManager$Listener.notify(DefaultPluginEventManager.java:196)
at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:70)
at com.atlassian.plugin.manager.DefaultPluginManager.shutdown(DefaultPluginManager.java:172)
at com.atlassian.jira.ComponentManager$PluginSystem.shutdown(ComponentManager.java:1303)
at com.atlassian.jira.ComponentManager.shutdown(ComponentManager.java:200)
at com.atlassian.jira.util.CompositeShutdown.shutdown(CompositeShutdown.java:32)
at com.atlassian.jira.upgrade.ConsistencyCheckImpl.destroy(ConsistencyCheckImpl.java:94)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextDestroyed(ConsistencyLauncher.java:88)
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3836)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4366)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1067)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1067)
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448)
at org.apache.catalina.core.StandardService.stop(StandardService.java:510)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:734)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
at org.apache.catalina.startup.Catalina.start(Catalina.java:577)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)

What solution would you suggest if upgrade of Jira is not an option?

Thanks in advance for your reply Petr

Nic Brough -Adaptavist-

Mmm, I've had a similar problem - later versions of Crowd simply do not work with Jira 4.0

Your options are limited I'm afraid -

1) Upgrade Jira (I know you've said you've got business reasons for not doing it, but it's well worth doing, as 4.0 is unsupported, insecure and not as nice as 4.4 and above)

2) Use an older version of Crowd that is compatible with Jira 4.0 (Your license allows for this, I don't know if your other Crowd-using systems will cope)

3) Grab the source code of Crowd and amend it to enable backward compatibility with Jira 4.0

4) Grab the source code of Jira 4.0 and amend it to be compatible with Crowd (I suspect this is a much nicer option than the one above, as it's only one module you'll need to rewrite)