Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326228

Summary:

[Discovery][JmDNS] Upgrade to JmDNS 3.x

Product:

[RT] ECF

Reporter:

Markus Kuppe <bugs.eclipse.org>

Component:

ecf.providers

Assignee:

Markus Kuppe <bugs.eclipse.org>

Status:

REOPENED ---

QA Contact:

Severity:

enhancement

Priority:

CC:

luigi.sgro, olabrosse

Version:

3.3.0

Target Milestone:

---

Hardware:

All

OS:

All

Whiteboard:

Bug Depends on:

Bug Blocks:

202774, 348487, 392655

Attachments:

Description	Flags
changes necessary in the provider	none
mylyn/context/zip	none
mylyn/context/zip	none

Description Markus Kuppe

2010-09-25 07:48:40 EDT

JmDNS has received a bunch of enhancements since 2.x. Thus we should upgrade to the 3.x code base.

Comment 1 Markus Kuppe

2010-09-25 07:59:40 EDT

CQ https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4472 has been filed

Comment 2 Markus Kuppe

2010-09-25 08:05:39 EDT

Created attachment 179568 [details]
changes necessary in the provider

Comment 3 Markus Kuppe

2010-09-25 08:05:43 EDT

Created attachment 179569 [details]
mylyn/context/zip

Comment 4 Markus Kuppe

2010-10-01 08:30:26 EDT

Reverted to 2.x code base. 3.x code base is showing a couple of problems which have to be sorted out first.

Comment 5 Markus Kuppe

2010-10-01 08:32:08 EDT

REOPENED due to previous comment

Comment 6 Markus Kuppe

2010-10-24 09:01:32 EDT

A new branch 326228 [0] has been pushed to git.eclipse.org that will serve as an integration branch with JmDNS upstream for now.

[0] http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/log/?h=326228

Comment 7 Markus Kuppe

2010-10-24 09:01:34 EDT

Created attachment 181593 [details]
mylyn/context/zip

Comment 8 Olivier Labrosse

2012-11-29 14:30:20 EST

Relating my experience with ECF's JmDNS provider...

I was getting "buffer full" exceptions thrown at line 144 of DNSOutgoing.java.  It looked alot like a multi-threading issue where the array and offset would change to values that caused the guard to test true.  In any case, this exception would cause our remote services to fail registration and would ultimately leave the JmDSNImpl instance in some corrupt state that caused a deadlock to occur at line 542 of said class (unregisterService() method) when the application closed.

Because we're developing an Eclipse application already with a 1.7 compliance level, it was relatively easy to get around the new JmDNS requirements.  I created a replacement plugin from the ECF master branch and JmDNS's HEAD, changed the manifest and classpath, and all is working now.  No more exceptions.

If you haven't updated JmDNS due to the 1.6 compliance issues, I must say I understand the stalemate situation this issue appears to be in.

Comment 9 Scott Lewis

2014-02-14 15:21:27 EST

*** Bug 392655 has been marked as a duplicate of this bug. ***