EOIO issue

Hi,
while processing 2 GB file from sender file channel am facing some issue. as I used EOIO in file cc.
Am attached the error . Am expecting to increase the tablespace. there is issue from DB end in PI. Please confirm.
Error: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not assign next EOIO sequence number for SC: XI_OUTBOUND_BOM__GTQ100_Q. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not insert message 0c445fc0-e736-11e3-8561-00000924352b(OUTBOUND) into database. Reason: java.sql.SQLException: caused by java.io.IOException: ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP at oracle.jdbc.driver.DatabaseError.SQLToIOException(DatabaseError.java:517) at oracle.jdbc.driver.OracleBlobOutputStream.flushBuffer(OracleBlobOutputStream.java:214) at oracle.jdbc.driver.OracleBlobOutputStream.write(OracleBlobOutputStream.java:144) at com.sap.sql.jdbc.oracle.Oracle10gPreparedStatement.convertStreamToBlob(Oracle10gPreparedStatement.java:415) at com.sap.sql.jdbc.oracle.Oracle10gPreparedStatement.setBinaryStream(Oracle10gPreparedStatement.java:175) at com.sap.sql.jdbc.direct.DirectPreparedStatement.setBinaryStream(DirectPreparedStatement.java:830) at com.sap.sql.jdbc.common.dispatch.BlobHostVariable.setBinaryStream(BlobHostVariable.java:125) at com.sap.sql.jdbc.common.dispatch.SetterDispatcherImpl.setBinaryStream(SetterDispatcherImpl.java:76) at com.sap.sql.jdbc.common.CommonPreparedStatement.setBinaryStream(CommonPreparedStatement.java:802) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setBinaryStream(PreparedStatementWrapper.java:517) at com.sap.engine.messaging.impl.core.store.MessageStore.insertMessage(MessageStore.java:482) at com.sap.engine.messaging.impl.core.store.MessageStore.putMessage(MessageStore.java:321) at com.sap.engine.messaging.impl.core.MessageController.putMessageInStore(MessageController.java:146) at com.sap.engine.messaging.impl.core.MessageController.putMessageInStore(MessageController.java:129) at com.sap.engine.messaging.impl.core.store.access.StoreAccess.assignSequenceNumber(StoreAccess.java:392) at com.sap.engine.messaging.impl.core.service.Send.execute(Send.java:187) at com.sap.engine.messaging.impl.spi.ServicesImpl.send(ServicesImpl.java:226) at com.sap.aii.adapter.xi.ms.XIMessage.prepareAndSend(XIMessage.java:2521) at com.sap.aii.adapter.xi.ms.XIEventHandler.onSend(XIEventHandler.java:254) at com.sap.engine.messaging.impl.api.ConnectionImpl.send(ConnectionImpl.java:181) at com.sap.aii.af.app.modules.CallAdapterWithMessageBean.process_sender(CallAdapterWithMessageBean.java:383) at com.sap.aii.af.app.modules.CallAdapterWithMessageBean.process(CallAdapterWithMessageBean.java:211) at sun.reflect.GeneratedMethodAccessor7796.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:74) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy316.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:290) at sun.reflect.GeneratedMethodAccessor4115.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:74) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy304.process(Unknown Source) at com.sap.aii.adapter.file.File2XI.send(File2XI.java:3519) at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1315) at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:630) at com.sap.aii.af.lib.scheduler.JobBroker$Worker.run(JobBroker.java:532) 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:182) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:280)

Hi Aman,
It is suggest to use chunk mode for big files and 2 GB is huge size. Please refer the below blogs
PI/XI: PI 7.3 processing of large files - teaser
File/FTP Adapter - Large File Transfer (Chunk Mode)
regards,
Harish

Similar Messages

Mapping Issue

