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...

Similar Messages

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

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

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

Sender Communication Channel Problem

Hi,
We have some issues with respect to files picking up and getting archived without processing.
Interestingly, there is no trace in comm monitor except for Processsing started and Processing Finished.
It doesnt happen at all times, moreover we need to reprocess the same file again and again until XI picks it up for processing,
The only think i dont understand is that how those files are picked and archived without processing.
Also note that I have configured multiple file names to be picked in the communication channel.
Please help me in this regard.
Krish

Hello Guys,
Thanks for your suggestions.
I have already made all these checks whether any other scenario runs with the same directory configuration.
Moreover the interesting point is that there is no log in the communication channel. The files are just getting archived without a log.
Moreover, I had checked in my Development and Test Environment whether any other interface is referring the same directory or not.
One more thing which i found out was when the file path is been changed to some other directory , it works well, I believe this is something to do with the FTP server directory, some authorizations or permissions.
But still, From xi point of you, it is confusing that how it can be archived without being processing.
Regards

Soap adapter communication channel problem

Hi...
While doing Webservices to file scenario, in component monitoring, the soap adapter communication channel is showing as (in small traiangle inyellow color) channel started but inactive

Hi leelaratnam,
Please check that you have only 1 communication channel active and running.
This happens when more than 1 CC is pointing or waiting for the same incoming data.
Also perform a dummy activate (i.e. write somthing in description and activate) in your message mapping and communication channel objects in case you are using PI 7.0
Thanks,
Varun

End of communication channel problem

I have a pl/sql block which works in oracle version 9.2.0.1.0 but the same code is not working in Oracle version 9.2.0.4.0. When i execute the PL/SQL block, I the the following error and gets disconnected from the server.
" DECLARE
ERROR at line 1:
ORA-03113: end-of-file on communication channel".
Does anyone have a solution for this.
Thanks in advance.
My Pl/sql block is as follows
DECLARE
XML VARCHAR2(4000);
doc dbms_xmldom.DOMDocument;
v_nl dbms_xmldom.DOMNodeList;
begin
XML := '<TABLES>';
XML := XML || '<TABLE><tag1>#222-22</tag1>';
XML := XML || '</TABLE>';
XML := XML || '</TABLES>';
doc := dbms_xmldom.newDOMDocument(XML);
v_nl := dbms_xslprocessor.selectNodes(dbms_xmldom.makeNode(doc),'/TABLES/TABLE');
dbms_xmldom.freeDocument(doc);
END;

C:\oracle\ORCL9204\rdbms\admin>sqlplus "sys/oracle as sysdba"
SQL*Plus: Release 9.2.0.4.0 - Production on Wed Nov 5 05:53:36 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
SQL> SELECT comp_name, status, substr(version,1,10) as version from dba_registry;
COMP_NAME
STATUS VERSION
Oracle9i Catalog Views
VALID 9.2.0.4.0
Oracle9i Packages and Types
VALID 9.2.0.4.0
Oracle Workspace Manager
VALID 9.2.0.1.0
COMP_NAME
STATUS VERSION
JServer JAVA Virtual Machine
VALID 9.2.0.4.0
Oracle XDK for Java
VALID 9.2.0.6.0
Oracle9i Java Packages
VALID 9.2.0.4.0
COMP_NAME
STATUS VERSION
Oracle interMedia
VALID 9.2.0.4.0
Spatial
VALID 9.2.0.4.0
Oracle Text
VALID 9.2.0.4.0
COMP_NAME
STATUS VERSION
Oracle XML Database
VALID 9.2.0.4.0
Oracle Ultra Search
INVALID 9.2.0.4.0
Oracle Data Mining
VALID 9.2.0.4.0
COMP_NAME
STATUS VERSION
OLAP Analytic Workspace
UPGRADED 9.2.0.4.0
Oracle OLAP API
UPGRADED 9.2.0.4.0
OLAP Catalog
VALID 9.2.0.4.0
15 rows selected.

Communication Channel Problem

Hi there
We have a comm. Channel that picks up a flat file which is u201C|u201D delimited and containing about 90 000 lines. When XI picks up the file it fails in the message monitor. When I open the inbound payload it only processes about half of the lines. The file is 13MB in size; is there some limit to which XI can handle or can I change some parameter to allow XI to process large files?
Thanks,
Jan

Hi,
>>>The file is 13MB in size; is there some limit to which XI can handle or can I change some parameter to allow XI to process large files?
no, there is no limit and no parameter to change - 13 Mb is not much
correct your mapping and it should work
Regards,
Michal Krawczyk

XI communication channel missing in communication channel monitoring

Hello partners,
I have a problem with communication channel monitoring.
I have defined a communication channel of Adapter Type = "XI" in the integration directory.
I have also sent messages successfully via this communication channel.
But the communication does not appear in the list of available channels in the selection list of the communication channel monitoring.
Can someone tell me how I can get monitoring info of an "XI" communication channel?

