java.lang.reflect.InvocationTargetException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Hi, Our user integration failed this morning and cleared the email addresses of several users. This resulted in the error below that we got in several places, including the user picker making for example the "Assign issue" break. I know this shouldn't happen and the error is in our directory integration but I think that JIRA should handle this error more gracefully :) {code} 2013-01-09 09:12:39,525 ajp-bio-8109-exec-600 ERROR vs 552x839394x1 18tnl4u 10.42.105.148 /rest/api/2/user/viewissue/search [jira.rest.exception.ExceptionInterceptor] Returning internal server error in response java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:100) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept(ExpandInterceptor.java:38) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) ... Caused by: java.lang.NullPointerException at com.atlassian.jira.util.EmailFormatterImpl.formatEmail(EmailFormatterImpl.java:66) at com.atlassian.jira.util.EmailFormatterImpl.formatEmail(EmailFormatterImpl.java:76) at sun.reflect.GeneratedMethodAccessor2177.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) {code}
    via by Bjarni Thorbjornsson,
  • Hi, Our user integration failed this morning and cleared the email addresses of several users. This resulted in the error below that we got in several places, including the user picker making for example the "Assign issue" break. I know this shouldn't happen and the error is in our directory integration but I think that JIRA should handle this error more gracefully :) {code} 2013-01-09 09:12:39,525 ajp-bio-8109-exec-600 ERROR vs 552x839394x1 18tnl4u 10.42.105.148 /rest/api/2/user/viewissue/search [jira.rest.exception.ExceptionInterceptor] Returning internal server error in response java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:100) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept(ExpandInterceptor.java:38) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) ... Caused by: java.lang.NullPointerException at com.atlassian.jira.util.EmailFormatterImpl.formatEmail(EmailFormatterImpl.java:66) at com.atlassian.jira.util.EmailFormatterImpl.formatEmail(EmailFormatterImpl.java:76) at sun.reflect.GeneratedMethodAccessor2177.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) {code}
    via by Bjarni Thorbjornsson,
  • REST plugin currently assumes that all custom properties are strings: {code} public class PropertySetAdapter extends XmlAdapter<Map<String, String>, PropertySet> { ... @Override public HashMap<String, String> marshal(final PropertySet propertySet) { final HashMap<String, String> map = new HashMap<String, String>(); final Collection<String> keys = propertySet.getKeys(); for (String key : keys) { map.put(key, propertySet.getString(key)); } return map; } ... } {code} In case of e.g. Apache JIRA instance it supposedly uses non-String properties which leads to: {noformat} /rest/api/latest/issue/ISSUEKEYHERE [jira.rest.exception.ExceptionInterceptor] Returning internal server error in response java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1586.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:206) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:90) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.jira.rest.exception.ExceptionInterceptor.intercept(ExceptionInterceptor.java:59) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.jira.rest.v2.issue.scope.RequestScopeInterceptor.intercept(RequestScopeInterceptor.java:42) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept(ExpandInterceptor.java:38) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.invokeMethodWithInterceptors(DispatchProviderHelper.java:98) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.access$100(DispatchProviderHelper.java:28) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker._dispatch(DispatchProviderHelper.java:202) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:67) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:163) .... Caused by: com.opensymphony.module.propertyset.InvalidPropertyTypeException at com.opensymphony.module.propertyset.ofbiz.OFBizPropertySet.get(OFBizPropertySet.java:273) at com.opensymphony.module.propertyset.AbstractPropertySet.getString(AbstractPropertySet.java:305) at com.atlassian.jira.rest.v2.issue.PropertySetAdapter.marshal(PropertySetAdapter.java:32) at com.atlassian.jira.rest.v2.issue.AttachmentBeanBuilder.build(AttachmentBeanBuilder.java:95) at com.atlassian.jira.rest.v2.issue.IssueResource$3.get(IssueResource.java:905) at com.atlassian.jira.rest.v2.issue.IssueResource$3.get(IssueResource.java:902) at com.atlassian.jira.util.collect.TransformingIterator.next(TransformingIterator.java:38) at com.atlassian.jira.util.collect.CollectionUtil.foreach(CollectionUtil.java:43) at com.atlassian.jira.util.collect.CollectionUtil.toList(CollectionUtil.java:72) at com.atlassian.jira.util.collect.CollectionUtil.transform(CollectionUtil.java:141) at com.atlassian.jira.util.collect.CollectionUtil.transform(CollectionUtil.java:163) at com.atlassian.jira.rest.v2.issue.IssueResource.addAttachments(IssueResource.java:901) at com.atlassian.jira.rest.v2.issue.IssueResource.createIssue(IssueResource.java:881) at com.atlassian.jira.rest.v2.issue.IssueResource.getIssue(IssueResource.java:683) {noformat} See https://issues.apache.org/jira/browse/INFRA-3750 for more details.
    via by Wojciech Seliga,
  • When transit an issue to another state, we refer to the following transition ID found in the GET method JSON. For example: # GET http://localhost:8080/rest/api/latest/issue/TEST-1/transitions # The request returns the states 'Resolved' => '5', 'Closed' => '6', 'In Progress' => '3'. # POST http://localhost:8080/rest/api/latest/issue/TEST-1/transitions {code} {"transition":{"id":"7"}} {code} # This time with JSON data {"transition":{"id":"7"}} and get the '500 Internal Server Error' because transition ID = 7 is not exist. {code} 2015-01-21 17:54:29,343 http-bio-8080-exec-20 ERROR admin 1134x2089x1 xxxx xx.xx.xx.xx /rest/api/latest/issue/TEST-1/transitions [jira.rest.exception.ExceptionInterceptor] Returning internal server error in response java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:100) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) ... Caused by: java.lang.NullPointerException at com.atlassian.jira.workflow.WorkflowActionsBean.getFieldScreenForView(WorkflowActionsBean.java:59) at com.atlassian.jira.issue.fields.screen.StandardFieldScreenRendererFactory.getScreenFromAction(StandardFieldScreenRendererFactory.java:130) at com.atlassian.jira.issue.fields.screen.StandardFieldScreenRendererFactory.createFieldScreenRenderer(StandardFieldScreenRendererFactory.java:55) at com.atlassian.jira.issue.fields.screen.FieldScreenRendererFactoryImpl.getFieldScreenRenderer(FieldScreenRendererFactoryImpl.java:55) {code} The NPE error is misleading to user and it would be great if JIRA can handle the error by showing a meaningful error message. Besides being misleading it seems to indicate that there is a bug in the error handling routines, and IMHO should be fixed.
    via by John Chin Kim Loong [Atlassian],
  • REST plugin currently assumes that all custom properties are strings: {code} public class PropertySetAdapter extends XmlAdapter<Map<String, String>, PropertySet> { ... @Override public HashMap<String, String> marshal(final PropertySet propertySet) { final HashMap<String, String> map = new HashMap<String, String>(); final Collection<String> keys = propertySet.getKeys(); for (String key : keys) { map.put(key, propertySet.getString(key)); } return map; } ... } {code} In case of e.g. Apache JIRA instance it supposedly uses non-String properties which leads to: {noformat} /rest/api/latest/issue/ISSUEKEYHERE [jira.rest.exception.ExceptionInterceptor] Returning internal server error in response java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1586.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:206) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:90) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.jira.rest.exception.ExceptionInterceptor.intercept(ExceptionInterceptor.java:59) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.jira.rest.v2.issue.scope.RequestScopeInterceptor.intercept(RequestScopeInterceptor.java:42) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept(ExpandInterceptor.java:38) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.invokeMethodWithInterceptors(DispatchProviderHelper.java:98) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.access$100(DispatchProviderHelper.java:28) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker._dispatch(DispatchProviderHelper.java:202) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:67) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:163) .... Caused by: com.opensymphony.module.propertyset.InvalidPropertyTypeException at com.opensymphony.module.propertyset.ofbiz.OFBizPropertySet.get(OFBizPropertySet.java:273) at com.opensymphony.module.propertyset.AbstractPropertySet.getString(AbstractPropertySet.java:305) at com.atlassian.jira.rest.v2.issue.PropertySetAdapter.marshal(PropertySetAdapter.java:32) at com.atlassian.jira.rest.v2.issue.AttachmentBeanBuilder.build(AttachmentBeanBuilder.java:95) at com.atlassian.jira.rest.v2.issue.IssueResource$3.get(IssueResource.java:905) at com.atlassian.jira.rest.v2.issue.IssueResource$3.get(IssueResource.java:902) at com.atlassian.jira.util.collect.TransformingIterator.next(TransformingIterator.java:38) at com.atlassian.jira.util.collect.CollectionUtil.foreach(CollectionUtil.java:43) at com.atlassian.jira.util.collect.CollectionUtil.toList(CollectionUtil.java:72) at com.atlassian.jira.util.collect.CollectionUtil.transform(CollectionUtil.java:141) at com.atlassian.jira.util.collect.CollectionUtil.transform(CollectionUtil.java:163) at com.atlassian.jira.rest.v2.issue.IssueResource.addAttachments(IssueResource.java:901) at com.atlassian.jira.rest.v2.issue.IssueResource.createIssue(IssueResource.java:881) at com.atlassian.jira.rest.v2.issue.IssueResource.getIssue(IssueResource.java:683) {noformat} See https://issues.apache.org/jira/browse/INFRA-3750 for more details.
    via by Wojciech Seliga,
  • When transit an issue to another state, we refer to the following transition ID found in the GET method JSON. For example: # GET http://localhost:8080/rest/api/latest/issue/TEST-1/transitions # The request returns the states 'Resolved' => '5', 'Closed' => '6', 'In Progress' => '3'. # POST http://localhost:8080/rest/api/latest/issue/TEST-1/transitions {code} {"transition":{"id":"7"}} {code} # This time with JSON data {"transition":{"id":"7"}} and get the '500 Internal Server Error' because transition ID = 7 is not exist. {code} 2015-01-21 17:54:29,343 http-bio-8080-exec-20 ERROR admin 1134x2089x1 xxxx xx.xx.xx.xx /rest/api/latest/issue/TEST-1/transitions [jira.rest.exception.ExceptionInterceptor] Returning internal server error in response java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:100) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) ... Caused by: java.lang.NullPointerException at com.atlassian.jira.workflow.WorkflowActionsBean.getFieldScreenForView(WorkflowActionsBean.java:59) at com.atlassian.jira.issue.fields.screen.StandardFieldScreenRendererFactory.getScreenFromAction(StandardFieldScreenRendererFactory.java:130) at com.atlassian.jira.issue.fields.screen.StandardFieldScreenRendererFactory.createFieldScreenRenderer(StandardFieldScreenRendererFactory.java:55) at com.atlassian.jira.issue.fields.screen.FieldScreenRendererFactoryImpl.getFieldScreenRenderer(FieldScreenRendererFactoryImpl.java:55) {code} The NPE error is misleading to user and it would be great if JIRA can handle the error by showing a meaningful error message. Besides being misleading it seems to indicate that there is a bug in the error handling routines, and IMHO should be fixed.
    via by Chin Kim Loong,
  • WorldEdit not working...
    via GitHub by Yuri6037
    ,
  • File Upload - Primefaces
    via GitHub by marceloas
    ,
    • java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:234) at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:100) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61) at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept(ExpandInterceptor.java:38) at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:61)

    Users with the same issue

    Tolly67p
    1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    110 more bugmates