| Author |
Message
|
| dilse |
 Posted: Tue Apr 10, 2007 6:52 pm Post subject: BIP2628, BIP2230, BIP7095 and BIP2648 |
 |
|
Master
Joined: 24 Jun 2004
Posts: 270
|
All:
I am working on Windows workstation and I am seeing continuous BIP2628, BIP2230, BIP7095, and BIP2648 as long as my broker is running. But I was able to deploy the message flows and was able to run them with no problem. I am not sure why am I seeing these. So I deleted the old Broker, Config and created new ones even used new Queue Manager. But still I am seeing this sequence of errors even before not deploying any message flows into Broker. Not sure whats causing this behaviour.
I am seeing message("$") being put repeatedly in the assigned DEAD LETTER QUEUE by a put application name of "30\eclipse\jre\bin\javaw.exe" and with the report reason "Pass correlation identifier". Hope this helps in analyzing the situation.
Here is my environment:
WMQV6
WMBV6
DB2 8.1
Following are the explanation of errors I am seeing in EventViewer
| Quote: |
BIP2628:
( MY_BROKER.$SYS_mqsi ) Exception condition detected on input node 'PubSubControlMsgFlow.InputNode'.
The input node 'PubSubControlMsgFlow.InputNode' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages. |
| Quote: |
BIP2230:
( MY_BROKER.$SYS_mqsi ) Error detected whilst processing a message in node 'PubSubControlMsgFlow.ControlNode'.
The message broker detected an error whilst processing a message in node 'PubSubControlMsgFlow.ControlNode'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error. |
| Quote: |
BIP7095:
( MY_BROKER.$SYS_mqsi ) Requested response cannot be sent for non-RFH message.
A message requesting a response was received by the Publish/Subscribe Service. In order to send a response, the Publish/Subscribe Service requires that the message contains an RFH or RFH2 format header. The received message contained neither.
Ensure that the message was placed on the correct queue for the required message flow. If the correct queue was used, ensure that the message sent for this operation has an RFH or RFH2 header, or ensure that the report options in the message descriptor are set so that a response is not requested. |
| Quote: |
BIP2648:
( MY_BROKER.$SYS_mqsi ) Message backed out to a queue; node 'PubSubControlMsgFlow.InputNode'.
Node 'PubSubControlMsgFlow.InputNode' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.
Examine previous messages and the message flow to determine why the message is being backed out. Correct this situation if possible |
Hope someone already faced this situation. It is kind of irritating to see these errors all over Event Viewer.
Thanks in advance.
DilSe.. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Apr 10, 2007 8:45 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Well the source of the problem is clearly explained:
Trying to publish a message that is missing an RFH publish header...
So fix it already....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dilse |
| Posted: Wed Apr 11, 2007 8:45 am Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Thanks fjb_saper. But I do not have any flows to publish at all. As I mentioned I deleted all old objects and created the new QM, Broker and ConfigMgr. I didnt even deploy a single message flow but I am already getting these errors. How come this is possible? Please explain the possibility..
MORE INFO:
I am seeing the reason code on DEAD LETTER QUEUE as "MQFB_APPL_FIRST" and the put application is eclipse of MessageBrokerToolkit. Hope this helps in analyzing the situation.
Thanks.. |
|
| Back to top |
|
|
| dilse |
| Posted: Wed Apr 11, 2007 10:59 am Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Does anyone know when we get the reason "MQFB_APPL_FIRST"?
All I could find on this was
| Quote: |
MQFB_APPL_FIRST
Lowest value for application-generated feedback. |
But what does this mean? Whats wrong if it is a lowest value when it is acceptable? Can some one shed some light on this.
Thanks for your help.
DilSe.. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 11, 2007 11:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Broker just uses those codes when it throws messages on the DLQ.
Usually there are BIP errors in the log that tell you why the message went on the DLQ.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dilse |
| Posted: Wed Apr 11, 2007 11:23 am Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Thanks for the quick response Jeff.
I am continuously getting this sequence of BIP errors as I mentioned in my primary description of the problem. It is also inserting a message continously into the dead letter queue. I do not have any flow that is deployed and has a Publish/Subscribe use. So I am wondering what could be the cause of the problem. I did not even put a single message in the flows. I am seeing the Destination Queue on DLH as "SYSTEM.BROKER.CONTROL.QUEUE" but I am not referring this anywhere in the flows that I deployed to my broker. Please help here.. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 11, 2007 11:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What happens when you do a full deploy of the topology?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dilse |
| Posted: Wed Apr 11, 2007 1:01 pm Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Jeff
I did a full deploy of the topology and it was showing a successful deploy in the Eclipse event log. But the errors in the system event log were not stopped they are keep on coming and the DEAD LETTER QUEUE is keep on growing. I am kind of lost as to what to do.
Thanks.. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 11, 2007 1:06 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Are you using the same qmgr for ConfigMgr and Broker?
Is there anything "wrong" with SYSTEM.BROKER.CONTROL.QUEUE?
This appears to be a problem with the "internal" setup of your environment. You'll probably need to open a PMR.
Are you seeing core dumps or other error files anywhere? Look particularly in C:\Documents and Settings\All Users\Application Data\IBM\MQSI\common\errors
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dilse |
| Posted: Wed Apr 11, 2007 2:54 pm Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Yes. They both are using the same Queue Manager. As far as I can see there is nothing wrong with the SYSTEM.BROKER.CONTROL.QUEUE. Are there any checks that I can do to assure? I can use different ones if needed. Do you think if I could create a separate QM for each of the component will resolve the problem? This is not production but just my machine. So I can do whatever works.
Thanks... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 11, 2007 2:59 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I would stop all components, make sure all actual processes are really shut down (kill them if necessary).
Then look for abends/core files in the directory I pointed out.
Then start configmgr, and see what happens.
Then start broker and see what happens.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dilse |
| Posted: Wed Apr 11, 2007 3:08 pm Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Jeff,
I checked for core dumps but couldn't find any. Also I stopped everything and then started Username server and Configmgr first which didnt produce any errors but when I started the Broker it started generating this sequence of errors. I am not sure as to what causing this problem.
Thanks...
Last edited by dilse on Wed Apr 11, 2007 3:52 pm; edited 1 time in total |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 11, 2007 3:49 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yeah.
That suggests that there's something wrong with the configmgr.
Or somehow with your toolkit...
Try using the Config Mgr Proxy API Exerciser and see if it causes the same symptoms.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dilse |
| Posted: Wed Apr 11, 2007 3:53 pm Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Sorry Jeff. I just updated the last post. Here is the observation:
I checked for core dumps but couldn't find any. Also I stopped everything and then started Username server and Configmgr first which didnt produce any errors but when I started the Broker it started generating this sequence of errors. I am not sure as to what causing this problem. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 11, 2007 6:16 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay, so it only throws errors when you start broker.
So stop everything, clear all SYSTEM.BROKER.* queues, and then start everything again.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
