The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
UCMDB and UD Practitioners Forum (Previously CMS)
cancel
Showing results for 
Search instead for 
Did you mean: 

CMS 10.01 AM Push integration test connection failed

Highlighted
yalcari
Super Collector

CMS 10.01 AM Push integration test connection failed

Hi Experts,

I am trying to integrate with UCMDB 10.01 and AM using asset manger push adapter. 

test connection is getting failes.

can any one suggest me the solution please.

below is the error.

 

com.hp.ucmdb.discovery.probe.request.ProbeSideProcessorException: [ErrorCode [802] General
Integration Error{AM with push Adapter}]
Failed to create start the Generic Push Adapter Connector
[com.hp.ucmdb.adapters.ampush.AMPushAdapter]. Verify that the class name is correct and that the
jar is included in the adapter package

--- Start of probe-side exception
---
com.mercury.topaz.cmdb.shared.fcmdb.dataAccess.exception.AdapterAccessGeneralException: [ErrorCode
[802] General Integration Error{AM with push Adapter}]
Failed to create start the Generic Push
Adapter Connector [com.hp.ucmdb.adapters.ampush.AMPushAdapter]. Verify that the class name is
correct and that the jar is included in the adapter package
at
com.hp.ucmdb.dataAccess.exceptions.ExceptionConverter.createAdapterAccessGeneralException(ExceptionConverter.java:331)
at
com.hp.ucmdb.dataAccess.exceptions.ExceptionConverter.createAdapterAccessException(ExceptionConverter.java:150)
at
com.hp.ucmdb.dataAccess.exceptions.ExceptionConverter.createAdapterAccessException(ExceptionConverter.java:65)
at
com.hp.ucmdb.discovery.probe.processor.FederationNoneLifeCycleProbeProcessor.process(FederationNoneLifeCycleProbeProcessor.java:74)
at
com.hp.ucmdb.discovery.probe.processor.FederationNoneLifeCycleProbeProcessor.process(FederationNoneLifeCycleProbeProcessor.java:27)
at
com.hp.ucmdb.discovery.probe.agents.probemgr.adhoctasks.AdHocProbeRequestOperation.performAction(AdHocProbeRequestOperation.java:59)
at
com.hp.ucmdb.discovery.probe.agents.probemgr.taskdispatcher.AdHocTaskDispatcher.dispatchTask(AdHocTaskDispatcher.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111)
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:250)
at javax.management.StandardMBean.invoke(StandardMBean.java:405)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791)
at
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:305)
at
org.springframework.jmx.access.MBeanClientInterceptor.doInvoke(MBeanClientInterceptor.java:405)
at
org.springframework.jmx.access.MBeanClientInterceptor.invoke(MBeanClientInterceptor.java:353)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at $Proxy51.dispatchTask(Unknown Source)
at
com.hp.ucmdb.discovery.probe.agents.probegw.managementtasks.adhoctasks.AdhocThread.run(AdhocThread.java:54)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.hp.ucmdb.federationspi.exception.DataAccessGeneralException: Failed to create start
the Generic Push Adapter Connector [com.hp.ucmdb.adapters.ampush.AMPushAdapter]. Verify that the
class name is correct and that the jar is included in the adapter package
at
com.hp.ucmdb.adapters.push.AbstractInstancePushAdapter.testConnection(AbstractInstancePushAdapter.java:38)
at com.hp.ucmdb.adapters.push.PushAdapter.testConnection(PushAdapter.java:528)
at
com.hp.ucmdb.discovery.probe.processor.TestConnectionProbeRequestProcessor.processFederationNoneLifeCycle(TestConnectionProbeRequestProcessor.java:18)
at
com.hp.ucmdb.discovery.probe.processor.TestConnectionProbeRequestProcessor.processFederationNoneLifeCycle(TestConnectionProbeRequestProcessor.java:12)
at
com.hp.ucmdb.discovery.probe.processor.FederationNoneLifeCycleProbeProcessor.process(FederationNoneLifeCycleProbeProcessor.java:63)
... 25 more
Caused by: java.lang.ClassNotFoundException: com.hp.ucmdb.adapters.ampush.AMPushAdapter
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at
com.hp.ucmdb.dataAccess.manager.ChildFirstClassLoader.loadClass(ChildFirstClassLoader.java:57)
at
com.hp.ucmdb.dataAccess.manager.ChildFirstClassLoader.loadClass(ChildFirstClassLoader.java:26)
at
com.hp.ucmdb.dataAccess.manager.ChildFirstClassLoader.loadClass(ChildFirstClassLoader.java:57)
at
com.hp.ucmdb.dataAccess.manager.ChildFirstClassLoader.loadClass(ChildFirstClassLoader.java:26)
at
com.hp.ucmdb.adapters.push.AbstractInstancePushAdapter.ConstructPushConnector(AbstractInstancePushAdapter.java:68)
at
com.hp.ucmdb.adapters.push.AbstractInstancePushAdapter.testConnection(AbstractInstancePushAdapter.java:35)
... 29 more
--- End of probe-side exception ---

 

 

 

 

 

 

Regards,

Prasad

1 REPLY
Dima Gomel
HPE Expert

Re: CMS 10.01 AM Push integration test connection failed

Looking at the error you got: "Verify that the class name is correct and that the jar is included in the adapter package". I'd ask you to check that you are using correct adapter and/or that adapter was deployed successfully. 

Regards
-Dmitry Gomel, PMP
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Click the Like button at the bottom to say 'Thanks'.
//Add this to "OnDomLoad" event