Hi Gurus,
I have a JDBC-XI-RFC scenario (EOIO), where in I had to use Enhanced receiver determination to split the calls to RFC's (Regular Vs Emergency). Emergency call was directed using the filter queue to change the priority. We have tested in many env (d,q, pre prod) & now when I moved to Prod I get a strange error. When it first come to the integration engine & if it requires a split it fails showing a mapping error. But if I re-trigger it flow succesfully. Please fing the log from "moni" below(1) & a sussesful log (2).
Please see the below bolded log which I am getting confused
In case of error I get
<SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>
Else I get
<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION</SAP:Interface>
**(1)**
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">- <SOAP:Header>
<SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>4A6DF427-B0EE-7444-E100-00000AAA0C0C</SAP:MessageId>
<SAP:TimeSent>2009-07-28T13:37:05Z</SAP:TimeSent>
<SAP:Sender>
<SAP:Service>CIS_PROD_STORMS</SAP:Service>
<SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface> *
</SAP:Sender>
<SAP:Receiver>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<SAP:Service>BS_ENVISION_SAP_EMERG</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION_EMERG</SAP:Interface>
<SAP:Mapping notRequired="M">
<SAP:ObjectId>RNPgv18MOBmjhpr+oO1mNw==</SAP:ObjectId>
<SAP:SWCV>oZGAQNmpEdym2dnSCqoHjQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>
</SAP:Main>
<SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
<SAP:QueueId>XI_ENV_SERIALIZE</SAP:QueueId>
</SAP:ReliableMessaging>
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_ENVISION_WO_TO_SAP_NOTIF_EMERG_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
(2)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SOAP:Header>
<SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>4A6DDA42-B138-7443-E100-00000AAA0C0C</SAP:MessageId>
<SAP:TimeSent>2009-07-27T22:01:00Z</SAP:TimeSent>
<SAP:Sender>
<SAP:Service>CIS_PROD_STORMS</SAP:Service>
<SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>
</SAP:Sender>
<SAP:Receiver>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<SAP:Service>BS_ENVISION_SAP_REGULAR</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION</SAP:Interface>
<SAP:Mapping notRequired="M">
<SAP:ObjectId>oPLLbgxJOWimAK6rdZb/MA==</SAP:ObjectId>
<SAP:SWCV>oZGAQNmpEdym2dnSCqoHjQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION</SAP:Interface> *
</SAP:Main>
<SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
<SAP:QueueId>XI_ENV_SERIALIZE</SAP:QueueId>
</SAP:ReliableMessaging>
Regards
UK

Hi,
Sorry, My text help was not working due to some IE setting & I can understand the message got cluttered.
Anyways let me repost the actual thread,
I have a JDBC-XI-RFC scenario which requires an Enhanced receiver determination and requires calling two different RFC programs(emergency, regular) based on that. I use a queue filter to direct to XBQA* for emergency. As I indicated, it seems working fine with d,q,preprod. When I move it to prod, it show me some maping issue. However when I retrigger the same from my moni, they execute succesfully. Please see the log below for a message that goes error & the log when it is succesful (retrigger). Let me know if you need more details.
When there is error Please see the last tag
MI_TBL_WMS_SOURCE_STAGING_SDW_EGD is the sender
<SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>4A6DF427-B0EE-7444-E100-00000AAA0C0C</SAP:MessageId>
<SAP:TimeSent>2009-07-28T13:37:05Z</SAP:TimeSent>
<SAP:Sender>
<SAP:Service>CIS_PROD_STORMS</SAP:Service>
<SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>
</SAP:Sender>
<SAP:Receiver>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<SAP:Service>BS_ENVISION_SAP_EMERG</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION_EMERG</SAP:Interface>
<SAP:Mapping notRequired="M">
<SAP:ObjectId>RNPgv18MOBmjhpr+oO1mNw==</SAP:ObjectId>
<SAP:SWCV>oZGAQNmpEdym2dnSCqoHjQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
*<SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>
</SAP:Main>*
Blelow is when its succesful
<SAP:Interface namespace="urn:sap
-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION_EMERG</SAP:Interface>.
Regards
Unni
Edited by: Unni Krishnan on Jul 28, 2009 5:06 PM

Issue with the configuration of http xml port for sending the idoc

Hello,
      I am planning to send multiple idocs in a single file using http xml port.
Presently I am trying to send a single idoc, but am having the issue.
I am trying to create a RFC for HTTP XML port of type H i.e. HTTP Connection to ABAP System
In the how to guide for - How Tou2026 Send Multiple IDocs Within One XI Message
( https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b )
the following parameters are defined for the path prefix -
RFC destination of type H (HTTP Connection to R/3 System).
Specify the path prefix as follows:
/sap/xi/adapter_plain/
?namespace=< your namespace>
&interface=<IDoc_Type>
&service=<Sender System>
&qos=EO (or EOIO).
I am trying to use the following prefix -
/sap/xi/adapter_plain/
?namespace=urn:sap-com:document:sap:idoc:messages ( this is the standard namespace of SAP for all the idocs)
&interface=DEBMAS05 (Idoc type )
&service=SNDLS100 ( ECC system name )
&qos=EOIO
On testing the RFC connection, I am getting the error of page not found.
Can anyone please give me pointers for the issue.
Regards,
Mayank

