Invalid Registry Path Exception

book

Article ID: 199469

calendar_today

Updated On:

Products

CA Application Performance Management SaaS

Issue/Introduction

The Agent is throwing an exception "Invalid Registry Path Exception". What does that mean?

[ERROR] [IntroscopeAgent.InfrastructureAgent] 
com.wily.isengard.messageprimitives.service.ServiceNotFoundException: Invalid Registry Path Exception: /service/com.wily.introscope.spec.server.appmap.remotehttp.RemoteHttpCallService
 at com.wily.isengard.messageprimitives.service.MessageServiceFactory.internalGetServiceInterface(MessageServiceFactory.java:364)
 at com.wily.isengard.messageprimitives.service.MessageServiceFactory.internalGetServiceInterface(MessageServiceFactory.java:287)
 at com.wily.isengard.messageprimitives.service.MessageServiceFactory.getService(MessageServiceFactory.java:132)
 at com.wily.introscope.spec.server.appmap.remotehttp.RemoteHttpCallClient.getRemoteHttpCallService(RemoteHttpCallClient.java:71)
 at com.wily.introscope.spec.server.appmap.remotehttp.RemoteHttpCallClient.<init>(RemoteHttpCallClient.java:65)
 at com.wily.introscope.spec.server.appmap.remotehttp.RemoteHttpCallClient.<init>(RemoteHttpCallClient.java:53)
 at com.wily.introscope.spec.server.appmap.remotehttp.RemoteHttpCallClient.<init>(RemoteHttpCallClient.java:76)
 at com.wily.introscope.agent.environment.AgentInformationReporter.reportEnvironmentInformationInner(AgentInformationReporter.java:235)
 at com.wily.introscope.agent.environment.AgentInformationReporter.reportEnvironmentInformation(AgentInformationReporter.java:55)
 at com.wily.introscope.agent.environment.EnvironmentAdministrator$11.execute(EnvironmentAdministrator.java:671)
 at com.wily.util.heartbeat.WaitAndExecuteBehavior.ITimestampedRunnable_execute(WaitAndExecuteBehavior.java:31)
 at com.wily.util.heartbeat.IntervalHeartbeat$BehaviorNode.execute(IntervalHeartbeat.java:972)
 at com.wily.util.heartbeat.IntervalHeartbeat.executeNextBehaviorAndCalculateSleepTime(IntervalHeartbeat.java:491)
 at com.wily.util.heartbeat.IntervalHeartbeat.access$2(IntervalHeartbeat.java:445)
 at com.wily.util.heartbeat.IntervalHeartbeat$HeartbeatRunnable.run(IntervalHeartbeat.java:668)
 at java.lang.Thread.run(Thread.java:748)
Caused by: com.wily.isengard.util.tree.InvalidPathException
 at com.wily.isengard.util.tree.DirectoryTreeNode.getEntry(DirectoryTreeNode.java:176)
 at com.wily.isengard.util.tree.DirectoryTreeNode.getEntry(DirectoryTreeNode.java:179)
 at com.wily.isengard.registry.server.RegistryService.getEntry(RegistryService.java:254)
 at sun.reflect.GeneratedMethodAccessor118.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at com.wily.isengard.messageprimitives.MethodCallUtilities.callInterface(MethodCallUtilities.java:79)
 at com.wily.isengard.messageprimitives.MethodCallUtilities.callInterface(MethodCallUtilities.java:30)
 at com.wily.isengard.messageprimitives.service.MessageService.attemptMethodCall(MessageService.java:183)
 at com.wily.isengard.messageprimitives.service.MessageService.handleMethodCallMessage(MessageService.java:135)
 at com.wily.isengard.messageprimitives.service.MessageService.receiveMessage(MessageService.java:161)
 at com.wily.isengard.postoffice.Mailbox.handleMessage(Mailbox.java:252)
 at com.wily.isengard.postoffice.PostOffice.deliverInternal(PostOffice.java:532)
 at com.wily.isengard.postoffice.PostOffice.access$2(PostOffice.java:478)
 at com.wily.isengard.postoffice.PostOffice$DeliveryItem.run(PostOffice.java:882)
 at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
 ... 1 more

Environment

DX Application Performance Management any release.

Resolution

This ERROR message "com.wily.isengard.messageprimitives.service.ServiceNotFoundException: Invalid Registry Path Exception" often occurs upon the agent trying to communicate with a collector when the cluster was restarted or rebalanced. The exception was already handled by the collector and didn't seem to have an adverse impact so far. In the end, it is suggested as an enhancement to preempt such an exception for better run-time efficiency and implementation of best practice.
In some cases, this error happened just after the MOM balance the cluster, your Agent has moved from a collector to another, that is why you saw this message.