| Author |
Message
|
| ae06425 |
 Posted: Wed Jul 07, 2010 1:51 pm Post subject: jms topic connection factory |
 |
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
WAS version 6.x, MQ version 6.0.2.4
JMS publish/subscribe set up on MQ
broker service is running
jms topic connection factory and topics is configured on WAS 6.x
(all broker control, publication and jms subscription queues setup on WAS screen in respective fields...)
developer is able to send message and we can see in SYSTEM.BROKER.DEFAULT.STREAM (tested by trapping msg via get disabling this queue)
the messages do not show up in subscriber queue(s) and I checked all jms subscriber queues; curdepth(0).. I even get disabled subscriber queues for testing to trap message but no msg appeared...
We expected messages to end up in subcriber queue(s) as there is no consumers setup yet.
1-- so where the messages possibly being end up? is it being discarded, thrown away or something?
2--is there any way to trace the message: from SYSTEM.BROKER.DEFAULT.STREAM to destination?
3-- Looking for good websphere topic connection factory and topics setup documents, links etc.. for WAS 6.x
Thanks.... |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jul 07, 2010 2:26 pm Post subject: Re: jms topic connection factory |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ae06425 wrote: |
| We expected messages to end up in subcriber queue(s) as there is no consumers setup yet. |
So no consumers but you're sure the subscriptions are properly in place?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ae06425 |
| Posted: Wed Jul 07, 2010 2:35 pm Post subject: |
|
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
topic connection factories:
Broker control queue=SYSTEM.BROKER.CONTROL.QUEUE
Broker publication queue=SYSTEM.BROKER.DEFAULT.STREAM
Broker subscription queue=SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
Broker CC subscription queue=SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE
topics
Broker durable subscription queue=SYSTEM.JMS.D.SUBSCRIBER.QUEUE
Broker CC durable subscription queue=SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE
Enable multicast transport=AS CONNECTION FACTORY |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jul 07, 2010 8:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| ae06425 wrote: |
topic connection factories:
Broker control queue=SYSTEM.BROKER.CONTROL.QUEUE
Broker publication queue=SYSTEM.BROKER.DEFAULT.STREAM
Broker subscription queue=SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
Broker CC subscription queue=SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE
topics
Broker durable subscription queue=SYSTEM.JMS.D.SUBSCRIBER.QUEUE
Broker CC durable subscription queue=SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE
Enable multicast transport=AS CONNECTION FACTORY |
So this is an infrastructure definition. With this there is no topic defined and certainly no subscription defined.
A little trick: When you submit your subscription (durable or not) specify a request type message and a reply to Destination (qmgr + queue). The reply message to the subscription will let you know whether your subscription was successful or not.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| calanais |
| Posted: Wed Jul 07, 2010 11:59 pm Post subject: |
|
|
Apprentice
Joined: 12 Mar 2010
Posts: 32
|
Just having the subscriber queues defined is not the same as actually having a subscription in place.
If there are no subscriptions (durable or non-durable) defined then when a message is published the pub/sub engine will just discard the message if there is nobody actively 'listening'. Or at least having a durable subscription registered indicating an intent to 'listen' |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 08, 2010 4:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ae06425 wrote: |
topic connection factories:
Broker control queue=SYSTEM.BROKER.CONTROL.QUEUE
Broker publication queue=SYSTEM.BROKER.DEFAULT.STREAM
Broker subscription queue=SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
Broker CC subscription queue=SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE
topics
Broker durable subscription queue=SYSTEM.JMS.D.SUBSCRIBER.QUEUE
Broker CC durable subscription queue=SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE
Enable multicast transport=AS CONNECTION FACTORY |
So no subscriptions then? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ae06425 |
| Posted: Thu Jul 08, 2010 5:20 am Post subject: |
|
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
topics is defined on WAS 6.x
Resources
JMS
Topics
with
Name
JNDI Name
Base Topic Name
and other fields....
so, where do you set up subcription..? Pls shed more light on this..
I am MQ SA working with developer on this...
thnx |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 08, 2010 6:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ae06425 wrote: |
| so, where do you set up subcription..? Pls shed more light on this.. |
Either set up a durable subscription or better still have the developer you're working with produce a subscribing application. This would be the best solution as presumably that's what you're working towards.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ae06425 |
| Posted: Thu Jul 08, 2010 1:58 pm Post subject: |
|
|
Centurion
Joined: 02 Apr 2007
Posts: 100
|
We are successfully set up the mq broker pub/sub environment for application. Developer's subscribers working fine.
I had to authenticate subscriber and jms.admin and broker.control queues for application user_id.
Thanks eveyone.. |
|
| Back to top |
|
|
|
|
