> -----Original Message-----
> From: David Jencks [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 12, 2001 5:40 PM
> To: Bill Burke
> Cc: Andreas Schaefer; Sacha Labourey;
> [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] RE: Deployment exception on Clustering
>
>
> What are the mbean dependencies here? Is it possible to add a service to a
> running cluster? How is it synchronized? (what does synchronized
> mean here,
> anyway?).
>
Unfortunately at this moment in time it is not possible to hot-deploy a
clustered service that depends on state-transfer. You can hot-deploy
clustered EJBs though, well at least for SLSB and EBs. Sacha, what about
SFSBs?
> If it is not possible to add a service to a started cluster, you should
> document the contents of the cluster with an mbean-ref-list tag including
> all mbean-ref-list-elements participating in the cluster. The cluster can
> then do whatever it wants with them, they will be started before the
> cluster is started.
>
Yes, yes. I know about dependencies.
> If it is possible to add a service to a started cluster, each service can
> depend on the cluster, so it will be started after the cluster,
> and can get
> whatever synchronization it needs set up when it starts.
>
> What are the problems with this approach? I used the second with jbossmq
> startup.
>
Services requiring state-transfer like HA-JNDI must register with an object
created by the ClusterPartition. The ClusterPartition cannot complete
JavaGroups connections until the all these HA services have registered with
the ClusterPartition. The ClusterPartition should not know about who
depends on it.
Because of quirkiness of JavaGroups, services cannot ask for
state-synchronization once the Group connection has been initiated.
BTW, I originally did nothing in init(), until I discovered that I needed a
2 phase initialization. Please, trust me, I need 2 phase initialization in
order for a clean design.
Bill
> thanks
> david jencks
>
> On 2001.11.12 16:10:27 -0500 Bill Burke wrote:
> > Yes this a very serious problem and it wouldn't show up with your Farm
> > stuff. THis is my fault because I didn't document the code very well,
> > but
> > can we please switch this back?
> >
> > In the init phase, all services register with the cluster (HAPartition)
> > for
> > cluster events that want to listen to and also if they require state
> > synchronization. In the start phase, the ClusterPartition
> mbean does the
> > final Connect to the JavaGroups message Channel. When the Connect
> > happens,
> > state synchronization starts. Services will not have their state
> > synchronized if everything is done in the start phase.
> >
> > Bill
> >
> > > -----Original Message-----
> > > From: Andreas Schaefer [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, November 12, 2001 3:50 PM
> > > To: Bill Burke
> > > Cc: Sacha Labourey; [EMAIL PROTECTED]
> > > Subject: Re: Deployment exception on Clustering
> > >
> > >
> > > Hi Bill
> > >
> > > I added all the code from init() into start(). Is this a problem ?
> > >
> > > At least when I use the Farm it works like a charm.
> > >
> > > Andy
> > >
> > > ----- Original Message -----
> > > From: "Bill Burke" <[EMAIL PROTECTED]>
> > > To: "David Jencks" <[EMAIL PROTECTED]>; "Andreas
> > Schaefer"
> > > <[EMAIL PROTECTED]>
> > > Cc: "Sacha Labourey" <[EMAIL PROTECTED]>;
> > > <[EMAIL PROTECTED]>
> > > Sent: Monday, November 12, 2001 12:59 PM
> > > Subject: RE: Deployment exception on Clustering
> > >
> > >
> > > > Guys,
> > > >
> > > > The clustering stuff is dependent on init and start both being
> > > there. Can
> > > > we put back the init? Otherwise you break our stuff. Why are you
> > doing
> > > > this anyways?
> > > >
> > > > Bill
> > > >
> > > > > -----Original Message-----
> > > > > From: David Jencks [mailto:[EMAIL PROTECTED]]
> > > > > Sent: Monday, November 12, 2001 2:33 PM
> > > > > To: Andreas Schaefer
> > > > > Cc: David Jencks; Bill Burke; Sacha Labourey;
> > > > > [EMAIL PROTECTED]
> > > > > Subject: Re: Deployment exception on Clustering
> > > > >
> > > > >
> > > > > Thanks, must have missed that one.
> > > > >
> > > > > I generally copied the init[Service] code and put it in
> > start[Service]
> > > at
> > > > > the beginning, similarly for destroy.
> > > > >
> > > > > As far as I could tell, everything covered by the testsuite works
> > as
> > > well
> > > > > after the changes as before.
> > > > >
> > > > > Please let me know of other problems.
> > > > >
> > > > > The Service interface still has init and destroy since these are
> > used
> > > > > heavily in the interceptor chain. I think they are unnecessary,
> > but
> > > won't
> > > > > have time to try to change them for a while. This could probably
> > > > > be a part
> > > > > if turning the interceptor chains into mbeans.
> > > > >
> > > > > Thanks!
> > > > > david jencks
> > > > >
> > > > > On 2001.11.12 14:13:41 -0500 Andreas Schaefer wrote:
> > > > > > Hi David
> > > > > >
> > > > > > The ClusterPartition.java class is not started correctly
> > > > > > because now init() is not called anymore and therefore
> > > > > > the JavaGroups JChannel are not initialized.
> > > > > >
> > > > > > I will go ahead and fix it but maybe there are other MBeans
> > > > > > out there which needs attention, too.
> > > > > >
> > > > > > Thanx
> > > > > >
> > > > > > xxxxxxxxxxxxxxxxx
> > > > > > Andreas Schaefer
> > > > > > Senior Consultant
> > > > > > JBoss Group, LLC
> > > > > > xxxxxxxxxxxxxxxxx
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
