com.atlassian.jira.rpc.exception.RemoteException: Error removing project: TEST-PROJECT-KEYCaused by com.atlassian.jira.rpc.exception.RemoteException: Error removing issues: com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.Caused by com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.

Atlassian JIRA | Oswaldo Hernandez [Atlassian] | 7 years ago
  1. 0

    A deleteProject SOAP call may try to delete an issue more than one time causing it to fail with an Exception. The SOAP deleteProject call gets all issues for the given project through the OfbizDelegator, and then calls on a deleteIssue back-end action which deletes the Issue and its sub-tasks amongst other things. Now, if a parent issue is placed before any of its sub-tasks in the list gotten by the OfBizDelegator, the deleteProject call will try to delete the subtask(s) twice. The first time implicitly by calling the deleteIssue back-end action on the parent (which will delete the sub-tasks associated with this parent issue), and the second time by trying to delete the sub-task explicitly because it is in the list of issues to be deleted, but this will fail because that sub-task has already been deleted. The failure will be in lines 446-447 when it tries to verify permissions on the Project this issue belongs to and the project will be null because the issue is null too (it doesn't exist anymore). Therefore, the if on line 447 will become true (project == null), and we will get a RemotePermissionException saying "The project specified does not exist or you don't have permission to delete issues in it." The stack trace will look like: Exception in thread "main" AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: com.atlassian.jira.rpc.exception.RemoteException: Error removing project: TEST-PROJECT-KEYCaused by com.atlassian.jira.rpc.exception.RemoteException: Error removing issues: com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.Caused by com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it. at com.atlassian.jira.rpc.soap.service.IssueServiceImpl.retrieveIssue(IssueServiceImpl.java:889) at com.atlassian.jira.rpc.soap.service.IssueServiceImpl.getIssue(IssueServiceImpl.java:150) at com.atlassian.jira.rpc.soap.service.IssueServiceImpl.deleteIssue(IssueServiceImpl.java:446) at com.atlassian.jira.rpc.soap.service.ProjectServiceImpl.deleteProject(ProjectServiceImpl.java:490) at com.atlassian.jira.rpc.soap.JiraSoapServiceImpl.deleteProject(JiraSoapServiceImpl.java:405)

    Atlassian JIRA | 7 years ago | Oswaldo Hernandez [Atlassian] Bugmaster
    com.atlassian.jira.rpc.exception.RemoteException: Error removing project: TEST-PROJECT-KEYCaused by com.atlassian.jira.rpc.exception.RemoteException: Error removing issues: com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.Caused by com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.
  2. 0

    A deleteProject SOAP call may try to delete an issue more than one time causing it to fail with an Exception. The SOAP deleteProject call gets all issues for the given project through the OfbizDelegator, and then calls on a deleteIssue back-end action which deletes the Issue and its sub-tasks amongst other things. Now, if a parent issue is placed before any of its sub-tasks in the list gotten by the OfBizDelegator, the deleteProject call will try to delete the subtask(s) twice. The first time implicitly by calling the deleteIssue back-end action on the parent (which will delete the sub-tasks associated with this parent issue), and the second time by trying to delete the sub-task explicitly because it is in the list of issues to be deleted, but this will fail because that sub-task has already been deleted. The failure will be in lines 446-447 when it tries to verify permissions on the Project this issue belongs to and the project will be null because the issue is null too (it doesn't exist anymore). Therefore, the if on line 447 will become true (project == null), and we will get a RemotePermissionException saying "The project specified does not exist or you don't have permission to delete issues in it." The stack trace will look like: Exception in thread "main" AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: com.atlassian.jira.rpc.exception.RemoteException: Error removing project: TEST-PROJECT-KEYCaused by com.atlassian.jira.rpc.exception.RemoteException: Error removing issues: com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.Caused by com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it. at com.atlassian.jira.rpc.soap.service.IssueServiceImpl.retrieveIssue(IssueServiceImpl.java:889) at com.atlassian.jira.rpc.soap.service.IssueServiceImpl.getIssue(IssueServiceImpl.java:150) at com.atlassian.jira.rpc.soap.service.IssueServiceImpl.deleteIssue(IssueServiceImpl.java:446) at com.atlassian.jira.rpc.soap.service.ProjectServiceImpl.deleteProject(ProjectServiceImpl.java:490) at com.atlassian.jira.rpc.soap.JiraSoapServiceImpl.deleteProject(JiraSoapServiceImpl.java:405)

    Atlassian JIRA | 7 years ago | Oswaldo Hernandez [Atlassian]
    com.atlassian.jira.rpc.exception.RemoteException: Error removing project: TEST-PROJECT-KEYCaused by com.atlassian.jira.rpc.exception.RemoteException: Error removing issues: com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.Caused by com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.
  3. 0

    As can be seen in JENKINS-2552, and another one in FindBugs (I forgot the bug number) scm-issue-link daemon can occasionally go crazy and just keep putting the same comment over and over again to the same issue. The daemon execution log reveals the following exception: {noformat} Started Parsing stdin Subject: svn commit: r24705 - trunk/hudson/main/core/src/main: java/hudson/diagnosis java/hudson/node_monitors resources/hudson/node_monitors/AbstractDiskSp... Found [hudson-2552] Updating hudson-2552 Exception in thread "main" AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: com.atlassian.jira.rpc.exception.RemoteException: Error occurred when running workflow action Resolve Issue: Errors: {} Error Messages: [Action 5 is invalid] faultActor: faultNode: faultDetail: {}com.atlassian.jira.rpc.exception.RemoteException:null {http://xml.apache.org/axis/}hostname:jira com.atlassian.jira.rpc.exception.RemoteException: Error occurred when running workflow action Resolve Issue: Errors: {} Error Messages: [Action 5 is invalid] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at java.lang.Class.newInstance0(Class.java:350) at java.lang.Class.newInstance(Class.java:303) at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:104) at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:90) at hudson.plugins.jira.soap.RemoteException.getDeserializer(RemoteException.java:75) 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:585) at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154) at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:84) at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:464) at org.apache.axis.encoding.DeserializationContext.getDeserializerForType(DeserializationContext.java:547) at org.apache.axis.message.SOAPFaultDetailsBuilder.onStartChild(SOAPFaultDetailsBuilder.java:157) at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) at org.apache.axis.client.Call.invokeEngine(Call.java:2784) at org.apache.axis.client.Call.invoke(Call.java:2767) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at hudson.plugins.jira.soap.JirasoapserviceV2SoapBindingStub.progressWorkflowAction(JirasoapserviceV2SoapBindingStub.java:3578) at com.sun.javanet.cvsnews.cli.UpdateCommand.execute(UpdateCommand.java:122) at com.sun.javanet.cvsnews.cli.Main.run(Main.java:76) at com.sun.javanet.cvsnews.cli.Main.main(Main.java:53) Finished: FAILURE {noformat} Thus the daemon thinks the issue update had failed, and so the mail server will keep retrying the delivery, until it abandons the delivery.

    Jenkins JIRA | 7 years ago | Kohsuke Kawaguchi
    com.atlassian.jira.rpc.exception.RemoteException: Error occurred when running workflow action Resolve Issue: Errors: {} Error Messages: [Action 5 is invalid]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    As can be seen in JENKINS-2552, and another one in FindBugs (I forgot the bug number) scm-issue-link daemon can occasionally go crazy and just keep putting the same comment over and over again to the same issue. The daemon execution log reveals the following exception: {noformat} Started Parsing stdin Subject: svn commit: r24705 - trunk/hudson/main/core/src/main: java/hudson/diagnosis java/hudson/node_monitors resources/hudson/node_monitors/AbstractDiskSp... Found [hudson-2552] Updating hudson-2552 Exception in thread "main" AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: com.atlassian.jira.rpc.exception.RemoteException: Error occurred when running workflow action Resolve Issue: Errors: {} Error Messages: [Action 5 is invalid] faultActor: faultNode: faultDetail: {}com.atlassian.jira.rpc.exception.RemoteException:null {http://xml.apache.org/axis/}hostname:jira com.atlassian.jira.rpc.exception.RemoteException: Error occurred when running workflow action Resolve Issue: Errors: {} Error Messages: [Action 5 is invalid] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at java.lang.Class.newInstance0(Class.java:350) at java.lang.Class.newInstance(Class.java:303) at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:104) at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:90) at hudson.plugins.jira.soap.RemoteException.getDeserializer(RemoteException.java:75) 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:585) at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154) at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:84) at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:464) at org.apache.axis.encoding.DeserializationContext.getDeserializerForType(DeserializationContext.java:547) at org.apache.axis.message.SOAPFaultDetailsBuilder.onStartChild(SOAPFaultDetailsBuilder.java:157) at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) at org.apache.axis.client.Call.invokeEngine(Call.java:2784) at org.apache.axis.client.Call.invoke(Call.java:2767) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at hudson.plugins.jira.soap.JirasoapserviceV2SoapBindingStub.progressWorkflowAction(JirasoapserviceV2SoapBindingStub.java:3578) at com.sun.javanet.cvsnews.cli.UpdateCommand.execute(UpdateCommand.java:122) at com.sun.javanet.cvsnews.cli.Main.run(Main.java:76) at com.sun.javanet.cvsnews.cli.Main.main(Main.java:53) Finished: FAILURE {noformat} Thus the daemon thinks the issue update had failed, and so the mail server will keep retrying the delivery, until it abandons the delivery.

    Jenkins JIRA | 7 years ago | Kohsuke Kawaguchi
    com.atlassian.jira.rpc.exception.RemoteException: Error occurred when running workflow action Resolve Issue: Errors: {} Error Messages: [Action 5 is invalid]
  6. 0

    Resolve/Close issue in JIRA using PHP

    Stack Overflow | 5 years ago | Johal
    com.atlassian.jira.rpc.exception.RemoteException: java.lang.NumberFormatException: For input string: "Array"

    Root Cause Analysis

    1. com.atlassian.jira.rpc.exception.RemoteException

      Error removing project: TEST-PROJECT-KEYCaused by com.atlassian.jira.rpc.exception.RemoteException: Error removing issues: com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.Caused by com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.

      at com.atlassian.jira.rpc.soap.service.IssueServiceImpl.retrieveIssue()
    2. com.atlassian.jira
      JiraSoapServiceImpl.deleteProject
      1. com.atlassian.jira.rpc.soap.service.IssueServiceImpl.retrieveIssue(IssueServiceImpl.java:889)
      2. com.atlassian.jira.rpc.soap.service.IssueServiceImpl.getIssue(IssueServiceImpl.java:150)
      3. com.atlassian.jira.rpc.soap.service.IssueServiceImpl.deleteIssue(IssueServiceImpl.java:446)
      4. com.atlassian.jira.rpc.soap.service.ProjectServiceImpl.deleteProject(ProjectServiceImpl.java:490)
      5. com.atlassian.jira.rpc.soap.JiraSoapServiceImpl.deleteProject(JiraSoapServiceImpl.java:405)
      5 frames