MQSeries.net :: View topic - Basic SQL Exception CONTINUE HANDLER

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Basic SQL Exception CONTINUE HANDLER

Goto page 1, 2, 3, 4 Next

Basic SQL Exception CONTINUE HANDLER

« View previous topic :: View next topic »

Author

Message

EricCox

Posted: Mon Mar 26, 2012 11:12 am Post subject: Basic SQL Exception CONTINUE HANDLER

Master

Joined: 08 Apr 2011
Posts: 292

To all,

Here is the ESQL of a very basic SQL Exception DECLARE CONTINUE HANDLER. Although I can make the Flow produce a SQL State SQL Exception the HANDLER is not picking up the details.

In the case of success I simply want to confirm the database call is made successfully through the trace, which it is and produce the most basic XML in a message going to the MQOutput Node.

In the case of SQL Exception I want it to show the four detail elements in a block of XML going to one of the Error Handling Nodes.

The flow is MQInputNode set to parse XML going to Compute Node going to MQOutput Node.

MQInput.Out>>>>TryCatch.Try>>>Compute>>>Trace>>>MQOutput
.Catch>>>Trace

Both trace nodes have Pattern = ${ExceptionList}. The MQInput.Failure Terminal is wired to an MQOutput Node.

In the case of the SQL Exception occuring I am not getting any Trace details...the HANDLER doesn't appear to be working.

In the case of success the message gets put to the SYSTEM.DEAD.LETTER.QUEUE. I can't get the flow to produce the message I want going to the queue destination I want in either scenario.

Can someone point me to the key things I'm doing wrong here?

Thanks everyone for the great help,
Eric

ComputeNode ESQL:

Code:

CREATE COMPUTE MODULE DB_EXCEPTION_HANDLER_RQ_Compute
CREATE FUNCTION Main() RETURNS BOOLEAN
BEGIN
   CALL CopyMessageHeaders();
   --CALL CopyEntireMessage();

   SET OutputRoot.Properties.MessageFormat = 'XML';

   DECLARE ref_CustInfo REFERENCE TO "InputRoot"."XML"."soapenv:Envelope"."soapenv:Body"."getCustomerInfo"."CustInfo";
   DECLARE sqlCode    CHARACTER;
   DECLARE sqlState    CHARACTER;
   DECLARE sqlNativeError CHARACTER;
   DECLARE sqlErrorText CHARACTER;

   SET OutputRoot.MQMD."Encoding" = MQENC_NATIVE;
   SET OutputRoot.MQMD.CodedCharSetId = MQCCSI_Q_MGR;
   SET OutputRoot.MQMD.UserIdentifier = '252525';
   SET OutputRoot.MQMD.ReplyToQMgr = 'BKRD01';
   SET OutputRoot.MQMD.ReplyToQ = 'Q1';
   SET OutputRoot.MQMD.Report = ' ';
   SET OutputRoot.MQMD.Report = ' ';
   SET OutputRoot.MQMD.MsgType = MQMT_REPLY;
   SET OutputRoot.MQMD.Format = MQFMT_STRING;

   SET OutputRoot.XML.(XML.XmlDecl)='';
   SET OutputRoot.XML.(XML.XmlDecl).(XML.Version)='1.0';
   SET "OutputRoot"."XML"."cfg-env:Envelope".(XML.Attribute)"xmlns" =
      'http://www.citizensbank.com/schemas/CFX/';
   SET "OutputRoot"."XML"."cfg-env:Envelope".(XML.Attribute)"xmlns:cfg-env" =
      'http://www.citizensbank.com/schemas/cfg-env/';
   SET "OutputRoot"."XML"."cfg-env:Envelope".(XML.Attribute)"xmlns:cfg-hdr" =
      'http://www.citizensbank.com/schemas/cfg-hdr/';
   SET "OutputRoot"."XML"."cfg-env:Envelope"."cfg-env:Header"."cfg-hdr:MessageHeader"."cfg-hdr:ErrorList"."cfg-hdr:Status" = 'Here';


   BEGIN
      DECLARE CONTINUE HANDLER FOR SQLSTATE LIKE'%'
      BEGIN

         SET sqlCode = SQLCODE;
         SET sqlState = SQLSTATE;
         SET sqlNativeError = SQLNATIVEERROR;
         SET sqlErrorText = SQLERRORTEXT;

         SET OutputRoot.XML.Top.WHILE.mySQLCODE = SQLCODE;
         SET OutputRoot.XML.Top.WHILE.mySQLSTATE = SQLSTATE;
      SET OutputRoot.XML.Top.WHILE.mySQLNATIVEERROR = SQLNATIVEERROR;
      SET OutputRoot.XML.Top.WHILE.mySQLERRORTEXT = SQLERRORTEXT;

      END;

      DECLARE prodCode character;
      DECLARE prodDesc ROW;

      IF ref_CustInfo."RelInfo"[0]."AcctType"."Code" = 'AL' THEN

      SET prodCode = COALESCE(ref_CustInfo."RelInfo"[0]."AcctInfo"."Product"."Code", '000') ;

         SET "Environment"."prodDesc"[] =
            (SELECT p.PROD_DESC
         FROM Database.GIABKR.PRODCODES AS p
      WHERE p.ACCT_TYPE = 'III' AND p.PROD_CODE = prodCode);

      END IF;
   END;

   RETURN TRUE;
