Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

WebLogic plugin - Control Actions fail for WebLogic WebApp due to MBean instance not found error

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.3, 4.4, 4.5
  • Fix Version/s: 5.0
  • Component/s: Plugins
  • Environment:
    HQ-server 4.5.0-EE running on RHEL 5.4
    HQ-agent 4.5.0-EE running on RHEL 5.4
     - WebLogic 11gR1 running with HQ-agent
  • Importance:
    2-High
  • Case Links:
  • Regression:
    No
  • Story Points:
    3
  • Tags:

Description

WebLogic plugin - Control Actions fail for WebLogic WebApp due to MBean instance not found error.

When attempting to execute one of the following control actions on a WebLogic WebApp:

  • Deploy
  • Stop
  • Undeploy
  • Start

The operation fails and errors with the command status:
MBean instance not found: mydomain:Application=jfreechart-sample,Name=myserver_/jfreechart-sample,Type=WebAppComponent

Expected Result:
The Control Actions should function successfully.

Actual Result:
The listed control actions do not complete successfully and report Error.

Steps to Reproduce:
1. Log into HQ
2. Select the platform resource where WebLogic is installed and configured
3. Select the WebLogic Admin WebApp autogroup under Services
4. Select the WebApp from under Group Memeber
5. Select the Control tab
6. Select one of the listed control actions from above within the dropdown list
7. Click the Play (Execute) button
8. Note the Command Status fails with the Error: MBean instance is not found.

Work Around:
Execute control actions directly in the WebLogic Admin Console

Additional Information:
No additional details posted to server.log or agent.log.

Activity

Hide
Frederic Calindas added a comment -

This is not regression. Verified with HQ 4.4 and HQ 4.3 using same WLS server and able to reproduce reported error.

Show
Frederic Calindas added a comment - This is not regression. Verified with HQ 4.4 and HQ 4.3 using same WLS server and able to reproduce reported error.
Hide
Mayan Weiss added a comment -

resolving in order to reopen

Show
Mayan Weiss added a comment - resolving in order to reopen
Hide
German Laullon added a comment -

I reopen it by mistake.

Show
German Laullon added a comment - I reopen it by mistake.
Hide
Edward Gonzales added a comment -

German, the status for this one shows Reopened. will this be fixed in a future version to be bundled with Hyperic or will this be something for the Solution Exchange?

Show
Edward Gonzales added a comment - German, the status for this one shows Reopened. will this be fixed in a future version to be bundled with Hyperic or will this be something for the Solution Exchange?
Hide
Edward Gonzales added a comment -

German, does this one still need to be worked or was it reopened by mistake?

Show
Edward Gonzales added a comment - German, does this one still need to be worked or was it reopened by mistake?
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Yaron Borenstein added a comment -

Itaretion 5 bugs meeting 25/2/2013

Show
Yaron Borenstein added a comment - Itaretion 5 bugs meeting 25/2/2013
Hide
Edward Gonzales added a comment -

The last comment indicated it was targeted for Iteration 5. Would it be OK to provide the improved plugin internally (to Andrei and Nevenka) or to the customer for testing? We could pull it out of the current build.

Show
Edward Gonzales added a comment - The last comment indicated it was targeted for Iteration 5. Would it be OK to provide the improved plugin internally (to Andrei and Nevenka) or to the customer for testing? We could pull it out of the current build.
Hide
Yoav Epelman added a comment -

<Bugs division between team leaders>
We are not going to fix that in the near future.

Show
Yoav Epelman added a comment - <Bugs division between team leaders> We are not going to fix that in the near future.

People

Vote (1)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    33 weeks, 2 days ago