Topic configuration Required.

[Su...@sungard.com]

Please confirm about the topic configuration in qpid broker as it is required for broadcasting. It fails to reconnect the broker on restart when it is a topic while it is working fine in case of POP (queues).Currently; we are using the following configuration of queues and topics in virtualhosts.xml for our testing.


Queue Conf:

           <queue>

                    <name>response.GLAXV_GLAXVALBBDBGEN1.response_queue_1</name>

                    <test-queue>

                        <exchange>response</exchange>

                        <durable>true</durable>

                    </test-queue>

                </queue>

Topic Conf:

<exchange>

                    <type>topic</type>

                    <name>broadcast.GLAXV_GLAXVALBBDBGEN1.Workflow</name>

                  <durable>true</durable>

                </exchange>



Best Regards,
Sumit Tyagi * Specialist Product Development *  SunGard * Global Technolgy *  Westend Center One, Aundh, Pune, 411 007, India * Tel +91 20 4149 1000 x 2824 * Mobile +91 8007775938 *  www.sungard.com<http://www.sungard.com/>

Re: Topic configuration Required.

[Robbie Gemmell <ro...@gmail.com>]

Hi Sumit,

The below exchange declaration (which looks to be ok) could certainly
be used in performing pub-sub messaging, but it doesn't really help us
to identify what it is you are trying to do beyond that or how you are
going about it. Could you elaborate on what you mean by 'fails to
reconnect on broker restart when it is a topic'? Are you looking to
have Topic subscriptions which retain their messages across a broker
restart (i.e a DurableSubscriber in JMS terms) and finding that they
do not?

Posting the Topics / address strings that you are using and snippets
of what your client application is doing might be useful to give us a
better idea of what you are trying to achieve and how.

Regards,
Robbie

On 7 March 2012 10:12,  <Su...@sungard.com> wrote:
> Please confirm about the topic configuration in qpid broker as it is required for broadcasting. It fails to reconnect the broker on restart when it is a topic while it is working fine in case of POP (queues).Currently; we are using the following configuration of queues and topics in virtualhosts.xml for our testing.
>
>
> Queue Conf:
>
>           <queue>
>
>                    <name>response.GLAXV_GLAXVALBBDBGEN1.response_queue_1</name>
>
>                    <test-queue>
>
>                        <exchange>response</exchange>
>
>                        <durable>true</durable>
>
>                    </test-queue>
>
>                </queue>
>
> Topic Conf:
>
> <exchange>
>
>                    <type>topic</type>
>
>                    <name>broadcast.GLAXV_GLAXVALBBDBGEN1.Workflow</name>
>
>                  <durable>true</durable>
>
>                </exchange>
>
>
>
> Best Regards,
> Sumit Tyagi * Specialist Product Development *  SunGard * Global Technolgy *  Westend Center One, Aundh, Pune, 411 007, India * Tel +91 20 4149 1000 x 2824 * Mobile +91 8007775938 *  www.sungard.com<http://www.sungard.com/>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org