Thanks Barry!!!
Now I am getting a different message.
In RFC...it is giving me the following message ->
Status HTTP Response     204
Status Text     Body is empty
In case of Idoc, the status is till 02...
the error description for the idoc is --
"When transferring the IDoc by HTTP, the return code with the message '500<SAP:Error><SAP:Category>XIServer</SAP:Category><S' has occurred.
The target address was: http://emgeccsnd1:8001/sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interf
Check whether the IDoc can be sent again.
It is unfortunately not possible to determine automatically whether the IDoc has in fact arrived in the target system and the error occurred afterwards"
I am still not able to resolve the issue.
Regards,
Mayank

Issue with file to file in PI 7.3 (Splitting huge files)

Hi All,
Need your help in fixing the issue with file splitting
We are doing some sample scenarios(file to file) on PI 7.3 server.
We are trying to split a 10MB file by using the 'Advanced Mode' option in the sender file adapter. We gave max split file size as 2MB. The file got split into 5 chunks and was successfully sent to receiver file adapter. In receiver adapter we are able to see that. But in the target folder only 1 file was seen with size 2MB. All other chunks were missing. We need to have the whole data sent from source to target.
How to fix this issue? please provide your inputs.
Thanks and Regards,
Lakshmi Narayana

PI 7.3 has capable of processing larger size files.
Questions:
Have you picked EOIO quality of service? Hope you dont do mapping or content conversion for this file?
have you seen this link
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a06d79f3-d094-2e10-1a81-f4d802d0bcf1?QuickLink=index&overridelayout=true
http://help.sap.com/saphelp_nw73/helpdata/en/44/682BCD7F2A6D12E10000000A1553F6/frameset.htm

Mapping issue in QA

*Hai Experts!*
*I am facing an issue in Quality server. The scenario is SOAP to JDBC. Which is working fine in Development server. But in QA the mapping is not happening and the Following error is displaying in the Trace view.*
*Can any one help me in solve this issue.*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
</Trace>
<Trace level="1" type="T">system-ID = OXQ</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2011-08-09T05:06:42Z CET </Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace>
<Trace level="1" type="T">Message-GUID = 5EE4A690C24511E08056E41F1320CC6A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">
<Trace level="1" type="T">Queue name : XBTI0007</Trace>
<Trace level="1" type="T">Generated prefixed queue name = </Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message </Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_OUT_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
</Trace>
<Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace>
<Trace level="1" type="T">Continue single processing </Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = OXQ</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2011-08-09T05:06:42Z CET </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace>
<Trace level="1" type="T">>>>PID delete old pid determination coding </Trace>
<Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="1" type="T">Reading sender agreement </Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place </Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
</Trace>
<Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
<Trace level="1" type="T">number of receivers: 2 </Trace>
<Trace level="1" type="T">Multi-receiver split case </Trace>
<Trace level="1" type="T">Persisting initial (pre-split) message </Trace>
<Trace level="1" type="T">Persisting split messages (split kids) </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop start </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Split Induced Change EO -> EOIO with QId: XI_SERIALIZE0000</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBQO3___</Trace>
<Trace level="1" type="T">Persisting split kid = 4E4085AB74480E30E1008000C0A8004E</Trace>
<Trace level="1" type="T">Generated prefixed queue name = </Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_OUT_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </Trace>
<Trace level="1" type="T">Loop 0000000001 </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_OPS_IN_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">Hence set action to DEL </Trace>
</Trace>
<Trace level="1" type="T">Split Induced Change EO -> EOIO with QId: XI_SERIALIZE0000</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBQO3___</Trace>
<Trace level="1" type="T">Persisting split kid = 4E4085AC74480E30E1008000C0A8004E</Trace>
<Trace level="1" type="T">Generated prefixed queue name = </Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_OUT_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </Trace>
<Trace level="1" type="T">Loop 0000000001 </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_IN_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">Hence set action to DEL </Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop end </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to Call qRFC for execution of split kids ... </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_OUT_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </Trace>
<Trace level="1" type="T">Loop 0000000001 </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_OPS_IN_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </Trace>
<Trace level="1" type="T">Loop 0000000002 </Trace>
<Trace level="1" type="T">select interface ShipmentAdvice_iOlam_IN_ASYN_SI </Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:ShipmentAdvice::iOlam:OPS:10 </Trace>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">Hence set action to DEL </Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST"></Trace>
</SAP:Trace>
Regard's
Preethi
Edited by: preethi_malu on Aug 9, 2011 7:59 AM

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">system-ID = OXQ</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2011-08-10T08:23:48Z CET</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = BE8DFF410EFD44533BEDA93E4E7FD402</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">
<Trace level="1" type="T">Queue name : XBTI0006</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface dealTicket_OPS_OUT_ASYN_SI</Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:DealTicket:OPS:iOlam:20</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace>
<Trace level="1" type="T">Continue single processing</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = OXQ</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2011-08-10T08:23:48Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 2</Trace>
<Trace level="1" type="T">Multi-receiver split case</Trace>
<Trace level="1" type="T">Persisting initial (pre-split) message</Trace>
<Trace level="1" type="T">Persisting split messages (split kids)</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop start</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Split Induced Change EO -> EOIO with QId: XI_SERIALIZE0067</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBQO0___</Trace>
<Trace level="1" type="T">Persisting split kid = 4E42267021350B00E1008000C0A8004E</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface dealTicket_OPS_OUT_ASYN_SI</Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:DealTicket:OPS:iOlam:20</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface InterfaceCollection</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/XI/System</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</Trace>
<Trace level="1" type="T">Split Induced Change EO -> EOIO with QId: XI_SERIALIZE0067</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBQO0___</Trace>
<Trace level="1" type="T">Persisting split kid = 4E42267121350B00E1008000C0A8004E</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface dealTicket_OPS_OUT_ASYN_SI</Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:DealTicket:OPS:iOlam:20</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface dealTicket_OPS_IN_ASYN_SI</Trace>
<Trace level="1" type="T">select interface namespace urn:olam-com:DealTicket:OPS:iOlam:20</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop end</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to Call qRFC for execution of split kids ...</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

