3 Replies Latest reply on Aug 6, 2004 2:36 PM by josefine

    Identifying a stuck subscriber

    richieb

      (this is a repost with corrected subject line)

      We have a problem with one of our client programs that subscribes to a topic (this is a temp subscription). The thread that processes the subscribed messages gets "stuck".

      Initial effect was that a lot of messages queued up on the topic (in one case we had over 200,000). Now we set a maxDepth on the topic, so that everyone gets an exception when the topic reaches the maxDepth. The topic queue remains full, although other publishers and subscribers still seem to work.

      I'd like to be able to identify the "stuck" subscriber and kill it's connection.

      I'm not sure where to look though. Would enabling "ClientMonitorInterceptor" help? I expect messages from each client at least once a minute.

      Any suggestions will be greatly appreciated...

      ...richie

        • 1. Re: Identifying a stuck subscriber

          Enable trace logging on the client, see what error you get.

          Regards,
          Adrian

          • 2. Re: Identifying a stuck subscriber
            richieb

             

            "adrian@jboss.org" wrote:
            Enable trace logging on the client, see what error you get.

            Regards,
            Adrian


            Unfortunately, this only seems to occur on production machines and I cannot enable trace there. :(

            What we did though, was to implement a simple timer inside the client. Then if we find that the client executes for too long, we kill the client. We also log data, so hopefully this will catch the problem and give us enough info to really solve it.

            ...richie

            • 3. Re: Identifying a stuck subscriber
              josefine

              Hi Richie,

              does you find a useful solution for your problem, besides the described one?

              It seems that we have the same problem and we are very intresting in getting further information, which would give us some suggestions for fixing the problem.

              we also thought about solving the problem at client-side. but this doesn't work steady at the moment.

              best regards.

              josefine