value. Address Settings Using address settings involves defining address-setting elements whose match corresponds with the destination names the clients will use along with the proper delimiter to enabled matching. For example, broker.xml could use the following: match="queue/#"> ANYCAST ANYCAST match="topic/#"> MULTICAST

0 码力 | 539 页 | 11.16 MB | 1 年前

3

value. Address Settings Using address settings involves defining address-setting elements whose match corresponds with the destination names the clients will use along with the proper delimiter to enabled matching. For example, broker.xml could use the following: match="queue/#"> ANYCAST ANYCAST match="topic/#"> MULTICAST

0 码力 | 539 页 | 11.14 MB | 1 年前

3

value. Address Settings Using address settings involves defining address-setting elements whose match corresponds with the destination names the clients will use along with the proper delimiter to enabled matching. For example, broker.xml could use the following: match="queue/#"> ANYCAST ANYCAST match="topic/#"> MULTICAST

0 码力 | 537 页 | 11.11 MB | 1 年前

3

value. Address Settings Using address settings involves defining address-setting elements whose match corresponds with the destination names the clients will use along with the proper delimiter to enabled matching. For example, broker.xml could use the following: match="queue/#"> ANYCAST ANYCAST match="topic/#"> MULTICAST

0 码力 | 537 页 | 11.11 MB | 1 年前

3

value. Address Settings Using address settings involves defining address-setting elements whose match corresponds with the destination names the clients will use along with the proper delimiter to enabled matching. For example, broker.xml could use the following: match="queue/#"> ANYCAST ANYCAST match="topic/#"> MULTICAST

0 码力 | 528 页 | 10.88 MB | 1 年前

3

value. Address Settings Using address settings involves defining address-setting elements whose match corresponds with the destination names the clients will use along with the proper delimiter to enabled matching. For example, broker.xml could use the following: match="queue/#"> ANYCAST ANYCAST match="topic/#"> MULTICAST

0 码力 | 525 页 | 10.75 MB | 1 年前

3

value. Address Settings Using address settings involves defining address-setting elements whose match corresponds with the destination names the clients will use along with the proper delimiter to enabled matching. For example, broker.xml could use the following: match="queue/#"> ANYCAST ANYCAST match="topic/#"> MULTICAST

0 码力 | 525 页 | 10.76 MB | 1 年前

3

value. Address Settings Using address settings involves defining address-setting elements whose match corresponds with the destination names the clients will use along with the proper delimiter to enabled matching. For example, broker.xml could use the following: match="queue/#"> ANYCAST ANYCAST match="topic/#"> MULTICAST

0 码力 | 524 页 | 10.73 MB | 1 年前

3

will now expect the CN or Subject Alternative Name values of the broker's SSL certificate to match the hostname in the client's URL. This impacts all core-based clients including core JMS clients address-setting for it whose match is anything but # . To solve this problem one can specify the temporary-queue-namespace in broker.xml and then create an address-setting whose match value corresponds temp match="temp.#"> false

will now expect the CN or Subject Alternative Name values of the broker's SSL certificate to match the hostname in the client's URL. This impacts all core-based clients including core JMS clients address-setting for it whose match is anything but # . To solve this problem one can specify the temporary-queue-namespace in broker.xml and then create an address-setting whose match value corresponds temp match="temp.#"> false