I have to check what the start script does exactly.
Anyway, the start() method is synchronized in InstanceImpl.
So as it's handled by the same JVM, concurrent access to the
instance.properties should be handled.
It should be better using the start instance from the root instance.
Regards
JB
On 03/07/2012 10:44 AM, Epik, Sergiy wrote:
Hi
We can try to start instance using ssh command admin:start on root karaf. Does
it help to avoid concurrent modification of instance.properties (as a temporary
solution)?
Thank you.
Best regards, Sergiy
-----Original Message-----
From: Jean-Baptiste Onofré [mailto:[email protected]]
Sent: Wednesday, March 07, 2012 11:30 AM
To: [email protected]
Subject: Re: Instances startup
Hi Sergiy,
We should have a lock system for the instances.properties (as the pid is
written in this file).
It sounds like a bug to me. I will raise the Jira and fix that.
Regards
JB
On 03/07/2012 09:47 AM, Epik, Sergiy wrote:
Hi,
we have several instances of karaf (2.2.3) and each instance is started
using scripts $KARAF_HOME/instances/${instance_name}/bin/start.
The problem happens when scripts are started at the same time (by RHEL
cluster, for example).
AdminService modifies instance.properties concurrently and instance,
that started later, overwrites PID of instance that started earlier.
Can anyone suggest the correct way to start instances in this case?
Thank you.
Regards, Sergiy
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
