| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Can't stop ConfigMgr service and always time out in Control |
« View previous topic :: View next topic » |
| Author |
Message
|
| Yanghui |
 Posted: Thu May 09, 2002 6:57 am Post subject: |
 |
|
Disciple
Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland
|
Hi, there,
When setup a local(all-in-one) WMQI environment on NT4 workstation & DB2 for my customer, I got a strange problem that I always get time out error after doing connection in Control Center. It seems the ConfigMgr has no response to this connection request.
The further problem I found is I couldn't bring down the ConfigMgr service no matter from NT services window or by issuing the command "mqsistop ConfigMgr". The only way to stop ConfigMgr is to end the process bigconfigmgr.ex from TaskManager. Then I got a error in the event viewer 2015 which is not a surprise.
There is no error in installation or ConfigMgr creatation. I also have done countless checking regarding to the host name, port number and queue manager name.
It looks like a simple problem but I am really lost especially regarding to why it's impossible to bring down ConfigMgr service. Does anybody have any idea about this? Any comments or suggestion are highly appreciated. Many thanks in advance.
Regards
-Yanghui
|
|
| Back to top |
|
 |
| kirani |
| Posted: Thu May 09, 2002 7:48 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Do you see any errors in the Event viewer? What Service Pack have you installed on Windows NT?
Probably your configuration manager is busy in doing something .. and not able to recover from the error. Do you see any MQSeries FDC files created on your system?
Are you able to stop/start broker service?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Yanghui |
| Posted: Fri May 10, 2002 7:24 am Post subject: |
|
|
Disciple
Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland
|
Hi,
I think I got closer to this problem. I found the following info in the "Problem Determination Guide":
>Resources hang at startup on Windows NT
>Scenario: You try to start the Configuration Manager or a broker on Windows NT,
>but nothing happens in the Event log to show that it has started connecting.
>In rare cases, this problem is indicated by processes having only one thread. >To see if that is the case, check the Task Manager to see if the process >bipconfigmgr.exe or dataflowengine.has started. If they have, check the number >of threads owned by the process. If it has only one, you probably have this rare problem, and should do the following:
My problem is exactly same as what described above. After I followed the instruction, I got the runtime error
Program C:wmqibinbipconfigmgr.exe
R6016
-not enough space for thread data
I checked my environment. There is plenty memory and harddisk. So, what does this runtime error mean? Can I do anything to solve this problem? I have to keep working on this till this problem can be solved
Many Thanks again.
-Yanghui
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
