Sure Rob. Today we have started qpid broker and my app in background. Tomorrow morning I will come to know if it's still up and if the solution worked. I will update you immediately.
Also I will Google the command and understand it before using it. Thanks Bhargav On 31-Aug-2016 5:58 PM, "Rob Godfrey" <[email protected]> wrote: > Hi Bhargav, > > so given what you want to do, you'll be wanting to use nohup... but it's > probably worth you Googling a little so you understand exactly what nohup > is doing / how UNIX commands interact with shell sessions (this is not in > any way a Qpid specific thing). For instance this page ( > http://linux.101hacks.com/unix/nohup-command/ - first result when I > Googled) gives a very brief introduction to what nohup does. > > hope this helps, > Rob > > On 31 August 2016 at 12:11, Bhargav Bhalerao <[email protected]> > wrote: > > > Hi Rob > > > > I open unix console, traverse to qpid bin directory and run command > > sh qpid-server.sh > > > > oh...so is it like when console session ends, the server will go down? > > > > You have mentioned 2 options > > > > qpid-server.sh & > > nohup qpid-server.sh & > > > > Which one is the best? Which one should I use? > > > > Thank you very much for this eye opener. > > > > Thanks > > Bhargav > > > > > > > > > > On Wed, Aug 31, 2016 at 4:30 PM, Rob Godfrey <[email protected]> > > wrote: > > > > > How are you running the qpid-server.sh script? In the foreground (e.g. > > > "bin/qpid-server.sh"), the background (e.g. "bin/qpid-server.sh &") or > > > using nohup (e.g. "nohup bin/qpid-server.sh &")? > > > > > > Unless it is the latter then obviously the script (and the broker)will > be > > > terminated whenever your console session that started the server is > > closed. > > > > > > -- Rob > > > > > > On 31 August 2016 at 11:21, Bhargav Bhalerao < > [email protected] > > > > > > wrote: > > > > > > > Hi Rob > > > > > > > > Thanks for your inputs. > > > > I am running qpid broker and my application on red hat linux system > by > > > > running qpid-server.sh script. > > > > I have deleted JMX and RMI ports. I have kept only AMQP and HTTP > ports > > > > active. > > > > > > > > Your guess that some external factor is killing the process is valid > > > since > > > > I have not observed this behaviour when I run qpid and my application > > on > > > > windows. It runs for days without any issue. > > > > > > > > Do you have any clue how can I findout who could be killing qpid > > broker?? > > > > > > > > Thanks > > > > Bhargav > > > > > > > > > > > > > > > > > > > > On Wed, Aug 31, 2016 at 2:14 PM, Rob Godfrey < > [email protected]> > > > > wrote: > > > > > > > > > From looking at your last log file we see the line > > > > > > > > > > 2016-08-25 22:46:25,819 DEBUG [QpidBrokerShutdownHook] > > (server.Broker) > > > - > > > > > Shutdown hook running > > > > > > > > > > The shutdown hook is run when the kill signal is received by the > > > broker. > > > > > This would imply that the broker is being killed by an external > actor > > > > (e.g. > > > > > an explicit kill command against the java process, or a CTRL-C if > the > > > > > process is running interactively). As such I don't think this is > > > really > > > > a > > > > > Qpid issue - it is something happening in your environment. > > > > > > > > > > How are you running the broker? > > > > > > > > > > Cheers, > > > > > Rob > > > > > > > > > > > > > > > On 31 August 2016 at 09:08, Bhargav Bhalerao < > > > [email protected] > > > > > > > > > > wrote: > > > > > > > > > > > Hi All > > > > > > > > > > > > > > > > > > > > > > > > I have 5 amqp queues in created in java qpid broker 0.32. I have > > > > enabled > > > > > > all amqp versions on these queues. > > > > > > > > > > > > My spring java application listens to these 5 queues continuously > > > using > > > > > > spring framework jms listeners using qpid v0.32 jms client. > > > > > > > > > > > > I have set heartbeat=5 in client url. > > > > > > > > > > > > SSL is enabled. > > > > > > > > > > > > > > > > > > When qpid and application is idle overnight, it is observed that > > qpid > > > > > > broker automatically shuts down. > > > > > > > > > > > > > > > > > > We have to restart it everyday morning. > > > > > > > > > > > > > > > > > > Please suggest a solution. > > > > > > > > > > > > > > > > > > exhaustive debug logs attached for the time just before qpid goes > > > down. > > > > > > > > > > > > > > > > > > I am new to qpid broker and did not understand much in logs. > > > > > > > > > > > > > > > > > > Request your kind help. > > > > > > > > > > > > -- > > > > > > Regards, > > > > > > > > > > > > Bhargav Bhalerao > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------ > > > --------- > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Regards, > > > > > > > > Bhargav Bhalerao > > > > > > > > > > > > > > > -- > > Regards, > > > > Bhargav Bhalerao > > >
