Jersey 1.9 bug

[Jim Klucar <kl...@gmail.com>]

Paul pointed out an error message in the Resource Manager logs that pops up
with the new Dashboard. Without going into too much detail, its not an
issue, It comes from a bug in Jersey 1.9. Hadoop has found this same
problem and documented it here:

https://issues.apache.org/jira/browse/HADOOP-11461

So it looks like we should upgrade to Jersey 1.10 at some point.

Re: Jersey 1.9 bug

[Paul Read <pd...@gmail.com>]

Back in April I had completed issue #10 which is the mapping btw the NodeId
and TaskId which requires a rest call to the NM after its launched. To make
the rest call I used Jersey 1.9. I'm getting ready to make that PR. Since
the code is in the Executor and the classpath includes the hadoop jars
which include the jersey 1.9 its not like we have much choice until hadoop
upgrades or a fancy class loader is created that will find the newest
version of any jar.

On Wed, Jun 10, 2015 at 10:24 AM, Jim Klucar <kl...@gmail.com> wrote:

> Our gradle doesn't declare it directly, but its getting sucked into the
> classpath somewhere. If you look at that Hadoop JIRA, I'm seeing the same
> exact error in our logs. The Myriad REST api documents itself via the wadl
> generator which is where the error is coming from. We should probably
> depend on it directly if we use it.
>
> On Wed, Jun 10, 2015 at 10:15 AM, Ken Sipe <ke...@mesosphere.io> wrote:
>
> > jim,
> >
> > I don’t see that we have a dependency on jersey.   am I missing
> something?
> >
> > ken
> > > On Jun 8, 2015, at 8:03 AM, Jim Klucar <kl...@gmail.com> wrote:
> > >
> > > Paul pointed out an error message in the Resource Manager logs that
> pops
> > up
> > > with the new Dashboard. Without going into too much detail, its not an
> > > issue, It comes from a bug in Jersey 1.9. Hadoop has found this same
> > > problem and documented it here:
> > >
> > > https://issues.apache.org/jira/browse/HADOOP-11461
> > >
> > > So it looks like we should upgrade to Jersey 1.10 at some point.
> >
> >
>

Re: Jersey 1.9 bug

[Jim Klucar <kl...@gmail.com>]

Our gradle doesn't declare it directly, but its getting sucked into the
classpath somewhere. If you look at that Hadoop JIRA, I'm seeing the same
exact error in our logs. The Myriad REST api documents itself via the wadl
generator which is where the error is coming from. We should probably
depend on it directly if we use it.

On Wed, Jun 10, 2015 at 10:15 AM, Ken Sipe <ke...@mesosphere.io> wrote:

> jim,
>
> I don’t see that we have a dependency on jersey.   am I missing something?
>
> ken
> > On Jun 8, 2015, at 8:03 AM, Jim Klucar <kl...@gmail.com> wrote:
> >
> > Paul pointed out an error message in the Resource Manager logs that pops
> up
> > with the new Dashboard. Without going into too much detail, its not an
> > issue, It comes from a bug in Jersey 1.9. Hadoop has found this same
> > problem and documented it here:
> >
> > https://issues.apache.org/jira/browse/HADOOP-11461
> >
> > So it looks like we should upgrade to Jersey 1.10 at some point.
>
>

Re: Jersey 1.9 bug

[Ken Sipe <ke...@mesosphere.io>]

jim,

I don’t see that we have a dependency on jersey.   am I missing something?

ken
> On Jun 8, 2015, at 8:03 AM, Jim Klucar <kl...@gmail.com> wrote:
> 
> Paul pointed out an error message in the Resource Manager logs that pops up
> with the new Dashboard. Without going into too much detail, its not an
> issue, It comes from a bug in Jersey 1.9. Hadoop has found this same
> problem and documented it here:
> 
> https://issues.apache.org/jira/browse/HADOOP-11461
> 
> So it looks like we should upgrade to Jersey 1.10 at some point.