Hi,
From SP17, you have a new feature
http://help.sap.com/saphelp_nw04/helpdata/en/44/46d1a56faf52d3e10000000a1553f6/content.htm
<i>The Runtime Workbench has the following new functions:
● Component monitoring: Communication channel monitor
In component monitoring, you can use the new communication channel monitor to call information about the status of your communication channels and the corresponding adapters. You can also administrate your communication channels.
Unlike the adapter monitor, the communication channel monitor also provides current runtime information about the communication channels of individual adapters, as long as they are registered for communication channel monitoring.
To monitor adapters that do not provide runtime information to communication channel monitoring, continue to use the adapter monitor.</i>
Regards,
Bhavesh

Connection Interrupted when opening a Communication Channel

Dear all
We have suddenly experienced problems after starting the Integration Directory.
When trying to edit one of the Communication Channels, a dialogue box appears saying:
Connection Interrupted
You can log on again once the server is available again
Do you want to log on again?
Password:
After entering the password, a new box appears saying: Reconnection to server was successful. Repeat the action
But the info about the communication channel is still not showing, and the same error message appears when trying to edit the Communication Channel again (going into a loop)
When debugging with Java Web Start the following error occurs:
#91 09:57:13 [AWT-EventQueue-0] DEBUG com.sap.aii.utilxi.swing.framework.cmd.OpenCommand: Open 'Communication Channel | HRDCLNT270 | SenderABAPProxy (DirContext)'
#92 09:57:14 [AWT-EventQueue-0] DEBUG com.sap.aii.ib.clsif.login.LoginService: Found cached remote interface QueryServiceBean
#93 09:57:14 [AWT-EventQueue-0] DEBUG com.sap.aii.ib.clsif.login.LoginService: Found cached remote interface ObjectAccessBean
#94 09:57:15 [AWT-EventQueue-0] WARNING com.sap.aii.ib.clsif.gen.AccessUtil: A problem occurred that is tried to be solved by reconnect.
Thrown:
com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
     java.io.InvalidClassException: com.sap.aii.ibdir.bom.cpa.Channel; local class incompatible: stream classdesc serialVersionUID = 366016170231986765, local class serialVersionUID = 2790972994638010697
     java.io.InvalidClassException: com.sap.aii.ibdir.bom.cpa.Channel; local class incompatible: stream classdesc serialVersionUID = 366016170231986765, local class serialVersionUID = 2790972994638010697
java.io.InvalidClassException: com.sap.aii.ibdir.bom.cpa.Channel; local class incompatible: stream classdesc serialVersionUID = 366016170231986765, local class serialVersionUID = 2790972994638010697
     at java.io.ObjectStreamClass.initNonProxy(Unknown Source)
     at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
     at java.io.ObjectInputStream.readClassDesc(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
     at java.io.ObjectInputStream.readSerialData(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Unknown Source)
     at java.io.ObjectInputStream.readObject(Unknown Source)
     at com.sap.aii.ib.sbeans.oa.ObjectAccessRemote_Stub.read(ObjectAccessRemote_Stub.java:1318)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
     at $Proxy8.read(Unknown Source)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:108)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:97)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:310)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:208)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:196)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:134)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:206)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:123)
     at com.sap.aii.utilxi.swing.framework.navigation.impl.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:472)
     at com.sap.aii.utilxi.swing.framework.navigation.impl.ThreadedTree.executeStandardOperation(ThreadedTree.java:1805)
     at com.sap.aii.utilxi.swing.framework.navigation.impl.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:1770)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Does anyone have a solution to this problem? We could edit the Communication Channel earlier so it seems like the problem have occured during the last week.
Regards
Andreas

Hi Chirag
I've tried what you've suggested but the error messages does still appear when trying to edit the Communication Channel after exiting and starting the integration builder.
The error that concerns me is:
com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
     java.io.InvalidClassException: com.sap.aii.ibdir.bom.cpa.Channel; local class incompatible: stream classdesc serialVersionUID = 366016170231986765, local class serialVersionUID = 2790972994638010697
     java.io.InvalidClassException: com.sap.aii.ibdir.bom.cpa.Channel; local class incompatible: stream classdesc serialVersionUID = 366016170231986765, local class serialVersionUID = 2790972994638010697
java.io.InvalidClassException: com.sap.aii.ibdir.bom.cpa.Channel; local class incompatible: stream classdesc serialVersionUID = 366016170231986765, local class serialVersionUID = 2790972994638010697
It seems like the class com.sap.aii.ibdir.bom.cpa.Channel has a different UID locally and in the stream...

Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

Hello All,
One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
Is the (IDoc) Communication Channel from Sending system to XI required to configured?
Many thanks in advanced!
Jochen

Hi Jochen,
for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
Thanks,
Rajeev Gupta

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>

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

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?

About PI communication channel problem

Similar Messages

Maybe you are looking for