END;

CREATE PROCEDURE CopyMessageHeaders() BEGIN
   DECLARE I INTEGER 1;
   DECLARE J INTEGER;
   SET J = CARDINALITY(InputRoot.*[]);
   WHILE I < J DO
      SET OutputRoot.*[I] = InputRoot.*[I];
      SET I = I + 1;
   END WHILE;
END;

CREATE PROCEDURE CopyEntireMessage() BEGIN
   SET OutputRoot = InputRoot;
END;
END MODULE;

Vitor

Posted: Mon Mar 26, 2012 11:22 am Post subject: Re: Basic SQL Exception CONTINUE HANDLER

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

EricCox wrote:

Both trace nodes have Pattern = ${ExceptionList}. The MQInput.Failure Terminal is wired to an MQOutput Node.

What's the MQInput node's Catch terminal wired to?

EricCox wrote:

In the case of success the message gets put to the SYSTEM.DEAD.LETTER.QUEUE. I can't get the flow to produce the message I want going to the queue destination I want in either scenario.

I'm assuming this is the dead letter queue assigned to the queue manager (grumble!)? Can you confirm that the reason in the dead letter header is in the range 65000 - 65999?

EricCox wrote:

Can someone point me to the key things I'm doing wrong here?

Not running a user trace to see what's happening.
_________________
Honesty is the best policy.
Insanity is the best defence.

EricCox

Posted: Mon Mar 26, 2012 11:27 am Post subject: Re: Basic SQL Exception CONTINUE HANDLER

Master

Joined: 08 Apr 2011
Posts: 292

Vitor wrote:

EricCox wrote:

Both trace nodes have Pattern = ${ExceptionList}. The MQInput.Failure Terminal is wired to an MQOutput Node.

What's the MQInput node's Catch terminal wired to?

EricCox wrote:

In the case of success the message gets put to the SYSTEM.DEAD.LETTER.QUEUE. I can't get the flow to produce the message I want going to the queue destination I want in either scenario.

I'm assuming this is the dead letter queue assigned to the queue manager (grumble!)? Can you confirm that the reason in the dead letter header is in the range 65000 - 65999?

EricCox wrote:

Can someone point me to the key things I'm doing wrong here?

Not running a user trace to see what's happening.

The MQInput.Catch Terminal is wired to MQOutput.In Terminal. I'll catch the failure trace and show that in my next message. I just try to send that .Catch message to a queue so I can see.

lancelotlinc

Posted: Mon Mar 26, 2012 11:33 am Post subject: Re: Basic SQL Exception CONTINUE HANDLER

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

EricCox wrote:

Vitor wrote:

EricCox wrote:

Both trace nodes have Pattern = ${ExceptionList}. The MQInput.Failure Terminal is wired to an MQOutput Node.

What's the MQInput node's Catch terminal wired to?

EricCox wrote:

In the case of success the message gets put to the SYSTEM.DEAD.LETTER.QUEUE. I can't get the flow to produce the message I want going to the queue destination I want in either scenario.

