Results 1 to 3 of 3

Thread: Object reference no longer valid

  1. #1
    Join Date
    Jan 2007
    Location
    Norway.
    Posts
    20

    Unhappy Object reference no longer valid

    Hi.

    I use a SimpleRemoteStatelessSessionProxyFactoryBean to connect to an EJB on an OC4J appserver. While stresstesting some transaction logic, I kept killing the server to see if the transaction was able to complete on reconnect. This worked well most times, however, som times I got the error:

    Object reference no longer valid (Disconnected)

    With this error, Spring was not able to reload. I have set RefreshHomeOnConnectFailure, and as I said it works most of the time. It seems spring holds on to a connection it thinks is valid somehow. Is there anyway to make a complete refresh of the context, so that it can "start fresh"? If I restart the client without restarting the server after an error like this, everything works normally, so there must be something on the client.

    Any ideas?
    Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end. (Henry Spencer)

  2. #2
    Join Date
    Aug 2004
    Posts
    2,715

    Default

    Maybe there is a case for which Spring could not detect that a connect failure happened. I suggest opening a Jira report (if none already exists) providing a full stacktrace.

    Regards,
    Andreas

  3. #3
    Join Date
    Jan 2007
    Location
    Norway.
    Posts
    20

    Default Done

    Here is the solution. Check it out.

    http://opensource.atlassian.com/proj...rowse/SPR-3113
    Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end. (Henry Spencer)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •