Exception in thread "Thread-332" java.lang.NullPointerException
        at
org.apache.hadoop.chukwa.datacollection.writer.SocketTeeWriter$Tee.setup(SocketTeeWriter.java:178)
        at
org.apache.hadoop.chukwa.datacollection.writer.SocketTeeWriter$Tee.run(SocketTeeWriter.java:136)
        at java.lang.Thread.run(Thread.java:662)
2011-11-16 02:44:07,147 INFO Thread-6 SocketTeeWriter - got connection from
/10.32.149.15

And the 10.32.149.15 is our hadoop cluster.

This exception arises very frequently , every 5 mins.

But the collector seemed doesn't been influenced .

Why this exception arises? Is there something wrong with the hadoop?

--
Best regards,

Ivy Tang

Hrm.

Is there some process that's connecting to the SocketTeeWriter port
[9094 by default] and then not sending a command? I think you'll get
that NPE if you open the connection and then close it without sending
anything.

As you suspect, it should be benign, since all that's being killed
there is the per-connection handler thread.

--Ari

On Wed, Nov 16, 2011 at 12:49 AM, IvyTang <[EMAIL PROTECTED]> wrote:
> Exception in thread "Thread-332" java.lang.NullPointerException
>         at
> org.apache.hadoop.chukwa.datacollection.writer.SocketTeeWriter$Tee.setup(SocketTeeWriter.java:178)
>         at
> org.apache.hadoop.chukwa.datacollection.writer.SocketTeeWriter$Tee.run(SocketTeeWriter.java:136)
>         at java.lang.Thread.run(Thread.java:662)
> 2011-11-16 02:44:07,147 INFO Thread-6 SocketTeeWriter - got connection from
> /10.32.149.15
> And the 10.32.149.15 is our hadoop cluster.
> This exception arises very frequently , every 5 mins.
> But the collector seemed doesn't been influenced .
> Why this exception arises? Is there something wrong with the hadoop?
> --
> Best regards,
> Ivy Tang
>
>
>

--
Ari Rabkin [EMAIL PROTECTED]
UC Berkeley Computer Science Department