I'm assuming this is the dead letter queue assigned to the queue manager (grumble!)? Can you confirm that the reason in the dead letter header is in the range 65000 - 65999?

EricCox wrote:

Can someone point me to the key things I'm doing wrong here?

Not running a user trace to see what's happening.

The MQInput.Catch Terminal is wired to MQOutput.In Terminal. I'll catch the failure trace and show that in my next message. I just try to send that .Catch message to a queue so I can see.

Would rather use a Trace node instead of a queue.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

EricCox

Posted: Mon Mar 26, 2012 11:33 am Post subject: SQL Exception Scenario

Master

Joined: 08 Apr 2011
Posts: 292

Code:

Timestamps are formatted in local time, 240 minutes before GMT.
Trace written by version 6009; formatter version 6009

2012-03-26 15:31:54.700813 8372 UserTrace BIP4040I: The Execution Group ''Samples'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2012-03-26 15:31:54.701549 8372 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''QMBKRD01''. The MQCC was '0' and the MQRC was '0'.
2012-03-26 15:31:54.701599 8372 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''QMBKRD01''.
2012-03-26 15:31:58.680976 14004 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'DB_EXCEPTION_HANDLER_RQ.IAB.TLR.TESTQ2'.
2012-03-26 15:31:58.681140 14004 UserTrace BIP4080I: Message propagated to try terminal from try-catch node 'DB_EXCEPTION_HANDLER_RQ.TryCatch'.
The try-catch node 'DB_EXCEPTION_HANDLER_RQ.TryCatch' has received a message and is propagating it to any nodes connected to its try terminal.
No user action required.
2012-03-26 15:31:58.681491 14004 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'DB_EXCEPTION_HANDLER_RQ.IAB.TLR.TESTQ2' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2012-03-26 15:31:58.681552 14004 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'DB_EXCEPTION_HANDLER_RQ.IAB.TLR.TESTQ2' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2012-03-26 15:31:58.681713 14004 UserTrace BIP6061I: Parser type ''XML'' created on behalf of node 'DB_EXCEPTION_HANDLER_RQ.IAB.TLR.TESTQ2' to handle portion of incoming message of length '1849' bytes beginning at offset '364'. Parser type selected based on value ''XML'' from previous parser.
2012-03-26 15:31:58.912990 14004 UserTrace BIP2231E: Error detected whilst processing a message in node 'DB_EXCEPTION_HANDLER_RQ.ComputeException'.
The message broker detected an error whilst processing a message in node 'DB_EXCEPTION_HANDLER_RQ.ComputeException'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2012-03-26 15:31:58.913146 14004 DatabaseException BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.
2012-03-26 15:31:58.913173 14004 DatabaseException BIP2322E: Database error: SQL State ''28000''; Native Error Code '1017'; Error Text ''[DataDirect][ODBC Oracle driver][Oracle]ORA-01017: invalid username/password; logon denied ''.
The error has the following diagnostic information: SQL State ''28000'' SQL Native Error Code '1017' SQL Error Text ''[DataDirect][ODBC Oracle driver][Oracle]ORA-01017: invalid username/password; logon denied ''
This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error.
2012-03-26 15:31:58.913509 14004 UserTrace BIP2638I: The MQ output node 'DB_EXCEPTION_HANDLER_RQ.IAB.TLR.TESTQ1' attempted to write a message to queue ''IAB.TLR.TESTQ1'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2012-03-26 15:31:58.913585 14004 UserTrace BIP2622I: Message successfully output by output node 'DB_EXCEPTION_HANDLER_RQ.IAB.TLR.TESTQ1' to queue ''IAB.TLR.TESTQ1'' on queue manager ''''.
2012-03-26 15:31:58.914066 10868 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'DB_EXCEPTION_HANDLER_RS.MQInput'.
2012-03-26 15:31:58.914150 10868 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'DB_EXCEPTION_HANDLER_RS.MQInput' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2012-03-26 15:31:58.914199 10868 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'DB_EXCEPTION_HANDLER_RS.MQInput' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2012-03-26 15:31:58.914241 10868 UserTrace BIP6061I: Parser type ''BLOB'' created on behalf of node 'DB_EXCEPTION_HANDLER_RS.MQInput' to handle portion of incoming message of length '1849' bytes beginning at offset '364'. Parser type selected based on value ''NONE'' from previous parser.
2012-03-26 15:31:58.918022 10868 Error BIP2628E: Exception condition detected on input node 'DB_EXCEPTION_HANDLER_RS.MQInput'.
The input node 'DB_EXCEPTION_HANDLER_RS.MQInput' 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.
2012-03-26 15:31:58.918052 10868 RecoverableException BIP2230E: Error detected whilst processing a message in node 'DB_EXCEPTION_HANDLER_RS.Compute'.
The message broker detected an error whilst processing a message in node 'DB_EXCEPTION_HANDLER_RS.Compute'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2012-03-26 15:31:58.918087 10868 RecoverableException BIP2488E: ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '58.5') Error detected whilst executing the SQL statement ''''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
2012-03-26 15:31:58.918468 10868 RecoverableException BIP2580E: ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '59.15') : No external data source specified for this node.
An attempt was made to access an external database table, but no database inputs have been specified for this Compute, Filter or Database node.
Correct the syntax of your ESQL expression in node ''.DB_EXCEPTION_HANDLER_RQ_Compute.Main'', around line and column ''59.15'', then redeploy the message flow: Add database inputs for each table that is accessed, and redeploy the message flow.
2012-03-26 15:31:59.920055 10868 Error BIP2648E: Message backed out to a queue; node 'DB_EXCEPTION_HANDLER_RS.MQInput'.
Node 'DB_EXCEPTION_HANDLER_RS.MQInput' 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. Perform any local error recovery processing required.
2012-03-26 15:32:00.002923 10868 UserTrace BIP2638I: The MQ output node 'DB_EXCEPTION_HANDLER_RS.MQInput' attempted to write a message to queue ''SYSTEM.DEAD.LETTER.QUEUE'' connected to queue manager ''QMBKRD01''. The MQCC was '0' and the MQRC was '0'.
2012-03-26 15:32:00.002998 10868 UserTrace BIP2615I: The WebSphere MQ input node 'DB_EXCEPTION_HANDLER_RS.MQInput' has backed out the message to the backout requeue or the dead letter queue.
Message backout processing has been invoked, and the message has either been backed out by being written to the backout requeue or dead letter queue, as determined by the WebSphere MQ queue manager and queue configuration.
No user action required.
2012-03-26 15:32:15.197565 8372 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2012-03-26 15:32:15.197753 8372 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2012-03-26 15:32:15.197798 8372 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2012-03-26 15:32:15.198196 8372 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '350' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.

