ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergi Vladykin <sergi.vlady...@gmail.com>
Subject Re: OverlappingFileLockException in nodes startup same time in Linux
Date Wed, 16 Sep 2015 23:39:46 GMT
Another option is to put Ignite in some common module for all the
applications that require Ignite. This way Ignite
classes must be loaded only once.
See https://docs.jboss.org/author/display/WFLY9/Class+Loading+in+WildFly

Sergi

2015-09-17 2:27 GMT+03:00 vkulichenko <valentin.kulichenko@gmail.com>:

> roar109 wrote
> > If I understand your suggestion correctly is to make single Ignite
> > instance per jboss in this case to avoid this sync mechanism?
>
> This should help too. But it sounds like that in your case you can simply
> disable shared memory communication. To do this add the following in your
> configuration file:
>
> <property name="communicationSpi">
>     <bean
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>         <property name="sharedMemoryPort" value="-1"/>
>     </bean>
> </property>
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/OverlappingFileLockException-in-nodes-startup-same-time-in-Linux-tp1415p1428.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Mime
View raw message