java.lang.NumberFormatException: null

JIRA | Michael Garvin | 2 years ago
  1. 0

    {panel:title=*This issue has moved*} {color:red}This issue has been moved permanently to [Adaptavist's Product Support JIRA instance|https://productsupport.adaptavist.com/browse/GRV-615].{color} All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the [Can't access your account|https://productsupport.adaptavist.com/secure/ForgotLoginDetails.jspa] link in order to reset to a new password. {panel}When upgraded to JIRA 6.2.6 we saw a flood of Null pointer excpetions in our JIRA log (catalina.out) due to JIRA Behaviors plugin. We've fixed our Groovy scripting, but still many errors from the Java/Groovy source code of the JIRA Behaviors related classes themselves...which can not fix since we do not have source code for the Script Runner plugin. We have had stability issues with JIRA and in order ensure JIRA Behaviors is not the root cause, we need to get the null pointer exceptions cleaned up, not just in case they are the root cause, but because in large installations like ours, large amounts of file writing (exceptions) to the JIRA log causes JIRA to have timing issues. So we need to make our log quiet, and one of the biggest contributors ... is JIRA Behaviors. The example case is: - The MoveUpdateIssue.jspa page - The CreateIssue.jspa page (right click on Create Issue and select Open in New Tab) In such cases we see the plugin do a post like this: {code} POST https://.../rest/com.onreso...ugin.Behaviours/1.0/behaviours/runvalidator.json 500 Internal Server Error {code} Via: https://.../MoveIssueUpdateFields!default.jspa?id=685918&assignee=null and we get an exception (in the log) like this: {code} 2015-01-30 16:39:35,965 http-bio-8080-exec-7 ERROR mgarvin 999x221659x1 1ysivrm 135.105.162.188,0:0:0:0:0:0:0:1 /rest/com.onresolve.jira.plugin.Behaviours/1.0/behaviours/runvalidator.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: null java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:404) at java.lang.Long.parseLong(Long.java:483) at java_lang_Long$parseLong.call(Unknown Source) at com.onresolve.jira.behaviours.BehaviourManagerImpl.runValidator(BehaviourManagerImpl.groovy:115) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166) at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145) at com.onresolve.jira.behaviours.BehaviourManagerImpl.runValidator(BehaviourManagerImpl.groovy:95) at com.onresolve.jira.behaviours.restservice.BehavioursEndpoint.runValidator(BehavioursEndpoint.groovy:74) … {code} I can provide more detail but it will need to be by email/PM, as this is a public support site.

    JIRA | 2 years ago | Michael Garvin
    java.lang.NumberFormatException: null
  2. 0

    {panel:title=*This issue has moved*} {color:red}This issue has been moved permanently to [Adaptavist's Product Support JIRA instance|https://productsupport.adaptavist.com/browse/GRV-615].{color} All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the [Can't access your account|https://productsupport.adaptavist.com/secure/ForgotLoginDetails.jspa] link in order to reset to a new password. {panel}When upgraded to JIRA 6.2.6 we saw a flood of Null pointer excpetions in our JIRA log (catalina.out) due to JIRA Behaviors plugin. We've fixed our Groovy scripting, but still many errors from the Java/Groovy source code of the JIRA Behaviors related classes themselves...which can not fix since we do not have source code for the Script Runner plugin. We have had stability issues with JIRA and in order ensure JIRA Behaviors is not the root cause, we need to get the null pointer exceptions cleaned up, not just in case they are the root cause, but because in large installations like ours, large amounts of file writing (exceptions) to the JIRA log causes JIRA to have timing issues. So we need to make our log quiet, and one of the biggest contributors ... is JIRA Behaviors. The example case is: - The MoveUpdateIssue.jspa page - The CreateIssue.jspa page (right click on Create Issue and select Open in New Tab) In such cases we see the plugin do a post like this: {code} POST https://.../rest/com.onreso...ugin.Behaviours/1.0/behaviours/runvalidator.json 500 Internal Server Error {code} Via: https://.../MoveIssueUpdateFields!default.jspa?id=685918&assignee=null and we get an exception (in the log) like this: {code} 2015-01-30 16:39:35,965 http-bio-8080-exec-7 ERROR mgarvin 999x221659x1 1ysivrm 135.105.162.188,0:0:0:0:0:0:0:1 /rest/com.onresolve.jira.plugin.Behaviours/1.0/behaviours/runvalidator.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: null java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:404) at java.lang.Long.parseLong(Long.java:483) at java_lang_Long$parseLong.call(Unknown Source) at com.onresolve.jira.behaviours.BehaviourManagerImpl.runValidator(BehaviourManagerImpl.groovy:115) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166) at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145) at com.onresolve.jira.behaviours.BehaviourManagerImpl.runValidator(BehaviourManagerImpl.groovy:95) at com.onresolve.jira.behaviours.restservice.BehavioursEndpoint.runValidator(BehavioursEndpoint.groovy:74) … {code} I can provide more detail but it will need to be by email/PM, as this is a public support site.

    JIRA | 2 years ago | Michael Garvin
    java.lang.NumberFormatException: null
  3. 0

    Any validation script set for components field, e.g. {code}String str = "1"{code} produced java.lang.NumberFormatException: null when issue is being moved to another type or project. /rest/com.onresolve.jira.plugin.Behaviours/1.0/behaviours/runvalidator.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service java.lang.NumberFormatException: null at java.lang.Long.parseLong(Unknown Source) at java.lang.Long.parseLong(Unknown Source) at java_lang_Long$parseLong.call(Unknown Source) at com.onresolve.jira.groovy.BehaviourManagerImpl.runValidator(BehaviourManagerImpl.groovy:106) at sun.reflect.GeneratedMethodAccessor1873.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:231) at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:52) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145) at com.onresolve.jira.groovy.BehaviourManagerImpl.runValidator(BehaviourManagerImpl.groovy:88) at com.onresolve.jira.behaviour.restservice.MessageResource.runValidator(MessageResource.java:75) at sun.reflect.GeneratedMethodAccessor1872.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source)

    JIRA | 3 years ago | Jaroslaw L.
    java.lang.NumberFormatException: null
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [groovy-user] Negative hex string conversion to long

    Google Groups | 5 years ago | citron
    java.lang.NumberFormatException: For input string: "80000000000000004308000000000000"

  1. treefolk 1 times, last 2 weeks ago
  2. MoYapro 5 times, last 3 weeks ago
  3. Handemelindo 2 times, last 1 month ago
  4. marcbouvierdav 1 times, last 2 months ago
  5. tyson925 4 times, last 2 months ago
