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 » Subscribe to Topics using Rfhutil

Post new topic  Reply to topic Goto page 1, 2  Next
 Subscribe to Topics using Rfhutil « View previous topic :: View next topic » 
Author Message
angka
PostPosted: Thu Jan 10, 2008 8:43 pm    Post subject: Subscribe to Topics using Rfhutil Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

I used Message Broker toolkit to add a Topics Sports/Soccer. I wanna use rfhutil to subscribe to Sports/Soccer.

What I did but not working:
1) on rfhutil main tab, I putting to SYSTEM.BROKER.CONTROL.QUEUE
2) on the MQMQ tab, I set Reply to QM as QMB(subscriber QM) and Reply to Queue as Q1(subscriber local Q)
3) on PubSub tab, I chose "Sub" and under Topics I set Sports/Soccer

Then I write to Queue. The message go to the System.dead.letter.queue. the DLQ header is 65536 so I have no clue on what went wrong.

Is there any other setting required?

Btw I am running Message Broker and MQ on the same Windows machine and the rfhutil is also on the same machine.

Thanks
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Jan 10, 2008 8:49 pm    Post subject: Reply with quote

Grand High Poobah

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

The information you set on the MQMD tab is not for the subscription.
Make the message a request message and the broker will send there a status message telling you whether the subscription was successful or not.

The subscription queue and qmgr are set on the Pub/Sub tab. You may have to look at the fields on the bottom.
You need as well to make sure you checked all the right radio buttons for the RFH2 header...

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
angka
PostPosted: Thu Jan 10, 2008 10:26 pm    Post subject: Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

I tried putting in the Sub QM as QMB(subscriber QM) and Sub Q as Q1(subscriber local Q) it still get to the SYSTEM.DEAD.LETTER.QUEUE. I look at the Qmgr error log nothing is written?? In the RFH tab, I checked the Include RFH V2 Header with PubSub and Pscr checked also. I add a transmission queue in QMA (Broker QM) as QMB and a sender channel associate with it it still dun work..

did i leave out sth?

Thanks
Back to top
View user's profile Send private message
AkankshA
PostPosted: Thu Jan 10, 2008 11:55 pm    Post subject: Reply with quote

Grand Master

Joined: 12 Jan 2006
Posts: 1494
Location: Singapore

In RFHUtil pub sub tab provide topic/subQ and QM name

Queue Manager to connect to should be your broker QM


for reply msgs populate the MQMD tab
_________________
Cheers
Back to top
View user's profile Send private message Visit poster's website
angka
PostPosted: Fri Jan 11, 2008 12:07 am    Post subject: Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

I did just tt. and it still get to the System DLQ.

I did get the reply working when i purposely choose CorrelAsId on the PubSub tab but i set 0 on the MQMD tab for CorrelID. And the reply show the error with MQRC_CORREL_ID_ERROR. so the reply part is ok.. but when i unchecked CorrelAsId and send the message, the message get to the System DLQ.

btw do I need to configure anything on the broker toolkit? Thanks
Back to top
View user's profile Send private message
AkankshA
PostPosted: Fri Jan 11, 2008 12:46 am    Post subject: Reply with quote

Grand Master

Joined: 12 Jan 2006
Posts: 1494
Location: Singapore

ione sec.. wait a min...

your subscriptions is getting registered and the reply if going to dead letter queue.. or is it that the subscription is not getting registered all together...
_________________
Cheers
Back to top
View user's profile Send private message Visit poster's website
angka
PostPosted: Fri Jan 11, 2008 12:58 am    Post subject: Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

The subscription is not going registered at all.
I look at the Windows Event Viewer, everytime i wrote a message, there are errors regarding parsing of mqmd user id etc... is it due to the user id too long?? i am using administrator..

Thanks
Back to top
View user's profile Send private message
AkankshA
PostPosted: Fri Jan 11, 2008 1:12 am    Post subject: Reply with quote

Grand Master

Joined: 12 Jan 2006
Posts: 1494
Location: Singapore

length shall not be an issue..