Big File to IDOC - performance issue

Hi All,
I am trying to create scenario where I have a file with aproximately 10 000 rows. From each row I am creating one IDOC and want to send it to R/3. Interface looks fine - it is working, but it is killing XI box for some time and u cant access it.
Full scenario look like this
File -> BPM (for 1:n) -> IDOC
I tried to find some solutions for doing the workload smaller by splitting file to less lines (500rows per file) but then file adapter picks up all file and processed them in parallel. So this is new scenario:
BigFile -> XI -> File -> BPM(1:n) -> IDOC
I tried to put second file sender communication channel as EOIO but looks like this does not work - or messages from queue are processed to fast. When one message starts BPM another file message start to be processed.
Do You have any ideas on how to make it more responsive and less performance impact?
thanks in advance.
Dawid

Hi ;
Since mappings are processed by the J2EE Engine, the maximum available Java heap may be a limit-ing factor for the maximum document size the XI mapping service is able to process. Tests have shown that processing of XSLT mappings consumes up to 20 times the source document size (using identity mapping). The maximum available Java heap for 32bit JVMs is platform-dependent. Using 64bit JVM platforms is an option here.
Current maximum heap sizes 32bit
OS
Maximum heap (GB)
Linux
2
Windows
1.2 1.4
The Java heap is limited by the heap limit of the process (may be limited by address space because operating system code or libraries may also be loaded within the same address space). Also, Java internal memory areas such as the permanent space for loading Java classes must fit into the same address space.
Java VM tuning is one of the most crucial tuning steps, especially for more complex scenarios. For information about setting baseline JVM parameters, see SAP Note 723909. You must also take plat-form-specific parameters into account (for example, JIT compiler settings). The impact of Garbage Collection (GC) behavior especially may become a critical issue. Overall GC times for the J2EE appli-cation should be well below 5%. For more information about GC behavior and settings, see also SAP Note 552522.
Specific to XI is the fact that you sometimes need to process large documents for mapping or when using signatures. This can lead to excessive memory usage on the Java side. Therefore, you must observe Garbage Collection and the available Java heap in order to evaluate performance and pre-vent OutOfMemory exceptions. Since XI mapping is processed by stateless session beans that are called using a JCo interface, this may lead to a reduction of parallel JCo server threads within the JCo RFC Provider service of a J2EE server node (you can compensate for this by adding J2EE server nodes).
Mudit

MQ Series - Error while reading messages from MQ in Sender adapter if EOIO

