Optimize For Infra - Communication issue

Hi Experts,

I am new to UM and wM version 9.8.
Managed to get the environment up and running on windows and strugling with linux :frowning:

My setup worked fine; have successfully setup Optimize and added components to monitor and it all works fine.
As test case i tried bouncing IS and the reading in Analysis Overview reflected fine. Changed to RED and then back to GREEN once the environment is back up.

Issue i am facing is with the updates on Analysis Overview. It stopped reflecting the updates.
When i tried to shutdown IS it reflected offline with RED color and when i start the IS back the change never reflected. It stayed RED all the time indicating Offline.
In logs SoftwareAG\optimize\analysis\logs\server.log i see the below errors.

Tested connection in IS (JNDI) all okay. UM is up and running fine. Checked the SERVER status as well AE is fine.
Tried restarting the environment in the below order

  1. UM - No luck
  2. AE - No Luck
  3. MWS- No Luck
  4. IS - It started working fine and i see the Object status GREEN.

May i know what caused the issue and why was it resolved with the restart if IS. I waited 15 min for each activity and observed the behaviour and proceeded wiht the other.

Also wanted to know how to update the pooling interval of Optimize for Infrastructure. Its 1 min by default.

OPTIMIZE) [Analytic Engine v9.8.0.0.JmsMessageConsumer.jndiCreateMessageConsumerError] 2016-06-10 02:47:14.324 AST ERROR: Error creating consumer to destination: queue/rule_dim_disabled
(OPTIMIZE) [Analytic Engine v9.8.0.0.JmsMessageConsumer.jndiCreateMessageConsumerError] 2016-06-10 02:47:14.545 AST ERROR: Error creating consumer to destination: queue/kpi_aggregate_diagnosis
(OPTIMIZE) [CommonLib.MWS.002] 2016-06-12 10:24:52.505 AST WARN: com.webmethods.portal.portlet.wm_xt_portalrules.mechanics.PortalRulesMechanics
(OPTIMIZE) [CommonLib.MWS.002] 2016-06-12 10:24:52.505 AST WARN: Unable to initialize Component: wm_xt_portalrules Null class returned
[com.softwareag.eda.nerv.jms.util.JmsProviderUtil] 2016-06-12 10:25:19,870 WARN : JMS provider URL is set to “nsp://localhost:9000” and the hostname denotes a loopback address. Remote clients will not be able to establish a connection to the JMS server.
[com.softwareag.eda.nerv.error.handling.ErrorHandlerConfiguration] 2016-06-12 10:25:19,948 WARN : Guaranteed delivery of NERV is enabled. Therefore, specified value for property ‘com.softwareag.eda.nerv.maximum.redelivery.attempts’ will be ignored. Instead, ‘-1’ will be set as redeliveries count, thus configuring infinite re-delivery attempts.
[com.webmethods.jms.db.DbJMSClient] 2016-06-12 10:25:49,616 WARN : Deleting inactive subscription: 182
[com.webmethods.jms.db.DbJMSClient] 2016-06-12 10:25:49,618 WARN : Deleting inactive subscription: 183
[com.webmethods.jms.db.DbJMSClient] 2016-06-12 10:25:49,618 WARN : Deleting inactive subscription: 181
(OPTIMIZE) [CommonLib.MWS.002] 2016-06-12 10:32:10.800 AST WARN: Unable to load logger from: com.webmethods.sc.mws.CDSJournalLogger
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:27:57.597 AST ERROR: JNDI Context cannot be initialized with {java.naming.provider.url=nsp://localhost:9000, java.naming.factory.initial=com.pcbsys.nirvana.nSpace.NirvanaContextFactory, jms.provider.url=nsp://localhost:9000, connection_factory.name=jms/optimize/connection_factory}
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:27:57.597 AST ERROR: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsp://localhost:9000
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:27:57.597 AST ERROR: at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:140)
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:27:57.597 AST ERROR: wraps: com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:com.pcbsys.foundation.base.fException: Retry count=2 exceeded attempting to connect to host - [nsp://localhost:9000/]
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:27:57.597 AST ERROR: at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:140)
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:27:57.597 AST ERROR: wraps: com.pcbsys.foundation.base.fException: Retry count=2 exceeded attempting to connect to host - [nsp://localhost:9000/]
at com.pcbsys.foundation.drivers.fDriverFactory.connect(fDriverFactory.java:371)
at com.pcbsys.foundation.drivers.fDriverFactory.connect(fDriverFactory.java:359)
at com.pcbsys.foundation.io.fDefaultConnectionFactory.establishConnection(fDefaultConnectionFactory.java:86)
at com.pcbsys.foundation.io.fConnection.createConnection(fConnection.java:751)
at com.pcbsys.nirvana.client.nSession.establishConnection(nSession.java:7492)
at com.pcbsys.nirvana.client.nSession.establishFirstConnection(nSession.java:7507)
at com.pcbsys.nirvana.client.nSession.actualInit(nSession.java:6246)
at com.pcbsys.nirvana.client.nSession.init(nSession.java:6175)
at com.pcbsys.nirvana.client.nSession.init(nSession.java:6127)
at com.pcbsys.nirvana.client.nSession.init(nSession.java:6111)
at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:123)
at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:70)
at com.pcbsys.nirvana.nSpace.NirvanaContextFactory.getContext(NirvanaContextFactory.java:53)
at com.pcbsys.nirvana.nSpace.NirvanaContextFactory.getInitialContext(NirvanaContextFactory.java:35)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.(InitialContext.java:216)
at com.webmethods.optimize.jndiUtil.JMSJNDIUtil.(JMSJNDIUtil.java:56)
at com.webmethods.optimize.jndiUtil.JMSJNDIUtil.(JMSJNDIUtil.java:33)
at com.webmethods.optimize.stack.Stack.startJmsContext(Stack.java:171)
at com.webmethods.optimize.stack.Stack.initializeJMS(Stack.java:132)
at com.webmethods.optimize.stack.Stack.startSingletons(Stack.java:96)
at com.webmethods.optimize.service.external.util.HttpWSServer.startEngineServices(HttpWSServer.java:146)
at com.webmethods.optimize.service.external.util.HttpWSServer.start(HttpWSServer.java:129)
at com.webmethods.optimize.stack.Stack.(Stack.java:68)
at com.webmethods.optimize.stack.Stack.main(Stack.java:393)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:264)
at java.lang.Thread.run(Thread.java:745)
(OPTIMIZE) [Analytic Engine v9.8.0.0.Stack.UnknownKey] 2016-06-14 11:27:57.681 AST ERROR: Error initialing JMS server! Retrying every 30 seconds until a valid connection is obtained.
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:28:33.553 AST ERROR: JNDI Context cannot be initialized with {java.naming.provider.url=nsp://localhost:9000, java.naming.factory.initial=com.pcbsys.nirvana.nSpace.NirvanaContextFactory, jms.provider.url=nsp://localhost:9000, connection_factory.name=jms/optimize/connection_factory}
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:28:33.553 AST ERROR: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsp://localhost:9000
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:28:33.553 AST ERROR: at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:140)
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:28:33.553 AST ERROR: wraps: com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:com.pcbsys.foundation.base.fException: Retry count=2 exceeded attempting to connect to host - [nsp://localhost:9000/]
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:28:33.553 AST ERROR: at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:140)
(OPTIMIZE) [Analytic Engine v9.8.0.0.JNDIUtil.jndiUtilInitError] 2016-06-14 11:28:33.553 AST ERROR: wraps: com.pcbsys.foundation.base.fException: Retry count=2 exceeded attempting to connect to host - [nsp://localhost:9000/]
at com.pcbsys.foundation.drivers.fDriverFactory.connect(fDriverFactory.java:371)
at com.pcbsys.foundation.drivers.fDriverFactory.connect(fDriverFactory.java:359)
at com.pcbsys.foundation.io.fDefaultConnectionFactory.establishConnection(fDefaultConnectionFactory.java:86)
at com.pcbsys.foundation.io.fConnection.createConnection(fConnection.java:751)
at com.pcbsys.nirvana.client.nSession.establishConnection(nSession.java:7492)
at com.pcbsys.nirvana.client.nSession.establishFirstConnection(nSession.java:7507)
at com.pcbsys.nirvana.client.nSession.actualInit(nSession.java:6246)
at com.pcbsys.nirvana.client.nSession.init(nSession.java:6175)
at com.pcbsys.nirvana.client.nSession.init(nSession.java:6127)
at com.pcbsys.nirvana.client.nSession.init(nSession.java:6111)
at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:123)
at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:70)
at com.pcbsys.nirvana.nSpace.NirvanaContextFactory.getContext(NirvanaContextFactory.java:53)
at com.pcbsys.nirvana.nSpace.NirvanaContextFactory.getInitialContext(NirvanaContextFactory.java:35)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.(InitialContext.java:216)
at com.webmethods.optimize.jndiUtil.JMSJNDIUtil.(JMSJNDIUtil.java:56)
at com.webmethods.optimize.jndiUtil.JMSJNDIUtil.(JMSJNDIUtil.java:33)
at com.webmethods.optimize.stack.Stack.startJmsContext(Stack.java:171)
at com.webmethods.optimize.stack.Stack.initializeJMS(Stack.java:132)
at com.webmethods.optimize.stack.Stack.startSingletons(Stack.java:96)
at com.webmethods.optimize.service.external.util.HttpWSServer.startEngineServices(HttpWSServer.java:146)
at com.webmethods.optimize.service.external.util.HttpWSServer.start(HttpWSServer.java:129)
at com.webmethods.optimize.stack.Stack.(Stack.java:68)
at com.webmethods.optimize.stack.Stack.main(Stack.java:393)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:264)
at java.lang.Thread.run(Thread.java:745)
(OPTIMIZE) [CommonLib.MWS.002] 2016-06-14 11:29:52.775 AST WARN: com.webmethods.portal.portlet.wm_xt_portalrules.mechanics.PortalRulesMechanics
(OPTIMIZE) [CommonLib.MWS.002] 2016-06-14 11:29:52.775 AST WARN: Unable to initialize Component: wm_xt_portalrules Null class returned
[com.softwareag.eda.nerv.jms.util.JmsProviderUtil] 2016-06-14 11:30:14,103 WARN : JMS provider URL is set to “nsp://localhost:9000” and the hostname denotes a loopback address. Remote clients will not be able to establish a connection to the JMS server.
[com.softwareag.eda.nerv.error.handling.ErrorHandlerConfiguration] 2016-06-14 11:30:14,182 WARN : Guaranteed delivery of NERV is enabled. Therefore, specified value for property ‘com.softwareag.eda.nerv.maximum.redelivery.attempts’ will be ignored. Instead, ‘-1’ will be set as redeliveries count, thus configuring infinite re-delivery attempts.
[com.webmethods.jms.db.DbJMSClient] 2016-06-14 11:30:50,105 WARN : Deleting inactive subscription: 202
[com.webmethods.jms.db.DbJMSClient] 2016-06-14 11:30:50,106 WARN : Deleting inactive subscription: 203
[com.webmethods.jms.db.DbJMSClient] 2016-06-14 11:30:50,106 WARN : Deleting inactive subscription: 205
(OPTIMIZE) [CommonLib.MWS.002] 2016-06-14 11:37:08.664 AST WARN: Unable to load logger from: com.webmethods.sc.mws.CDSJournalLogger
[eventService] 2016-06-14 12:30:46,761 WARN : Remote IB delivery exception: BufferingQueue shutdown requested
com.webmethods.rtl.event.BufferingQueue$ShutdownException: BufferingQueue shutdown requested
at com.webmethods.rtl.event.BufferingQueue.get(BufferingQueue.java:186)
at com.webmethods.rtl.event.RemoteDeliverer$IbDeliverer.run(RemoteDeliverer.java:281)
(OPTIMIZE) [CommonLib.MWS.002] 2016-06-14 12:31:01.986 AST WARN: com.webmethods.portal.portlet.wm_xt_portalrules.mechanics.PortalRulesMechanics
(OPTIMIZE) [CommonLib.MWS.002] 2016-06-14 12:31:01.987 AST WARN: Unable to initialize Component: wm_xt_portalrules Null class returned
[com.softwareag.eda.nerv.jms.util.JmsProviderUtil] 2016-06-14 12:31:04,029 WARN : JMS provider URL is set to “nsp://localhost:9000” and the hostname denotes a loopback address. Remote clients will not be able to establish a connection to the JMS server.
[com.softwareag.eda.nerv.error.handling.ErrorHandlerConfiguration] 2016-06-14 12:31:04,061 WARN : Guaranteed delivery of NERV is enabled. Therefore, specified value for property ‘com.softwareag.eda.nerv.maximum.redelivery.attempts’ will be ignored. Instead, ‘-1’ will be set as redeliveries count, thus configuring infinite re-delivery attempts.
(OPTIMIZE) [CommonLib.MWS.002] 2016-06-14 13:20:19.161 AST WARN: Unable to load logger from: com.webmethods.sc.mws.CDSJournalLogger

Hi,

Try few things.

Disable WMIsExtDC package and re-enable in respected IS in the first place.

Per logs UM and AE connectivity issues pretty evident, if UM is not installed same machine then remap appropriate UM host name by creating appropriate hostname.

Try to re-deploy environment, see if still same behaviour

HTH

Hi Raj,

Thanks for the prompt response.

I have them all installed in same machine.

Before restarting IS i tried to re-enable WMARTExtDC and WMIsExtDc. 15 min is the time i waited for the outcome as nothing happened i restarted IS.

Which Rule you referring underneath, Analytics Overview > Integration Server > ??
Perhaps you could try disable/enable that particular rule.