Threads encountered in this trace:
10868 14004 8372

Vitor

Posted: Mon Mar 26, 2012 11:34 am Post subject: Re: Basic SQL Exception CONTINUE HANDLER

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

EricCox wrote:

The MQInput.Catch Terminal is wired to MQOutput.In Terminal.

So both the Catch terminal of the TryCatch & the Catch terminal of the MQInput node are wired to an MQOutput message.

EricCox wrote:

I just try to send that .Catch message to a queue so I can see.

If you're trying to catch the exception list that won't work. The ExceptionList isn't part of Root or associated with a parser. So it doesn't get written out. It's clearly a trival task to do both of those tasks to get a message out of it.
_________________
Honesty is the best policy.
Insanity is the best defence.

EricCox

Posted: Mon Mar 26, 2012 11:40 am Post subject: Success Scenario Trace:

Master

Joined: 08 Apr 2011
Posts: 292

Code:

Timestamps are formatted in local time, 240 minutes before GMT.
Trace written by version 6009; formatter version 6009

2012-03-26 15:36:39.920284 8372 UserTrace BIP4040I: The Execution Group ''Samples'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2012-03-26 15:36:39.921207 8372 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''QMBKRD01''. The MQCC was '0' and the MQRC was '0'.
2012-03-26 15:36:39.921253 8372 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''QMBKRD01''.
2012-03-26 15:36:47.384151 10756 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'DB_EXCEPTION_HANDLER_RQ.IAB.TLR.TESTQ2'.
2012-03-26 15:36:47.384281 10756 UserTrace BIP4080I: Message propagated to try terminal from try-catch node 'DB_EXCEPTION_HANDLER_RQ.TryCatch'.
The try-catch node 'DB_EXCEPTION_HANDLER_RQ.TryCatch' has received a message and is propagating it to any nodes connected to its try terminal.
No user action required.
2012-03-26 15:36:47.384975 10756 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'DB_EXCEPTION_HANDLER_RQ.IAB.TLR.TESTQ2' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2012-03-26 15:36:47.385574 10756 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'DB_EXCEPTION_HANDLER_RQ.IAB.TLR.TESTQ2' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2012-03-26 15:36:47.386268 10756 UserTrace BIP6061I: Parser type ''XML'' created on behalf of node 'DB_EXCEPTION_HANDLER_RQ.IAB.TLR.TESTQ2' to handle portion of incoming message of length '1849' bytes beginning at offset '364'. Parser type selected based on value ''XML'' from previous parser.
2012-03-26 15:36:47.592800 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''BEGIN ... END;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '2.2').
2012-03-26 15:36:47.593040 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''CopyEntireMessage();'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '4.3').
2012-03-26 15:36:47.593082 10756 UserTrace BIP2538I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''CopyEntireMessage()'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '4.8').
2012-03-26 15:36:47.593139 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''BEGIN ... END;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.CopyEntireMessage', '1.39').
2012-03-26 15:36:47.593250 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot = InputRoot;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.CopyEntireMessage', '2.3').
2012-03-26 15:36:47.593330 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''InputRoot'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.CopyEntireMessage', '2.20'). This resolved to ''InputRoot''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2012-03-26 15:36:47.593376 10756 UserTrace BIP2568I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Copying sub-tree from ''InputRoot'' to ''OutputRoot''.
2012-03-26 15:36:47.593971 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.Properties.MessageFormat = 'XML';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '6.3').
2012-03-26 15:36:47.594036 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''XML''' to field / variable ''OutputRoot.Properties.MessageFormat''.
2012-03-26 15:36:47.594074 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''DECLARE ref_CustInfo REFERENCE TO InputRoot.XML.soapenv:Envelope.soapenv:Body.getCustomerInfoForTellerRs.CustInfo;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '8.3').
2012-03-26 15:36:47.594364 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''DECLARE sqlCode CHARACTER;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '9.3').
2012-03-26 15:36:47.594398 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''DECLARE sqlState CHARACTER;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '10.3').
2012-03-26 15:36:47.594429 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''DECLARE sqlNativeError CHARACTER;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '11.3').
2012-03-26 15:36:47.594459 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''DECLARE sqlErrorText CHARACTER;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '12.3').
2012-03-26 15:36:47.594505 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.MQMD.Encoding = MQENC_NATIVE;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '14.3').
2012-03-26 15:36:47.594535 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''MQENC_NATIVE'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '14.36'). This resolved to ''MQENC_NATIVE''. The result was ''546''.
2012-03-26 15:36:47.594566 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value ''546'' to field / variable ''OutputRoot.MQMD.Encoding''.
2012-03-26 15:36:47.594596 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.MQMD.CodedCharSetId = MQCCSI_Q_MGR;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '15.3').
2012-03-26 15:36:47.594623 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''MQCCSI_Q_MGR'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '15.40'). This resolved to ''MQCCSI_Q_MGR''. The result was ''0''.
2012-03-26 15:36:47.594646 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value ''0'' to field / variable ''OutputRoot.MQMD.CodedCharSetId''.
2012-03-26 15:36:47.594673 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.MQMD.UserIdentifier = 'N016438';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '16.3').
2012-03-26 15:36:47.594856 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''N016438''' to field / variable ''OutputRoot.MQMD.UserIdentifier''.
2012-03-26 15:36:47.594890 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.MQMD.ReplyToQMgr = 'BKRD01';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '17.3').
2012-03-26 15:36:47.594917 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''BKRD01''' to field / variable ''OutputRoot.MQMD.ReplyToQMgr''.
2012-03-26 15:36:47.594947 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.MQMD.ReplyToQ = 'Q1';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '18.3').
2012-03-26 15:36:47.594974 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''Q1''' to field / variable ''OutputRoot.MQMD.ReplyToQ''.
2012-03-26 15:36:47.595001 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.MQMD.Report = ' ';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '19.3').
2012-03-26 15:36:47.595027 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value ''' ''' to field / variable ''OutputRoot.MQMD.Report''.
2012-03-26 15:36:47.595069 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.MQMD.Report = ' ';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '20.3').
2012-03-26 15:36:47.595096 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value ''' ''' to field / variable ''OutputRoot.MQMD.Report''.
2012-03-26 15:36:47.595123 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.MQMD.MsgType = MQMT_REPLY;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '21.3').
2012-03-26 15:36:47.595153 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''MQMT_REPLY'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '21.33'). This resolved to ''MQMT_REPLY''. The result was ''2''.
2012-03-26 15:36:47.595176 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value ''2'' to field / variable ''OutputRoot.MQMD.MsgType''.
2012-03-26 15:36:47.595207 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.MQMD.Format = MQFMT_STRING;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '22.3').
2012-03-26 15:36:47.595245 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''MQFMT_STRING'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '22.32'). This resolved to ''MQFMT_STRING''. The result was '''MQSTR '''.
2012-03-26 15:36:47.595279 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''MQSTR ''' to field / variable ''OutputRoot.MQMD.Format''.
2012-03-26 15:36:47.595314 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.XML.(XML.XmlDecl)*:* = '';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '24.3').
2012-03-26 15:36:47.595352 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''XML.XmlDecl'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '24.23'). This resolved to ''XML.XmlDecl''. The result was ''83886104''.
2012-03-26 15:36:47.595470 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''''' to field / variable ''OutputRoot.XML.(XML.XmlDecl)*:*''.
2012-03-26 15:36:47.595504 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.XML.(XML.XmlDecl)*:*.(XML.Version)*:* = '1.0';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '25.3').
2012-03-26 15:36:47.595535 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''XML.XmlDecl'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '25.23'). This resolved to ''XML.XmlDecl''. The result was ''83886104''.
2012-03-26 15:36:47.595565 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''XML.Version'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '25.37'). This resolved to ''XML.Version''. The result was ''100663313''.
2012-03-26 15:36:47.595600 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''1.0''' to field / variable ''OutputRoot.XML.(XML.XmlDecl)*:*.(XML.Version)*:*''.
2012-03-26 15:36:47.595630 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.XML.cfg-env:Envelope.(XML.Attribute)xmlns = 'http://www.citizensbank.com/schemas/CFX/';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '26.3').
2012-03-26 15:36:47.596191 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''XML.Attribute'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '26.46'). This resolved to ''XML.Attribute''. The result was ''50331648''.
2012-03-26 15:36:47.596256 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''http://www.citizensbank.com/schemas/CFX/''' to field / variable ''OutputRoot.XML.cfg-env:Envelope.(XML.Attribute)xmlns''.
2012-03-26 15:36:47.596298 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.XML.cfg-env:Envelope.(XML.Attribute)xmlns:cfg-env = 'http://www.citizensbank.com/schemas/cfg-env/';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '28.3').
2012-03-26 15:36:47.596351 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''XML.Attribute'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '28.46'). This resolved to ''XML.Attribute''. The result was ''50331648''.
2012-03-26 15:36:47.596473 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''http://www.citizensbank.com/schemas/cfg-env/''' to field / variable ''OutputRoot.XML.cfg-env:Envelope.(XML.Attribute)xmlns:cfg-env''.
2012-03-26 15:36:47.596508 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.XML.cfg-env:Envelope.(XML.Attribute)xmlns:cfg-hdr = 'http://www.citizensbank.com/schemas/cfg-hdr/';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '30.3').
2012-03-26 15:36:47.596549 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''XML.Attribute'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '30.46'). This resolved to ''XML.Attribute''. The result was ''50331648''.
2012-03-26 15:36:47.596584 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''http://www.citizensbank.com/schemas/cfg-hdr/''' to field / variable ''OutputRoot.XML.cfg-env:Envelope.(XML.Attribute)xmlns:cfg-hdr''.
2012-03-26 15:36:47.596611 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET OutputRoot.XML.cfg-env:Envelope.cfg-env:Header.cfg-hdr:MessageHeader.cfg-hdr:ErrorList.cfg-hdr:Status = 'Here';'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '32.3').
2012-03-26 15:36:47.596641 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''Here''' to field / variable ''OutputRoot.XML.cfg-env:Envelope.cfg-env:Header.cfg-hdr:MessageHeader.cfg-hdr:ErrorList.cfg-hdr:Status''.
2012-03-26 15:36:47.596679 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''BEGIN ... END;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '35.3').
2012-03-26 15:36:47.596706 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''DECLARE prodCode CHARACTER;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '51.4').
2012-03-26 15:36:47.596744 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''DECLARE prodDesc ROW;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '52.4').
2012-03-26 15:36:47.596817 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''IF ref_CustInfo.RelInfo[0].AcctType.Code = 'AL' THEN... END IF;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '54.4').
2012-03-26 15:36:47.597396 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''ref_CustInfo.RelInfo[0].AcctType.Code'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '54.7'). This resolved to ''ref_CustInfo.RelInfo[0].AcctType.Code''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Code' Value='AL'''.
2012-03-26 15:36:47.597480 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''ref_CustInfo.RelInfo[0].AcctType.Code = 'AL''' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '54.51'). This resolved to ''ROW... Root Element Type=16777216 NameSpace='' Name='Code' Value='AL' = 'AL'''. The result was ''TRUE''.
2012-03-26 15:36:47.597530 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET prodCode = COALESCE(ref_CustInfo.RelInfo[0].AcctInfo.Product.Code, '000');'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '56.10').
2012-03-26 15:36:47.597572 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''ref_CustInfo.RelInfo[0].AcctInfo.Product.Code'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '56.34'). This resolved to ''ref_CustInfo.RelInfo[0].AcctInfo.Product.Code''. The result was '''067'''.
2012-03-26 15:36:47.597599 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''COALESCE(ref_CustInfo.RelInfo[0].AcctInfo.Product.Code, '000')'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '56.25'). This resolved to ''COALESCE('067')''. The result was '''067'''.
2012-03-26 15:36:47.597637 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''SET Environment.prodDesc[ ] = (SELECT COLUMN(0) AS :PROD_DESC FROM DATABASE(, prodCode));'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '58.5').
2012-03-26 15:36:47.597827 10756 UserTrace BIP2538I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''(SELECT COLUMN(0) AS :PROD_DESC FROM DATABASE(, prodCode))'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '59.15').
2012-03-26 15:36:47.597881 10756 UserTrace BIP2573W: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '59.15') : Finding first SELECT result.
2012-03-26 15:36:47.597938 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''prodCode'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '61.57'). This resolved to ''prodCode''. The result was '''067'''.
2012-03-26 15:36:47.597976 10756 UserTrace BIP2544I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing database SQL statement ''SELECT p.PROD_DESC FROM GIABKR.PRODCODES p WHERE ((p.ACCT_TYPE)=('CHK'))AND((p.PROD_CODE)=(?))'' derived from ('', '1.1'); expressions ''prodCode''; resulting parameter values '''067'''.
2012-03-26 15:36:47.627590 10756 UserTrace BIP2539I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Evaluating expression ''DATABASE(, prodCode)'' at ('', '1.1'). This resolved to ''SELECT p.PROD_DESC FROM GIABKR.PRODCODES p WHERE ((p.ACCT_TYPE)=('CHK'))AND((p.PROD_CODE)=(?))''. The result was ''Complex result''.
2012-03-26 15:36:47.628498 10756 UserTrace BIP2562I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning a list to ''Environment.prodDesc[]''.
2012-03-26 15:36:47.628570 10756 UserTrace BIP2566I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Assigning value '''Business Account Charges''' to field / variable ''Environment.prodDesc[1]''.
2012-03-26 15:36:47.628601 10756 UserTrace BIP2574W: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '59.15') : Finding next SELECT result.
2012-03-26 15:36:47.628631 10756 UserTrace BIP2571W: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '59.15') : Failed to find any more items in the FROM clause satisfying the WHERE clause.
2012-03-26 15:36:47.628707 10756 UserTrace BIP2537I: Node 'DB_EXCEPTION_HANDLER_RQ.ComputeException': Executing statement ''RETURN TRUE;'' at ('.DB_EXCEPTION_HANDLER_RQ_Compute.Main', '66.3').
2012-03-26 15:36:47.628795 10756 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'DB_EXCEPTION_HANDLER_RQ.ComputeException'.
2012-03-26 15:36:47.629283 10756 UserTrace BIP2638I: The MQ output node 'DB_EXCEPTION_HANDLER_RQ.Q1' attempted to write a message to queue ''Q1'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2012-03-26 15:36:47.629310 10756 UserTrace BIP2622I: Message successfully output by output node 'DB_EXCEPTION_HANDLER_RQ.Q1' to queue ''Q1'' on queue manager ''''.
2012-03-26 15:37:01.234344 8372 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2012-03-26 15:37:01.234452 8372 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2012-03-26 15:37:01.234539 8372 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2012-03-26 15:37:01.234853 8372 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '350' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.

Threads encountered in this trace:
10756 8372

Vitor

Posted: Mon Mar 26, 2012 11:41 am Post subject:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Please put ESQL & Trace in @code@ tags!

Last time I'm editing for you....
_________________
Honesty is the best policy.
Insanity is the best defence.

EricCox

Posted: Mon Mar 26, 2012 11:44 am Post subject: DLQ Header Reason

Master

Joined: 08 Apr 2011
Posts: 292

The DLQ Reason is: 65536

EricCox

Posted: Mon Mar 26, 2012 11:45 am Post subject:

Master

Joined: 08 Apr 2011
Posts: 292

Vitor wrote:

Please put ESQL & Trace in @code@ tags!

Last time I'm editing for you....

Sorry, I didn't know there was a tag to wrap around. I'll look for the FAQ. My apology.

Vitor

Posted: Mon Mar 26, 2012 11:46 am Post subject: Re: SQL Exception Scenario

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

EricCox wrote:

Code:

So this shows a message failing because of an invalid user / password being written to IAB.TLR.TESTQ1 by an MQOutput node, being rolled back and then put to SYSTEM.DEAD.LETTER.QUEUE because the backout count has been exceeded and there's no connection on the MQInput node's Failure terminal.

This is what I'd expect aside from you'd previously stated the Failure terminal was connected. You should investigate this.
_________________
Honesty is the best policy.
Insanity is the best defence.

