This is mostly done, though I won't know for a while if it actually works.
The only think that it needs is a way to wait until the server has become
active (it is ready to serve) or timeout after x.
This should be fairly straight forward, just a tiny polling client.
start timer
attempt to connect, loop until connected
lookup come mbean (not sure which is best at the moment)
ask it if its done, if not sleep else exit
That would be really helpful when managing scripts which need to background
the vm, but eventually need to know that it is working as configured.
A side note, this could be handled by a seperate vm, which had the sole job
of managing other jboss instances on the same machine. it would run a
stripped down jboss, with a spawenr bean, which would accept jmx, rmi, html,
telnet, whatever requests to start, stop, pool...
Write a simple client-side api & helper objects and you've got yourself a
set sweet tool to manage clusters of jboss instances.
throw a jython or dynamicjava (any bsf really) on top of that and you have a
simple way to control a huge group of such jboss nodes.
--jason
On Thu, 30 Aug 2001, David Jencks wrote:
> On 2001.08.30 00:48:14 -0400 Jason Dillon wrote:
> > > > checkout jboss-all from cvs
> > > > build
> > > > start (in separate jvm)
> > > > run tests
> > > > email results
> > > > stop
> >
> > chicken or the egg.
> >
> > do you mean to update the current workspace, clone the current workspace,
> > or get a workspace without already having one?
> I was thinking new workspace -- I guess I left out the rmdir jboss-all
> step.
> Well, I mostly want an exact copy of cvs. I'm _sure_ i'll get one if I rm
> everything there already and checkout fresh. If you think cvs update -d is
> accurate enough that's ok too. Then you need to completely kill the output
> directories though -- it might be simpler just to do a whole new checkout.
> >
> > the rest is peanuts.
>
> For you, I thought it would be ;-)
>
> btw, do you see any value in adding the depend task before each compile? I
> found it useful on another project.
>
> david jencks
> >
> > --jason
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
