• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Space pointer error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Space pointer error

    Hi Support,

    We're having internal pointer error problems that we can't trace. I've been able to trace a job log showing following:

    Message ID . . . . . . : MCH0601 Severity . . . . . . . : 40
    Message type . . . . . : Escape
    Date sent . . . . . . : 22/04/20 Time sent . . . . . . : 12:28:39

    Message . . . . : Space offset X'00000000' or X'0000000DB93A9AC0' is outside
    current limit for object VALENCE52PQTMHHTTP 032979.
    Cause . . . . . : A program tried to set a space pointer, tried to use
    storage outside a space, or tried to use an unallocated page in teraspace.
    The space class is X'07'. The space class designates the type of space:
    00-primary associated space (includes space objects).
    01-secondary associated space 0.
    02-implicit process space for automatic storage.
    03-implicit process space for static storage in activation group mark
    X'0000000000000000'.
    04-implicit process space for heap identifier X'00000000' in activation
    group mark X'0000000000000000'.
    05-constant space.
    06-space for handle-based heap identifier X'00000000'.
    07-teraspace offset X'0000000DB93A9AC0'.
    08-teraspace for System i5 PASE memory address X'0000000DB93A9AC0'.
    Offset X'00000000' only applies to storage outside teraspace.
    X'80000000000000000000000DB93A9AC0' is a pointer to the teraspace page or
    the start of the implicit process space for the allocation.

    Doing F9 to show message details reveals:

    Message ID . . . . . . : MCH0601 Severity . . . . . . . : 40
    Date sent . . . . . . : 22/04/20 Time sent . . . . . . : 12:38:39
    Message type . . . . . : Escape
    From . . . . . . . . . : QTMHHTP1 CCSID . . . . . . . . : 65535

    From program . . . . . . . . . : ARRAYLIST
    From library . . . . . . . . : VALENCE52P
    From module . . . . . . . . : ARRAYLIST
    From procedure . . . . . . . : arraylist_get
    From statement . . . . . . . : 417

    To program . . . . . . . . . . : ARRAYLIST
    To library . . . . . . . . . : VALENCE52P
    To module . . . . . . . . . : ARRAYLIST
    To procedure . . . . . . . . : arraylist_get
    To statement . . . . . . . . : 417


    I think this causes HTTP server to slow down because users complain. But the job remains active and continues anyway, users just try again.

  • #2
    Hi Peter,

    This appears to be coming from the JSON parse utility. Do any of your programs use VVJSON? Are you sure the job is not terminating or going into MSGW? Seems odd that it would just continue after a message of that severity. It would be really helpful to see a call stack at the time of the error. Is anything getting thrown into the Valence error log?

    Is there a specific program or app they're using that appears to trigger this problem where the users just try again?
    Last edited by robert.swanson; 04-22-2020, 09:54 AM.

    Comment


    • #3
      This will take some effort to trace because this is a live application and there are hundreds of external users. Let me do some investigation tomorrow.

      Comment

      Working...
      X