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 10.3 Plugin UI - Modification of the start command path while WLS is down is unsupported

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Trivial Trivial
  • Resolution: Deferred
  • Affects Version/s: 4.6.5
  • Fix Version/s: None
  • Component/s: UI / UX
  • Environment:
    (10.17.188.64): Linux version 2.6.18-274.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-50))
  • Case Links:
    none
  • HQ Fix Version:
    4.6.5
  • 3.0 Category:
    UI, Plugins
  • Regression:
    No

Description

Symptom:

Modifying the program attribute residing in the program attribute under the Serves/Weblogic Admin 10.3/Inventory/Control section while the monitored Weblogic server is down cause the following error (see screenshot attachment):

The configuration has not been set for this resource due to: Invalid configuration: Error contacting resource: java.net.ConnectionException: t3://localhost:7001: Destination unreachable

Expected Result:

Static file-system path is unrelated to server availability and should suppoprt modifications in such scenarios.

Activity

Hide
Guy Segev added a comment -

Error excerpt from agent.log

15-02-2012 14:55:35,040 UTC ERROR [Thread-5] [RuntimeAutodiscoverer@279] Unexpected error running autodiscoverer for plugin: Weblogic Admin 10.3: java.net.ConnectException: t3://127.0.01:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination
org.hyperic.hq.product.PluginException: java.net.ConnectException: t3://127.0.01:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination
at org.hyperic.hq.plugin.weblogic.jmx.WeblogicRuntimeDiscoverer.discoverAs(WeblogicRuntimeDiscoverer.java:146)
at org.hyperic.hq.plugin.weblogic.jmx.WeblogicRuntimeDiscoverer.discoverResources(WeblogicRuntimeDiscoverer.java:119)
at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan_internal(RuntimeAutodiscoverer.java:272)
at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan(RuntimeAutodiscoverer.java:205)
at org.hyperic.hq.autoinventory.ScanManager.mainRunLoop(ScanManager.java:165)
at org.hyperic.hq.autoinventory.ScanManager.access$000(ScanManager.java:41)
at org.hyperic.hq.autoinventory.ScanManager$1.run(ScanManager.java:107)
Caused by: java.lang.SecurityException: java.net.ConnectException: t3://127.0.01:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination
at org.hyperic.hq.plugin.weblogic.WeblogicAuth.getSubject(WeblogicAuth.java:148)
at org.hyperic.hq.plugin.weblogic.WeblogicAuth.runAs(WeblogicAuth.java:125)
at org.hyperic.hq.plugin.weblogic.jmx.WeblogicRuntimeDiscoverer.discoverAs(WeblogicRuntimeDiscoverer.java:143)
... 6 more
15-02-2012 14:55:35,040 UTC INFO [Thread-5] [RuntimeAutodiscoverer@266] Running runtime autodiscovery for HQ Agent
15-02-2012 14:55:35,046 UTC INFO [Thread-5] [RuntimeAutodiscoverer@275] HQ Agent discovery took 0
15-02-2012 14:55:35,046 UTC INFO [Thread-5] [RuntimeAutodiscoverer@266] Running runtime autodiscovery for ProcessServer
15-02-2012 14:55:35,052 UTC INFO [Thread-5] [RuntimeAutodiscoverer@275] ProcessServer discovery took 0
15-02-2012 14:55:44,663 UTC WARN [commandlistener-generic-0] [CommandListener@223] Error invoking method
org.hyperic.hq.agent.AgentRemoteException: Failed to unschedule metrics for entity 2:10006: No measurement schedule for: 2:10006
at org.hyperic.hq.measurement.agent.server.MeasurementCommandsService.unscheduleMeasurements(MeasurementCommandsService.java:433)
at org.hyperic.hq.measurement.agent.server.MeasurementCommandsServer.dispatchCommand(MeasurementCommandsServer.java:167)
at org.hyperic.hq.agent.server.CommandDispatcher.processRequest(CommandDispatcher.java:113)
at org.hyperic.hq.agent.server.CommandListener.handleConn(CommandListener.java:216)
at org.hyperic.hq.agent.server.CommandListener.access$100(CommandListener.java:57)
at org.hyperic.hq.agent.server.CommandListener$AgentDispatchTask.run(CommandListener.java:200)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
15-02-2012 14:55:53,484 UTC ERROR [commandlistener-generic-0] [MeasurementCommandsService@248] Error getting real time measurement: Error contacting resource: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination
15-02-2012 14:55:53,870 UTC ERROR [commandlistener-generic-0] [MeasurementCommandsService@248] Error getting real time measurement: Error contacting resource: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination
15-02-2012 14:55:54,365 UTC ERROR [commandlistener-generic-0] [MeasurementCommandsService@248] Error getting real time measurement: Error contacting resource: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination
15-02-2012 14:55:55,547 UTC ERROR [commandlistener-generic-0] [MeasurementCommandsService@248] Error getting real time measurement: Error contacting resource: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination

Show
Guy Segev added a comment - Error excerpt from agent.log
15-02-2012 14:55:35,040 UTC ERROR [Thread-5] [RuntimeAutodiscoverer@279] Unexpected error running autodiscoverer for plugin: Weblogic Admin 10.3: java.net.ConnectException: t3://127.0.01:7001: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination org.hyperic.hq.product.PluginException: java.net.ConnectException: t3://127.0.01:7001: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination at org.hyperic.hq.plugin.weblogic.jmx.WeblogicRuntimeDiscoverer.discoverAs(WeblogicRuntimeDiscoverer.java:146) at org.hyperic.hq.plugin.weblogic.jmx.WeblogicRuntimeDiscoverer.discoverResources(WeblogicRuntimeDiscoverer.java:119) at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan_internal(RuntimeAutodiscoverer.java:272) at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan(RuntimeAutodiscoverer.java:205) at org.hyperic.hq.autoinventory.ScanManager.mainRunLoop(ScanManager.java:165) at org.hyperic.hq.autoinventory.ScanManager.access$000(ScanManager.java:41) at org.hyperic.hq.autoinventory.ScanManager$1.run(ScanManager.java:107) Caused by: java.lang.SecurityException: java.net.ConnectException: t3://127.0.01:7001: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination at org.hyperic.hq.plugin.weblogic.WeblogicAuth.getSubject(WeblogicAuth.java:148) at org.hyperic.hq.plugin.weblogic.WeblogicAuth.runAs(WeblogicAuth.java:125) at org.hyperic.hq.plugin.weblogic.jmx.WeblogicRuntimeDiscoverer.discoverAs(WeblogicRuntimeDiscoverer.java:143) ... 6 more 15-02-2012 14:55:35,040 UTC INFO [Thread-5] [RuntimeAutodiscoverer@266] Running runtime autodiscovery for HQ Agent 15-02-2012 14:55:35,046 UTC INFO [Thread-5] [RuntimeAutodiscoverer@275] HQ Agent discovery took 0 15-02-2012 14:55:35,046 UTC INFO [Thread-5] [RuntimeAutodiscoverer@266] Running runtime autodiscovery for ProcessServer 15-02-2012 14:55:35,052 UTC INFO [Thread-5] [RuntimeAutodiscoverer@275] ProcessServer discovery took 0 15-02-2012 14:55:44,663 UTC WARN [commandlistener-generic-0] [CommandListener@223] Error invoking method org.hyperic.hq.agent.AgentRemoteException: Failed to unschedule metrics for entity 2:10006: No measurement schedule for: 2:10006 at org.hyperic.hq.measurement.agent.server.MeasurementCommandsService.unscheduleMeasurements(MeasurementCommandsService.java:433) at org.hyperic.hq.measurement.agent.server.MeasurementCommandsServer.dispatchCommand(MeasurementCommandsServer.java:167) at org.hyperic.hq.agent.server.CommandDispatcher.processRequest(CommandDispatcher.java:113) at org.hyperic.hq.agent.server.CommandListener.handleConn(CommandListener.java:216) at org.hyperic.hq.agent.server.CommandListener.access$100(CommandListener.java:57) at org.hyperic.hq.agent.server.CommandListener$AgentDispatchTask.run(CommandListener.java:200) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 15-02-2012 14:55:53,484 UTC ERROR [commandlistener-generic-0] [MeasurementCommandsService@248] Error getting real time measurement: Error contacting resource: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination 15-02-2012 14:55:53,870 UTC ERROR [commandlistener-generic-0] [MeasurementCommandsService@248] Error getting real time measurement: Error contacting resource: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination 15-02-2012 14:55:54,365 UTC ERROR [commandlistener-generic-0] [MeasurementCommandsService@248] Error getting real time measurement: Error contacting resource: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination 15-02-2012 14:55:55,547 UTC ERROR [commandlistener-generic-0] [MeasurementCommandsService@248] Error getting real time measurement: Error contacting resource: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination
Hide
German Laullon added a comment -

This is the expected behavior. The plugin has to check all options and if the server is down the connections options can't be checked and a error is reported.

This is not a Weblogic plugin "error", it happend with (mostly) all plugins.

Show
German Laullon added a comment - This is the expected behavior. The plugin has to check all options and if the server is down the connections options can't be checked and a error is reported. This is not a Weblogic plugin "error", it happend with (mostly) all plugins.
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    40 weeks, 5 days ago