Flavio Junqueira created BOOKKEEPER-437:
-------------------------------------------
Summary: org.apache.hedwig.client.TestPubSubClient not executing
Key: BOOKKEEPER-437
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-437
Project: Bookkeeper
Issue Type: Bug
Reporter: Flavio Junqueira
The test gets stuck because of the following exception:
{noformat}
2012-10-16 23:50:48,540 - WARN - [New I/O client worker #4-1:Log4JLogger@83] -
An exception was thrown by ChannelFutureListener.
java.lang.NoSuchMethodError:
org.apache.hedwig.protocol.PubSubProtocol$SubscriptionOptions.getDeliveryThrottleValue()I
at
org.apache.hedwig.client.netty.NetUtils.options2Preferences(NetUtils.java:196)
at
org.apache.hedwig.client.netty.NetUtils.buildSubscribeRequest(NetUtils.java:118)
at
org.apache.hedwig.client.netty.NetUtils.buildPubSubRequest(NetUtils.java:87)
at
org.apache.hedwig.client.netty.impl.HChannelImpl.executeOpAfterConnected(HChannelImpl.java:143)
at
org.apache.hedwig.client.netty.impl.HChannelImpl.submitOp(HChannelImpl.java:132)
at
org.apache.hedwig.client.netty.impl.AbstractHChannelManager.submitOpThruChannel(AbstractHChannelManager.java:266)
at
org.apache.hedwig.client.netty.impl.DefaultServerChannel$1.operationComplete(DefaultServerChannel.java:87)
at
org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:381)
at
org.jboss.netty.channel.DefaultChannelFuture.notifyListeners(DefaultChannelFuture.java:372)
at
org.jboss.netty.channel.DefaultChannelFuture.setSuccess(DefaultChannelFuture.java:316)
at
org.jboss.netty.channel.socket.nio.NioWorker$RegisterTask.run(NioWorker.java:767)
at
org.jboss.netty.channel.socket.nio.NioWorker.processRegisterTaskQueue(NioWorker.java:256)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:198)
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:680)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
