Unable To Deploy Cartridge Using The Cartridge Management Tool due to Error Could not connect to HTTP server on.
(Doc ID 1562326.1)
Last updated on APRIL 03, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.2.2 and laterInformation in this document applies to any platform.
Goal
During cartridge deployment using the Cartridge Management Tool the user receives the following error:
<13-Jun-2013 5:40:05,088 IST PM> <ERROR> <plugin.AutomationEventHandlerImpl> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <Failed to load automationPlugin[CreateServiceOrchestrationOrder.automatedtask.rog-osmcentralorchestration.CreateServiceOrchestrationOrder] from automationMap at uri[osmmodel:///XXX/1.0.0.0.0/resources/automation/automationMap.xml] due to [Could not connect to HTTP server on "XXXX".]>
javax.xml.transform.TransformerException: Could not connect to HTTP server on "XXXX".
at oracle.communications.ordermanagement.util.net.a.resolveAsFileObject(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.a(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.refresh(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl$1.refresh(Unknown Source)
at oracle.communications.ordermanagement.b.a.a.a(Unknown Source)
at com.mslv.oms.model.MetaDataManager$1.onMetaDataRefresh(Unknown Source)
at com.mslv.oms.model.MetaDataManager.refresh(Unknown Source)
at com.mslv.oms.security.HandlerFactory.refreshMetadata(Unknown Source)
at oracle.communications.ordermanagement.cluster.BusinessRequestBalancer.p(Unknown Source)
at com.mslv.oms.priviledgeoperations.PriviledgedOperationsEJB.refreshMetaData(Unknown Source)
at com.mslv.oms.priviledgeoperations.PriviledgedOperations_helmzh_ELOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
at com.mslv.oms.priviledgeoperations.PriviledgedOperations_helmzh_ELOImpl.refreshMetaData(Unknown Source)
at com.mslv.oms.eventengine.EventDispatcherEJB.refreshCache(Unknown Source)
at com.mslv.oms.eventengine.EventDispatcher_86q3j1_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at com.mslv.oms.eventengine.EventDispatcher_86q3j1_EOImpl.refreshCache(Unknown Source)
at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.e(Unknown Source)
at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.a(Unknown Source)
at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:583)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:486)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:388)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
If you are using Design Studio 7.2.2.0 the cartridge should be deployed without the error mentioned above.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |