mq
  1. mq
  2. MQ-344

client got misleading 'Invalid client ID' err msg when timed out in setting client id

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1 (RI-Bug-Fix)
    • Fix Version/s: 5.1 (RI-Bug-Fix)
    • Component/s: broker-core
    • Labels:
      None

      Description

      On processing set client ID request, when the client id lock request timeout, broker correctly logs the following exception message, however the TIMEOUT status is not propagated to client as expected, which causes client 'Invalid client ID' error message instead of 'C4330=Timed out in setting client id yy for connection xx'

      – in broker log:
      com.sun.messaging.jmq.jmsserver.util.BrokerException: [B4457]: Timed out in acquiring cluster lock for client id yy for connection guest@127.0.0.1:38459

        Activity

        Hide
        amyk added a comment -

        now fixed in 5.0.1

        Show
        amyk added a comment - now fixed in 5.0.1
        Hide
        amyk added a comment -

        This is internal bug 17378722

        test case (fault injection)
        tonga/jmsserver/bugs/bugMQ344

        Show
        amyk added a comment - This is internal bug 17378722 test case (fault injection) tonga/jmsserver/bugs/bugMQ344

          People

          • Assignee:
            amyk
            Reporter:
            amyk
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: