Highlighted
Arunkumar1
Visitor.
1422 views

HP BSM Events not triggering

Jump to solution

Hi,

Events are not getting triggered from Sitescope also internally when triggered from Sendevent.bat, it's not coming.

 

Getting error connection failed while triggered through send event.bat.

Kindly let me know the logs to be checked and steps to be taken. 

I am getting errors in GW server hac-sm.log file as "Failed to start Component loader" .

Is there anything to be checked in Databse.

BSM version - 9.25

1 GW 1 DPS. Kindly update on this.

 

Thanks,

Arunkumar.K

Labels (2)
0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Re: HP BSM Events not triggering

Jump to solution

Hi Arunkumar.K,

thanks for the update.

My first guess would be that there is an issue with the BUS in general, so you might wanna check the BUS logs (<HPBSM>\log\bus) for obvious errors.

In case there are errors, the next steps would be
- delete Sonic cache
   stop BSM on all servers (GW first, then DPS)
   delete <HPBSM>\Sonic\Containers\Domain1.DomainManager\container.cache directory (only if Domain Manager runs on the machine)
   delete <HPBSM>\Sonic\runtime\MsgBroker\*cache* files
   start BSM on all servers (DPS first, then GW)

if this doesn't help
- delete and initialize the storage (potential data loss)
   stop BSM on all servers (GW first, then DPS)
   delete <HPBSM>\Sonic\Containers\Domain1.DomainManager\SonicMQStore directory (only if Domain Manager runs on the machine)
   delete <HPBSM>\Sonic\runtime\MsgBroker\SonicMQStore

   run <HPBSM>\Sonic\bin\InitializeDMStorage.bat (only if Domain Manager runs on the machine)
   run <HPBSM>\Sonic\bin\InitializeStorage.bat MsgBroker
   start BSM on all servers (DPS first, then GW)

if this doesn't help
- reinstall Sonic MQ following KCS document KM00344928

Greetings
Siggi

Customer Support
Micro Focus

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.

View solution in original post

9 Replies
Micro Focus Expert
Micro Focus Expert

Re: HP BSM Events not triggering

Jump to solution

check your <GW>\log\wde for specific errors. make sure WDE service (in the BSM status page) is running.

0 Likes
Arunkumar1
Visitor.

Re: HP BSM Events not triggering

Jump to solution

HI Asaf,

 

WDE is running in BSM status page. I am getting this error in wde.log file "ERROR - Failed to start WebDataEntry (service manager should retry)"

 

Thanks,

Arunkumar.K

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: HP BSM Events not triggering

Jump to solution

Hi Arunkumar.K,
please post some of the lines printed in the log after the message, it would most likely look like this:

<date/time> [Thread-21] (LoadControllerClientsExtension.java:202) INFO  - Failed to load WDE class com.mercury.am.platform.wde.main.WDEServiceProvider
org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [com.hp.bsm.platform.analytics.metadata.customermapping.MetadataSegmentMappingFactoryImpl] for bean with name 'analytics.metadata.segments.mapping.factory' defined in file [C:\HPBSM\conf\wde\spring\analytics-common-spring.xml]; nested exception is java.lang.ClassNotFoundException:

If however you see something like
..
<date/time> [localhost-startStop-1] (WDEServiceProvider.java:34) ERROR - Failed to start WebDataEntry (service manager should retry)
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'CIResolutionEnrichmentService' defined in file [C:\HPBSM\conf\wde\spring\cir-enrichment-service-spring.xml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: Could not initialize class com.mercury.topaz.sitescopetmc.ciresolver.wde.enrich.CIResolutionEnrichmentService
..

then the CI resolver fails to start (within wde, mercuryAS or opr-backend). By default, the CI Resolver is configured to write the CI information it needs into a cache. This cache is implemented in an H2 database with the DB files located at /Temp/CI_RESOLVER*.h2.db. There will be CI_RESOLVER_OMI_opr-backend.h2.db (on DPS), CI_RESOLVER_OMI_wde.h2.db and CI_RESOLVER_OMI_mercury_as.h2.db (on GW) for each of the processes implementing a CI Resolver. The *.trace.db files are the H2 logfiles. When disk space on the /Temp partition gets tight, then there is a chance that the .h2.db files become corrupt.

As CI Resolver's H2 DB is just a cache, it can be deleted without losing any data. The CI resolver will then rebuild the cache:
• Completely stop BSM on the affected machine
• Remove (or move/rename) the corresponding <HPBSM>/Temp/CI_RESOLVER*.h2.db file.
• Start BSM.
See KM02413776 - BSM 9.24 - Top View / Watchlist shows blue icons for SiteScope, no data

Greetings
Siggi

Customer Support
Micro Focus

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
Arunkumar1
Visitor.

Re: HP BSM Events not triggering

Jump to solution

Hi Siggi,

 

Thanks for the reply,

Below is the lines from wede.log file in GW server.

 

2017-02-02 22:13:59,154 [localhost-startStop-1] (WDEServiceProvider.java:26) INFO - Start WebDataEntry ServiceProvider
2017-02-02 22:13:59,155 [localhost-startStop-1] (Configurator.java:39) INFO - Configuration loaders : {ManagementDBConfLoader=com.mercury.am.platform.wde.configuration.ManagementDBConfigurationLoaderImpl@1c786c41, CustomerConfLoader=com.mercury.am.platform.wde.configuration.ConfigurationLoaderImpl@260b2e01}
2017-02-02 22:13:59,158 [localhost-startStop-1] (SampleValidatorManager.java:54) INFO - Loaded 1 validators from spring
2017-02-02 22:13:59,160 [localhost-startStop-1] (WDElateArriveSampleSHMonitor.java:52) INFO - WDE Late Arrivals monitor was created LATE_ARRIVE_TIME_IN_SEC: 3600; LATE_ARRIVE_THRESHOLD: 1
2017-02-02 22:13:59,161 [localhost-startStop-1] (WDEManagerImpl.java:114) INFO - Register Bus State Listener
2017-02-02 22:13:59,161 [localhost-startStop-1] (WDEManagerImpl.java:117) INFO - Starting setting adapter
2017-02-02 22:13:59,165 [localhost-startStop-1] (WDEManagerImpl.java:120) INFO - Starting configurator
2017-02-02 22:13:59,211 [localhost-startStop-1] (WDEManagerImpl.java:123) INFO - Starting configuration listener
2017-02-02 22:13:59,212 [localhost-startStop-1] (HttpResponseDelegator.java:61) INFO - Loaded 10 http responders from spring
2017-02-02 22:13:59,213 [localhost-startStop-1] (WDEManagerImpl.java:128) INFO - Starting data decoder delegator
2017-02-02 22:13:59,214 [localhost-startStop-1] (DataDecoderDelegator.java:89) INFO - Loaded 10 decoders from spring
2017-02-02 22:13:59,214 [localhost-startStop-1] (DataDecoderDelegator.java:58) INFO - Decoders mapping by url: {wde_bin_handler=com.mercury.am.platform.wde.decode.UDXDataDecoder, nonmdrv_client_handler=com.mercury.am.platform.wde.decode.UDXDataDecoder, report_transaction=com.mercury.am.platform.wde.decode.TransactionDataDecoder, test=com.mercury.am.platform.wde.decode.EmptyDecoder, md_sample=com.mercury.am.platform.wde.decode.MdSampleDataDecoder, report_traceroute=com.mercury.am.platform.wde.decode.TracerouteDataDecoder, report_soa=com.mercury.am.platform.wde.decode.SOADataDecoder, md_sample_array=com.mercury.am.platform.wde.decode.MdSampleDataDecoder, report_ss_samples=com.mercury.am.platform.wde.decode.SISDataDecoder, report_samples=com.mercury.am.platform.wde.decode.UDXDataDecoder}
2017-02-02 22:13:59,215 [localhost-startStop-1] (Enricher.java:36) INFO - Loaded 11 enrichments
2017-02-02 22:14:00,344 [localhost-startStop-1] (WDEServiceProvider.java:34) ERROR - Failed to start WebDataEntry (service manager should retry)
com.mercury.am.platform.dcchannel.DCChannelException: com.mercury.am.platform.dcchannel.DCChannelException: Failed to initialize
at com.mercury.am.platform.dcchannel.DEInternalChannelFactoryImpl.createDEInternalChannel(DEInternalChannelFactoryImpl.java:26)
at com.mercury.am.platform.wde.main.WDEManagerImpl.createDEInternalChannel(WDEManagerImpl.java:207)
at com.mercury.am.platform.wde.main.WDEManagerImpl.init(WDEManagerImpl.java:133)
at com.mercury.am.platform.wde.main.WDEServiceProvider.startServiceProvider(WDEServiceProvider.java:28)
at com.mercury.am.platform.sm.extensions.LoadControllerClientsExtension.loadProvider(LoadControllerClientsExtension.java:198)
at com.mercury.am.platform.sm.extensions.LoadControllerClientsExtension.loadProviders(LoadControllerClientsExtension.java:178)
at com.mercury.am.platform.sm.extensions.LoadControllerClientsExtension.load(LoadControllerClientsExtension.java:55)
at com.mercury.am.platform.sm.extensions.LoadControllerClientsExtension.execute(LoadControllerClientsExtension.java:36)
at com.mercury.am.platform.sm.SMServiceManager.runExtensions(SMServiceManager.java:47)
at com.mercury.am.platform.sm.SMServiceManager.start(SMServiceManager.java:55)
at com.mercury.am.platform.sm.jmx.SMServiceManagerJMX.start(SMServiceManagerJMX.java:23)
at com.mercury.am.platform.sm.SMProcessImpl.start(SMProcessImpl.java:118)
at com.mercury.am.platform.sm.SMProcessImpl.start(SMProcessImpl.java:47)
at com.mercury.am.platform.wde.servlet.WebDataEntryInitServlet.init(WebDataEntryInitServlet.java:28)
at javax.servlet.GenericServlet.init(GenericServlet.java:160)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1280)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1193)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1088)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5176)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5460)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:976)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1653)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.mercury.am.platform.dcchannel.DCChannelException: Failed to initialize
at com.mercury.am.platform.dcchannel.DEInternalChannelImpl.<init>(DEInternalChannelImpl.java:41)
at com.mercury.am.platform.dcchannel.DEInternalChannelFactoryImpl.createDEInternalChannel(DEInternalChannelFactoryImpl.java:24)
... 30 more
Caused by: com.mercury.infra.bus.JMSUtils.JmsUtilsException: couldn't create connection
at com.mercury.infra.bus.JMSUtils.ConnectionPoolBase.createConnection(ConnectionPoolBase.java:226)
at com.mercury.infra.bus.JMSUtils.ConnectionPoolBase.getConnection(ConnectionPoolBase.java:94)
at com.mercury.am.platform.dcchannel.DEInternalChannelImpl.<init>(DEInternalChannelImpl.java:39)
... 31 more
Caused by: com.sonicsw.mf.mgmtapi.runtime.ProxyRuntimeException
at com.sonicsw.mq.mgmtapi.runtime.impl.BrokerProxy.getConnections(BrokerProxy.java:741)
at com.mercury.infra.bus.JMSUtils.JmsUtils.dropConnection(JmsUtils.java:177)
at com.mercury.infra.bus.JMSUtils.JmsUtils.dropConnection(JmsUtils.java:165)
at com.mercury.infra.bus.JMSUtils.ConnectionPoolBase.createConnection(ConnectionPoolBase.java:198)
... 33 more
Caused by: javax.management.RuntimeMBeanException: java.lang.IllegalStateException: The broker must be online to invoke the requested operation
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:839)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:852)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:821)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.sonicsw.mf.framework.agent.ContainerImpl$ExternalRequestHandler.invoke(ContainerImpl.java:5062)
at com.sonicsw.mf.framework.agent.ContainerImpl$ExternalRequestHandler.invoke(ContainerImpl.java:4988)
at com.sonicsw.mf.framework.agent.ContainerImpl$ExternalRequestHandler.invoke(ContainerImpl.java:4982)
at com.sonicsw.mf.framework.agent.JMSConnectorServer$RequestHandlerDelegate.onMessage(JMSConnectorServer.java:753)
at com.sonicsw.mf.framework.agent.JMSConnectorServer$2.run(JMSConnectorServer.java:559)
at com.sonicsw.mf.framework.agent.TaskScheduler$ExecutionThread.run(TaskScheduler.java:512)
Caused by: java.lang.IllegalStateException: The broker must be online to invoke the requested operation
at com.sonicsw.mq.components.BrokerComponent.validateState(BrokerComponent.java:1849)
at com.sonicsw.mq.components.BrokerComponent.getConnections(BrokerComponent.java:1303)
at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.sonicsw.mf.framework.agent.AbstractMBean.internalInvoke(AbstractMBean.java:1370)
at com.sonicsw.mf.framework.agent.AbstractMBean.internalInvoke(AbstractMBean.java:1282)
at com.sonicsw.mf.framework.agent.ComponentMBean.internalInvoke(ComponentMBean.java:762)
at com.sonicsw.mf.framework.agent.AbstractMBean.invoke(AbstractMBean.java:956)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
... 10 more

 

