cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Full and Delta CPACache refresh.

Former Member
0 Kudos

Hi Experts,

In our production environent we have a SOAP -> XI - > PROXY scenario [Synchronous].

The Consumer of the WebService has reported an error:

500_Internal_Server_Error = SOAP:Server_Server_Error_XIAdapter_ADAPTER.JAVA_EXC

When I checked there are no messages in SXMB_MONI , but when I checked the Cache Refresh History I found that

there was error in both Full and Delta Cache Refresh. But the restart of the XI(Production) server resolved the issue.

The error is as shown below:

<?xml version="1.0" encoding="UTF-8" ?>

- <CacheRefreshError>

<EngineType>AE</EngineType>

<EngineName>af.pxi.su0956</EngineName>

<RefreshMode>F</RefreshMode>

- <GlobalError>

<Message>Couldn't parse Configuration Data cache update XML string from Directory.</Message>

org.xml.sax.SAXException: JavaErrors Tag found in cache update XML. at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.startElement(DirectoryDataSAXHandler.java:157) at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.startElementEnd(SAXDocHandler.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Inlined Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java(Inlined Compiled Code)) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java(Compiled Code)) at javax.xml.parsers.SAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) 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.servlet.CacheRefresh.process(CacheRefresh.java:104) at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.doGet(CacheRefresh.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code)) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code)) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code)) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))

Can anyone tell me what is the cause of this error and how restart of the XI server resolved the issue?

Thannks,

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hey All,

The issue has been resolved....

Former Member
0 Kudos

Hi Kalyan,

Can you please provide your solution to this problem.  We are experiencing the same issue.

Thanks,

Nate

Former Member
0 Kudos

Hi Nathan,

For me the issue was resolved by a Java Stack restart.

You can contact your BASIS Team for further help if required.

Thanks,

Kalyan Batabyal

Former Member
0 Kudos

Guys,

I have deployed the below components and after this repository could not be started which gives the below error.

1000.7.11.10.18.20130529165100SAP AGsap.comSAP_XIAF
1000.7.11.10.11.20130529165100SAP AGsap.comSAP_XIESR
1000.7.11.10.15.20130529165100SAP AGsap.comSAP_XITOOL

We have the same issue. Still the Restart did not solve ths issue.

Can anybody help? We are not able to start the XI Repository.

Our PI components are as below

  1. com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/com.sap.xi.repository; nested exception is: java.rmi.RemoteException: [ERROR

CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is:

        com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean sap.com/com.sap.xi.repository*xml|com.sap.xpi.ibrep.server.jar*xm

l|CacheRefreshMDB^M

        at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315)^M

        at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106)^M

        at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55)^M

1000.7.11.10.6.20121015232500SAP AGsap.comMESSAGING

Regards

Omkar

Former Member
0 Kudos

This is fixed after Deploying Java Messgign to SP10 patch 19 level.

Regards

Omkar

former_member192238
Participant
0 Kudos

Hi,

If you are facing updating problems with full cache refresh please check the below configuration and SAP NOTE 999962

NWA-Configuration management-Infrastructure-java system properties:

choose XPI service:CPA Cache there we can see the following property SLD access =False.

Setting it to True and restarting the CPA Cache.

Regards

Praveen reddy

Former Member
0 Kudos

Hi,

The RFC destination INTEGRATION_DIRECTORY_HMI with path prefix /dir/CacheRefresh is used to update the cache that you see in SXI_CACHE. It should have the user XIISUSER. can you confirm the same? also test the destination to see if it is working fine.

please go through below blog,

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01b...

also refer

http://help.sap.com/saphelp_nw04s/helpdata/en/8f/770f41218ff023e10000000a155106/content.htm

regards,

ganesh.

Former Member
0 Kudos

Hi ,

I checked the RFC Destination INTEGRATION_DIRECTORY_HMI in SM59 and found the Logon User XIAFUSER.

Is it normal ?

Also when I did TEST Connection i got the following

HEADER NAME HEADER VALUE

~response_line HTTP/1.1 500 Internal Server Error

~server_protocol HTTP/1.1

~status_code 500

~status_reason Internal Server Error

connection close

server SAP J2EE Engine/6.40

pragma no-cache

content-type text/html;charset=ISO-8859-1

content-length 1936

~remote_addr

~uri_scheme_expanded NONE

Please suggest if everything is working fine.