• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

ProcessBuilder start() and RMI

 
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I have a server application that has a remote object(call it A). I register it with RMI. I dont run rmic to generate the stubs, but before I bind the object to registry, I do exportObject on the fly and then register it.

Now my server process will spawn new processes and they in turn will talk to my remote objects. The client process also has some remote objects(call it B). But I dont register them with RMI registry, rather pass them as parameters when I call the remote object A's methods. ie A.somethod(B).

To launch the new process, I use ProcessBuilder's start() method. They work fine in my machine in the developemnt environment. But it does not work in my collegues machine.(also development env). The process gets started, but the newly started process never calls back the method in my server object.

Could someone help me what is going wrong here. Also I am not setting any RMISecurityManager either in my server process or in client process. Do I need to set one?

Any help would be appreciated.

Thanks,
Arun.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic