Petals ESB Container

Bad behavior of Petals mbean server

Details

  • Description:
    Hide

    During the bc mail uninstallation, one error may be appear and the stacktrace in Petals log provided (attachment file) was logged.

    I think problem was appear during uninstall processing task for bc mail, after Petals wasn't able to recover the bc mail entity and it was certaintly removed and not longer exists in the repository.

    Show
    During the bc mail uninstallation, one error may be appear and the stacktrace in Petals log provided (attachment file) was logged. I think problem was appear during uninstall processing task for bc mail, after Petals wasn't able to recover the bc mail entity and it was certaintly removed and not longer exists in the repository.
  • Environment:
    Petals ESB 3.2 SNAPSHOT

Attachments

  1. Text File
    petals-mbean-unregister.log
    (51 kB)
    Adrien Ruffie
    Mon, 18 Apr 2011 - 15:56:07 +0200

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Adrien Ruffie made changes - Mon, 18 Apr 2011 - 15:56:07 +0200
Field Original Value New Value
Priority Blocker [ 1 ]
Attachment petals-mbean-unregister.log [ 10562 ]
Hide
Permalink
Christophe DENEUX added a comment - Wed, 20 Apr 2011 - 09:05:55 +0200 - edited

We can see in the log file at 16:38:46,716 the loading of the petal-bc-mail installer whereas it was not previously unloaded.
Perhaps a concurrency problem about loading and unloading of the same component installer.

Show
Christophe DENEUX added a comment - Wed, 20 Apr 2011 - 09:05:55 +0200 - edited We can see in the log file at 16:38:46,716 the loading of the petal-bc-mail installer whereas it was not previously unloaded. Perhaps a concurrency problem about loading and unloading of the same component installer.
Hide
Permalink
Adrien Ruffie added a comment - Wed, 20 Apr 2011 - 09:08:55 +0200

Whats do you propose ? A check if the same component was correctly unloaded before try to (re) load ?

Show
Adrien Ruffie added a comment - Wed, 20 Apr 2011 - 09:08:55 +0200 Whats do you propose ? A check if the same component was correctly unloaded before try to (re) load ?
Hide
Permalink
Christophe DENEUX added a comment - Wed, 20 Apr 2011 - 10:08:56 +0200

Reading source code, we can see in InstallationServiceImpl that the same trace ("Installer of the component '" + componentName + "' loaded") is logged by both methods loadNewInstaller and loadInstaller. The trace should be different for each method.

Are you able to reproduce the problem ? Is it an unexpected result of integration tests ? What is it doing on the JMX client side ?

Show
Christophe DENEUX added a comment - Wed, 20 Apr 2011 - 10:08:56 +0200 Reading source code, we can see in InstallationServiceImpl that the same trace ("Installer of the component '" + componentName + "' loaded") is logged by both methods loadNewInstaller and loadInstaller. The trace should be different for each method. Are you able to reproduce the problem ? Is it an unexpected result of integration tests ? What is it doing on the JMX client side ?
Christophe DENEUX made changes - Wed, 20 Apr 2011 - 10:17:19 +0200
Link This issue depends on PETALSESBCONT-138 [ PETALSESBCONT-138 ]
Hide
Permalink
Christophe DENEUX added a comment - Wed, 20 Apr 2011 - 16:56:27 +0200 - edited

Moreover, it seems to me that the behaviour of loadInstaller and loadNewInstaller is not clear. We are able to invoke loadInstaller even is the component is already installed. We can invoke the loadInstaller more than one time.

Show
Christophe DENEUX added a comment - Wed, 20 Apr 2011 - 16:56:27 +0200 - edited Moreover, it seems to me that the behaviour of loadInstaller and loadNewInstaller is not clear. We are able to invoke loadInstaller even is the component is already installed. We can invoke the loadInstaller more than one time.
Hide
Permalink
Adrien Ruffie added a comment - Wed, 20 Apr 2011 - 17:05:50 +0200

I think (for me) the loadNewInstaller() is invoke the first time a component must be loaded, after that if the previous component is unloaded, I think you can be able to reload component installer by invoking loadInstaller().

Because installer the installer was already installed once

Show
Adrien Ruffie added a comment - Wed, 20 Apr 2011 - 17:05:50 +0200 I think (for me) the loadNewInstaller() is invoke the first time a component must be loaded, after that if the previous component is unloaded, I think you can be able to reload component installer by invoking loadInstaller(). Because installer the installer was already installed once



People

Dates

  • Created:
    Mon, 18 Apr 2011 - 15:55:42 +0200
    Updated:
    Mon, 2 May 2011 - 14:08:57 +0200
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.