This page contains frequently asked questions and known issues about RPC, in relation to JIRA.
On this page:
Table of Contents |
---|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Couldn't build RPC Plugin due to NullPointerExceptionIf you are getting a Getting InfrastructureException or ClassCastException upon invocationIf you are getting a If this is not the case and this error is occurring, then it is highly likely that autotyping is the culprit. To resolve this problem, you will need to disable autotyping or alternatively, explicitly declare the data types for the arguments. |
Panel | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||
Converting to type as defined in WSDLYou may occasionally encounter problems mapping the correct data type of your programming language to the one defined in WSDL. If you are running into difficulties related to data mapping, we recommend that you consult the user guide or API documentation of the client library you are using, e.g. WSDL<->Java mapping, Python's SOAPpy, etc, for assistance. Changing the authentication token timeout valueIf you wish to change the timeout value of the authentication token (which is obtained once you've logged in), you will need to update the value for the Providing schemes to method's argumentsUsers are often unsure whether they should construct or retrieve the scheme object(s) which will be passed to an argument. For your understanding, internally, the RPC plugin recognises just the Could not update an issue with a RemoteIssue objectUnfortunately, you can only create an issue with a RemoteIssue object. You cannot update an issue with a RemoteIssue object. The Setting the value of cascading select customfieldSetting the value of a cascading select custom field can be complicated, as the create issue and update issue scenarios are different. Please refer to the points below for assistance in setting up your cascading select custom field correctly:
The same logic applies to XML-RPC, please refer to this example. Could not invoke methods due to session invalidationA known issue exists where methods may be prevented from being invoked due to session invalidation, i.e. an
Please refer to the bug report being tracked at JRA-8009. We would appreciate any comments added to this issue, if you encounter this problem. Getting fixed targetNamespaceGetting a fixed targetNamespace is a known issue, which is being tracked at JRA-10849. The Having concurrency problem with multiple issue updateConstantly or simultaneously updating an issue causes data inconsistency of the issue. This is a known issue which is currently being tracked at JRA-11382. Could not invoke user-group methods due to deserialisation or invalid element problemsIf you are using Python (SOAPpy) and encountering deserialisation or invalid element problems while invoking the
you should be able to resolve this by following the workarounds described in these issues — JRA-7920 and JRA-7971 Using the addActorsToProjectRole methodIf you are having problems using the For example,
Could not upload attachments to an issue due to OutOfMemoryErrorIf your Java (Axis) SOAP client is throwing an Getting content-type complaint with .NET clientThis seems to be the problem with the .NET web service library. We would appreciate your contributions to tracking issue, JRA-11515, if you encounter a similar problem. Setting the reporter value upon issue creationIf you are not able to set the reporter value (to someone other than the current SOAP client) even though it is provided, you may be using the old RPC plugin (3.6.x and older). This improvement (JRA-8794) is delivered in the latest version (3.7.x onwards). Other Known RPC IssuesUnfortunately there are a number of known RPC issues, which are currently unsupported. These have already been raised in our issue tracker and are listed below. If you would like to try manually patching or customising the RPC plugin to address these issues yourself, the source code of the RPC plugin is freely available for you to modify.
|
Please take note that a number of the frequently asked XML-RPC questions are similar to the respective SOAP questions above, as some of the functions of the XML-RPC service are underpinned by the SOAP service. Hence, the questions may not be mentioned again below.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Could not create and update issue with same DictionaryIf you are running into problems creating and updating issues with the same Directory, you may be specifying the arguments incorrectly. Internally, JIRA's XmlRpcService uses SOAP to create and update an issue. Due to this reason, the Dictionary (or Hashtable, or Map) argument in This Perl XMLRPC::Lite example demonstrates how an issue is created and updated:
Setting the value of cascading select customfieldPlease refer to the explanation in SOAP section. |
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
If you can't find an answer to your question on this page, you may want to try searching the Atlassian forums and Issue Tracker. These two resources often contain helpful discussion on RPC topics that may solve your problem. The following documents may also help answer your question: |