MQSeries.net :: View topic - Catching downstream propogation in your own InputNode

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 » Catching downstream propogation in your own InputNode

Catching downstream propogation in your own InputNode

« View previous topic :: View next topic »

Author

Message

bbakerman

Posted: Mon Aug 15, 2005 12:12 am Post subject: Catching downstream propogation in your own InputNode

Apprentice

Joined: 17 Dec 2003
Posts: 41

I am writing my own InputNode in Java that talks custom TCPIP to a source system and then "propogates" the received message down
the an Out terminal.

If I detect a downstram exception in the flow I want to catch it and
tell the source system (on the other end of the TCPIP connection) that the message was not sucessfully received.

So part of my code (once I have created the message assembly etc..) is this :

Code:

         try {
            // down the out terminal we go. If we come back OK, then its been processed
            // and accepted by the message flow,
            //
            outTerminal.propagate(outputAssembly);
            outputMsg.clearMessage();
            outputLEMsg.clearMessage();
         } catch (MbException mbe) {
            brokerIssue = mbe;
         }

Now I though that a down stream exception would be caught by the try catch in Java and then I could determine what happens next.

But it does look like this is happening. When I am running under the JVM remote debugger I get an suspended MbBrokerException as follows

Code:

Thread [Thread-11] (Suspended (exception com.ibm.broker.plugin.MbBrokerException))
com.ibm.broker.plugin.MbOutputTerminal.propagate(com.ibm.broker.plugin.MbMessageAssembly) line: 135 [local variables unavailable]
com.ibm.wbihmb.nodes.TcpHL7InputNode.run(com.ibm.broker.plugin.MbMessageAssembly) line: 112

and then it does not continue control back at my code. It just seems to stop the ........

HANG on, in writing this posting I discovered that the MbBrokerException is not derived from MbException and hence the code above does not work.

Ahh must read the specs carefully.

I though I would leave this post for others that might fall into the same trap.

Cheers
Brad

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Catching downstream propogation in your own InputNode

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