We can use some hacks (which do not seem to be a good solutions to me):
1. throw exception from startStopwatch() if start time has already been
inited. Ugly since currently this method does not throw any error.
2. check if resources have already been injected to SPI before doing new
injection. Not always working since SPI may not use injected resources.
I think that each SPI should check for repeating start attempts itself.
How about implementing spiStart() in SPI adapter and set some flag there or
throw exception if it has already been set. All internal implementation
will be changed to call super.spiStart() as first statement.
Val, if you agree please file a newbie ticket.
--Yakov
2016-02-20 1:55 GMT+03:00 Valentin Kulichenko <
[hidden email]
>:
> Crossposting to dev@.
>
> Folks,
>
> This is not the first time I see this issue. Is there a way to detect it
> and throw an exception?
>
> -Val
>
> On Fri, Feb 19, 2016 at 2:42 PM, vkulichenko <
>
[hidden email]> wrote:
>
>> Hi Vinay,
>>
>> Yes, you should always create the configuration object from scratch when
>> starting a node. Mainly it's because it contains SPIs (e.g.,
>> TcpDiscoverySpi) which have lifecycle and can't be reused.
>>
>> Makes sense?
>>
>> -Val
>>
>>
>>
>> --
>> View this message in context:
>>
http://apache-ignite-users.70518.x6.nabble.com/Ignite-instance-hangs-during-restart-in-client-mode-tp3101p3106.html>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
Locked
