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

Atlassian JIRA | Zulfadli Noor Sazali [Atlassian] | 3 years ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 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 | 3 years ago | Zulfadli Noor Sazali [Atlassian]
    com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
  2. 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 | 3 years ago | Zulfadli Noor Sazali [Atlassian]
    com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
  3. 0

    Could not determine database type - Atlassian Answers

    atlassian.com | 1 year ago
    com.atlassian.jira.util.dbc.Assertions$NullArgumentException: jiraLicenseService should not be null!
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    If I install a plugin in the /plugins/installed-plugins directory that doesn't have a pluginsVersion="2" in the atlassian-plugin.xml, I see the following error in the logs and nothing else to indicate what the problem might be: {noformat} 2009-05-04 11:00:21,386 main ERROR [com.atlassian.jira.ComponentManager] Error occurred while starting PluginManager. com.atlassian.jira.util.dbc.Assertions$NullArgumentException: name should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:24) at com.atlassian.jira.util.dbc.Null.not(Null.java:12) at com.atlassian.jira.plugin.PluginVersionImpl.<init>(PluginVersionImpl.java:31) at com.atlassian.jira.plugin.JiraPluginManager.storePluginVersion(JiraPluginManager.java:155) at com.atlassian.jira.plugin.JiraPluginManager.storePluginVersions(JiraPluginManager.java:130) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:50) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1243) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:197) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:183) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:59) at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:40) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:709) at org.apache.catalina.startup.Catalina.start(Catalina.java:551) 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:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432) 2009-05-04 11:00:21,388 main FATAL [atlassian.jira.upgrade.ConsistencyLauncher] A RuntimeException occurred during ConsistencyLauncher servlet context initialisation - Error occurred while starting PluginManager.. com.atlassian.jira.InfrastructureException: Error occurred while starting PluginManager. at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1248) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:197) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:183) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:59) at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:40) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:709) at org.apache.catalina.startup.Catalina.start(Catalina.java:551) 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:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432) Caused by: com.atlassian.jira.util.dbc.Assertions$NullArgumentException: name should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:24) at com.atlassian.jira.util.dbc.Null.not(Null.java:12) at com.atlassian.jira.plugin.PluginVersionImpl.<init>(PluginVersionImpl.java:31) at com.atlassian.jira.plugin.JiraPluginManager.storePluginVersion(JiraPluginManager.java:155) at com.atlassian.jira.plugin.JiraPluginManager.storePluginVersions(JiraPluginManager.java:130) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:50) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1243) ... 19 more {noformat} and JIRA doesn't start. The following error indicates the problem, but really, there should be an error saying plugin "blah.jar" has an invalid descriptor: {noformat} 2009-05-04 11:00:20,113 main INFO [atlassian.plugin.manager.DefaultPluginManager] Updating plugin 'auiplugin-0.8-dashboardAJS.jar:0.0 No plugin factories found for plugin file Unit: /home/jroper/src/atlassian/upm/acceptance-tests/jira/target/jira-home/plugins/.bundled-plugins/auiplugin-0.8-dashboardAJS.jar (1241398806000)' to 'auiplugin-0.8-dashboardAJS.jar:0.0 No plugin factories found for plugin file Unit: /home/jroper/src/atlassian/upm/acceptance-tests/jira/target/jira-home/plugins/installed-plugins/auiplugin-0.8-dashboardAJS.jar (1241162237000)' {noformat}

    Atlassian JIRA | 8 years ago | James Roper [Atlassian]
    com.atlassian.jira.util.dbc.Assertions$NullArgumentException: name should not be null!
  6. 0

    {noformat} java.lang.RuntimeException: Could not open JAR file for reading: e:\blitz\home\plugins\installed-plugins\jira-toolkit-0.7.29-SNAPSHOT.jar at com.atlassian.plugin.JarPluginArtifact.getInputStream(JarPluginArtifact.java:106) at com.atlassian.plugin.factories.XmlDynamicPluginFactory.canCreate(XmlDynamicPluginFactory.java:123) at com.atlassian.plugin.loaders.ScanningPluginLoader.deployPluginFromUnit(ScanningPluginLoader.java:111) at com.atlassian.plugin.loaders.ScanningPluginLoader.loadAllPlugins(ScanningPluginLoader.java:87) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:150) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1276) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:200) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:186) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:59) at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:40) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) 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:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Caused by: java.io.FileNotFoundException: e:\blitz\home\plugins\installed-plugins\jira-toolkit-0.7.29-SNAPSHOT.jar (Access is denied) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at com.atlassian.plugin.JarPluginArtifact.getInputStream(JarPluginArtifact.java:102) ... 25 more 2009-06-11 19:42:53,970 Main Thread INFO [atlassian.plugin.manager.DefaultPluginManager] Plugin system started in 0:00:15.734 2009-06-11 19:42:53,970 Main Thread ERROR [com.atlassian.jira.ComponentManager] Error occurred while starting PluginManager. com.atlassian.jira.util.dbc.Assertions$NullArgumentException: name should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:24) at com.atlassian.jira.util.dbc.Null.not(Null.java:12) at com.atlassian.jira.plugin.PluginVersionImpl.<init>(PluginVersionImpl.java:31) at com.atlassian.jira.plugin.JiraPluginManager.storePluginVersion(JiraPluginManager.java:155) at com.atlassian.jira.plugin.JiraPluginManager.storePluginVersions(JiraPluginManager.java:130) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:50) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1276) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:200) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:186) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:59) at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:40) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) 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:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) 2009-06-11 19:42:53,986 Main Thread FATAL [atlassian.jira.upgrade.ConsistencyLauncher] A RuntimeException occurred during ConsistencyLauncher servlet context initialisation - Error occurred while starting PluginManager.. com.atlassian.jira.InfrastructureException: Error occurred while starting PluginManager. at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1281) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:200) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:186) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:59) at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:40) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) 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:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Caused by: com.atlassian.jira.util.dbc.Assertions$NullArgumentException: name should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:24) at com.atlassian.jira.util.dbc.Null.not(Null.java:12) at com.atlassian.jira.plugin.PluginVersionImpl.<init>(PluginVersionImpl.java:31) at com.atlassian.jira.plugin.JiraPluginManager.storePluginVersion(JiraPluginManager.java:155) at com.atlassian.jira.plugin.JiraPluginManager.storePluginVersions(JiraPluginManager.java:130) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:50) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1276) {noformat}

    Atlassian JIRA | 8 years ago | Brenden Bain [Atlassian]
    com.atlassian.jira.util.dbc.Assertions$NullArgumentException: name 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
      Assertions.notNull
      1. com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:38)
      1 frame