ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Advise on JMSInput Node

Post new topic  Reply to topic Goto page Previous  1, 2, 3
 Advise on JMSInput Node « View previous topic :: View next topic » 
Author Message
jorro004
PostPosted: Mon Mar 31, 2008 3:41 pm    Post subject: Reply with quote

Acolyte

Joined: 25 Aug 2007
Posts: 50

This time I get the below error, When I changed the format to "MQSTR"

]BIP2628E: Exception condition detected on input node TESTFLOW.TEST_BRK.IN.'. : DEV_BROKER.e3bb7391-1601-0000-0080-f8a85570e534: /build/S000_P/src/DataFlowEngine/ImbCommonInputNode.cpp: 1562: ImbCommonInputNode::run: ComIbmMQInputNode: TESTFLOW#FCMComposite_1_1
BIP2230E: Error detected whilst processing a message in node TESTFLOW.Publish Test.ComIbmPSService'. : DEV_BROKER.e3bb7391-1601-0000-0080-f8a85570e534: /build/S000_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubEngineNode.cpp: 499: ImbPubSubEngineNode::evaluate: ComIbmPSServiceNode: TESTFLOW#FCMComposite_1_4.ComIbmPublication#FCMComposite_1_1
BIP2230E: Error detected whilst processing a message in node ''. : DEV_BROKER.e3bb7391-1601-0000-0080-f8a85570e534: /build/S000_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubEngineNode.cpp: 775: ImbPubSubEngineNode::publish: ComIbmPSServiceNode: TESTFLOW#FCMComposite_1_4.ComIbmPublication#FCMComposite_1_1
BIP6062W: Invalid message body/header sequence 'xmlns'/'MQHRF2' encountered by node TESTFLOW.TEST_BRK.IN.'. : DEV_BROKER.e3bb7391-1601-0000-0080-f8a85570e534: /build/S000_P/src/DataFlowEngine/ImbRootParser.cpp: 286: ImbRootParser::refreshBitStreamFromElements: ComIbmMQInputNode: TESTFLOW#FCMComposite_1_1

Can you please explain what the exception is , As I didn't get any error earlier. Looks like it is not able to validate the Message format mentioned in the Input Node to that of one in the Compute node.?

Thanks
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Apr 01, 2008 12:39 am    Post subject: Reply with quote

Grand High Poobah

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

jorro004 wrote:
Can you please explain what the exception is


It seems fairly clear.

jorro004 wrote:
Looks like it is not able to validate the Message format mentioned in the Input Node to that of one in the Compute node.?


Not to me.

What it does look like is you need to spend more time thinking about what you're doing, reading the documentation and possibly obtaining budget for some training. Questions are one thing, this is on the brink of turning into a spoon feeding exersise!


_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jorro004
PostPosted: Fri Apr 04, 2008 6:34 am    Post subject: Reply with quote

Acolyte

Joined: 25 Aug 2007
Posts: 50

Hi Folks,

I did some study on the Pub/Sub and tried to implement and couldnt succeed and that is the reason for posting my questions in this form, As I belive that this forum is the best for Advise.

Please help me in solving this.I would like repeat the setup again which I have.
I have a Publish and subscriber flow in WBIMB 6, Which has the following details
Publish Flow

MQInputNode -> Compute -> Publish Node(Topic)

Code inside the Compute

SET OutputRoot = InputRoot;
SET OutputRoot.MQMD.Format = MQFMT_RF_HEADER_2;
SET OutputRoot.MQRFH2.psc.Command = 'Publish';
SET OutputRoot.MQRFH2.psc.Topic = 'TestTopic';
SET OutputRoot.MQRFH2.CodedCharSetId = 1208;
SET OutputRoot.MQRFH2.(MQRFH2.Field)Version = 2;
SET OutputRoot.MQRFH2.(MQRFH2.Field)Format = 'MQSTR';
SET OutputRoot.MQRFH2.(MQRFH2.Field)NameValueCCSID = 1208;

I belive code will Publish the Message with the Topic 'TestTopic'

Subscriber Flow

JMSInputNode -> JMSMQTransform -> MQOutput Node(Queue)

I have a bindings file where it was defined from JMSAdmin with the following details

