admin
Immortal
Immortal

Error registering trigger in server.log

0 Kudos
2 Replies
laullon
VMware Employee
VMware Employee

Hello...

After I update server versión from 2.7.3 to 2.7.5, i obtain this
exception in server.log...
Some ideas?..

2006-11-20 08:49:49,907 INFO
[org.hyperic.hq.events.AlertConfigLoader$ConfigClassesInitializer ]
actions list:
2006-11-20 08:49:49,938 ERROR
[org.hyperic.hq.events.ext.RegisteredTriggers] Error registering
trigger
org.hyperic.hq.events.InvalidTriggerDataException
at org.hyperic.hq.bizapp.server.trigger.frequency.DurationTrigger.init
(DurationTrigger.java:150)
at org.hyperic.hq.events.ext.RegisteredTriggers.registerTrigger(RegisteredTriggers.java:238)
at org.hyperic.hq.events.ext.RegisteredTriggers.init(RegisteredTriggers.java:100)
at org.hyperic.hq.events.ext.RegisteredTriggers.getTriggerMap
(RegisteredTriggers.java:141)
at org.hyperic.hq.events.ext.RegisteredTriggers.getInterestedTriggers(RegisteredTriggers.java:189)
at org.hyperic.hq.bizapp.server.mdb.RegisteredDispatcherEJBImpl.dispatchEvent(RegisteredDispatcherEJBImpl.java
:75)
at org.hyperic.hq.bizapp.server.mdb.RegisteredDispatcherEJBImpl.onMessage(RegisteredDispatcherEJBImpl.java:111)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:475)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:149)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:106)
at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext
(AbstractTxInterceptorBMT.java:158)
at org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT.invoke(MessageDrivenTxInterceptorBMT.java:32)
at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java
:101)
at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:94)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke
(ProxyFactoryFinderInterceptor.java:122)
at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:389)
at org.jboss.ejb.Container.invoke(Container.java:873)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke
(JMSContainerInvoker.java:1077)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1379)
at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:256)
at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:904)
at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:160)
at org.jboss.mq.SpySession.run(SpySession.java :333)
at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Unknown Source)
Caused by: org.hyperic.util.NestedRuntimeException$NestedEx: timeRange
must be >= 1
at org.hyperic.util.config.ConfigOption.invalidOption(ConfigOption.java:60)
at org.hyperic.util.config.LongConfigOption.checkOptionIsValid
(LongConfigOption.java:54)
at org.hyperic.util.config.ConfigResponse.setValue(ConfigResponse.java:146)
at org.hyperic.util.config.ConfigResponse.decode(ConfigResponse.java:238)
at org.hyperic.hq.bizapp.server.trigger.frequency.DurationTrigger.init
(DurationTrigger.java:137)
... 32 more

--
-------------------------------------------------------
Germán Laullón

--
-------------------------------------------------------
Germán Laullón

0 Kudos
admin
Immortal
Immortal

There should not be any incompatibility with 2.7.3 and 2.7.5. Do you
have alerts defined in your environment that uses the setting "When
conditions are met for XXX minutes within a time period of XXX
minutes"? If so, you can clear this out by updating these alert
definitions (simply hitting OK should do the trick).

Charles




0 Kudos