groovy.json.JsonException: Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized.

Atlassian JIRA | Ankur Dhawan | 3 years ago
  1. 0

    When i click on "View issues in issue navigator" in Agile / GH board, it shows me following error "Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized." Also after wards if i click on , isues link available in JIRA it shows me a error message: "The JIRA server could not be contacted. This may be a temporary glitch or the server may be down." This time i also see following error in the logs catalina.out log file: 506x44265x1 mtwyf1 10.178.46.230,127.0.0.1 /rest/api/1.0/menus/find_link [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service groovy.json.JsonException: Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized. at groovy.json.JsonLexer.nextToken(JsonLexer.java:83) at groovy.json.JsonSlurper.parse(JsonSlurper.java:73) at groovy.json.JsonSlurper.parseText(JsonSlurper.java:59) at groovy.json.JsonSlurper$parseText.call(Unknown Source) at com.onresolve.jira.groovy.jql.IssuesInSprint.execMethod(script13729186275822048495194.groovy:117) at com.onresolve.jira.groovy.jql.IssuesInSprint.this$3$execMethod(script13729186275822048495194.groovy) at sun.reflect.GeneratedMethodAccessor1850.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) this is happening every time I follow these two steps, if i login and click on Issues link, it brings up all options properly.. Can you look into this issue..

    JIRA | 3 years ago | Ankur Dhawan
    groovy.json.JsonException: Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized.
  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-291].{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 i click on "View issues in issue navigator" in Agile / GH board, it shows me following error "Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized." Also after wards if i click on , isues link available in JIRA it shows me a error message: "The JIRA server could not be contacted. This may be a temporary glitch or the server may be down." This time i also see following error in the logs catalina.out log file: 506x44265x1 mtwyf1 10.178.46.230,127.0.0.1 /rest/api/1.0/menus/find_link [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service groovy.json.JsonException: Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized. at groovy.json.JsonLexer.nextToken(JsonLexer.java:83) at groovy.json.JsonSlurper.parse(JsonSlurper.java:73) at groovy.json.JsonSlurper.parseText(JsonSlurper.java:59) at groovy.json.JsonSlurper$parseText.call(Unknown Source) at com.onresolve.jira.groovy.jql.IssuesInSprint.execMethod(script13729186275822048495194.groovy:117) at com.onresolve.jira.groovy.jql.IssuesInSprint.this$3$execMethod(script13729186275822048495194.groovy) at sun.reflect.GeneratedMethodAccessor1850.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) this is happening every time I follow these two steps, if i login and click on Issues link, it brings up all options properly.. Can you look into this issue..

    JIRA | 3 years ago | Ankur Dhawan
    groovy.json.JsonException: Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized.
  3. 0

    When i click on "View issues in issue navigator" in Agile / GH board, it shows me following error "Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized." Also after wards if i click on , isues link available in JIRA it shows me a error message: "The JIRA server could not be contacted. This may be a temporary glitch or the server may be down." This time i also see following error in the logs catalina.out log file: 506x44265x1 mtwyf1 10.178.46.230,127.0.0.1 /rest/api/1.0/menus/find_link [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service groovy.json.JsonException: Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized. at groovy.json.JsonLexer.nextToken(JsonLexer.java:83) at groovy.json.JsonSlurper.parse(JsonSlurper.java:73) at groovy.json.JsonSlurper.parseText(JsonSlurper.java:59) at groovy.json.JsonSlurper$parseText.call(Unknown Source) at com.onresolve.jira.groovy.jql.IssuesInSprint.execMethod(script13729186275822048495194.groovy:117) at com.onresolve.jira.groovy.jql.IssuesInSprint.this$3$execMethod(script13729186275822048495194.groovy) at sun.reflect.GeneratedMethodAccessor1850.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) this is happening every time I follow these two steps, if i login and click on Issues link, it brings up all options properly.. Can you look into this issue..

    Atlassian JIRA | 3 years ago | Ankur Dhawan
    groovy.json.JsonException: Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    When i click on "View issues in issue navigator" in Agile / GH board, it shows me following error "Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized." Also after wards if i click on , isues link available in JIRA it shows me a error message: "The JIRA server could not be contacted. This may be a temporary glitch or the server may be down." This time i also see following error in the logs catalina.out log file: 506x44265x1 mtwyf1 10.178.46.230,127.0.0.1 /rest/api/1.0/menus/find_link [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service groovy.json.JsonException: Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized. at groovy.json.JsonLexer.nextToken(JsonLexer.java:83) at groovy.json.JsonSlurper.parse(JsonSlurper.java:73) at groovy.json.JsonSlurper.parseText(JsonSlurper.java:59) at groovy.json.JsonSlurper$parseText.call(Unknown Source) at com.onresolve.jira.groovy.jql.IssuesInSprint.execMethod(script13729186275822048495194.groovy:117) at com.onresolve.jira.groovy.jql.IssuesInSprint.this$3$execMethod(script13729186275822048495194.groovy) at sun.reflect.GeneratedMethodAccessor1850.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) this is happening every time I follow these two steps, if i login and click on Issues link, it brings up all options properly.. Can you look into this issue..

    Atlassian JIRA | 3 years ago | Ankur Dhawan
    groovy.json.JsonException: Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized.
  6. 0

    Serviio • View topic - SeasonVar.ru (Web Resource)

    serviio.org | 8 months ago
    org.serviio.library.online.metadata.OnlineResourceParseException: Unexpected error while invoking plugin (SeasonVar): Lexing failed on line: 1, column: 8, while reading 'i', no possible valid JSON value or punctuation could be recognized.

    1 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. groovy.json.JsonException

      Lexing failed on line: 7, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized.

      at groovy.json.JsonLexer.nextToken()
    2. Groovy
      JsonSlurper$parseText.call
      1. groovy.json.JsonLexer.nextToken(JsonLexer.java:83)
      2. groovy.json.JsonSlurper.parse(JsonSlurper.java:73)
      3. groovy.json.JsonSlurper.parseText(JsonSlurper.java:59)
      4. groovy.json.JsonSlurper$parseText.call(Unknown Source)
      4 frames
    3. com.onresolve.jira
      IssuesInSprint.this$3$execMethod
      1. com.onresolve.jira.groovy.jql.IssuesInSprint.execMethod(script13729186275822048495194.groovy:117)
      2. com.onresolve.jira.groovy.jql.IssuesInSprint.this$3$execMethod(script13729186275822048495194.groovy)
      2 frames
    4. Java RT
      Method.invoke
      1. sun.reflect.GeneratedMethodAccessor1850.invoke(Unknown Source)
      2. sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      3. java.lang.reflect.Method.invoke(Unknown Source)
      3 frames