Petals ESB Container

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

Details

  • Type: Task Task
  • Status: Resolved Resolved
  • Priority: Major 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

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Wed, 18 Mar 2015 - 12:38:34 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Christophe DENEUX made changes - Wed, 18 Mar 2015 - 12:38:41 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Wed, 18 Mar 2015 - 19:21:53 +0100

Reworked in trunk.

The JMX connection is checked using operation PetalsAdminMBean.ping() on borrowing a JMX Client from the pool. SO a JMX connection previously established on a restarted container is not returned.

Show
Christophe DENEUX added a comment - Wed, 18 Mar 2015 - 19:21:53 +0100 Reworked in trunk. The JMX connection is checked using operation PetalsAdminMBean.ping() on borrowing a JMX Client from the pool. SO a JMX connection previously established on a restarted container is not returned.
Christophe DENEUX made changes - Wed, 18 Mar 2015 - 19:21:53 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.0.0 [ 10413 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
11s
1
Christophe DENEUX
Wed, 18 Mar 2015 - 12:38:34 +0100
Open Open In Progress In Progress
7s
1
Christophe DENEUX
Wed, 18 Mar 2015 - 12:38:41 +0100
In Progress In Progress Resolved Resolved
6h 43m
1
Christophe DENEUX
Wed, 18 Mar 2015 - 19:21:53 +0100



People

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
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.