[Opensource] Future Code for Expresso 5.1 and beyond [LONG THINK TANK ARTICLE]

[Michael Rimov]

At 08:14 AM 11/5/2002 -0700, you wrote:

<snip> <snip>

> >
> > STEP 3: Work on an out of VM Job Handler.  AFAICT, this will require
> > something like RMI to provide decent IPC communication to the Job
> > Handler.  [Or JMS if we want multiple Job Servers].  This would
> > DEFINITELY
> > be a replacement component for the in-VM Job Handler since it
> > would require
> > additional servers such as RMI Registry or JMS server.  But we
> > can work on
> > it without affecting the current code base because we've componentized
> > JobHandler as listed in step 1.
>
>I have worked with RMI in the past and found it unsatisfying and would like
>to recommend a JMS server solution but to be fair in my vote, I have never
>worked with JMS before so it might be just as much or more of a pain then
>RMI.  Any comments from folks who have done a JMS implementation, would this
>be a good use of JMS?

Well, I've used OpenJMS and JBoss JMS via the Apache Messenger 
project.  I've had troubles with Messages disappearing, it could be Apache 
Messenger's fault rather than the server, but I HAVE seen bugs in the 
Spyder MQ (JBOSS) that the author classed as critical that could have had 
an affect on the work.  Obviously there are good JMS servers out there... 
otherwise aspects of NASDAQ, Southwest Airlines, etc wouldn't be run off of 
a Message Queuing system.  It's just that so far I haven't been able to get 
something to work reliably, and have been unable to get help from the 
respective communities.

In fact the very project that I was going to use JMS for, I ended up 
switching back to RMI and got it all working fairly good.

We also could just do raw sockets authenticated with a shared secret stored 
in expresso-config.xml too. [I believe this is how the mod_jk Apache to 
Tomcat modules do it].

                                                 -Mike