13 more registered users
17 unregistered visitors
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. java.lang.NumberFormatException

    null

    at java.lang.Long.parseLong()
  2. Java RT
    Long.parseLong
    1. java.lang.Long.parseLong(Long.java:404)
    2. java.lang.Long.parseLong(Long.java:483)
    2 frames
  3. Unknown
    java_lang_Long$parseLong.call
    1. java_lang_Long$parseLong.call(Unknown Source)
    1 frame
  4. com.onresolve.jira
    BehaviourManagerImpl.runValidator
    1. com.onresolve.jira.behaviours.BehaviourManagerImpl.runValidator(BehaviourManagerImpl.groovy:115)
    1 frame
  5. Java RT
    Method.invoke
    1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    2. sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    3. sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    4. java.lang.reflect.Method.invoke(Method.java:606)
    4 frames
  6. Groovy
    AbstractCallSite.callCurrent
    1. org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166)
    2. org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:56)
    3. org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145)
    3 frames
  7. com.onresolve.jira
    BehavioursEndpoint.runValidator
    1. com.onresolve.jira.behaviours.BehaviourManagerImpl.runValidator(BehaviourManagerImpl.groovy:95)
    2. com.onresolve.jira.behaviours.restservice.BehavioursEndpoint.runValidator(BehavioursEndpoint.groovy:74)
    2 frames