Petals ESB Container

The component 'JMXService' uses a map of JMXClient instead of an object pool

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

Details

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

Description:

Hide

The TopologyPinger that is in charge of container state detection (STARTED or STOPPED) uses JMXService to get a JMX client to remote container.

When a remote container was restarted, the JMX client returned by JMXService can not be used because it was closed when stopping the remote container.
So the TopologyPinger should be able to invalidate the JMX client on such case. That's why it is interresting to replace the map of JMX client by a real object pool.

Show
The TopologyPinger that is in charge of container state detection (STARTED or STOPPED) uses JMXService to get a JMX client to remote container. When a remote container was restarted, the JMX client returned by JMXService can not be used because it was closed when stopping the remote container. So the TopologyPinger should be able to invalidate the JMX client on such case. That's why it is interresting to replace the map of JMX client by a real object pool.

Environment:

-

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

11s

1

Christophe DENEUX

Wed, 18 Mar 2015 - 12:38:34 +0100

Open

In Progress

7s

1

Christophe DENEUX

Wed, 18 Mar 2015 - 12:38:41 +0100

In Progress

Resolved

6h 43m

1

Christophe DENEUX

Wed, 18 Mar 2015 - 19:21:53 +0100

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Wed, 18 Mar 2015 - 12:38:23 +0100

Updated:

Wed, 18 Mar 2015 - 19:21:53 +0100

Resolved:

Wed, 18 Mar 2015 - 19:21:53 +0100