Petals ESB Container

Uniformise the JMX RMI naming

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Task
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 5.0.0
Fix Version/s: 5.0.1
Component/s: JMX
Security Level: Public

Description:
Hide
The JMX API is exposed through RMI and for that it uses the RMI Registry to register a stub to be found by clients i.e., petals-ant and petals-cli).
This means there is a shared knowledge between the container and the clients which is:

the ip/port of the RMI Registry

the name of the RMI Registry entry for the stub.

The first point is knowledge used by admins, but the second one is hardcoded in the java code.
It would be better to make that runtime dependency explicit in the code.
Show
The JMX API is exposed through RMI and for that it uses the RMI Registry to register a stub to be found by clients i.e., petals-ant and petals-cli). This means there is a shared knowledge between the container and the clients which is:

the ip/port of the RMI Registry

the name of the RMI Registry entry for the stub.

The first point is knowledge used by admins, but the second one is hardcoded in the java code. It would be better to make that runtime dependency explicit in the code.

Environment:

-

Issue Links

Depends

This issue blocks:
~~PETALSANT-12~~ Uniformise the JMX RMI naming
~~PETALSESBCLI-129~~ Uniformise the JMX RMI naming

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

17s

1

Victor NOËL

Wed, 2 Dec 2015 - 09:45:49 +0100

Open

In Progress

5s

1

Victor NOËL

Wed, 2 Dec 2015 - 09:45:54 +0100

In Progress

Resolved

1m 1s

1

Victor NOËL

Wed, 2 Dec 2015 - 09:46:55 +0100

People

Assignee:

Victor NOËL

Reporter:

Victor NOËL
Watchers:

0

Dates

Created:

Wed, 2 Dec 2015 - 09:45:32 +0100

Updated:

Wed, 2 Dec 2015 - 09:51:58 +0100

Resolved:

Wed, 2 Dec 2015 - 09:46:55 +0100