com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!

Atlassian JIRA | Yilin Mo [Atlassian] | 4 years ago
  1. 0

    h3. Summary Unable to edit project roles h3. Steps to Reproduce # Create 24 project roles. # Create 451 projects. # Open page "Administration >> Users >> Project roles (for any user)" then edit the project role. # Save the changes. h3. Expected Results Saving the changes without any error. h3. Actual Results A 500 error page will be displayed. You may find either of the exceptions below in the logs: {noformat} 2013-04-25 18:34:15,707 http-bio-6523-exec-14 ERROR [500ErrorPage.jsp] Exception caught in 500 page null java.lang.NullPointerException at com.atlassian.jira.web.action.admin.user.EditUserProjectRoles.updateRoleActorsForProjectRole(EditUserProjectRoles.java:146) at com.atlassian.jira.web.action.admin.user.EditUserProjectRoles.doExecute(EditUserProjectRoles.java:54) at webwork.action.ActionSupport.execute(ActionSupport.java:165) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:82) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:221) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:150) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:153) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) (...) at java.lang.Thread.run(Thread.java:680) {noformat} {noformat} com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null! com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:29) at com.atlassian.jira.security.roles.actor.UserRoleActorFactory.createRoleActor(UserRoleActorFactory.java:71) at com.atlassian.jira.security.roles.PluginDelegatingRoleActorFactory.createRoleActor(PluginDelegatingRoleActorFactory.java:38) at com.atlassian.jira.bc.projectroles.DefaultProjectRoleService.createRoleActors(DefaultProjectRoleService.java:962) at com.atlassian.jira.bc.projectroles.DefaultProjectRoleService.updateActorsToProjectRole(DefaultProjectRoleService.java:891) at com.atlassian.jira.bc.projectroles.DefaultProjectRoleService.addActorsToProjectRole(DefaultProjectRoleService.java:1207) at com.atlassian.jira.web.action.admin.user.EditUserProjectRoles.updateRoleActorsForProjectRole(EditUserProjectRoles.java:170) at com.atlassian.jira.web.action.admin.user.EditUserProjectRoles.doExecute(EditUserProjectRoles.java:52) at webwork.action.ActionSupport.execute(ActionSupport.java:165) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:87) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) (...) at java.lang.Thread.run(Thread.java:722) {noformat} h3.Workaround # Backup the {{server.xml}} file. # Edit the {{server.xml}} file and add the parameter below in the *Connector* used for JIRA: {code} maxParameterCount="-1" {code} Example: {code:borderStyle=solid|borderColor=#6A8EB3|bgColor=#F8F8F8} <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8080" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true" maxParameterCount="-1"/> {code} # Restart JIRA. Source: https://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Common_Attributes

    Atlassian JIRA | 4 years ago | Yilin MO [Atlassian]
    com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
  2. 0

    h3. Summary Unable to edit project roles h3. Steps to Reproduce # Create 24 project roles. # Create 451 projects. # Open page "Administration >> Users >> Project roles (for any user)" then edit the project role. # Save the changes. h3. Expected Results Saving the changes without any error. h3. Actual Results A 500 error page will be displayed. You may find either of the exceptions below in the logs: {noformat} 2013-04-25 18:34:15,707 http-bio-6523-exec-14 ERROR [500ErrorPage.jsp] Exception caught in 500 page null java.lang.NullPointerException at com.atlassian.jira.web.action.admin.user.EditUserProjectRoles.updateRoleActorsForProjectRole(EditUserProjectRoles.java:146) at com.atlassian.jira.web.action.admin.user.EditUserProjectRoles.doExecute(EditUserProjectRoles.java:54) at webwork.action.ActionSupport.execute(ActionSupport.java:165) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:82) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:221) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:150) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:153) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) (...) at java.lang.Thread.run(Thread.java:680) {noformat} {noformat} com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null! com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:29) at com.atlassian.jira.security.roles.actor.UserRoleActorFactory.createRoleActor(UserRoleActorFactory.java:71) at com.atlassian.jira.security.roles.PluginDelegatingRoleActorFactory.createRoleActor(PluginDelegatingRoleActorFactory.java:38) at com.atlassian.jira.bc.projectroles.DefaultProjectRoleService.createRoleActors(DefaultProjectRoleService.java:962) at com.atlassian.jira.bc.projectroles.DefaultProjectRoleService.updateActorsToProjectRole(DefaultProjectRoleService.java:891) at com.atlassian.jira.bc.projectroles.DefaultProjectRoleService.addActorsToProjectRole(DefaultProjectRoleService.java:1207) at com.atlassian.jira.web.action.admin.user.EditUserProjectRoles.updateRoleActorsForProjectRole(EditUserProjectRoles.java:170) at com.atlassian.jira.web.action.admin.user.EditUserProjectRoles.doExecute(EditUserProjectRoles.java:52) at webwork.action.ActionSupport.execute(ActionSupport.java:165) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:87) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) (...) at java.lang.Thread.run(Thread.java:722) {noformat} h3.Workaround # Backup the {{server.xml}} file. # Edit the {{server.xml}} file and add the parameter below in the *Connector* used for JIRA: {code} maxParameterCount="-1" {code} Example: {code:borderStyle=solid|borderColor=#6A8EB3|bgColor=#F8F8F8} <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8080" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true" maxParameterCount="-1"/> {code} # Restart JIRA. Source: https://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Common_Attributes

    Atlassian JIRA | 4 years ago | Yilin Mo [Atlassian]
    com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
  3. 0

    h3. Summary If JIRA has non-existing user in the _Administer project_ permission of the Project Permission then it stops showing top dropdown header. h3. Steps to Reproduce Use Project Configurator plugin # On Source: ## Create a project ## Create a user called TestUser1 ## Amend the permission scheme to use this user, add as admin for project ## Export the project config with PC plugin # On Dest ## DO NOT CREATE USER TestUser1 ## Import project config via PC plugin h3. Expected Results It works fine h3. Actual Results Top dropdown page header is not present. The below exception is thrown in the atlassian-jira.log file: {noformat} 2016-04-14 09:51:57,891 http-bio-8443-exec-26 ERROR admin 591x87653x2 1x6uly9 127.0.0.1 /secure/project/ViewProjects.jspa [webwork.util.ValueStack] METHOD: "projectAdmin", exception: com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:29) at com.atlassian.jira.security.type.SingleUser.hasPermission(SingleUser.java:150) at com.atlassian.jira.security.type.SingleUser.hasPermission(SingleUser.java:138) at com.atlassian.jira.permission.DefaultPermissionSchemeManager$4.hasPermission(DefaultPermissionSchemeManager.java:591) at com.atlassian.jira.permission.DefaultPermissionSchemeManager.hasSchemePermission(DefaultPermissionSchemeManager.java:844) at com.atlassian.jira.permission.DefaultPermissionSchemeManager.hasSchemePermission(DefaultPermissionSchemeManager.java:586) at com.atlassian.jira.security.DefaultPermissionManager.doProjectPermissionCheck(DefaultPermissionManager.java:361) at com.atlassian.jira.security.DefaultPermissionManager.hasPermission(DefaultPermissionManager.java:218) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:144) <+2> (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:83) at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28) at com.sun.proxy.$Proxy14.hasPermission(Unknown Source) at com.atlassian.jira.web.action.project.ViewProjects.isProjectAdmin(ViewProjects.java:98) <+2> (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) .... {noformat} h3. Notes Problem may occurs executing other actions, eg: Issue Create. h3.Workaround * Check project permission page and remove non-existing users * Use updated version of Project Configurator plugin. The versions with the fix (*1.13.1-J6* and *1.13.1-J7*) were released 2016-06-10.

    Atlassian JIRA | 8 months ago | Andriy Yakovlev [Atlassian]
    com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    h4. Summary Trying to add JIRA Charts in Confluence page will render the chart properly in the screens before inserting it to the page, but clicking on _Insert_ will get the chart disssapear and the Confluence page is unable to be saved. Seems like Confluence renders JIRA Charts data using both Application URL and Display URL. h4. Steps to reproduce (*execute the test from machine1*) # Set up JIRA on machine1 (sample IP: 10.60.5.193) and Confluence on machine2 (sample IP: 10.60.5.198) # (Test scenario) Current Base URL of JIRA is *http://10.60.5.193:8630/jira* and Confluence is *http://10.60.5.198:10561/confluence* # Set up /etc/hosts on machine1 with _127.0.0.1 jiraisawesome_ # Login to *http://10.60.5.193:8630/jira* from *machine1* # Set up application link using IP and ports (e.g: connect to *http://10.60.5.198:10561/confluence*) # Login to *http://10.60.5.198:10561/confluence* from *machine1* # Create a new Confluence Page # Insert JIRA Chart by searching any existing JIRA project and Save the page (_Chart is displayed successfully_) # Login to *http://10.60.5.193:8630/jira* from *machine1* # Change the base URL of JIRA to use *http://jiraisawesome:8630/jira* # Login to *http://10.60.5.198:10561/confluence* from *machine1* # Modify the application link of JIRA - Display URL in Confluence to use *http://jiraisawesome:8630/jira* # Perform Step 7 and 8 again Here are the results * We can view the chart in the preview of the prompt, but when _insert_ the chart, its not showing in the page preview and unable to click on the save button. * URLs of the problem can be seen in the browser's developer mode {code}HTTP 200 http://jiraisawesome:8624/jira/charts?filename=jfreechart-onetime-2627007503907999135.png HTTP 504 http://10.60.2.176:8553/553/plugins/servlet/image-generator?macro=jirachart&jql=project+%3D+DEMO&statType=assignees&appId=29d6aed3-a496-3929-a14b-c4653473b6b3&chartType=pie&authenticated=true{code} h4. Logs information * Confluence log {noformat}2014-06-04 17:33:33,503 ERROR [http-bio-8090-exec-3] [confluence.plugins.jira.AbstractProxyServlet] requestByAnonymousUser Can not retrieve data from jira servers by anonymous user -- url: /plugins/servlet/image-generator | userName: admin com.atlassian.sal.api.net.ResponseException at com.atlassian.confluence.plugins.jira.ImageGeneratorServlet.handleResponse(ImageGeneratorServlet.java:185) at com.atlassian.confluence.plugins.jira.AbstractProxyServlet.requestByAnonymousUser(AbstractProxyServlet.java:176){noformat} * JIRA logs {noformat}2014-06-04 17:33:33,498 http-bio-8080-exec-6 ERROR anonymous 1053x2945x1 - 192.168.200.3 /rest/gadget/1.0/piechart/generate [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:38) at com.atlassian.jira.charts.piechart.PieChartUrlGeneratorFactory.<init>(PieChartUrlGeneratorFactory.java:41){noformat} h4. Additional Information JIRA 6.2.7 Confluence 5.5.3 h4. Use case There are users who configures JIRA and Confluence integration to be using a different Application URL than the Display URL. This configuration is used when the two servers not able to be contacted between each other using the Display URL. At times this is the prefered configuration with communication between two internal servers to be using internal IP/hostnames instead of the external IP/hostnames. h4. Expected behaviour The charts to be rendered normally in Confluence when using configurations of Display URL different than Application URL. With Display URL not necessarily able to reach the other server, but Application URL can.

    Atlassian JIRA | 2 years ago | Zulfadli Noor Sazali [Atlassian]
    com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
  6. 0

    h4. Summary Trying to add JIRA Charts in Confluence page will render the chart properly in the screens before inserting it to the page, but clicking on _Insert_ will get the chart disssapear and the Confluence page is unable to be saved. Seems like Confluence renders JIRA Charts data using both Application URL and Display URL. h4. Steps to reproduce (*execute the test from machine1*) # Set up JIRA on machine1 (sample IP: 10.60.5.193) and Confluence on machine2 (sample IP: 10.60.5.198) # (Test scenario) Current Base URL of JIRA is *http://10.60.5.193:8630/jira* and Confluence is *http://10.60.5.198:10561/confluence* # Set up /etc/hosts on machine1 with _127.0.0.1 jiraisawesome_ # Login to *http://10.60.5.193:8630/jira* from *machine1* # Set up application link using IP and ports (e.g: connect to *http://10.60.5.198:10561/confluence*) # Login to *http://10.60.5.198:10561/confluence* from *machine1* # Create a new Confluence Page # Insert JIRA Chart by searching any existing JIRA project and Save the page (_Chart is displayed successfully_) # Login to *http://10.60.5.193:8630/jira* from *machine1* # Change the base URL of JIRA to use *http://jiraisawesome:8630/jira* # Login to *http://10.60.5.198:10561/confluence* from *machine1* # Modify the application link of JIRA - Display URL in Confluence to use *http://jiraisawesome:8630/jira* # Perform Step 7 and 8 again Here are the results * We can view the chart in the preview of the prompt, but when _insert_ the chart, its not showing in the page preview and unable to click on the save button. * URLs of the problem can be seen in the browser's developer mode {code}HTTP 200 http://jiraisawesome:8624/jira/charts?filename=jfreechart-onetime-2627007503907999135.png HTTP 504 http://10.60.2.176:8553/553/plugins/servlet/image-generator?macro=jirachart&jql=project+%3D+DEMO&statType=assignees&appId=29d6aed3-a496-3929-a14b-c4653473b6b3&chartType=pie&authenticated=true{code} h4. Logs information * Confluence log {noformat}2014-06-04 17:33:33,503 ERROR [http-bio-8090-exec-3] [confluence.plugins.jira.AbstractProxyServlet] requestByAnonymousUser Can not retrieve data from jira servers by anonymous user -- url: /plugins/servlet/image-generator | userName: admin com.atlassian.sal.api.net.ResponseException at com.atlassian.confluence.plugins.jira.ImageGeneratorServlet.handleResponse(ImageGeneratorServlet.java:185) at com.atlassian.confluence.plugins.jira.AbstractProxyServlet.requestByAnonymousUser(AbstractProxyServlet.java:176){noformat} * JIRA logs {noformat}2014-06-04 17:33:33,498 http-bio-8080-exec-6 ERROR anonymous 1053x2945x1 - 192.168.200.3 /rest/gadget/1.0/piechart/generate [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:38) at com.atlassian.jira.charts.piechart.PieChartUrlGeneratorFactory.<init>(PieChartUrlGeneratorFactory.java:41){noformat} h4. Additional Information JIRA 6.2.7 Confluence 5.5.3 h4. Use case There are users who configures JIRA and Confluence integration to be using a different Application URL than the Display URL. This configuration is used when the two servers not able to be contacted between each other using the Display URL. At times this is the prefered configuration with communication between two internal servers to be using internal IP/hostnames instead of the external IP/hostnames. h4. Expected behaviour The charts to be rendered normally in Confluence when using configurations of Display URL different than Application URL. With Display URL not necessarily able to reach the other server, but Application URL can.

    Atlassian JIRA | 2 years ago | Zulfadli Noor Sazali [Atlassian]
    com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.jira.util.dbc.Assertions$NullArgumentException

      parameter should not be null!

      at com.atlassian.jira.util.dbc.Assertions.notNull()
    2. com.atlassian.jira
      EditUserProjectRoles.doExecute
      1. com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:29)
      2. com.atlassian.jira.security.roles.actor.UserRoleActorFactory.createRoleActor(UserRoleActorFactory.java:71)
      3. com.atlassian.jira.security.roles.PluginDelegatingRoleActorFactory.createRoleActor(PluginDelegatingRoleActorFactory.java:38)
      4. com.atlassian.jira.bc.projectroles.DefaultProjectRoleService.createRoleActors(DefaultProjectRoleService.java:962)
      5. com.atlassian.jira.bc.projectroles.DefaultProjectRoleService.updateActorsToProjectRole(DefaultProjectRoleService.java:891)
      6. com.atlassian.jira.bc.projectroles.DefaultProjectRoleService.addActorsToProjectRole(DefaultProjectRoleService.java:1207)
      7. com.atlassian.jira.web.action.admin.user.EditUserProjectRoles.updateRoleActorsForProjectRole(EditUserProjectRoles.java:170)
      8. com.atlassian.jira.web.action.admin.user.EditUserProjectRoles.doExecute(EditUserProjectRoles.java:52)
      8 frames
    3. webwork.action
      ActionSupport.execute
      1. webwork.action.ActionSupport.execute(ActionSupport.java:165)
      1 frame
    4. com.atlassian.jira
      JiraActionSupport.execute
      1. com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:87)
      1 frame
    5. webwork.interceptor
      DefaultInterceptorChain.proceed
      1. webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39)
      1 frame