IBM Support

JMSListener AutoReconnect properties misconception

Troubleshooting


Problem

There appears to be a common misconception regarding the application of the JMS DSA Listener properties for AutoReconnect

Symptom

AutoReconnect fails

Cause

Properties for the JMSListener in the file:

$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props

have been set as:

impact.[JMSListenerName].jms.autoreconnect=true
impact.[JMSListenerName].jms.autoreconnect.pollinterval=[TimeValue]

Resolving The Problem

Properties for the JMSListener in the file:

$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props

Where [ImpactServerName] is the name of the ImpactServer (for example: NCI) and [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and the properties should be set as:

impact.[JMSListenerName].autoreconnect=true
impact.[JMSListenerName].autoreconnect.pollinterval=[TimeValue]

Where [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and [TimeValue] is the desired polling interval value in milliseconds (for example: 30000 (equivalent to 30 seconds)). So, the properties are without the additional .jms bit.

[{"Product":{"code":"SSSHYH","label":"Tivoli Netcool\/Impact"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Netcool\/Impact","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"}],"Version":"6.1;6.1.1;7.1.0","Edition":""}]

Document Information

Modified date:
17 June 2018

UID

swg21567091