cancel
Showing results for 
Search instead for 
Did you mean: 

XI ADAPTER PROBLEM

Former Member
0 Kudos

Hi All,

I was using my QA server for the file processing.

Suddenly i found that the File adapter is not working and it is in grey...

I restart the server also but still the same problem is happening.

I checked in XI CONFIGURATION->Environment>Cache notification and found that there is some problem in the cache refresh.

Can anyone look at this and let me know.

I have already checked the XIDIRUSER and it is NOT LOCKED.

============================================================

com.sap.aii.ib.server.abapcache.CacheRefreshException: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://drprd-db1:50300/rep/query/int?container=any" with user "XIDIRUSER". Response code is 500, response message is "Internal Server Error"

at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:144)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:370)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:294)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:142)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)

at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)

at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)

at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)

at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)

at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)

at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)

at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)

at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)

at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

com.sap.aii.ib.core.query.QueryServiceException: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://drprd-db1:50300/rep/query/int?container=any" with user "XIDIRUSER". Response code is 500, response message is "Internal Server Error"

at com.sap.aii.ib.core.query.QueryServiceHttp30.generalQuery(QueryServiceHttp30.java:78)

at com.sap.aii.ib.server.query.QueryServiceImpl.generalQuery(QueryServiceImpl.java:187)

at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.readReferences(CacheCPA.java:512)

at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:129)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:370)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:294)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:142)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)

at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)

at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)

at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)

at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)

at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)

at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)

at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)

at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)

at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

=====================================================

thanks \

JGD.

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

Thanks a lot to all of you...

If this kind of problem occur then try to refresh the cache present inside the Administrator>Cache Overview>Integration overview -->cache refresh..

Former Member
0 Kudos

Thanks a lot to all you guys,,

I solve the problem by my own..

The problem was with the cache refresh that we have under the administrator ...Cache overview Full cache refresh..

Thanks a lot ..

Point will be assigned to all of you for helpful answer..

Former Member
0 Kudos

Hi,

I Provided the below details:

http://dev-db1:8003/AdapterMonitoring/monitor/monitor.jsp

It return me an error :

404 Not Found SAP J2EE Engine/6.40

The requested resource /AdapterMonitoring/monitor/monitor.jsp is not available

Details: File [AdapterMonitoring/monitor/monitor.jsp] not found in application root of alias [/] of J2EE application [sap.com/com.sap.engine.docs.examples].

Thanks

Former Member
0 Kudos

Hi,

URL: http://<host>:<J2eePort>/AdapterFramework/monitor/monitor.jsp

Hope it helps..

Thanks

kumar

Edited by: Vasanth Kumar.S on Sep 2, 2008 12:08 PM

Edited by: Vasanth Kumar.S on Sep 2, 2008 12:09 PM

Former Member
0 Kudos

Hi,

Thanks a lot.

I am using XI 3.0 with a patch level 15.

Now i clicked on Component Monitoring --->Adapter Engine>>>>STATUS tab i can see the following options:

Repeat Ping ,, Repeat Self Test,, Security Archiving,Background processing and then Adapter Monitoring.

There is no such option called Communication Channle MOnitoring.

Is ther any table for this where we can also check it out.

Thanks.

Former Member
0 Kudos

Hi

use this URL to monitor..

http://<host>:<port>/AdapterMonitoring/monitor/monitor.jsp

Hope it helps..

Thanks,

kumar.

Former Member
0 Kudos

Thanks a lot for your reply,

Already checked the SX_CACHE ,, it is clear..

Already cehcked the ADAPTER MONITORING and ALL ADAPTERS .. few of them are still in grey..

Can you please let me know where can i check the COMMUNICATION CHANNEL MONITORING..

Former Member
0 Kudos

Hi,

As i have told..

Click on Adapter Engine in the RWB..Scroll down the page..

You will find the communication channel monitoring tab separately..

Hope it helps..

Thanks,

kumar.

Former Member
0 Kudos

Hi All,

I just checked the Message Monitoring and found some message stuck off, So i tried to check the sequence number and then cancle the message from the Message Monitoring.

The starange thing is that,, all the ADAPTERS(FILE,RFC,SOAP,) became inactive and other are still in active state(XI,Marketplace,BC)

The file is still in inbox rather then being picked up.

1. Is there any connection bettween MMonitoring and other cache details.

2. Is there any relation between MMonitoring and other adapters.

3. Where to check if the ADAPTERS are not working properlly or still in inactive state..

Can anyone please help me out..

Thanks.

JAY

Former Member
0 Kudos

Hi,

Try to register the queue in SMQ1 and SMQ2.

Also check whether the CC for the interfaces are active or inactive.

Regards,

Nithiyanandam

Former Member
0 Kudos

Hi,

1.) First chcek your cache is updated using SXI_CACHE

2.) You can adpater status in Connunication channel

goto --> Parameter Tab

-


>Adavnaced-->Adapter Status - >Active/Inactive

3.) You can check you communacation channel monitoring under

Goto ->RWB>ComponentMonitoring->AdpaterEngine-->CommuncatiionChannelMonitoring

Here you can the status of the CC which can be configured by you..

Hope it helps..

Thanks,

kumar.

prateek
Active Contributor
0 Kudos

This doesn't seem to look like a user related error. Try SAP Note 804124 and 807000.

Regards,

Prateek