on 09-04-2007 9:10 PM
Hi All,
we have installed PI 7.0 SP12. Dev system is working fine. In quality system, in the adpater monitoring we can only see the JPR adapter <b>but no other standard adapters (FILE, JDBC etc) are displayed</b>. No Communication Channel shows up in Communication Channel Monitoring.
We can select adapters during creating a communication channel in Integration directory. (we <b>imported the adapter meta-data</b> into IR, SAP BASIS SWCV 7.0, <b>re-imported</b> also)
<b>We have followed "How to Handle Caches" guide step by step</b> and getting error in the following tests (Everything else looks fine):
1) Tring to refresh the CPA Cache (Using the right URL and right user PIDIRUSER to login)
Results: <b>Never able to refresh CPA Cache</b>. We are getting following errors in CPACache history:
<?xml version="1.0" encoding="UTF-8" ?>
- <CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.piq.hostname</EngineName>
<RefreshMode>C</RefreshMode>
- <GlobalError>
<Message><b>CPA Cache not updated with directory data</b>.</Message>
<Trace>com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: <b>Couldn't open Directory URL (http://hostname:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.piq.hostname), due to: HTTP 503: Service Unavailable at</b> com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDataFromDirectory(DirectoryAccess.java:382) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDeltaCacheUpdateXML(DirectoryAccess.java:547) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:596) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.initializeCPACache(CacheManager.java:266) at com.sap.aii.af.service.cpa.impl.startup.StartupManager.initializeCPACache(StartupManager.java:220) at com.sap.aii.af.service.cpa.impl.j2ee.sapengine630.ServiceFrameImpl.startCPACache(ServiceFrameImpl.java:129) at com.sap.aii.af.service.cpa.impl.j2ee.sapengine630.ServiceFrameImpl.start(ServiceFrameImpl.java:49) at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214) at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144) at com.sap.engine.frame.core.thread.Task.run(Task.java:64) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)</Trace>
</GlobalError>
- <GlobalError>
<Message><b>Confirmation handling failed</b>.</Message>
<Trace><b>com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Service Unavailable at</b> com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.invokeConfirmationURL(DirectoryAccess.java:454) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:797) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.initializeCPACache(CacheManager.java:266) at com.sap.aii.af.service.cpa.impl.startup.StartupManager.initializeCPACache(StartupManager.java:220) at com.sap.aii.af.service.cpa.impl.j2ee.sapengine630.ServiceFrameImpl.startCPACache(ServiceFrameImpl.java:129) at com.sap.aii.af.service.cpa.impl.j2ee.sapengine630.ServiceFrameImpl.start(ServiceFrameImpl.java:49) at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214) at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144) at com.sap.engine.frame.core.thread.Task.run(Task.java:64) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)</Trace>
</GlobalError>
</CacheRefreshError>
2) Checking the Cache Notification Status/Checking the Cache Update Status
Integration Directory --> Choose Environment --> Cache Notifications .Problem Tab
Results: In the Problem tab we have erros for all communication channels:-
<b>com.sap.aii.af.service.cpa.CPAException: Schema not available for JDBC|b38bcd00e47111d7afacde420a1145a5|http://sap.com/xi/XI/System.
at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.endElement(DirectoryDataSAXHandler.java:294)</b> at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:156)
at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1951)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1844)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:56)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:871)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:640)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:456)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
3) Cache Connetion Test
Runtime Workbench --> Component Monitoring --> Choose Display --> Cache Connectivity Test --> choose Start Test.
Results: All the components are green accept Central Adapter Engine. For Central Adapter Engine we are getting following error/warning:-
<b>Attempt to fetch cache data from Integration Directory not yet started or still in process</b>
Please let us know if anyone has idea how to resolve above problems.
Thank You,
Indrasena Janga
Dear Janga,
I managed to solve this kind of issue by increasing the number of server process of JCO RFC providers.
Generally 503 Service unavailable comes when server process unable to handle the load and services are busy serving for huge number of concurrent requests.
Regards,
Shanaka.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Indrasena,
Which user you are using while calling the URL? Use XIAFUSER. Also check whether the XIAFUSER is locked ?
-raj.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
Please refer SAP " <b>Note 1057882 - XI 3.0 SP20 / PI 7.0 SPS12: Full CPACache refresh is stuck</b>".
Symptom
The full CPA Cache update is stuck and does not finish.
Reason and Prerequisites
The problem described above may only occur for the XI 3.0 SP 20 and PI 7.0 SPS12 releases.
Solution
The described problem is solved with
patch 02 of Support Package 20
of the XI ADAPTERFRAMEWORK CORE 3.0 software component.
and patch 01 of Support Package 12
of the XI ADAPTERFRAMEWORK CORE 7.0 software component.
The archives and the support package stack guide can be found on the
services marketplace as described in SAP Note 952402.
Thank You,
Indrasena Janga
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.