So do I need to remove the CI_RESOLVER*.h2.db files in GW server? There aree 2 files as below

CI_RESOLVER_OMI_mercury_as_1_2.h2

CI_RESOLVER_OMI_wde_1_2.h2

Among these which needs to be removed. Kindly suggest on this.

 

Thanks,

Arunkumar.K

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: HP BSM Events not triggering

Jump to solution

Hi Arunkumar.K,

No!

You obviosuly have a totally different error, which is not related at all to the CI Resolver,
but to WDE being unable to establish a JMS connection

2017-02-02 22:14:00,344 [localhost-startStop-1] (WDEServiceProvider.java:34) ERROR - Failed to start WebDataEntry (service manager should retry)
com.mercury.am.platform.dcchannel.DCChannelException: com.mercury.am.platform.dcchannel.DCChannelException: Failed to initialize
at com.mercury.am.platform.dcchannel.DEInternalChannelFactoryImpl.createDEInternalChannel(DEInternalChannelFactoryImpl.java:26)
..
Caused by: com.mercury.am.platform.dcchannel.DCChannelException: Failed to initialize
..
Caused by: javax.management.RuntimeMBeanException: java.lang.IllegalStateException: The broker must be online to invoke the requested operation
..
Caused by: java.lang.IllegalStateException: The broker must be online to invoke the requested operation

