jstatd is not terminated even though it cannot contact or bind to RMI Registry

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • 9
    • Affects Version/s: 9
    • Component/s: core-svc
    • None
    • b64

        It seems like there is a bug in the sun.tools.jstatd.Jstatd.bind(). If Naming.rebind(name, remoteHost) results in java.rmi.ConnectException or java.rmi.RemoteException bind() reports the failure but jstatd keeps running. After such exceptions are thrown the jstad seems to be unusable.

        Such a behaviour leads to poor testability and a lot of loose jstatd processes are floating around.

              Assignee:
              Yekaterina Kantserova (Inactive)
              Reporter:
              Yekaterina Kantserova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: