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

HQ 4.5 server crash after running for 6 days

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.5
  • Fix Version/s: None
  • Component/s: Core Monitoring
  • Environment:
    Release 4.5.0-EE-46,Platform:Linux,DB:MYSQL
  • Case Links:
    none
  • Regression:
    Yes
  • Story Points:
    3
  • Tags:

Description

Steps to Reproduce

Run HQ 4.5 build 46
server was not used much

Actual Results:

Server crash after 6 days

Server log errors:

2010-07-20 12:22:12,211 WARN [VMTransport] [org.apache.activemq.broker.TransportConnection.Service@282] Async error occurred: java.lang.IllegalArgumentException: The subscription does not exist: ID:vmc-ssrc-rh73-42071-1279229049336-2:0:2:1
java.lang.IllegalArgumentException: The subscription does not exist: ID:vmc-ssrc-rh73-42071-1279229049336-2:0:2:1
at org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:363)
at org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:470)
at org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:194)
at org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:74)
at org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:74)
at org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:85)
at org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:449)
at org.apache.activemq.command.MessageAck.visit(MessageAck.java:205)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:297)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:175)
at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:109)
at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
at org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:205)
at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122)
at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43)
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:619)
**********************************************************************************************************************
2010-07-20 12:22:12,514 ERROR [Thread-19] [org.apache.catalina.loader.WebappClassLoader@2202] A web application created a ThreadLocal with key of type [null] (value [org.hyperic.hq.ui.servlet.NavMapImageServlet$1@122bc701]) and a value of type [java.lang.String] (value [resourceTree_1279305221617_1:10100_]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.

  1. server.log
    23/Jul/10 9:56 AM
    2 kB
    Nipuna Bhayani
  2. server.log.2010-07-15
    23/Jul/10 9:56 AM
    78 kB
    Nipuna Bhayani
  3. server.log.2010-07-16
    23/Jul/10 9:56 AM
    1.52 MB
    Nipuna Bhayani
  4. wrapper.log
    23/Jul/10 9:57 AM
    0.6 kB
    Nipuna Bhayani

Activity

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:
    41 weeks, 3 days ago