Hi Aride,

I don’t get any errors, but I see this in the log file

2015-07-16T11:24:59.376+0530 b.s.m.n.Client [INFO] Reconnect started for 
Netty-Client-/192.168.1.117:6700... [1]
838 2015-07-16T11:25:09.532+0530 b.s.m.n.Client [INFO] Reconnect started for 
Netty-Client-/192.168.1.117:6700... [2]
839 2015-07-16T11:25:19.702+0530 b.s.m.n.Client [INFO] Reconnect started for 
Netty-Client-/192.168.1.117:6700... [3]
840 2015-07-16T11:25:29.837+0530 b.s.m.n.Client [INFO] Reconnect started for 
Netty-Client-/192.168.1.117:6700... [4]
841 2015-07-16T11:25:40.010+0530 b.s.m.n.Client [INFO] Reconnect started for 
Netty-Client-/192.168.1.117:6700... [5]
842 2015-07-16T11:25:50.187+0530 b.s.m.n.Client [INFO] Reconnect started for 
Netty-Client-/192.168.1.117:6700... [6]
843 2015-07-16T11:26:00.442+0530 b.s.m.n.Client [INFO] Reconnect started for 
Netty-Client-/192.168.1.117:6700... [7]
844 2015-07-16T11:26:10.760+0530 b.s.m.n.Client [INFO] Reconnect started for 
Netty-Client-/192.168.1.117:6700... [8]
845 2015-07-16T11:26:21.174+0530 b.s.m.n.Client [INFO] Reconnect started for 
Netty-Client-/192.168.1.117:6700... [9]

Even when I check Storm UI, the topology is successfully running, but none of 
the local logs are printed. None of the DB operations are executed. But 
everything are executed as expected with LocalCluster. 

-- 
Rahul J


On July 20, 2015 at 2:17:37 PM, Aride Chettali ([email protected]) wrote:

What error message are you getting ?


​​ Regards,
Aride Chettali 



On Mon, Jul 20, 2015 at 12:52 PM, Rahul <[email protected]> wrote:
I have two topology. One of which is very simple, Spout generates a random 
number and the Bolt saves the same in the database. This topology works fine 
both as a local cluster and when submitted to Storm using StormSubmitter.

The next one, though is little complicated, follows the same code pattern as 
the previous topology. This topology, works perfectly when implemented as 
LocalCluster but doesn't work when I use StormSubmitter. What could be the 
reason this fails?


-- 
Rahul J


Reply via email to