Hi Colm,
Massimiliano's answer is the best one and the way to follow.
I add this only for completion and to give visibility to a new technology.
In your case another approach could be the docker one.
You could have on the same machine two instances of docker running the same
syncope with the same
Thanks Massi, I have it working now, although I ran into issues with the H2
approach, I'm using MySQL instead and it works perfectly.
Colm.
On Wed, Jan 6, 2016 at 3:05 PM, Massimiliano Perrone <
massimiliano.perr...@tirasa.net> wrote:
>
>
> Il 06/01/2016 15:58, Colm O hEigeartaigh ha scritto:
>
Il 06/01/2016 15:58, Colm O hEigeartaigh ha scritto:
I'm aware of that :-) Obviously the Tomcat instances are on different
ports. I want to know if there is a way around the
"openjpa.RemoteCommitProvider" configuration, as you can't specify a
port per IP address here.
Hi Colm,
I found thi
I'm aware of that :-) Obviously the Tomcat instances are on different
ports. I want to know if there is a way around the
"openjpa.RemoteCommitProvider" configuration, as you can't specify a port
per IP address here.
Colm.
On Wed, Jan 6, 2016 at 1:04 PM, Leonardo K. Shikida
wrote:
> I think you
I think you cannot have 2 instances of anything in the same machine sharing
the same port
[]
Leo
On Wed, Jan 6, 2016 at 10:58 AM, Colm O hEigeartaigh
wrote:
> Hi all,
>
> I want to set up a trivial Syncope cluster on my machine (to test a
> CXF-based client using CXF's failover feature). I had
Hi all,
I want to set up a trivial Syncope cluster on my machine (to test a
CXF-based client using CXF's failover feature). I had thought of just
setting up two Tomcat instances on different ports using a shared H2
database file sitting on the hard drive.
Is it still necessary to set a value for
