Description of problem:

CLI shows 0 for most session stats of distributable web apps:

    "outcome" => "success",
    "result" => {
        "active-sessions" => 1,
        "context-root" => "/distributablewebapp",
        "duplicated-session-ids" => 0,
        "expired-sessions" => 0,
        "max-active-sessions" => 0,
        "rejected-sessions" => 0,
        "session-avg-alive-time" => 0,
        "session-max-alive-time" => 0,
        "sessions-created" => 0,
        "virtual-host" => "default-host",
        "servlet" => undefined
    }


Version-Release number of selected component (if applicable):

EAP 6.4.3


How reproducible:

Very

Steps to Reproduce:
1. Deploy distributable web app in ha/clustered environment
2. Generate/expire sessions on the distributable web app
3. Check session stats

Actual results:

active-sessions is the only populated metric

Expected results:

other metrics are populated

Additional info:

The WebDeploymentDefinition is fetching those stats for CLI from JBossWeb ManagerBase methods. The clustered app DistributableSessionManager extends ManagerBase, but it used different fields and variables to track these stats instead of the ones provided by the ManagerBase it extended.  But it did not expose those new fields through the standard ManagerBase methods, and so the CLI just gets the original 0 returns for those ManagerBase values that are left unmodified by the clustered DistributableSessionManager.