-[NSInvocation length]: selector not recognized [self = 0x30abd0]

  • Hello,

    I am posting this question again today, hoping somebody can give me a clue
    what I am missing. I am using distributed objects and managed to talk to
    server.
    Client is getting responses successfully from the server. However the
    problem is when client
    receives session id from the server and try to use that session id for
    further queries
    with the soap api it always get the error message from the server saying

    -[NSInvocation length]: selector not recognized [self = 0x30abd0]

    I do not understand what is that I am doing wrong. Do tell me if this is not
    the mailing list
    where I should post distributed object related stuff.

    Best regards

    S
  • On Sep 23, 2007, at 3:33 PM, NSTask wrote:

    > I am posting this question again today, hoping somebody can give me
    > a clue what I am missing. I am using distributed objects and
    > managed to talk to server. Client is getting responses successfully
    > from the server. However the problem is when client receives
    > session id from the server and try to use that session id for
    > further queries with the soap api it always get the error message
    > from the server saying
    >
    > -[NSInvocation length]: selector not recognized [self = 0x30abd0]

    If this error isn't the result of you obviously sending an message to
    an object which doesn't understand it, it is often the result of
    sending a message to a deallocated object (and a new object happens
    to exist at the same address as the old object.)

    NSZombie (in addition to reviewing your memory management code) is
    your first step to debugging this problem.

    Jim
  • Hi Jim,

    On 9/23/07, Jim Correia <jim.correia...> wrote:
    >
    > On Sep 23, 2007, at 3:33 PM, NSTask wrote:
    >
    >> I am posting this question again today, hoping somebody can give me
    >> a clue what I am missing. I am using distributed objects and
    >> managed to talk to server. Client is getting responses successfully
    >> from the server. However the problem is when client receives
    >> session id from the server and try to use that session id for
    >> further queries with the soap api it always get the error message
    >> from the server saying
    >>
    >> -[NSInvocation length]: selector not recognized [self = 0x30abd0]
    >
    > If this error isn't the result of you obviously sending an message to
    > an object which doesn't understand it, it is often the result of
    > sending a message to a deallocated object (and a new object happens
    > to exist at the same address as the old object.)
    >
    > NSZombie (in addition to reviewing your memory management code) is
    > your first step to debugging this problem.

    NSZombie has returned this.

    Selector 'retain' sent to dealloced instance 0x30ca40 of class NSInvocation.
    Break at '-[_NSZombie retain]' to debug.

    /S
  • On 9/23/07, NSTask <nstask...> wrote:
    > Hi Jim,
    >
    >
    > On 9/23/07, Jim Correia <jim.correia...> wrote:
    >>
    >> On Sep 23, 2007, at 3:33 PM, NSTask wrote:
    >>
    >>> I am posting this question again today, hoping somebody can give me
    >>> a clue what I am missing. I am using distributed objects and
    >>> managed to talk to server. Client is getting responses successfully
    >>> from the server. However the problem is when client receives
    >>> session id from the server and try to use that session id for
    >>> further queries with the soap api it always get the error message
    >>> from the server saying
    >>>
    >>> -[NSInvocation length]: selector not recognized [self = 0x30abd0]
    >>
    >> If this error isn't the result of you obviously sending an message to
    >> an object which doesn't understand it, it is often the result of
    >> sending a message to a deallocated object (and a new object happens
    >> to exist at the same address as the old object.)
    >>
    >> NSZombie (in addition to reviewing your memory management code) is
    >> your first step to debugging this problem.
    >
    >
    >
    > NSZombie has returned this.
    >
    > Selector 'retain' sent to dealloced instance 0x30ca40 of class NSInvocation.
    > Break at '-[_NSZombie retain]' to debug.

    Have you followed the advice given in that message? If you do so, then
    you'll see who exactly is retaining the dead object.

    --
    Clark S. Cox III
    <clarkcox3...>
previous month september 2007 next month
MTWTFSS
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
Go to today