Is the Message Broker up and running on the GW, is the DPS up and running?

Did anything happen prior to the issue?

Greetings
Siggi

Customer Support
Micro Focus

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
Arunkumar1
Visitor.

Re: HP BSM Events not triggering

Jump to solution

Hi SIggi,

Thanks for the reply.

All the services are UP and running in both GW and DPS.

There was a server reboot suddenly. After that events stopped coming.

Thanks,

Arunkumar.K

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: HP BSM Events not triggering

Jump to solution

Hi Arunkumar.K,

thanks for the update.

My first guess would be that there is an issue with the BUS in general, so you might wanna check the BUS logs (<HPBSM>\log\bus) for obvious errors.

In case there are errors, the next steps would be
- delete Sonic cache
   stop BSM on all servers (GW first, then DPS)
   delete <HPBSM>\Sonic\Containers\Domain1.DomainManager\container.cache directory (only if Domain Manager runs on the machine)
   delete <HPBSM>\Sonic\runtime\MsgBroker\*cache* files
   start BSM on all servers (DPS first, then GW)

if this doesn't help
- delete and initialize the storage (potential data loss)
   stop BSM on all servers (GW first, then DPS)
   delete <HPBSM>\Sonic\Containers\Domain1.DomainManager\SonicMQStore directory (only if Domain Manager runs on the machine)
   delete <HPBSM>\Sonic\runtime\MsgBroker\SonicMQStore

   run <HPBSM>\Sonic\bin\InitializeDMStorage.bat (only if Domain Manager runs on the machine)
   run <HPBSM>\Sonic\bin\InitializeStorage.bat MsgBroker
   start BSM on all servers (DPS first, then GW)

if this doesn't help
- reinstall Sonic MQ following KCS document KM00344928

Greetings
Siggi

Customer Support
Micro Focus

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.

View solution in original post

Arunkumar1
Visitor.

Re: HP BSM Events not triggering

Jump to solution

Hi SIggi,

 

Thanks for the reply.

Events started triggering after performing the below steps.

1.Stop BSM in both GW and DPS server

2.Delete the contents in the folder ""D:\HPBSM\Sonic\runtime\MsgBroker\SonicMQStore"" in both GW and DPS

3.In GW server change the line as below

 message.broker.status=configured to message.broker.status=nonconfigured in  D:\HPBSM\conf\bus\jms.configuration.status.properties

4.In DPS server change the line as below

message.broker.status=configured to message.broker.status=nonconfigured 

domain.manager.status=configured to domain.manager.status=nonconfigured

in D:\HPBSM\conf\bus\jms.configuration.status.properties

5.Now restart the services.

 

Thanks,

Arunkumar.K

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: HP BSM Events not triggering

Jump to solution

Hi Arunkumar.K,

thanks for your update and the good news., good to hear that all works now.

Greetings
Siggi

Customer Support
Micro Focus

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.