| Author |
Message
|
| selfown |
 Posted: Tue Dec 13, 2005 1:56 am Post subject: mqsistop problems on Solaris |
 |
|
Apprentice
Joined: 07 Jan 2005
Posts: 39
|
Hi,
I've a broker(V5) installed on Solaris.
In the dev env, whenever I try to stop the broker using mqsistop, in majority of the cases it does not work.
I'm forced to use mqsistop -i command. I'm not sure what ill effects this command has apart from killing of the execution groups manually..
What I want to know is why the broker is unable to respond to the general command.
Thanks |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Tue Dec 13, 2005 2:26 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Are the queue managers and channels up....??
What about the database.
And most important, how long did you wait....it does take a little time 
You should open another connection and check the services that are running for the broker.
What does the user log say ?
Regards. |
|
| Back to top |
|
|
| selfown |
| Posted: Tue Dec 13, 2005 2:36 am Post subject: |
|
|
Apprentice
Joined: 07 Jan 2005
Posts: 39
|
| elvis_gn wrote: |
Are the queue managers and channels up....??
What about the database.
And most important, how long did you wait....it does take a little time
You should open another connection and check the services that are running for the broker.
What does the user log say ?
Regards. |
Elvis,
I have waited for almost 30 minutes in worst cases, but the processes still remain intact.
The QM, Channels and the database are all fine and running.
Even in the user log, I could not find anything related to this..
Right now, as I'm typing, I've run that command from the past 30 minutes (Between I had been to a meeting as well!!) .. Still nothing has happened.
Has this something to do with Remote Debugging. We are using a java program to open a port for us to enable remote debugging.. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Tue Dec 13, 2005 2:54 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi selfown,
I have not worked on Solaris so i'm not very sure about the command, but in AIX we do a ps -ef|grep <Broker Name> to see the services that are running for the Broker.
Sometimes it so happens that some EG is running a message, or has got hung.....In such a scenario the broker would not stop.
If we do a kill -9 <Service Code> of the particular hung service the Broker stops.
I guess if you have the equivalent commands for these you should be able to trace the problem.
Will let u know if i find something.
Regards. |
|
| Back to top |
|
|
| selfown |
| Posted: Tue Dec 13, 2005 2:58 am Post subject: |
|
|
Apprentice
Joined: 07 Jan 2005
Posts: 39
|
| elvis_gn wrote: |
Hi selfown,
I have not worked on Solaris so i'm not very sure about the command, but in AIX we do a ps -ef|grep <Broker Name> to see the services that are running for the Broker.
Sometimes it so happens that some EG is running a message, or has got hung.....In such a scenario the broker would not stop.
If we do a kill -9 <Service Code> of the particular hung service the Broker stops.
I guess if you have the equivalent commands for these you should be able to trace the problem.
Will let u know if i find something.
Regards. |
Hi Elvis,
I do that but I somehow am not happy doing kill -9 as it for the worst case scenario. When I've to do it more often, I feel that something is not working properly.
Is this anything to do with Broker efficiency on Solaris. On AIX, I've not seen this happening very frequently atleast. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Tue Dec 13, 2005 3:11 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
You are right, killing the process is not the way to stop and start stuff....
They are only worst case solutions....try ur user log,tail it and tell us the final few lines....that is the only way we are going to learn something....what about the event log.
Also, u dont need to quote my entire post with your reply
regards. |
|
| Back to top |
|
|
| JT |
| Posted: Tue Dec 13, 2005 8:06 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Since you specifically mentioned that this is occurring in the dev environment, is it possible that someone is using the debugger or has a breakpoint active? |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Fri Dec 16, 2005 9:22 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
I don't know, might be some bad code deploy hung the execution group? Did you recently deployed any thing?
In our Windows environment we killed the dataflowengine many times to stop the broker completely.
As JT said,we found it was a debugger problem(toolkit shutdown in the middle of debugging) and some times the dataflow engine using lought of memory(keep growing) after a bad deploy.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
|
|