Dear all,
we've configured a scenario with a sending JMS-adapter (MQSeries). With configured Quality-Of-Service = EO everything works fine. If we switch to Quality-Of-Service = EOIO we get the following error message:
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not assign next free EOIO sequence number for SC: OUTBOUND_TEST_MQ_SERIES_QUEUE_4__. Reason: Problem inserting b315acf4-61f3-42dc-3642-85450666fe91(OUTBOUND) into the database: java.lang.NullPointerException: DeliveryException: Could not assign next free EOIO sequence number for SC: OUTBOUND_TEST_MQ_SERIES_QUEUE_4__. Reason: Problem inserting b315acf4-61f3-42dc-3642-85450666fe91(OUTBOUND) into the database: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105)
Any ideas?
Kind regards, Stefan

We have the same issue, how did you solve yours?
For us it works fine with EO but EOIO fails with the same error message...
Kr,
Frederik-Jan.

IDOC creation issue at XI side - File to IDOC

Hi Everybody,
I am working on a File to IDOC scenario (XI 3.0).
We have to create Orders in the R/3 System using this Interface.
Mapping used is Java.
I am using 2 Classes : Group and SendIdoc one below the other in the Interface Mapping:
Firstly by using Group Class I am Grouping the Records in the file and then creating the IDOCs by using the next class(SendIdoc).
In the production environment if we drop like 20 files at a time in the source NFS folder the number of IDOCs created are wrong.
Say for example, for the first file dropped expected IDOCs are 10 but only 8 are created in SXMB_MONI .However in the input payload (in SXMB_MONI) the entire text file is read.
When we put the files sequentially say one after the other is processed, the number of IDOCs created are fine.
This is very strange problem.
I tried changing the polling interval of the channel but was of no help.
Any parameters we need to set in the channel or XI system to overcome this issue?
Can someone help me out on this?
Helpful answers will be rewarded points.
Thanks & Regards,
RK

Hi ,
When you placing files sequentially its working fine menas there is no problem with Java Code,one morething use synchronize methods or thread programming in Java maps is not advisable.
as per my knowledge File adapter picking up the recodrs when its giving inout to Java map some thing misisng....
for one file you need to create multiple IDocs try use QOS EOIO or if its not working then try to use record set per message one like that,let me know.
Regards,
Raj

File adapter with QoS=EOIO Is there any filesize limitation?

Dear Experts,
I'm using a File/FTP Sender adapter with Quality of Service = EOIO (Exactly Once In Order) to keep the polled order of the files.
In the processing parameters I defined a queue name and everything is working well for small (~1 MByte) files.
But if I want to transfer bigger (~25 MByte) files, the whole Java stack collapses and the system has to be restarted.
Is there any size limitation for this own defined queues?
Have you any experience with this kind of processing?
Any comments / experiences are welcome!
Best regards,
Andras

Hello,
there are several files to poll, we have to keep the alphabetical order of them.
It seems, that we have this issue only with EOIO. (EO works good)
After the system has restarted, the first file from the queue was processed, but with a n error message "Could not delete file 'filename.dat' after processing: java.lang.NullPointerException"
(the delete option is on after the transfer)
Is there any possibility to check the mentioned "QuicSized" settings?
I just wanted to know, if there is an "unofficial" size limit of these queues.
Thank you!

Error Handling in Inbound ABAP Proxy with EOIO

Hi,
The scenario
I have a File to ABAP Proxy scenario and since the requirement is that the messages have to be processed in a single queue in the SAP system (i.e. EOIO), the sender file channel was configured to be EOIO. This ensures that all messages that enters the SAP system are put in a single queue and then processed one after the other.
The Issue
Now if one of the messages that enter SAP system fails during the processing in the ABAP program, the queue gets stuck and all messages after that go into a scheduled state. And one has to manually clear the errored message in order to continue processing the other waiting messages.
The Question
I know this is a default behavior in an EOIO scenario, however is there any way in which if a message fails in the ABAP program then one can automatically push it out of the queue and keep processing the other messages after it ?
Thanks
Bharath

As a general rule I only use EOIO when there is a possibility of dependancy between messages (message 1 must be first and finsihed before message 2 starts). Assuming your just moving the errored message asside, I would assume that EOIO should be just EO.
Alternatively, change the ABAP proxy to handle the error and return a clean status. Exception handling (try/catch) should be used were ever dangerous code is being used.
If alerting in the proxy end point is to much trouble - change your proxy to a sync scenario return the error to PI and fire alerts from there <- I think this should be avoided but it will work.
The main point is the exception handling so that the proxy fails "gracefully".

