• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

RMI/JMS/???

 
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I'm looking for a solution to the following problem: we have a JVM1 in a app. server and JVM2 on web server. When something happens (an event fires) in AS I need to contact some object in JVM2. Now, I'm thinking JMS rather than RMI - can anyone point out which one is better and why?

To make things more interesting, most likely the clustering architecture will be involved.

I'd appreciate a comment, a simple example, whatever from someone that has already seen a situation similar to this one.

TIA,
Bojan
 
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
JMS you can use it for non-Java client. Where
RMI as known specific to Java client.

As you said there will be 2 JVM understood both willbe running in Java. So I hope RMi might useful .
 
Ranch Hand
Posts: 312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Natarajan Shankar:
JMS you can use it for non-Java client. Where RMI as known specific to Java client.

As you said there will be 2 JVM understood both willbe running in Java. So I hope RMi might useful .



JMS - Java Messaging Service is only for Java Clients. IBM MQSeries support any clients written in Java, C and JMS is basically for Asynchronous communication. i.e Sender will send the request and does not required to wait till it gets the response.

RMI - Remote Method Invocation is basically for Synchronous communication.
i.e Sender will send the request and wait till it gets the response.

You can choose the technology based on your synchronous/Asynchronous mode of communication.

Regards,
M.S.Raman.
 
When it is used for evil, then watch out! When it is used for good, then things are much nicer. Like this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
    Bookmark Topic Watch Topic
  • New Topic