Results 1 to 2 of 2

Thread: remoting using RMI and not always reachable server

  1. #1
    Join Date
    Apr 2005
    Posts
    23

    Default remoting using RMI and not always reachable server

    Hi,

    I've just started with spring yesterday, so please be patient

    I tried the RMI remoting example, and changed it a bit, and it works fine.

    However, I'm trying to use it in a scenario where the server won't always be up, so I'm not really sure how to configure the client. The problem is that if I use the normal config, the client won't even boot if the server is down (the client has several other features, so it should still boot, even without a server).

    So I was wondering what can I do about this, and after reading the spring reference, I'm thinking about having org.springframework.remoting.rmi.RmiProxyFactoryBe an configured as a prototype (non-singleton), so that it is only instantiated when my apps need actual remoting functionality.

    Is this the best way ? Any considerations ?

    thanks
    Ricardo

  2. #2
    Join Date
    Aug 2004
    Location
    Carlisle, UK
    Posts
    184

    Default

    I think in your config for RmiProxyFactoryBean, you want to set lookupStubOnStartup to false.
    You probably also want to set refreshStubOnConnectFailure to true.

    HTH
    Chris Harris
    Carlisle, UK

Posting Permissions

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