Details
-
Suggestion
-
Resolution: Won't Do
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
When JIRA does not have enough permission to read its own crowd.properties it will return the following stack trace:
Caused by: java.lang.IllegalArgumentException: org.apache.commons.httpclient.URIException: URI-Reference required at com.atlassian.crowd.integration.rest.service.RestExecutor.<init>(RestExecutor.java:78) at com.atlassian.crowd.integration.rest.service.RestCrowdClient.<init>(RestCrowdClient.java:78) at com.atlassian.crowd.integration.rest.service.factory.RestCrowdClientFactory.newInstance(RestCrowdClientFactory.java:26) at com.atlassian.crowd.integration.rest.service.factory.RestCrowdHttpAuthenticationFactory.createInstance(RestCrowdHttpAuthenticationFactory.java:43) at com.atlassian.crowd.integration.rest.service.factory.RestCrowdHttpAuthenticationFactory.<clinit>(RestCrowdHttpAuthenticationFactory.java:21) Caused by: org.apache.commons.httpclient.URIException: URI-Reference required at org.apache.commons.httpclient.URI.parseUriReference(URI.java:1874) at org.apache.commons.httpclient.URI.<init>(URI.java:165) at com.atlassian.crowd.integration.rest.service.RestExecutor.<init>(RestExecutor.java:59)
The above stack trace does not provide the necessary information to troubleshoot the issue as its only mentioned that the URL inputted in crowd.properties is incorrect which is not the case.
JIRA should be able to log properly when it is unable to read into crowd.properties.
Attachments
Issue Links
- is related to
-
JRASERVER-29199 Better logging regarding crowd.properties issue
- Closed