can u past the msgs from event viewer..
_________________
Cheers
Back to top
View user's profile Send private message Visit poster's website
angka
PostPosted: Fri Jan 11, 2008 1:29 am    Post subject: Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

Error 1:
( Broker_QM.default ) 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.

Error 2:
( Broker_QM.default ) 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.

Error 3:
( Broker_QM.default ) Error detected whilst processing a message in node ''caught exception''.

The message broker detected an error whilst processing a message in node ''caught exception''. An exception has been thrown to cut short the processing of the message.

See the following messages for details of the error.

Warning 1:
( Broker_QM.default ) Error in parser ''MQMD'' whilst writing the field named ''UserIdentifier'' to the bitstream.

This message gives the name of the field in the parser that was being written at the time the error occurred. The parser was trying to write ''Administrator'' into this field.

You should check for other messages issued with this one for the full context of the error.

Error 4:
( Broker_QM.default ) Source field ''410064006d0069006e006900730074007200610074006f007200'' is too long for a target field of length '12' when converting from unicode to codepage '437'.

When the character data in the source field is converted to the target codepage, the resulting character string was longer than the defined length of the target field.

Correct the application or compute expression that generated the message. Ensure that the definition of the field in the output message is correctly specified bearing in mind the codepage required for the message and check that the origin of the data within the source field is providing correct data.

Info 1:
( Broker_QM.default ) Publish/Subscribe state recovery completed.

Recovery of the Publish/Subscribe state from the broker's database is complete.

This message is for information only. No action is required.

Info 2:
( Broker_QM.default ) Publish/Subscribe state recovery started due to transaction rollback.

A transaction which involved an update to the Publish/Subscribe state has been rolled back in the broker. In order to restore the Publish/Subscribe state to its prior value, it will be recovered from the broker's database. The available information is given above in other messages. Refer to earlier messages for the original cause of the transaction failure.

This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.

Info 3:
( Broker_QM.default ) Publish/Subscribe state recovery completed.

Recovery of the Publish/Subscribe state from the broker's database is complete.

This message is for information only. No action is required.

Info 4:
( Broker_QM.default ) Publish/Subscribe state recovery started due to transaction rollback.

A transaction which involved an update to the Publish/Subscribe state has been rolled back in the broker. In order to restore the Publish/Subscribe state to its prior value, it will be recovered from the broker's database. The available information is given above in other messages. Refer to earlier messages for the original cause of the transaction failure.

This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.


Error 5:
(Broker_QM.default ) 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.



When I put the message to the System.broker.control.queue each time, this error will be generated.. Thanks
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Jan 11, 2008 4:02 am    Post subject: Reply with quote

Grand High Poobah

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

Quote:
Error 4:
( Broker_QM.default ) Source field ''410064006d0069006e006900730074007200610074006f007200'' is too long for a target field of length '12' when converting from unicode to codepage '437'.
This is the max length for the accountid/userId...
You should create a different id in the mqm group and use that.
Administrator is too long and should not be used anyway....

Why did you not use brkadmin or its equivalent in your shop?

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
angka
PostPosted: Fri Jan 11, 2008 6:30 am    Post subject: Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

Rfhutil V5.05 can let u connect using a different User Id. i tried that but still get the same error. I tried login to Windows with another user id in mqm group but i still get the same error. I have not tried using brkadmin.
Is the way i set the message correct? or is there any other things that i need to configure with Message Broker Toolkit??

Btw my version of MQ is 6.0.2.1 and Message Broker is 6.0.0.1

Thanks
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Jan 11, 2008 7:22 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It looks like your flow is improperly handling the UserIdentifier field, and trying to populate it with a hex character representation of the characters, rather than the characters themselves.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
angka
PostPosted: Fri Jan 11, 2008 9:00 am    Post subject: Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

So any ideas where I got it wrong?

Thanks
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Jan 11, 2008 9:37 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Yes, likely you're treating a BLOB as CHARACTER, or vice versa.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
angka
PostPosted: Sat Jan 12, 2008 9:33 pm    Post subject: Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

You mean rfhutil setting? or u mean 'PubSubControlMsgFlow' Messge broker default flow? if so what to change? Thanks
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Subscribe to Topics using Rfhutil
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.