Vitor

Posted: Mon Mar 26, 2012 11:48 am Post subject: Re: Success Scenario Trace:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

EricCox wrote:

Code:

This seems to be happily writing to Q1 having found "067" out of the database.
_________________
Honesty is the best policy.
Insanity is the best defence.

EricCox

Posted: Mon Mar 26, 2012 11:49 am Post subject: Re: SQL Exception Scenario

Master

Joined: 08 Apr 2011
Posts: 292

Vitor wrote:

EricCox wrote:

Code:

Yes, I do have the MQInput.Failure wired to TraceNode now. I'll look into that more.

Thanks

Vitor

Posted: Mon Mar 26, 2012 11:50 am Post subject: Re: DLQ Header Reason

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

EricCox wrote:

The DLQ Reason is: 65536

So it's being DLQ'd because the backout count was exceeded (as the trace indicates) and there's no backout queue specified. Again as I'd expect.

If you want it someplace else, specify the someplace else. Or figure out why it thinks the Failure terminal isn't connected.
_________________
Honesty is the best policy.
Insanity is the best defence.

EricCox

Posted: Mon Mar 26, 2012 11:50 am Post subject: Re: Success Scenario Trace:

Master

Joined: 08 Apr 2011
Posts: 292

Vitor wrote:

EricCox wrote:

Code:

This seems to be happily writing to Q1 having found "067" out of the database.

That is the funny thing. Although it shows the happy '0', '0' going to Q1 I never receive anything in the queue.

Display posts from previous:

Goto page 1, 2, 3, 4 Next

Page 1 of 4

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Basic SQL Exception CONTINUE HANDLER

Jump to:

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

Protected by Anti-Spam ACP