Details
-
Bug
-
Resolution: Obsolete
-
Low
-
4.2.4
-
None
-
4.02
-
Description
Jira is integrated with Crowd and when you try to add a user in JIRA, you get the following error. However despite of an exception, you find user is getting created in JIRA and also flowing down to Crowd.
2012-03-27 15:19:24,912 http-8085-6 ERROR [500ErrorPage.jsp] Exception caught in 500 page Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Could not receive fault.. Nested exception is org.codehaus.xfire.fault.XFireFault: No write method for property {http://rmi.java}cause in class java.rmi.RemoteException
org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Could not receive fault.. Nested exception is org.codehaus.xfire.fault.XFireFault: No write method for property {http://rmi.java}cause in class java.rmi.RemoteException
org.codehaus.xfire.fault.XFireFault: Could not receive fault.. Nested exception is org.codehaus.xfire.fault.XFireFault: No write method for property {http://rmi.java}cause in class java.rmi.RemoteException
at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:83)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
You also see a lot of this in logs:
2012-03-27 15:45:36,381 main WARN [org.twdata.pkgscanner.ExportPackageListBuilder] Package Scanner found duplicates for package 'org.jdom.output' with different versions. Files: jdom-1.0.jar and crowd-integration-client-2.4.0.jar '/data/atlassian/jira-4.2.4/atlassian-jira/WEB-INF/lib/jdom-1.0.jar' '/data/atlassian/jira-4.2.4/atlassian-jira/WEB-INF/lib/crowd-integration-client-2.4.0.jar' 2012-03-27 15:45:36,382 main WARN [org.twdata.pkgscanner.ExportPackageListBuilder] Package Scanner found duplicates for package 'org.jdom.input' with different versions. Files: jdom-1.0.jar and crowd-integration-client-2.4.0.jar '/data/atlassian/jira-4.2.4/atlassian-jira/WEB-INF/lib/jdom-1.0.jar' '/data/atlassian/jira-4.2.4/atlassian-jira/WEB-INF/lib/crowd-integration-client-2.4.0.jar' 2012-03-27 15:45:36,382 main WARN [org.twdata.pkgscanner.ExportPackageListBuilder] Package Scanner found duplicates for package 'org.jdom' with different versions. Files: jdom-1.0.jar and crowd-integration-client-2.4.0.jar '/data/atlassian/jira-4.2.4/atlassian-jira/WEB-INF/lib/jdom-1.0.jar' '/data/atlassian/jira-4.2.4/atlassian-jira/WEB-INF/lib/crowd-integration-client-2.4.0.jar' 2012-03-27 15:45:36,382 main WARN [org.twdata.pkgscanner.ExportPackageListBuilder] Package Scanner found duplicates for package 'org.jdom.filter' with different versions. Files: jdom-1.0.jar and crowd-integration-client-2.4.0.jar '/data/atlassian/jira-4.2.4/atlassian-jira/WEB-INF/lib/jdom-1.0.jar' '/data/atlassian/jira-4.2.4/atlassian-jira/WEB-INF/lib/crowd-integration-client-2.4.0.jar'
The root problem is because the passwords are not being set in the delegated LDAP directory that is attached via Crowd.
This is not really an error but just LDAP saying "Sorry you can't do that". The system tries to set the password after the user is created, which is why you are seeing what you are seeing. The messages "Package Scanner found duplicates for package" is annoying but not really an issue here.
In fact, in JIRA 4.2 the code does try and set the password unconditionally, so setting External Password Management On won't actually help.
This whole area has been completely rewritten in JIRA 4.3 onward and this particular behaviour is no longer a problem.