You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "P. Taylor Goetz (JIRA)" <ji...@apache.org> on 2014/03/05 20:34:49 UTC
[jira] [Resolved] (STORM-187) From ZMQ to Netty
"java.lang.IllegalArgumentException: timeout value is negative"
[ https://issues.apache.org/jira/browse/STORM-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
P. Taylor Goetz resolved STORM-187.
-----------------------------------
Resolution: Fixed
> From ZMQ to Netty "java.lang.IllegalArgumentException: timeout value is negative"
> ---------------------------------------------------------------------------------
>
> Key: STORM-187
> URL: https://issues.apache.org/jira/browse/STORM-187
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Reporter: Jose Ignacio Honrado
> Priority: Blocker
> Labels: netty, storm, zeromq
> Attachments: STORM-187.patch
>
>
> Hi,
> I am trying to use Netty as the transport layer in storm 0.9.0.1 but I am getting the following error trace:
> {code}
> java.lang.IllegalArgumentException: timeout value is negative
> at java.lang.Thread.sleep(Native Method)
> at backtype.storm.messaging.netty.Client.reconnect(Client.java:78)
> at backtype.storm.messaging.netty.StormClientHandler.exceptionCaught(StormClientHandler.java:108)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.exceptionCaught(FrameDecoder.java:377)
> at org.jboss.netty.channel.Channels.fireExceptionCaught(Channels.java:525)
> at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:109)
> at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:78)
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
> at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:41)
> 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:744)
> {code}
> I am using the following supervisor config:
> {code}
> storm.zookeeper.servers:
> - "son-rtl-dev-zook1"
> storm.zookeeper.port: 9000
> storm.local.dir: "/mnt/storm"
> storm.local.hostname: "son-rtl-dev-superv1"
> java.library.path: "/usr/local/lib"
> nimbus.host: "son-rtl-dev-nimbus"
> nimbus.task.launch.secs: 240
> supervisor.worker.start.timeout.secs: 240
> supervisor.worker.timeout.secs: 240
> supervisor.childopts: "-Xmx512m -Djava.net.preferIPv4Stack=true"
> supervisor.slots.ports:
> - 6700
> - 6701
> - 6702
> - 6703
> - 6704
> - 6705
> - 6706
> - 6707
> worker.childopts: "-Xmx512m -Djava.net.preferIPv4Stack=true"
> nimbus.childopts: "-Xmx512m -Djava.net.preferIPv4Stack=true"
> topology.message.timeout.secs: 1
> storm.messaging.transport: "backtype.storm.messaging.netty.Context"
> storm.messaging.netty.server_worker_threads: 1
> storm.messaging.netty.client_worker_threads: 1
> storm.messaging.netty.buffer_size: 5242880
> storm.messaging.netty.max_retries: 30
> storm.messaging.netty.max_wait_ms: 1000
> storm.messaging.netty.min_wait_ms: 100
> {code}
> Without these last config lines, topologies are working fine using ZMQ.
> Any idea?
> Thanks
--
This message was sent by Atlassian JIRA
(v6.2#6252)