4 Replies Latest reply on Mar 24, 2008 12:29 PM by marklittle

    A gateway topic requires an ESB-aware queue?

    ldimaggio

      I'm guessing that this is a limitation and not a bug - but just to be sure...

      I'm setting up a listener for a topic - where the topic must be defined as a gateway as it is the recipient of NotifyTopics notificationAction.

      My question involves the corresponding ESB queue/topic for the gateway topic. I noticed that the jms_topic quickstart associates ESB aware queues with topics. Is this a requirement/limitation (that topics cannot be used with gateway topics)?

      When I tried to associate an ESB-aware topic with a gateway topic:

      <jms-bus busid="notifiedTopic">
      <jms-message-filter dest-type="TOPIC" dest-name="topic/helloworldtopic" />
      </jms-bus>

      <jms-bus busid="notifiedTopicESB">
      <jms-message-filter dest-type="TOPIC" dest-name="topic/ESBhelloworldtopic"/>
      </jms-bus>

      I saw this rather confusing server.log sequence:

      21:48:50,357 INFO [TopicService] Topic[/topic/helloworldtopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      --->21:48:50,381 INFO [TopicService] Topic[/topic/helloworldtopicESB] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      21:48:50,397 INFO [QueueService] Queue[/queue/quickstart_helloworld_topic_notifier_Request_gw] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      21:48:50,622 INFO [JDBCDataStore] Generated token 'authToken:1EBAA4E0-F7B2-11DC-A2A5-CED4F9378256' for user: 'jbossesb/JBoss ESB User'
      21:48:50,665 INFO [JDBCDataStore] Generated token 'authToken:1EC30950-F7B2-11DC-A2A5-DD1300164758' for user: 'jbossesb/JBoss ESB User'
      21:48:52,289 ERROR [ExceptionUtil] SessionEndpoint[r6-g0vvi3ef-1-txzug3ef-emljnh-j4b2gs4] createTopic [s6-h0vvi3ef-1-txzug3ef-emljnh-j4b2gs4]
      --->javax.jms.JMSException: There is no administratively defined topic with name:topic/helloworldtopicESB

      Note the lines marked with ---> It looks like the topi was created - but then not found?

      Maybe the JMSException is a separate bug? - It's certainly confusing!