Mesh Errors?

[Albert Law]

Hi All,

Any idea what the following mesh.log error is trying to say? I'm
seeing this all over the place. :(

ERROR [New I/O worker #2] 2014-11-15 13:03:10,506 ChannelState.java
(line 313) messageReceived error
java.lang.NullPointerException
at com.addthis.meshy.service.file.FileTarget$ForwardingFileSource.receiveComplete(FileTarget.java:512)
at com.addthis.meshy.ChannelState.messageReceived(ChannelState.java:302)
at com.addthis.meshy.Meshy$MeshyChannelHandler.messageReceived(Meshy.java:372)
at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)



--
Albert Law
Lead Engineer - Data Acquisition
NewBrand
http://www.newbrandanalytics.com/

[Albert Law]

Hi All,

Given that there were Meshy issues, I changed Hydra v4.2.11 to use
Meshy v2.1.8 instead of Meshy v2.1.5. It looks like all the
NullPointerExceptions are now IOExceptions.

INFO [MeshyStats] 2014-11-16 00:34:45,148 MeshyServerGroup.java (line
209) seqReads=13 totalReads=18 bytesRead=148494 sN=5 sC=5 sO=0 sQ=0
sR=3 sW=0 sZ=0 fCH=0 fCE=434 fQ=0 fR=1 fF=36 fO=6459 fT=962 fTL=948
iSR=5 gcR=1 gcT=33 mD=0 mF=0 bMC=1,826,496 bML=1,425,408 bLO=0 bI=6518
bO=6518 bZ=0 mC=7 mS=7 mBI=29073 mBO=919324
java.io.IOException: Stream Closed
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:272)
at com.addthis.meshy.InputStreamWrapper.readBytes(InputStreamWrapper.java:62)
at com.addthis.meshy.InputStreamWrapper.nextBytes(InputStreamWrapper.java:85)
at com.addthis.meshy.service.stream.StreamTarget.doSendMore(StreamTarget.java:370)
at com.addthis.meshy.service.stream.StreamTarget.run(StreamTarget.java:322)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)

INFO [MeshyStats] 2014-11-16 00:34:46,148 MeshyServerGroup.java (line
209) seqReads=152 totalReads=185 bytesRead=2124363 sN=33 sC=33 sO=0
sQ=0 sR=46 sW=0 sZ=0 fCH=0 fCE=160 fQ=0 fR=0 fF=14 fO=2321 fT=806
fTL=797 iSR=32 gcR=0 gcT=0 mD=0 mF=0 bMC=1,826,496 bML=1,425,408 bLO=0
bI=2553 bO=2553 bZ=0 mC=7 mS=7 mBI=14922 mBO=2403281

Um, progress?

[Ian Barfield]

Try using meshy v2.1.6. That has the fix for the NPE from the first e-mail but does not look likely to have had any changes that might have required corresponding changes in hydra code. The version numbering could probably be a little more helpful in this regard, sorry.

--
You received this message because you are subscribed to the Google Groups "hydra-oss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hydra-oss+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Albert Law]

Hi Ian,

Oh, is Meshy v2.1.8 bad for some reason? I did have to make one minor
Hydra code change for v2.1.8 (something wasn't thrown anymore and is
now caught by Throwable).

[Ian Barfield]

Meshy v2.1.8 is fine, but the changes required for v2.1.7 might be more involved than expected.

https://github.com/addthis/hydra/commit/c964c5242442d1781cb2ae77a748f0d2820cb5c0

that is the commit to hydra that upgrades the meshy version to v2.1.7 (snapshot). A lot of that is just formatting, but there is some logic related to streams being closed that might be required for higher meshy versions. It is also apparently fixing a bug, and maybe that is simply the bug you are seeing now. Using the lower version seems like a good place to start though.

[Albert Law]

Ah, Meshy v2.1.7 it is!

[Ian Barfield]

I am saying v2.1.7 has additional changes required for it, and that you should try using v2.1.6.