DEF TCF(TestTopicConnFactory) clientid(BRK_ID)
DEF T(TestTopic) Topic(Topic/Information)

I configured the JMSInput to get the JNDI settings from bindings file and I searched the Subscriptions from the Broker Toolkit and it has the Following Information

Topic/Information with the Client ID

I think the Broker has the Subscriber info. But when I Publish message with the Topic ,I dont see any message at the Subscriber queue which is defined as TEST_OUT.

Can anyone please advise whether I missed any?

Thanks for your help!!
Back to top
View user's profile Send private message
kimbert
PostPosted: Fri Apr 04, 2008 7:28 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Your headers and body are the wrong way round because your ESQL is the wrong way round. Put in a Trace node and trace $Root - you will quickly see what the problem is.
Back to top
View user's profile Send private message
jorro004
PostPosted: Fri Apr 04, 2008 12:19 pm    Post subject: Reply with quote

Acolyte

Joined: 25 Aug 2007
Posts: 50

Hi Kimbert


Thanks for your suggestions
I changed the Code and looks like this

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

SET OutputRoot.MQMD.Format = MQFMT_RF_HEADER_2;
SET OutputRoot.MQRFH2.psc.Command = 'Publish';
SET OutputRoot.MQRFH2.psc.Topic = TestTopic;
SET OutputRoot.MQRFH2.CodedCharSetId = 1208;
SET OutputRoot.MQRFH2.(MQRFH2.Field)Version = 2;
SET OutputRoot.MQRFH2.(MQRFH2.Field)Format = 'MQSTR' ;
SET OutputRoot.MQRFH2.(MQRFH2.Field)NameValueCCSID = 1208;
SET OutputRoot.BLOB = InputRoot.BLOB ;

Below is my Trace.

(0x01000000):Properties = (
(0x03000000):MessageSet = ''
(0x03000000):MessageType = ''
(0x03000000):MessageFormat = ''
(0x03000000):Encoding = 273
(0x03000000):CodedCharSetId = 819
(0x03000000):Transactional = TRUE
(0x03000000):Persistence = FALSE
(0x03000000):CreationTime =
(0x03000000):ExpirationTime = -1
(0x03000000):Priority = 0
(0x03000000):ReplyIdentifier = (0x03000000):ReplyProtocol = 'MQ'
(0x03000000):Topic = 'TestTopic'
(0x03000000):ContentType = ''
(0x03000000):IdentitySourceType = ''
(0x03000000):IdentitySourceToken = ''
(0x03000000):IdentitySourcePassword = ''
(0x03000000):IdentitySourceIssuedBy = ''
(0x03000000):IdentityMappedType = ''
(0x03000000):IdentityMappedToken = ''
(0x03000000):IdentityMappedPassword = ''
(0x03000000):IdentityMappedIssuedBy = ''
)
(0x01000000):MQMD = (
(0x03000000):SourceQueue = 'BRK.IN.AQ'
(0x03000000):Transactional = TRUE
(0x03000000):Encoding = 273
(0x03000000):CodedCharSetId = 1208
(0x03000000):Format = 'MQHRF2 '
(0x03000000):Version = 2
(0x03000000):Report = 0
(0x03000000):MsgType = 8
(0x03000000):Expiry = -1
(0x03000000):Feedback = 0
(0x03000000):Priority = 0
(0x03000000):Persistence = 0
(0x03000000):MsgId =
(0x03000000):CorrelId =
(0x03000000):BackoutCount = 0
(0x03000000):ReplyToQ = ' '
(0x03000000):ReplyToQMgr = 'DEV_QM '
(0x03000000):UserIdentifier = 'mqm '
(0x03000000):AccountingToken =
(0x03000000):ApplIdentityData = ' '
(0x03000000):PutApplType = 28
(0x03000000):PutApplName = 'WebSphere MQ Client for Java'
(0x03000000):PutDate = DATE '2007-08-06'
(0x03000000):PutTime =
(0x03000000):ApplOriginData = ' '
(0x03000000):GroupId =
(0x03000000):MsgSeqNumber = 1
(0x03000000):Offset = 0
(0x03000000):MsgFlags = 0
(0x03000000):OriginalLength = -1
)
(0x01000000):MQRFH2 = (
(0x01000000):psc = (
(0x01000000):Command = (
(0x02000000): = 'Publish'
)
(0x01000000):Topic = (
(0x02000000): = 'TestTopic'
)
)
(0x01000000):CodedCharSetId = (
(0x02000000): = 1208
)
(0x03000000):Version = 2
(0x03000000):Format = 'MQSTR'
(0x03000000):NameValueCCSID = 1208
(0x01000000):mcd = (
(0x01000000):Msd = (
(0x02000000): = 'MQSTR'
)
)
)
(0x01000000):BLOB = (
(0x03000000):UnknownParserName = 'MQSTR'
(0x03000000):BLOB = X'3c6d696b4d6573736167653e0a3c6d696b4865616465723e0a093c536f757263653e524d5331325f4d51534

)

