The Axis2 integration already supports clustering. (Well, maybe a better
characterization is that it doesn't get in the way)
There's a few things do to to support clustering. First thing would be to
make the scheduler cluster-aware, to support work distribution (load
balancing) across different
Depending on how the Axis2 integration is done, it may be the case that
Ode would be inheriting Axis2 clustering ... or at least it may be not too
difficult to get that to work right!
Sanjiva.
Alex Boisvert wrote:
This question was asked 2 weeks ago,
http://markmail.org/message/gvnytftb5qpkny
This question was asked 2 weeks ago,
http://markmail.org/message/gvnytftb5qpknywh
alex
On Tue, May 6, 2008 at 7:13 AM, Wilson, Josh <[EMAIL PROTECTED]> wrote:
> Hi All. Has there been any updates on clustering support for ODE? Just
> wondering if there is any active work going on and if so wh
Hi All. Has there been any updates on clustering support for ODE? Just
wondering if there is any active work going on and if so what kind of time
frame we are looking at?
Hi all,
Matthieu Riou-5 wrote:
>
> I would guess it's a transaction boundaries problem again. When the timer
> fires it starts a new transaction, reloading the runtime context and the
> Jacob state for the database. It seems that at this point the timer
> channel
> can't be found which probably
[
https://issues.apache.org/jira/browse/ODE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594514#action_12594514
]
Sukma Verdianto commented on ODE-275:
-
Thanks Alexis,
That should solve the #1 step to ac
