| Author |
Message
|
| abhishekpreddy |
 Posted: Tue Apr 01, 2008 2:39 am Post subject: |
 |
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
HI ,
wats the fix pack level for your MB
Pack 6.0.2.0
does this happens to all of your message flow or only to one msg flow
Only a few flows not all.
any error logged in MQ Side
No errors on the MQ side as well. |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Apr 01, 2008 2:57 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| abhishekpreddy wrote: |
The Redeploy as well does not work , i was wondering if there is any setting in the configuration manager repository because of which the Flow engine is down , but i am not sure how to access the repository , can any one tell me how we can access the tables of the Config manager repository |
This is the one place, as you said, you are not able to deploy the bar files at all.
What the Event log says. hope the channels are up and running.
are there any abend files on broker side
if So Raise a PMR 
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| abhishekpreddy |
| Posted: Tue Apr 01, 2008 3:10 am Post subject: |
|
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
Yaa ,
The problem is that the Broker gets timed out when i try to undeploy the previously running bar file and try to redeploy it again on the same execution group |
|
| Back to top |
|
|
| fschofer |
| Posted: Tue Apr 01, 2008 3:46 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
may it be that the flows are running in a endless loop or wait for something like a http response.
Try to get disable the input queues, restart des broker or EG and try then to stop/start or deploy the flows.
Greetings
Frank |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Apr 01, 2008 3:50 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| fschofer wrote: |
Hi,
may it be that the flows are running in a endless loop or wait for something like a http response.
Try to get disable the input queues, restart des broker or EG and try then to stop/start or deploy the flows.
Greetings
Frank |
I had a mistake that put the flow in an endless loop. Had to kill the pid of the execution group.
  
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 01, 2008 4:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Also, to be very clear.
The "executiongroup" IS the "DataFlowEngine". The "application that listens behind the MQInput node" IS the "DataFlowEngine" which IS the ExecutionGroup.
GET Disable the input queue, and THEN kill the DataFlowEngine process.
And then examine the message on the queue to see why it's causing your flow to loop.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Apr 01, 2008 4:13 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| abhishekpreddy wrote: |
wats the fix pack level for your MB
Pack 6.0.2.0
|
This is the level of your Toolkit. At the WMB command prompt run 'mqsiservice -v'.
You should get:
BIPv600 en US
ucnv Console CCSID 437 dft ucnv CCSID 5348
ICUW ibm-5348_P100-1997 ICUA ibm-5348_P100-1997
BIP8996I: Version: 6007
BIP8997I: Product: WebSphere Message Brokers
BIP8998I: CMVC Level: S600-CSD07 DH600-CSD07
BIP8999I: Build Type: Production
BIP8071I: Successful command completion. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 01, 2008 4:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| JosephGramig wrote: |
| This is the level of your Toolkit. At the WMB command prompt run 'mqsiservice -v'. |
Or just read the text that comes up when you start the WMB command prompt...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| abhishekpreddy |
| Posted: Tue Apr 01, 2008 4:25 am Post subject: |
|
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
Sorry my mistake , the version of the Broker runtime is 6.0.0.2
bash-3.00$ mqsiservice -v
BIPv600 en US
ucnv Console CCSID 1208 dft ucnv CCSID 1208
ICUW ISO-8859-1 ICUA ISO-8859-1
BIP8996I: Version: 6002
BIP8997I: Product: WebSphere Message Brokers
BIP8998I: CMVC Level: S600-CSD02 DH600-CSD02
BIP8999I: Build Type: Production
BIP8071I: Successful command completion. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Apr 01, 2008 5:16 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
If you cannot delete the flow or redeploy it, then deleting the broker will be a waste of time. As soon as you deploy the flow again, you will have the same problem (most likely).
Follow jefflowrey's instructions to get the execution group to respond to deployment requests and delete the flow.
It looks like you are in UNIX and I'm wondering where you are looking for your runtime errors (these are the ones that will tell you that the queue is get inhibited and stuff like that). If you have not configured runtime messages to go to an additional file of your choosing, then look in the syslog file for runtime messages from the broker. If the input queue is inhibited you should at least see that message (when the flow is deployed).
PS: You are 5 maintenance levels behind but that is probably not your current problem. |
|
| Back to top |
|
|
| abhishekpreddy |
| Posted: Tue Apr 01, 2008 6:47 am Post subject: |
|
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
Hi Joseph ,
I have already redirected the Syslog errors to a different file , and i dont have any error messages in the file , and to follow jeffs advice, i already have some messages on the Q , so do you advice me to remove them and then set the Q to get inhibit and try to see if it works that way. |
|
| Back to top |
|
|
| abhishekpreddy |
| Posted: Tue Apr 01, 2008 6:48 am Post subject: |
|
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
Hi Jeff,
I did not understand this part of your suggestion "And then examine the message on the queue to see why it's causing your flow to loop." , what do you want me to examine the error log file to check for the error's |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 01, 2008 6:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
No.
I mean "debug your flow, using the message".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| abhishekpreddy |
| Posted: Tue Apr 01, 2008 7:27 am Post subject: |
|
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
Hi Jeff,
I Have done the steps which you have suggested , stopped the flows , undeployed the existing bar files and redeployed the bar again , I have debugged the flow using a sample message , but the message does not get picked up at all in the first instance |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Apr 01, 2008 10:21 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
If there are no messages in the your log, then stop and start one of the components (CM if it is there or Broker) and check for at least those messages. If they don't appear, your config is incorrect.
No message at all (in the runtime log) and the input queue set to inhibit on get indicates an incorrect config or queue name in the flow (which will create a 2085 or worse a connect to the wrong queue).
Try it with a simple Verification flow with incorrect queue names first. To verify the runtime log config. |
|
| Back to top |
|
|
|
|