Even though I change the code I dont see message in the subscriber queue. I have the entire setup on one broker where it uses same Queue Manager for both Pub and Sub, Can this be done ? Please help!!

Thanks
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Apr 04, 2008 3:00 pm    Post subject: Reply with quote

Grand High Poobah

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

Are you even [u]looking[/i] at this?

jorro004 wrote:
(0x01000000):mcd = (
(0x01000000):Msd = (
(0x02000000): = 'MQSTR'
)
...

(0x03000000):UnknownParserName = 'MQSTR'


If the publish message has a parser error, is it any surprise it's not published?

jorro004 wrote:
Can this be done ?


Only if you start reading the error messages, thinking about possible causes and not just guessing. Why would using a single queue manager be invalid?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jorro004
PostPosted: Sat Apr 05, 2008 1:52 pm    Post subject: Reply with quote

Acolyte

Joined: 25 Aug 2007
Posts: 50

Hi Vitor,

Sorry for the trouble, I'm new to JMS concepts and couldnt find the way to sort the problem out. I changed the flow and deployed the code and now the parser is pointed to be 'XMLNS'

It will be good if you can forward me examples on implementing Publication node and JMS Input for subscriber in WBIMB 6.0 and required configurations to be done.

my email id : jorro004@yahoo.com

After changing code to the handle the parser with 'XMLNS', I still dont see the messages on the queue

Following is my publish code

SET OutputRoot.MQMD.Format = MQFMT_RF_HEADER_2;
SET OutputRoot.MQRFH2.psc.Command = 'Publish';
SET OutputRoot.MQRFH2.psc.Topic = 'Test';
SET OutputRoot.MQRFH2.psc.PubOpt = 'Local' ;
SET OutputRoot.MQRFH2.CodedCharSetId = 1208;
SET OutputRoot.MQRFH2.(MQRFH2.Field)Version = 2;
SET OutputRoot.MQRFH2.(MQRFH2.Field)Format = 'MQSTR' ;
SET OutputRoot.MQRFH2.(MQRFH2.Field)NameValueCCSID = 1208;
SET OutputRoot.MQRFH2.mcd.Msd = 'XMLNS';
SET OutputRoot.XMLNS = InputRoot.XMLNS ;

Suggestions Please ?

Thanks!!
Back to top
View user's profile Send private message
Vitor
PostPosted: Sat Apr 05, 2008 2:57 pm    Post subject: Reply with quote

Grand High Poobah

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

jorro004 wrote:
Sorry for the trouble, I'm new to JMS concepts and couldnt find the way to sort the problem out.


This is why they make training courses.

jorro004 wrote:
It will be good if you can forward me examples on implementing Publication node and JMS Input for subscriber in WBIMB 6.0 and required configurations to be done.


There are more than enough examples on the Web. The Search Button Remains Your Friend.

jorro004 wrote:
After changing code to the handle the parser with 'XMLNS', I still dont see the messages on the queue


Not entirely surprising, given the pub/sub model if you think about it.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Apr 05, 2008 5:58 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

jorro004 wrote:
SET OutputRoot.MQRFH2.(MQRFH2.Field)Format = 'MQSTR' ;


Replace it with
Code:
 SET OutputRoot.MQRFH2.(MQRFH2.Field)Format = MQFMT_STRING ;



_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3 Page 3 of 3

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Advise on JMSInput Node
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
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.