Ok. I'll do that. Thanks. But still, where are the exceptions logged to? Is it to the worker log? Because there is nothing there and the topology is not consuming from the queue... It just fails some tupples and then stops processing the queue...
Here is the screenshot of the storm ui: https://www.dropbox .com/s/gfeeajw3zvdr9vc/Captura%20de%20tela%202013-11-08%2020.06.51.png Thanks. Ricardo Teixeira http://www.rteixeira.eu tel: +351 938655255 skype: rjsteixeira On Fri, Nov 8, 2013 at 1:30 PM, James Xu <[email protected]> wrote: > use slf4j API to do the logging. > > On 2013年11月8日, at 下午6:55, Ricardo Teixeira <[email protected]> wrote: > > > Hi. > > > > I have a topology that, after some time , is failing to consume a > > rabbit mq without writing anything to the worker-log. > > > > The topology is using a rabbitmq spout (storm-amqp-spout) and I think > > is that it is that spout that is failing to get the messages. I left > > it running during the night and in the morning the queue was full, the > > Storm UI said that the spout had some failed tuples but there is no > > error message: not on storm ui and not on the worker-log. > > > > When I run the topology in local mode, I can see, the > > System.out.println() I've put in there showing up in the console. > > Where is the console output going when I run the topology in the > > cluster? > > > > Thanks. > > > > Ricardo Teixeira > >
