| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| revisiting bip1510e, deploy didn't come back. |
« View previous topic :: View next topic » |
| Author |
Message
|
| waugh |
 Posted: Wed Aug 18, 2004 2:14 pm Post subject: revisiting bip1510e, deploy didn't come back. |
 |
|
Master
Joined: 19 Feb 2004
Posts: 225
|
Windows XP, WBIMB 5 CSD03, DB2 8.1 FP6, MQ CSD 07
i tried all the solutions i can think of and are available in the forum.
I had same issue back in february. I was able to fix it with deleting 'DPLING' records and redeploy.
Solutions i tried so far:
1) I tried deleting and recreating the broker.
2) I changed timeout to 1000 second from 360 seconds. still not getting response back from broker.
3) deleted messages in broker queues and restarted the broker.
4) restarted the configuration manager.
5) deleting DPLING
another thing i noticed broker taking forever on mqsistop. even though there's only one execution group running(default) and no flows deployed.
broker and configmgr are using same queue manager and its on a development box and its fresh install, i was able to create components without an error. is this kind of permissions issue on any queue, channel?
the service user id i am using have full permissions on all.
Help is appreciated. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Aug 18, 2004 3:26 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I would open a PMR with IBM.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| waugh |
| Posted: Wed Aug 18, 2004 6:00 pm Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
|
| Back to top |
|
|
| TDS_tds_tds |
| Posted: Thu Aug 19, 2004 6:04 am Post subject: |
|
|
Novice
Joined: 31 Jul 2003
Posts: 16
|
Post your error messages from Event Viewer on your machine.
I had this problem once, it was related to DB2 access. |
|
| Back to top |
|
|
| waugh |
| Posted: Tue Aug 24, 2004 11:40 am Post subject: SOLVED |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
I donno how this happened, or what application changed it...
but i had to stop tracing on ODBC connections. Execution Groups were timing out on database transactions.
Here is what you gotto do...
start>settings>control panel>administrativ tools>Data Sources(ODBC)>Tracing TAB>Click on stop tracing button.
IBM pointed this out.
Courtesy: vivek |
|
| 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
|
|
|
|
