-
Enhancement
-
Resolution: Done
-
Minor
-
None
iiop and iiop-ssl socket binding doesn't show the runtime attributes bound, bound-address, bound-port as set, making it difficult to map the open ports to the socket bindings when the server is launched with a port offset.
"address" => [ ("host" => "master"), ("server" => "server-three"), ("socket-binding-group" => "full-ha-sockets"), ("socket-binding" => "iiop") ], "outcome" => "success", "result" => { "bound" => false, "bound-address" => undefined, "bound-port" => undefined, "client-mappings" => undefined, "fixed-port" => false, "interface" => "unsecure", "multicast-address" => undefined, "multicast-port" => undefined, "name" => "iiop", "port" => 3528 } }, { "address" => [ ("host" => "master"), ("server" => "server-three"), ("socket-binding-group" => "full-ha-sockets"), ("socket-binding" => "iiop-ssl") ], "outcome" => "success", "result" => { "bound" => false, "bound-address" => undefined, "bound-port" => undefined, "client-mappings" => undefined, "fixed-port" => false, "interface" => "unsecure", "multicast-address" => undefined, "multicast-port" => undefined, "name" => "iiop-ssl", "port" => 3529 } },
- is cloned by
-
JBEAP-16145 [GSS](7.2.z) unsecure interfaces / iiop does not log when binding port
- Closed
- is related to
-
JBEAP-15739 [GSS](7.1.z) Management model does not show all bound ports
- New