Communication channel - cache problem?

Hi experts,
sometimes when I change parameters in communication channels that have thrown an error (in order to solve the problem), this modification is not immediatly working after activation of CC: the CC still works with old configuration.
To solve the problem now I clear cache of XI everytime.
Is a problem that someone got?
Thanks
Fabio

Hi,
The problem is definitely with the cache refresh problem.
For this please check the  timeline maintained in the JVM(Java virtual Machine). I belive you need to provide a response time over there(Not sure Please check), secondly you can also try to restart the system once again.
For the initial cache refresh you need to refresh the cache by manually refreshing all the cache in the Integration builder-->profile>Integration directory cache refresh for java cache refresh and also you can refresh the ABAP cache from SXI_CACHE transaction.
Cheers,
Jay

Similar Messages

  • Regarding Receiver Communication Channel (Concurrency problem)

    Hi Masters ,
    In Receiver Communication Channel which is connected to oracle data base ..while updating records Status from N to C . i am getting following errors :
    **Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has reached maximum concurrency (5,000 concurrent messages) and no free resource found within 5,000 milliseconds; increase the maximum concurrency level**
    Actually we are updating 10000 records status from N to C....... earlier it was updating in 30min now its hanging and giving above error ...... after 3 hrs its automatically displays updated succesfully message .
    Can you help me to understand wht exactly happening and at wht level i have to do settings in communication channel so tht it should work properly..
    Thanks in Advance.............
    Jagannath.

    Hi Jagannath
    you can specify the maximum concurrency for receiver adapters.  This defines the number of messages an adapter can process in parallel on a cluster node.
    Enter the number of messages to be processed in parallel by the receiver channel. For example, if you enter the value 2, then two messages are processed in parallel. Default value is 1 and this means only one message can be processed at a time by the receiver channel.
    http://help.sap.com/saphelp_nw70/helpdata/EN/64/ce4e886334ec4ea7c2712e11cc567c/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/EN/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm
    increase this parameter from 1000 to a higher value you required and you would not be facing such problem
    Regards
    sandeep
    If helpful kindly reward points

  • JDBC Sender Communication Channel Problem

    Hello everybody,
    I have a sender communication channel, it is with green Functioning status in channel monitor in runtime workbench, and the log says "Process started" for every pool as configured, but it doesn't return any data to XI, and there's data to be taken, the problem started a few hours cause it was working fine, I've already executed a Complete refresh cache in SXI_CACHE, and changed the channel from Active to Inactive in ID, and Stopped and Started it again in RW, it doesn't give any errors, but it doesn't bring back any data that should be, any suggestions or maybe any information on how to refresh totally those channels????, thanks in advance.
    Regard's
    Paul

    Hi Paul
    Check for JDBC adapter locks. cpa cache locks are not relevant to your problem.
    Moreover check with the visual admin logs as well. if you can get info about the issue you have
    Thanks
    Gaurav

  • Communications Channel in SXI cache

    Hi,
    I am not able to see my business system under communication channel in SXI_Cache.
    All other Integration directory objects are reflected in SXI_CACHE for the interface. Delta refresh is not solving the problem.
    File is being picked up by the adapter, but in SXMB_MONI i dont see the message.
    Every thing is working fine if i use any other communication channel there in cache.
    What can i do to get my communication channel in cache.
    Pls suggest.
    Regards,
    Satish

    I beleive this thread has answer to ur query. I beleive you have configured only a sender file CC under your business system and so this data is not available in the ABAP stack. If you configure a receiver CC under the same Business System, i beleive it should show up SXI_CACHE, however u still will not see ur sender CC or sender agreement
    -Saravana

  • Problem with  communication channel on receiver side with file adapter

    Hi all,
    I m doing a scenario of collection of multiple idocs into a file.When i m testing this scenario,i m getting a flag successfully executed in SXMB_MONI.But,my file isn't created in my directory.When i monitor the communication channel in Runtime workbench,it's showing error :<b>Channel has not been correctly initialized and cannot process messages</b> for my receiver file adapter?I am not able to figure out the error.Anybody having idea about this problem.
    Regards,
    Anoop

    Hi Anoop
    Check it - File adapter is active ? try to Re-activate the same.
    Also do CPACache Refresh.
    Still problem, tyr out by restarting the Adapter Engine
    Cheers..
    Vasu
    <i>
    Reward Points if found useful **</i>

  • Problems in IDOC receiver communication channel

    Hi,
    I am trying to build an interface to get data from 3rd party legacy system using JDBC and post the data into ECC using IDOCS. I have IDOC built in ECC, I am able to import the metadata in IDX2 after creating port in IDX1. But after building the whole interface, I dont see the IDOC receiver communication channel which has to post IDOCS in the ECC 6.0 system.
    Please assist.
    Rgds
    Kishore

    OK in that case, we are getting the following error in the Message monitoring:
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
      <SAP:P1>-BS_AVN_TO_FILE_JDBCSERVER</SAP:P1>
      <SAP:P2>-BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:AdditionalText>
      <SAP:Stack>Problem occurred in receiver agreement for sender -BS_AVN_TO_FILE_JDBCSERVER to receiver -BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY: No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:Stack
    Please check and assist.
    Rgds
    Kishore

  • Problem in File Sender Communication channel

    Dear all,
    We have FIle TO RFC scenario, which have been running in Production since long time.
    Problem :  Many of the time we have obsereved that even if the FTP is up and running , but file is not getting picked from ftp server. File name and all other details are maintained correctly. Can you please suugest me to resolve this issue.
    Regards,
    Raghvendra

    First of all: the connect parameter should be set to 'Per Transfer': this ensures that a new connection to the FTP server is established for each file transfer. That means that you don't loose connection to the FTP server in case of a hick-up.
    Second: are there any errors in your communication channel monitoring?

  • Problem with ORA -03113 End of Communication Channel

    Hello,
    Oracle Database 10g Release 10.2.0.1.0 - Production
    Windows Server 2003 Version V5.2 Service Pack 2
    Im having this problem when executing an stored procedure that executes a SQL statement wich has uses db links... I get this end of communication channel error.. so I thought it was a network issue, but all connections are fine.
    The thing is that the procedure works fine, but just out of the nothing starts to give that problem, shutting down the database would not correct the problem, only restarting the server will fix the issue temporarily. I checked the dump file related to the process am running and I found this, I think it might be like a memory problem but not sure
    Windows thread id: 5632, image: ORACLE.EXE (J002)
    *** ACTION NAME:() 2010-09-01 09:18:59.490
    *** MODULE NAME:() 2010-09-01 09:18:59.490
    *** SERVICE NAME:(SYS$USERS) 2010-09-01 09:18:59.490
    *** SESSION ID:(545.34045) 2010-09-01 09:18:59.490
    *** 2010-09-01 09:18:59.490
    ksedmp: internal or fatal error
    ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kghalf+478] [PC:0x603BEB04] [ADDR:0x61E26AE8] [UNABLE_TO_WRITE] []
    No current SQL statement being executed.
    what do you recommend me to try here?

    Hi Ogan,
    I agree ! Of course we are often obliged to compose with minimal downtime, testing resources, editors, management, time etc.
    I have the same problems but keeping the base version is a pain and if you consider 10.2.0.5 you won't have to install many patchsets after this one on the 10gR2 homes/databases. It's a "good" investment if you have to keep the 10gR2 for several years (going to 11g is more difficult than installing a patchset !)
    Oracle patchsets are great and well tested and if you pay your Oracle license you pay for that ! The patchsets, patchset updates, support make the difference with the versions you can download "freely" on OTN.
    Best regards
    Phil

  • Problem in creating new communication channel template in IR

    Hi experts,
    I currently have problems with creating new communication channel template in Integration Repository. If I choose the New-Context (Adapter Objects-->Communication Channel Template) the dialog "CREATE OBJECT" is shown. After I have inserted the Name of my template I push the create button.
    Then the following error occurs:
    STOP: Internal error: Object cannot be changed in display mode
    DETAILS: Internal error: Object cannot be changed in display mode(CANT_SET_MODIFIED).
    So can anybody help me. Thanks for your help.
    Best regards.
    Mario

    Hi Mario,
                This is genral problem appearing in PI 7.0 with SP12.
                Previously, i have the same problem.
                i.e STOP: Internal error: Object cannot be changed in display mode
    DETAILS: Internal error: Object cannot be changed in display mode(CANT_SET_MODIFIED)
                Regarding this we raise an OSS note SAP people.
                they gave the suggestion that update with SP13.
              i discuss with basis team and install the SP13.
               now the problem is solved, i can able to create the Communication Channel Template.
    Please award points, if it really help to u
    Regards
    Mahesh.

  • Problem in Communication channel monitoring..

    Dear friends,
    I am facing a problem in Communication channel monitoring.
    Problem:
    I have designed several communication channels in the Integration directory.
    To check the status of channel i will go to RWB->Component Monitoring->Adapter Engine->Communication channel monitoring, then we have a selection screen to filter out the channel, adapter,etc..
    Here i am NOT seen any channels to filter out. I.e. Channels in the Integration directory are not reflecting here.
    Can you please help out on this?

    HI,
    Do the CPACache refresh .
    ALso check this SAP Note- 937382
    Regards,
    Moorthy

  • About PI communication channel problem

    Hi Expert:
    anyone known  why my  communication channel  do not work smooth. the problem is that i stop the communication when communication channel  pull the date from database and not finished.(communication channel   is pulling  the data  when i stop the channel  ) . when i restart the communication channel .  Channel Monitoring log  show that Processing started   ,but not any data was pulled.
                best regard

    Hi Kevin,
    Have you made sure that the data is still available for your communication channel to process?
    If there is data and issue still persist, it could be due to some buffering issue. Why not try to do 'dummy' change to your communication channel like changing the description part, and try to reactivate it again?
    Regards,
    Lim...

  • Communication Channel Problem while reading from database

    Hi,
    I have a JDBC to IDoc scenario.
    The database here is AS400 and i need to read data from AS400 tables and send it to SAP IDocs.
    The communication channel picks up the data from AS400 based on the query and builds the IDocs.
    Suddenly the channel stops working and it doesnt pick up the data from AS400. When we change the name of the Communication Channel, it again starts picking up the data but again for some period.
    It sounds really strange as this is happening only with AS400 database and not it works perfectly when connecting to an SQL Server database.
    Please help me out in resolving this issue.
    Regards
    Kiran.

    Hi Kiran
    Can you check the Notes 717376 ,990892 and try to implement.
    Some tips:
    This error is caused by some optimization in the IBM VM for AS400 which can be disabled through the JIT compiler settings. The following VM setting -Dos400.run.mode=jitc must be set, according to note 717376. Any other value for this setting, as e.g. jitc_de can cause the described problem
    Also, please share the trace, so that, it would help to identify the problem.
    Also try to change the property in Vis Admin
    "cluster-data" -> "Global server configuration" -> "managers" -> "ApplicationThreadManager" -> "MaxThreadCount" ( like 400)
    Regards
    Chilla

  • Problem in finding the Communication channels under configuration

    helo all.
    i want to look at communication channels under cd1 (businness system)but i couldnt found.
    but when i take a look at these through my neighboous systems i did find those.
    can any body tell me wat would be the story behind this and do i need to have any settings under my system in XI.
    waiitng for u r response.
    bye.
    regards.
    seeta ram.

    Hi,
    If the objects are activated then u must be able to see it. Have u checked in the objects tab...where all the CC are listed under their respective business systems. Are you trying with ur user id in ur colleagues comp or their user id..?? Try to refresh the cache.
    Thanks!!

  • ExtractValue Problem----- ORA-03113: end-of-file on communication channel

    Dear Friend
    My system is now on this version
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
    PL/SQL Release 9.2.0.4.0 - Production
    CORE 9.2.0.3.0 Production
    TNS for Linux: Version 9.2.0.4.0 - Production
    NLSRTL Version 9.2.0.4.0 - Production
    earlier it was
    Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    PL/SQL Release 9.2.0.1.0 - Production
    CORE 9.2.0.1.0 Production
    TNS for Linux: Version 9.2.0.1.0 - Production
    NLSRTL Version 9.2.0.1.0 - Production
    I took the cold backup and restore in this version. after that my total system is working very fine, is very fast using than the previous. But only one SQL command is not working which is very urgent to solve
    when i am using this
    SELECT extractValue(value(t),'/produit/cod_pro') cod_pro
    FROM XMLTABLE X,
    TABLE ( xmlsequence (extract(XML_data,'/com/lProducts_list/produit'))) t;
    the table structure is
    SQL> desc XMLTABLE
    Name Null? Type
    DOC_ID NUMBER
    FILE_NAME VARCHAR2(100)
    FILE_DATE DATE
    XML_DATA XMLTYPE
    I got this error
    ORA-03113: end-of-file on communication channel
    Please guide me what to do to resolve this problem
    Farhad

    The error, ORA-03113: end-of-file on communication channel, is a client driver error.
    The client driver simply says "hey, the database server process servicing me has torn down our communication channel!". The communication channel is usually a TCP socket connection.
    The client driver has no idea why. Thus you have to find the answer on the server.
    The usual cause of this communication channel being closed, is the Oracle server process servicing the client session, crashing.
    When an Oracle server process crashes, it does not tell the client. It usually writes an entry to the Oracle alert log, dump a trace file, and terminates. When terminating, it tears down any communication channels (TCP sockets) it may have opened.
    Therefore you must look in
    - the alert log file for an error message listing the crash (which will include the dump file name)
    - look at this trace dump file (which is difficult if you're not familiar with Oracle internals)
    - investigate the stack trace and error codes on Metalink (which often turns up the bug notes for this, plus any workarounds or available patches)
    Usually however, one should log these types of Oracle server errors as a TAR with Oracle Support.

  • JMS Sender Communication  Channel problem

    Hi XI gurus!!
    I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
    In defaultTrace.XX.trc I see the following information and errors:
    #1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
    #1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
    {GenericConnectionProfileImpl
    {Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
    JmsMessageSelector=,
    ConnectionFactoryConstructor=null,
    ConnectionFactoryFactoryInvocation=null,
    ConnectionFactoryInvocations=[],
    DestinationConstructor=
    {ConstructorInvocation
    {className=null,
    invokeParams=[]
    DestinationInvocations=[],
    MessageInvocations=[],
    DestinationName=null,
    User=,
    Password=,
    isJmsSessionTransacted=true,
    InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
    LookupConnectionFactory=QueueConnectionFactory,
    LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
    SerializedConnectionFactoryPath=null,
    SerializedDestinationPath=null,
    Flags=0000000000000000000000000000000000000000000000000000100000000010
    #1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
    #1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
    #1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
    In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
    Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
    BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
    Thanks

    HI,
    As per the trace details given please consider few of the below options....
    What do u see in adapter monitoring tool for JMS adapter?
    http://hostname:5XX00/mdt/amtServlet
    Did you follow the document on correlation of JMS messages?
    In communication channel You have to set
    Correlation ID -> XI conversationID
    XI message ID->GUID
    XI Conversation ID -> JMS correlation ID.
    Now in the custom J2EE application you should set
    jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
    This thread deals with the issue..
    JMS Queue monitoring
    Check  if the JMS Sender adapter EOIO is with serialized messages 
    Thanks
    Swarup

Maybe you are looking for