IDOC Serialization(EOIO) using IDOC Adapter throwing Mapping error

Hello SDN Gurus,
The scenario I am working on is IDOC(PAYEXT & EUPEXR) --> XI (ABAP Mapping) --> Flat File (IDOC Structure).
The IDOCS produced in Appl system may be in the following order
PAYEXT
PAYEXT
EUPEXR
PAYEXT
PAYEXT
PAYEXT
EUPEXR
I need them to be processed in the same order into flat file.
The scenario is working good except for the serialization. So I did the following
Created two entries in IDXQUEUE one for each message type with the same Queue name in XI system.
Created a new rule for the queue and an associated function module. Used this rule in partner profile for both the message types. I used the following link to create the above two steps.
/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
The SAP system in based on WAS 6.4.
I can see the queue name & EOIO in the inbound message header.
I am getting a mapping error in ABAP program. If I inactivate the queue(in Appl system SAP ECC), I don't get any error.
Does anybody had this problem earlier? Please advice.
Thanks
Srini Vaidyam

I found an OSS note to resolve my issue. The note number is 1057573.
Whenever the queue is activated, the sender system will not send the <TABNAM> field value in EDI_DC40 structure. This note addresses this problem.
I found out this by comparing the results from SXI_MAPPING_TEST individually for the message that failed after queue is activated and the message that was successful if the queue is inactivated.
Only thing I noticed now is even if you selected the radio button "Trasfer Immediately" in Partner profile of Appl. system, the messages are not sent. They are getting collected. So we need to manually push them out using WE14.
This forum Rocks.
Thanks.
Srini Vaidyam

Messages are stucked in EOIO Backlog, please help me...

Dear Expert,
I am facing an issue the messages are stucked in EOIO Backlog, Those stucks are not flowing. why it is stucking in Engine status or backlog monitor.
and how it will reprocess those messages.
Regards,
Kiran Polani

Dear Friends,
Actually we developed an Idoc to soap synchronous using BPM in sap pi 7.0. suddenly required changed in field lever at sap r/3 side that's why we stopped communication channel for that interface.
But when we are stopped that interface it is stuked in EOIO Backlog and it is stayed in Holding state. Daily the message count is increasing. But here from sap they are triggering data for same idoc.
For that i have discussed with our team and deleted that interface in existing production enviroment.
now those signals are not stucked in Engine status EOIO Backlog. But my problem is how to delete or cancel existing not flown EOIO messages in Engine status.
Please find the screen shot for your reference.
Regards,
Kiran Polani

How to make EOIO for proxy messages in PI

Hi Experts,
We got different proxy outbound messages from ERP, we need to process all the messages in a sequence as it was sent from ERP, how can we make one queue in PI for all these messages.
Please give me some thoughts for this issue.

Refer to these blogs:
XI: Reliable Messaging u2013 EOIO in ABAP Proxies
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
ABAP PROXY TO FILE u2013 Handling Heavy Volumes in SAP PI
/people/praveen.gujjeti/blog/2010/05/31/abap-proxy-to-file-150-handling-heavy-volumes-in-sap-pi
Regards
Raj

EOIO for sender file adapter

PI picks up the records from a flat file of 500 records and 100 records.
I have selected EOIO as QoS. Gave the queue name.
The issue is that the 5 messages with 100 records each, seem to be not in a sequential order.
Can anyone please help me with this? Did anyone face this issue?
We are on PI 7.0 SP 14.
reg

Hi,
>>>The issue is that the 5 messages with 100 records each, seem to be not in a sequential order.
check if you have specified : Processing Sequence - by date
in sender channel
Regards,
Michal Krawczyk

File not getting picked up JMS sender communication chnanel in EOIO mode

Hi Experts,
We have a scenario to process the messages in sequence via JMS sender comm channel. We changed the jms channel to EOIO, after the change, the channel is in green but no message arrives to the Adapter engine.
We are working on a newly installed PI 7.11 system.
When i change the jms to EO the files are getting picked and processed by the channel from the JMS MQ client.
Is there any setting that needs to be checked or changed?
Are any drivers issue?
Thanks.

Did you create the Queue to be used for the EOIO messages ?
For EO it would used any of existing Queues to process the messages for EOIO you have to mention specific Queue name which has to hold the messages in EOIO fasion.
pls share the config details of JMS Sender Processing Tab. I'm sure once you setup the Queue it should work.
Thanks
Kishore

EOIO issue

Similar Messages

Maybe you are looking for