glassfish
  1. glassfish
  2. GLASSFISH-11365

Type name for 'Threshold Limit Behavior' need be i18ned

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: V3
    • Fix Version/s: V3
    • Component/s: admin_gui
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Macintosh

    • Issuezilla Id:
      11,365

      Description

      Tried v3 with multilingual language support. Click 'Config'->'JMS' ->'Physical
      destination'. Type name for 'Threshold Limit Behavior' show in english for Chinese:

      Reject newest messages
      Slow down producers
      Throw out oldest
      Throw out lowest-priority messages

        Activity

        Hide
        Anissa Lam added a comment -

        Looking at the code, i believe this is fixed in the 3.0 FCS release.

        jmsPhysDestinations.LimitBehavior=Threshold Limit Behavior:
        jmsPhysDestinations.LimitBehaviorHelp=Broker behavior when memory-limit
        threshold reached. If the value is "Throw out oldest" or "Throw out
        lowest-priority messages" and Use Dead Message Queue is set to true, excess
        messages are moved to the dead message queue.
        <sun:property labelAlign="left" noWrap="#

        {true}

        " overlapLabel="#

        {false}

        "
        label="$resource

        {i18njms.jmsPhysDestinations.LimitBehavior}

        "
        helpText="$resource

        {i18njms.jmsPhysDestinations.LimitBehaviorHelp}

        " >
        <sun:dropDown id="Type" values=

        {"REJECT_NEWEST", "FLOW_CONTROL","REMOVE_OLDEST","REMOVE_LOW_PRIORITY"}

        labels=

        {"Reject newest messages", "Slow down producers", "Throw out oldest", "Throw out lowest-priority messages"}

        selected="#

        {pageSession.valueMap['LimitBehavior']}

        "/>
        </sun:property>

        I am marking fixed. If you still see the problem, it maybe an i18n issue.

        Show
        Anissa Lam added a comment - Looking at the code, i believe this is fixed in the 3.0 FCS release. jmsPhysDestinations.LimitBehavior=Threshold Limit Behavior: jmsPhysDestinations.LimitBehaviorHelp=Broker behavior when memory-limit threshold reached. If the value is "Throw out oldest" or "Throw out lowest-priority messages" and Use Dead Message Queue is set to true, excess messages are moved to the dead message queue. <sun:property labelAlign="left" noWrap="# {true} " overlapLabel="# {false} " label="$resource {i18njms.jmsPhysDestinations.LimitBehavior} " helpText="$resource {i18njms.jmsPhysDestinations.LimitBehaviorHelp} " > <sun:dropDown id="Type" values= {"REJECT_NEWEST", "FLOW_CONTROL","REMOVE_OLDEST","REMOVE_LOW_PRIORITY"} labels= {"Reject newest messages", "Slow down producers", "Throw out oldest", "Throw out lowest-priority messages"} selected="# {pageSession.valueMap['LimitBehavior']} "/> </sun:property> I am marking fixed. If you still see the problem, it maybe an i18n issue.

          People

          • Assignee:
            Anissa Lam
            Reporter:
            leonfan
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: