ArrayIndexOutOfBoundsException is thrown when running memslap against jmemcached

[kobi]

I loaded a jmemcached node:java -Xmx1g -Xms1g -classpath "jmemcached-
core-0.8.jar:jmemcached-cli-0.8-main.jar"
com.thimbleware.jmemcached.Main
and ran a memslap : memslap -s 127.0.0.1:11211 -t 1m


INFO: Listening on 0.0.0.0:11211
May 23, 2010 5:32:19 PM
com.thimbleware.jmemcached.protocol.text.MemcachedResponseEncoder
exceptionCaught
SEVERE: error
java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at
org.jboss.netty.buffer.HeapChannelBuffer.setBytes(HeapChannelBuffer.java:
130)
at
org.jboss.netty.buffer.AbstractChannelBuffer.writeBytes(AbstractChannelBuffer.java:
390)
at
org.jboss.netty.buffer.AbstractChannelBuffer.writeBytes(AbstractChannelBuffer.java:
395)
at
com.thimbleware.jmemcached.protocol.text.MemcachedResponseEncoder.writeString(MemcachedResponseEncoder.java:
141)
at
com.thimbleware.jmemcached.protocol.text.MemcachedResponseEncoder.messageReceived(MemcachedResponseEncoder.java:
61)
at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:
87)
at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:
387)
at
com.thimbleware.jmemcached.protocol.MemcachedCommandHandler.messageReceived(MemcachedCommandHandler.java:
180)
at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:
87)
at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:
387)
at
com.thimbleware.jmemcached.protocol.text.MemcachedCommandDecoder.processLine(MemcachedCommandDecoder.java:
141)
at
com.thimbleware.jmemcached.protocol.text.MemcachedCommandDecoder.messageReceived(MemcachedCommandDecoder.java:
55)
at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:
87)
at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:
387)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.fireMessageReceived(FrameDecoder.java:
284)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:
261)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:
184)
at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:
87)
at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:
344)
at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:
331)
at
org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:303)
at
org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:
255)
at
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:176)
at
org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:
49)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

[Ryan]

Can you try this against the latest release version (0.9) or against
checkout from Mercurial? I suspect this has already been fixed.

R