Hi Nikolai.
I discovered the reason the two applications weren't seeing each other was
resolved by adding an explicit port number (Arrays.asList("127.0.0.1:47500")).
However, the two still deadlock when running concurrently.
The latest test shows one application blocked in getOrCreateCache, the
other blocked in Ignition.start. As soon as I kill the process stuck in
Iginition.start the other process continues successfully. I've attached the
latest test code.
Any ideas?
Matt
On Wed, Feb 22, 2017 at 10:30 AM, Matt Warner [via Apache Ignite Users] <
ml-node+s70518n10811...@n6.nabble.com> wrote:
> One other observation: with the third application acting as just the
> server, and just one of the clients running, there is no issue. Only when
> there are multiple clients do I get the deadlock on getOrCreateCache.
>
> Matt
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/getOrCreateCache-hang-
> tp10737p10811.html
> To unsubscribe from getOrCreateCache hang, click here
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=10737&code=bWF0dEB3YXJuZXJ0ZWNobm9sb2d5LmNvbXwxMDczN3wxNDczMjA0NTQy>
> .
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
testIgnite.tar.gz (14K)
<http://apache-ignite-users.70518.x6.nabble.com/attachment/10866/0/testIgnite.tar.gz>
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/getOrCreateCache-hang-tp10737p10866.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
