1 2 Previous Next 16 Replies Latest reply on Oct 27, 2008 10:36 AM by timfox Go to original post
      • 15. Re: JBoss Messaging - classcast exception
        prabhun
        prabhun Oct 27, 2008 10:31 AM (in response to prabhun)

        Hi,

        We took the JBossMessaging_1_4_0_SP3_CP04/ SP3-fix
        tag and tested. Now the class loader issue is resolved. And we replaced hypersonic with null persistance as recommended by Jboss.

        However we could not resolve the subscription id problem. We need this id to distinguish the different subscribers for the topic and also the message count (number of unread messages )always remains same for all the subscribers.Earlier the message count was always 0, now after testing with BossMessaging_1_4_0_SP3_CP04/ SP3-fix it shows some value, but the value is same for all the subscribers.
        Please let me know how to resolve the above issues?

        Regards,
        Prabhu

          • Actions
        • 16. Re: JBoss Messaging - classcast exception
          timfox
          timfox Oct 27, 2008 10:36 AM (in response to prabhun)

          What subscription id problem?

          As I mentioned before, subscription name and client id are only used for durable subscriptions, NOT non durable subscriptions.

          In JMS it is impossible to create a non durable subscription with a specific client id and name.

          See the JMS spec for more details.

            • Actions
          1 2 Previous Next