Manish, It'll be hard to say what's causing this. First of all... are you sure Sqoop 2 server dies? A pretty good way to see if it is still running at all is to follow the guide here: http://sqoop.apache.org/docs/1.99.2/Sqoop5MinutesDemo.html. Or, you can simply run a "netstat -tlnp" on your machine to see if there is still a server running on port 12000.
There are plenty of logs Sqoop 2 server generates. Sometimes, the real error is unfortunately hidden in one of the lesser known logs. The sqoop.log file is located in @LOGDIR@ and the rest should be in server/logs/*. Look for catalina.out, catalina.log, localhost-*.log, etc. There may be an exception in any of these files that lead you in a good direction. -Abe On Tue, Sep 24, 2013 at 9:24 PM, Manish Meshram <[email protected]>wrote: > Hi Abraham, > > I want to ask you about one more problem I told you.My sqoop server > stops automatically when my Client program runs. > There is no particular point at which server stops, I tried > debugging, it stops at any point of time during the execution of program > and then I get the exception: > > com.sun.jersey.api.client.ClientHandlerException: > java.net.ConnectException: Connection refused: connect > > After that I have to start the server again and then execute the > program.But still the server does not stays for a little more time. > Also it is not generating any logs for shutdown. > Do you think there is any chance of low memory? > Need your opinion. > > > Thanks, > Manish >
