# Java client not connecting after upgrade to 2.0 due to license issue?

**URL:** <https://discuss.elastic.co/t/java-client-not-connecting-after-upgrade-to-2-0-due-to-license-issue/34406>\
**Category:** Elasticsearch\
**Created:** [November 12, 2015, 11:28am UTC](https://discuss.elastic.co/t/java-client-not-connecting-after-upgrade-to-2-0-due-to-license-issue/34406 "2015-11-12T11:28:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmlucjav](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jmlucjav/32/5870_2.png) [@jmlucjav](https://discuss.elastic.co/u/jmlucjav)\
**Post date:** [November 12, 2015, 11:28am UTC](https://discuss.elastic.co/t/java-client-not-connecting-after-upgrade-to-2-0-due-to-license-issue/34406/1 "2015-11-12T11:28:09Z")

</div>

Hi,

I had a ESbeta1 java client connecting fine to ES. I upgraded both server and client to 2.0, and installed marvel too to check it out.

Suddenly the java client could not connect any longer. I tried to tweak discovery (unicast, multicast etc) to no avail. I enabled trace logs and saw some errors like this (sorry I deleted old log files so I dont have the whole stack trace):

```
No custom metadata prototype registered for type [licenses]

```

Eventually removed both plugins I had (marvel-agent and licenses), and this fixed the issue. I searched but found nothing similar reported. Did anyone see something like this? Note that I was still in the month of evaluation of marvel.

thanks  
xavi

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:38pm UTC](https://discuss.elastic.co/t/java-client-not-connecting-after-upgrade-to-2-0-due-to-license-issue/34406/2 "2017-07-05T23:38:59Z")

</div>

Closed on July 5, 2017, 11:38pm UTC