Hi Matej, this is normal. Clustering expects the same setup on all nodes - and the workspaces are a part of them.
Why do you have so many workspaces? It sounds like you might be better off by organizing your content model into a top-level structure inside one workspace. The number of workspaces should IMHO not depend on "input-data", like requests or content of imported data. Otherwise you can make your application code create all the necessary workspaces on startup - this is the typical way to do it. Regards, Alex On Sun, Jul 13, 2008 at 1:28 AM, Matej Knopp <[EMAIL PROTECTED]> wrote: > Hi, > > I have the following problem when running jackrabbit in clustered > environment. When I create workspace on cluster node A and then add a > node to that workspace, the proper event is sent to the journal, but > other cluster nodes are not able to process it because they don't have > the workspace. > > I did manage to intercept the this making the other nodes create the > workspace (subclassing ClusterNode, peeking in the record inside > #consume and creating the workspace there) but is it really necessary > to have to go over all these hoops? Couldn't be there way (at east an > option) to create workspace any time a node is being added to that > workspace for cluster nodes that don't have the workspace yet? > > Kind regards, > Matej Knopp > -- Alexander Klimetschek [EMAIL PROTECTED]
