| Author |
Message
|
| naveenkumarv08 |
 Posted: Mon Jul 14, 2014 4:44 am Post subject: 2667:Exception occured at PolicyExDeliverMF.PolicyEx_SF |
 |
|
Newbie
Joined: 27 Feb 2014
Posts: 5
|
Expecting solution for this exception .
<![CDATA[PolicyExDeliverMF on QL9002C1.BRKR:IND_2.1 threw error 2667.
Event Id: 05
Event Registry: WMB
Event Registry Version: 1
Event Display Text: Message Broker encountered a fatal error
Event Severity: Fatal
Event Priority: Urgent
Event Response Code: Failure
Complete Event Description: Exception occured at PolicyExDeliverMF.PolicyEx_SF.PolicyExRequestReply_SF.MQOutput: Caught exception and rethrowing; Error detected, rethrowing; Caught exception and rethrowing; Failed to put message; WMB.DP.EPOLICY.DELIVER.REQUEST.Q
]]>
Exception List :
2014-07-09 14:43:09,235 [Thread-21] ERROR PolicyExDeliverMF - Transaction: 20140709144312_000CG120340 --Exception List: (
(0x01000000):RecoverableException = (
(0x03000000):File = '/build/S700_P/src/DataFlowEngine/ImbComputeNode.cpp'
(0x03000000):Line = 489
(0x03000000):Function = 'ImbComputeNode::evaluate'
(0x03000000):Type = 'ComIbmComputeNode'
(0x03000000):Name = 'PolicyExDeliverMF#FCMComposite_1_9.PolicyEx_SF#FCMComposite_1_33'
(0x03000000):Label = 'PolicyExDeliverMF.PolicyEx_SF.FileUtility_Loop'
(0x03000000):Catalog = 'BIPmsgs'
(0x03000000):Severity = 3
(0x03000000):Number = 2230
(0x03000000):Text = 'Caught exception and rethrowing'
(0x01000000):RecoverableException = (
(0x03000000):File = '/build/S700_P/src/DataFlowEngine/ImbRdl/ImbRdlStatementGroup.cpp'
(0x03000000):Line = 643
(0x03000000):Function = 'SqlStatementGroup::execute'
(0x03000000):Type = 'ComIbmComputeNode'
(0x03000000):Name = 'PolicyExDeliverMF#FCMComposite_1_9.PolicyEx_SF#FCMComposite_1_33'
(0x03000000):Label = 'PolicyExDeliverMF.PolicyEx_SF.FileUtility_Loop'
(0x03000000):Catalog = 'BIPmsgs'
(0x03000000):Severity = 3
(0x03000000):Number = 2488
(0x03000000):Text = 'Error detected, rethrowing'
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = '.PolicyEx_SF_FileUtility_Loop.Main'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = '80.3'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'PROPAGATE TO TERMINAL 'out1' FINALIZE DEFAULT DELETE DEFAULT;'
)
(0x01000000):RecoverableException = (
(0x03000000):File = '/build/S700_P/src/DataFlowEngine/ImbMqOutputNode.cpp'
(0x03000000):Line = 870
(0x03000000):Function = 'ImbMqOutputNode::evaluate'
(0x03000000):Type = 'ComIbmMQOutputNode'
(0x03000000):Name = 'PolicyExDeliverMF#FCMComposite_1_9.PolicyEx_SF#FCMComposite_1_10.RequestReply_SF#FCMComposite_1_1'
(0x03000000):Label = 'PolicyExDeliverMF.PolicyEx_SF.PolicyExRequestReply_SF.MQOutput'
(0x03000000):Catalog = 'BIPmsgs'
(0x03000000):Severity = 3
(0x03000000):Number = 2230
(0x03000000):Text = 'Caught exception and rethrowing'
(0x01000000):MessageException = (
(0x03000000):File = '/build/S700_P/src/DataFlowEngine/ImbMqOutputNode.cpp'
(0x03000000):Line = 2158
(0x03000000):Function = 'ImbMqOutputNode::putMessage'
(0x03000000):Type = 'ComIbmMQOutputNode'
(0x03000000):Name = 'PolicyExDeliverMF#FCMComposite_1_9.PolicyEx_SF#FCMComposite_1_10.RequestReply_SF#FCMComposite_1_1'
(0x03000000):Label = 'PolicyExDeliverMF.PolicyEx_SF.PolicyExRequestReply_SF.MQOutput'
(0x03000000):Catalog = 'BIPmsgs'
(0x03000000):Severity = 3
(0x03000000):Number = 2667
(0x03000000):Text = 'Failed to put message'
(0x01000000):Insert = (
(0x03000000):Type = 2
(0x03000000):Text = '-1'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'MQW102'
)
(0x01000000):Insert = (
(0x03000000):Type = 2
(0x03000000):Text = '2030'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = ''
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = ''
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'WMB.DP.EPOLICY.DELIVER.REQUEST.Q'
)
)
)
)
) |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Jul 14, 2014 5:51 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
The key is in the exception list
| Code: |
(0x01000000):Insert = (
(0x03000000):Type = 2
(0x03000000):Text = '2030
|
Lookup the MQ error code reason for 2030 and you will get a clue as to the reason for the failure.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| naveenkumarv08 |
| Posted: Tue Jul 15, 2014 1:00 am Post subject: Hi |
|
|
Newbie
Joined: 27 Feb 2014
Posts: 5
|
Hi i have checked with mqrc reason code 2030 and i got the solution in the command console as 2030 0x000007ee MQRC_MSG_TOO_BIG_FOR_Q ,
so i have informed this to middle ware team to increase the message length of the queue but they replied like this :
Hi Naveen,
The issue seems to be with the messages here not with the queue, because the queue was created on 2013-03-07 and this is the first time that we came across this "MQRC_MSG_TOO_BIG_FOR_Q" error, that too only for three messages. Did you analyzed the messages why its big then the usually messages length.
Please check why the put application placed a big messages then the usual length. If you are sure that the putting application message length is increased due to a change or something then let us know the size that need to set.
If there is a need to increase the message length means then please let us know the flow so that we can increase message length for the other objects as well which involves in this flow, else provide the object list that need to be increased.
i have seen the message properties its size is just 13kb , so do we have any other solution for this exception |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Jul 15, 2014 1:53 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Write the message to a file instead of the queue as a temp measure and really see how long the message is.
You could then try to put the data contained in the message onto that queue
and see what happens.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| naveenkumarv08 |
| Posted: Tue Jul 15, 2014 11:33 am Post subject: Hi |
|
|
Newbie
Joined: 27 Feb 2014
Posts: 5
|
| Yes i will try that , but when i am trying to put the same xml message in INT and DEV Environment to the same queue through RFHutil c the message is going |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jul 15, 2014 11:53 am Post subject: Re: Hi |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| naveenkumarv08 wrote: |
| Yes i will try that , but when i am trying to put the same xml message in INT and DEV Environment to the same queue through RFHutil c the message is going |
It's not the same queue if it's in a different environment. It's most likely a queue of the same name hosted on an INT or DEV queue manager, and could have different properties to the PROD one. Like larger MAXMSGL values.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| naveenkumarv08 |
| Posted: Wed Jul 16, 2014 11:28 pm Post subject: Hi |
|
|
Newbie
Joined: 27 Feb 2014
Posts: 5
|
Hi in my company we are using the same queue name for different environments , but we are giving different Qmanager name like SFG.SUPPORT.CHANNEL/TCP/PDXLWMBi001(6431) for Int , SFG.SUPPORT.CHANNEL/TCP/PDXLWMBd001(6431) for Dev .......etc
Do we have any other solution for this exception except this one |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jul 17, 2014 12:25 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Dump the proerties for the problem queue on the QMGR where it works and also where it does not work and compare them.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 17, 2014 5:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| smdavies99 wrote: |
| Dump the proerties for the problem queue on the QMGR where it works and also where it does not work and compare them. |
And alluded to this above. It's not the "same" queue if you connect to different queue managers.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| naveenkumarv08 |
| Posted: Fri Jul 18, 2014 2:31 am Post subject: Hi |
|
|
Newbie
Joined: 27 Feb 2014
Posts: 5
|
WMB.DP.EPOLICY.DELIVER.REQUEST.Q
Hi can u check this Queue properties and tell me any solution , the message which failed is 13 kb in size
Properties :
in Extended Tab
Max Queue depth - 1000
Max Message length - 4194304
shareability - shareable
default input open option - input shared
message delivery sequence - priority
retention interval - 999999999
definition type - predefined
distribution lists - not supported
default read ahead - no
default put response type - synchronous
property control - compatiablity[/img] |
|
| Back to top |
|
|
|
|
