Sync/Async - JMS receiver comm. channel not processing

I have a Sync/Async scenario (without bpm) in PI 7.11:
RFC -> PI -> JMS
whereby the JMS receiver comm. channel does not fully process the message.
More specifically, the RFC sender comm. channel gets a message in and passes the message to the JMS channel, but that JMS channel within the RWB comm. channel log only shows the entry:
- Message processing started
The odd twist to this is that when we bring the PI server down, then back up again, (or wait a period of time, still trying to determine this period) the FIRST message attempt does successfully get processed, i.e. the first message on that JMS receiver comm. channel RWB log shows as:
- Channel successfully processed the message: 08499236-387c-11e0-b002-000025bab2c2
- Stored the correlation ID 08499236-387c-11e0-b002-000025bab2c2 of the request JMS message: ID:c3e2d840d4d8d4f24040404040404040c754dc12d8b54ec6 correponding to the XI message: 08499236-387c-11e0-b002-000025bab2c2
- Message processing started
(but then because of an issue on the target system, no response comes back, so then we'll additionally get the log entry:
- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no message received
Any suggestions appreciated on what I can check here to try and figure this out. Possibly because the first message eventually errors out, it is stopping the other subsequent msgs from getting processed...
When I check the audit logs of a 'success' msg vs. a not-successful msg, the success msg has an entry (and subsequent entries) of:
14.02.2011 12:50:19 Information Transform: transforming the payload ...
14.02.2011 12:50:19 Information Transform: successfully transformed
14.02.2011 12:50:19 Information ROB: entering RequestOnewayBean
14.02.2011 12:50:19 Information ROB: forwarding the request message
14.02.2011 12:50:19 Information ROB: leaving RequestOnewayBean
14.02.2011 12:50:19 Information JMS Message was forwarded to the JMS provider succesfully."
14.02.2011 12:50:19 Information XMB Message as Binary was forwarded to the SAP XI JMS service succesfully.
14.02.2011 12:50:19 Information WRB: entering WaitResponseBean
14.02.2011 12:50:19 Information WRB: retrieving the message for 08499236-387c-11e0-b002-000025bab2c2 ...
wheras the non-success msg shows only:
14.02.2011 12:55:30 Information Transform: transforming the payload ...
14.02.2011 12:55:30 Information Transform: successfully transformed
14.02.2011 12:55:30 Information ROB: entering RequestOnewayBean
14.02.2011 12:55:30 Information ROB: forwarding the request message
14.02.2011 12:55:30 Information ROB: leaving RequestOnewayBean
So, we can see that the message is not "forwarded to the JMS provider..." in the non-success case.
And also the sxi_monitor shows these messages with a status of "Log version".
Keith

Hi Siddhesh - yes that was a while back and am trying to remember the resolution. I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver. I can then compare to mine if you'd like. Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.
Regards,
Keith

Similar Messages

Erro in JMS receiver Comm Channel

Hi,
I am working on a scenario File(Sender) JMS (Receiver).The input is a text file The file sender polls this input file and the file sender CC does the content conversion and puts the XML message into the JMS Queue. But in the receiver JMS comm channel i get the error saying
Error sending message in sending to destination ABCF, the message message: TextMessage[null, <?xml version="1.0" encoding="...]: weblogic.jms.common.JMSException: Error sending mess
Please help me on this

Hi,
Please have a look at your message in SXMB_MONI and see if the payload is correct.
Also have a look at the MDT (http://<server>:<port>/MDT) and see what errors occur for your message.
Regards,
Yaghya

PI 7.3 receiver AAE idoc scenario-No receiver comm channel found in ICO

Hi,
I am working in PI 7.3 receiver AAE idoc scenario.When I try to configure Integrated Configuration(ICO),I am not able to see the receiver comm channel in receiver agreement.
What is the reason for this??I have configured the communication channel,but still its not shown in reciver agreement dropdown.
Please help.
Regards,
Sriparna

Hi Sriparna,
In PI 7.3 there is are two separate IDoc adapters: "standard" IDoc adapter and one that is dedicated for AAE (ICO). Make sure that you have used the right one - most probably not, which is why you cannot see the channel in the dropdown list.
Hope this helps,
Grzegorz

IDoc to File scenario... Receiver Comm Channel Error...

Hi Guru,
On the scenario IDoc to file, I'm encountering the ff error on my receiver comm channel (File Adapter)...
ttempt to access the 1 requested objects on 1 failed.
Detailed information:
com.sap.aii.ib.core.roa.RoaObjectAccessException:
Attempt to read object Adapter Metadata File | http://sap.com/xi/XI/System,
type AdapterMetaData from application REPOSITORY on
system REPOSITORY failed. Object does not exist. Detailed
informatio n: SWCV ID: << removed >>
does not exist in Enterprise Service Repository and
System Landscape Directory (ROA_MOA_NOTCOMPLETED)
<< removed >>
Attempt to access the 1 requested objects on 1 failed.
Detailed information:
com.sap.aii.ib.core.roa.RoaObjectAccessException:
Attempt to read object Adapter Metadata File | http://sap.com/xi/XI/System,
type AdapterMetaData from application REPOSITORY on
system REPOSITORY failed. Object does not exist. Detailed
informatio n: SWCV ID: e5a519a0766111dca2e8e95d0a115642
does not exist in Enterprise Service Repository and
System Landscape Directory (ROA_MOA_NOTCOMPLETED)
Attempt to access the 1 requested objects on 1 failed.
Detailed information:
com.sap.aii.ib.core.roa.RoaObjectAccessException:
Attempt to read object Adapter Metadata File | http://sap.com/xi/XI/System,
type AdapterMetaData from application REPOSITORY on
system REPOSITORY failed. Object does not exist. Detailed
informatio n: SWCV ID: e5a519a0766111dca2e8e95d0a115642
does not exist in Enterprise Service Repository and
System Landscape Directory (ROA_MOA_NOTCOMPLETED)
Please advise what possible solution can we apply?
Thanks.
Edited by: Rob Burbank on Dec 17, 2010 10:43 AM
Edited by: Rob Burbank on Jan 3, 2011 12:03 PM

Hi,
You can check File adapter metadata under Basis SWCV -->namespace http://sap.com/xi/XI/System in IR.
-Rahul

Error in receiver comm channel

Hi All,
   I am working on scenario file to file with out IR.just picking up the file from sap app server and placing in target ftp server.
My sender comm channel is picking the file fine but when in receiver comm channel i am getiing error as
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Unknown payload format 0 in message"
"Attempt to process file failed with Unknown payload format 0 in message"
i have checked in content of the file it contains no special character. are any security is being maintained.
please advise on this.
Thanks,
Bhaskar

Hi Jude,
I have checked in sender comm channel in message display tool under message content i am getting error as below.
messagecontent
message part [soap document]
500   Internal Server Error
SAP J2EE Engine/6.40
Application error occurred during request processing.
Details:   Error [javax.servlet.ServletException: null], with root cause [java.lang.NullPointerException: null].
Exception id: [00145E474044003F000018AD00003E0D000471A1CBF6A02A]
what would be the error and how can i find it.
Is this basis related issue?
Thanks,
Bhaskar

Creating SOAP Receiver comm.channel for axis web service

Hi,
I created Soap Receiver comm. channel fro Axis web service like below:
*Target URL* : http://<IP>:<Port>/<x>/service
*User:* <user>
*Password :* <password>
*SOAP Action:* <target namespace>/method
when i drive PI Message that use Soap Receiver it get error below
I do same method for .Net web service, it runs properly.
How can i solve this problem?
Error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID B3004965647F340C997B5F2CC9EA7E22 Software Component 4CF44F80503211DEB2A0D3F40A194B29</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID B3004965647F340C997B5F2CC9EA7E22 Software Component 4CF44F80503211DEB2A0D3F40A194B29</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
I did all but nothing changed?
I have doubt about axis side. Because respose like below.
<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="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
May be Soap Receiver setting for axis web service must be different.
Thanks.

What to be given in JDBC receiver comm channel?

Hi
I have given
JDBC driver:com.sap.aii.messaging.adapter.ModuleXMB2DB
Connection:jdbc:microsoft:sqlserver://sapep:1433;DatabaseName=SAPXI
am i giving correct params?
please help me where and how to check whether iam using correct params in my JDBC receiver comm channel.
Thanks

Hi Datta,
Check
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
/people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter
Best regards, Maksim Rashchynski.

JDBC Sender channel not processing the messages

Hello,
From yesterday onwards JDBC Sender channel not processing the messages. In CC monitoring it is showing in Green Led and status is functioning. Cahnnel is polling for messages to DB server as per polling interval. But it is not processing the msg's. Under Processing detials for cluster node it is showing only "Processing Started" for each polling interval.
I have done the check in DB server by executing the query in the channel, whether there are any records are exisitng or not. There are 1000+ records.
Previously the parameter "Disconnect from DB after processing each message" was not set. I have set the parameter and activated in Productiion. Still the messages are not processing by channel
What was the problem? How to rectify with this.
Cheers
Veera

Check in the Visual Admin >Cluster> "LOCKING ADAPTER"
we get a option of Display Locks .Check for an entry with
NAME : $XIDBAD.JDBC2XI
reset the locks and restart the CC ,now it works fine.
Note 1083488 - XI FTP/JDBC sender channel stop polling indefinitely(04/04S)

Issue with JMS Receiver Comm. Channel using Seeburger AttribMapper

Hello,
I'm using a JMS_RECEIVER Comm. Channel on which the Seeburger AttribMapper is configured (I need to use the DCJMSCorreleationID dynamic attribute).
In the module tab, I added a new module:
Module Name Module Type Module Key
localejbs/Seeburger/AttribMapper Local Enterprise Bean map
And I added the following parameter:
Module Key Parameter Name Parameter Value
map http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
When processing a message, I get the following error on the Communication Channel Monitoring:
Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of AttribMapper.
Does anyone has an idea on how to fix this problem?
Thanks for your help!
Benoit

HI,
Refer the discussion of
Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper
Dynamic subject in AS2 receiver
Thanks
Swarup

Sync/Async JMS without BPM - No receiver specified in message object

Hi All,
My scenario is Proxy - JMS - Proxy. I have chosen to do this without BPM and had followed closely to the instructions given in various help documents/blog/forum threads. During testing, the proxy returns a system fault 'No receiver specified in message object'. In RWB it indicates that the correlation is correct and the JMS Receiver adapter is getting the response, below is part of the audit log:
2009-08-03 18:12:32 Information WRB: retrieving the message for de80831d-97f5-08f1-bdaf-00145e6883af ...
2009-08-03 18:12:33 Information WRB: retrieved the message: ApplicationResponse
2009-08-03 18:12:33 Information WRB: leaving WaitResponseBean
2009-08-03 18:12:33 Information MP: leaving
2009-08-03 18:12:33 Information The message was successfully delivered to the application using connection JMS_http://sap.com/xi/XI/System.
2009-08-03 18:12:33 Information The message status was set to DLVD.
When I check SXMB_MONI in XI-ABAP, I see 2 messages with status 'System Error - Restart not possible' and 1 with status 'Log Version'. The message with status 'Log Version' is the respond. The other 2 messages has the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_RECEIVER</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver specified in message object</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
It seem to me that the system does not know where to go/what to do next after returning to the JMS Receiver adapter. I am at a lost what could have gone wrong. Here is how I've done my configuration.
Repository
- Sync Sender Interface for R/3 Backend
- Sync Receiver Interface for MQ
- Async Sender Interface for the reply
Directory
- 1 CC for JMS Recevier
- 1 CC for JMS Sender (for the respond)
- 1 CC for Proxy Sender
- 1 Interface Determination
- 1 Receiver Determination
- 1 Receiver Agreement for JMS Receiver
- 1 Sender Agreement for the reply
Any help is appreciated. Thanks.

Hi Prateek,
This is what was tried in my first case. I did exactly what was given in that link.But since the Message id being 32 bytes and length of correlation id is 24 bytes id is getting truncated.
So its not working fine.
@ke i am having a look at the note will update you on this
Thanks for your response
Rgds
Aditya

Sender JMS Synchronous communication channel not picking up files from JMS

Hello,
One of our Sender JMS synchronous communication channel (used Sync/Async bridge in the module section to make it Synchronous) is not picking up files from JMS system though the channel looks to be active (greeen).
When I am trying to stop the channel, it is giving error as "1 of 1 administered and selected channels have not been stopped", and after this when I start the cannel again it shows green but not picking up any files.
if anyone is haivng any solution for this, please reply back.
Thanks in advance.

Messages available in JMS system? please check queue's if message were there and it is not picking up then some thing wrong with cc.
simple solution create new communication channel with same details and try to use the same.

Sync/Async BPM scenario : Problem at Integration Process..!!

Hi All,
I am doing Sync/Async BPM scenario.
start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoR/3)->Send(Send Response) ---> stop.
When Iam trying to Activate, Integration process giving errors as
Source parameter AA_Payment_Req | http://XXXXXXXXX.com/SAP_PI/DirectSales/Payment not set Target parameter AA_Payment_Response | http://XXXXXXX.com/SAP_PI/DirectSales/Payment not set
Warning: Container element Response is defined but is neither initialized nor used.
But I am using them in the BPM. The same kind of scenario is working for another interface which is already running in production. When I tried to check that interface it is showing only Warning message as Container element Response is defined but is neither initialized nor used.
I tried deleting and creating again and still it is showing the same error.
Can anyone please suggest what might be the problem.
Regards
Deepthi

Hi,
could you pls let me know how its solved, while i am trying the same i am also getting the same problem..
could you pls explain bit more on this.
Thanks,
Venkat.

Problem in File Receiver comm channel

Hi,
I can't see anything in the Recevier communication channel in the RWB > Component Monitoring>Comm. channel monitoring-->Comm. channels.
I do have selected my comm channel.Its showing the message as "Comm. channel is configured correctly and started". But I cant see msgID and Explanation or error. Even, I cant fine any info in Error log.
The diagnosis i did as follows. Let me know if u come across any thing.
Checked the logs in VA but i didnt found any information and is not upto date. Bad luck
*Recreated the Rcvr comm channel again and teste. Nohope.
In the MONI its showing successfull, but i cant see output at destination.
*cache is uptodate
I have checked the queues, nothing got stuck.All queues are clear.
*I cant restart the Server since it is in production.
Your suggestions are highly appreciated.
Thanks
SRI

Nilesh,
All the things you mentioned are done by XI IS. FYI plz chk below..
Send binary file "/home/dpiadm/xi/tmp/passthru/EDI_250123.rpz", size 60, character encoding 8859_1 with QoS EO
2007-10-19 13:48:43 Success MP: Entering module processor
2007-10-19 13:48:43 Success MP: Processing local module localejbs/SFTPFileUploadDownloadAdapterModule
2007-10-19 13:48:43 Success 192.133.217.6 /XI/SFTPTest pimsp kuljasimsim EDI_250123.rpz /home/dpiadm/SridharRajuMahali /home/dpiadm/xi/tmp/passthru/ EDI_250123.rpz Enable
2007-10-19 13:48:43 Success EDI_250123.rpz
2007-10-19 13:48:43 Success SFTPOutBoundEDIFileToFile
2007-10-19 13:48:43 Success SFTP_Sender_File
2007-10-19 13:48:43 Success 8878c990-7e6b-11dc-8137-001a4b065b86
2007-10-19 13:48:43 Success SFTPServerNameOrIpAddress 192.133.217.6
2007-10-19 13:48:43 Success Indiashining.txt SFTPOutBoundEDIFileToFile SFTP_Sender_File 8878c990-7e6b-11dc-8137-001a4b065b86 SFTPOutBoundEEIFileToFile
UNDEFINED
2007-10-19 13:48:43 Success Host Key Verified
2007-10-19 13:48:43 Success Socket Opened for Transport and connected..
2007-10-19 13:48:43 Success SFTP SshClient is connected
2007-10-19 13:48:43 Success Authentication Method is Public Key
2007-10-19 13:48:43 Success Ssh2 Client is Connected and Authenticated
2007-10-19 13:48:43 Success pimsp kuljasimsim
2007-10-19 13:48:43 Success /XI/SFTPTest
2007-10-19 13:48:43 Success /XI/SFTPTest
2007-10-19 13:48:43 Success localFolder2 + dropFileName2 /home/dpiadm/xi/tmp/passthru/EDI_250123.rpz
Entering to download file
2007-10-19 13:48:43 Success Current Directory before LCD0 : /home/dpiadm
2007-10-19 13:48:43 Success Current Directory After LCD0 :/home/dpiadm/xi/tmp/passthru
2007-10-19 13:48:43 Success download completed
2007-10-19 13:48:43 Success MP: Processing local module localejbs/CallSapAdapter
2007-10-19 13:48:43 Success Application attempting to send an XI message asynchronously using connection File_http://sap.com/xi/XI/System.
2007-10-19 13:48:43 Success Trying to put the message into the send queue.
2007-10-19 13:48:43 Success Message successfully put into the queue.
2007-10-19 13:48:43 Success The application sent the message asynchronously using connection File_http://sap.com/xi/XI/System. Returning to application.
2007-10-19 13:48:43 Success MP: Leaving module processor
The message was successfully retrieved from the send queue.
2007-10-19 13:48:43 Success Confirmation mode test found. File sent.
2007-10-19 13:48:43 Success The message status set to DLNG.
2007-10-19 13:48:44 Success The message was successfully transmitted to endpoint http://quark:8005/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System.
2007-10-19 13:48:44 Success The message status set to DLVD.
2007-10-19 13:48:44 Success The message was successfully delivered.
Note:- I AM NOT ABLE TO SEE ANYTHING IN THE RCVR COMM CHANNEL(RWB).
any Idea about, where can I see the message if it got stuck in Integration server apart from logs
Thanks
Sri Raj

File Receiver Comm Channel in error

Hi All,
I am getting below error in my receiver communication channel -
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Unable to clone File Adapter receiver channel for parallel processing
This is just FiletoFile scenario. I am trying to use VARIABLE SUBSTITUTION here to give dynamic name to the file at receiver. I haven't use FCC here.
If I dont use VARIABLE SUBSTITUTION then scenario is working fine.
Thanks & Regards,
Rashmi Joshi

Hi Abhradeep,
I am getting new error now -
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: Vname
I have changed the reference value as -
Emp_ID
payload:MT_File,1,Record,1,Emp_ID,1
Thanks & regards,
Rashmi Joshi

File2file-receiver-comm channel-incorrect ftp server

Hello,
The scenario is file (xml) to file (xml) to jumpstart the learning process.
config details:-
a) sender
ftp file "/xi_input.dat" from server 10.20.30.98
processing mode: "delete"
b) receiver
ftp file "/xi_output.dat" to server 10:20:30:98
file construction mode: "create"
Expected result:-
file at sender should be read by XI and deleted. Output file should be created by XI.
Acheived result:-
SXMB_MONI status is "processed successfully-(white black flag). XI read sender file "xi_input.dat" and it was deleted as requested in the config. But there was no output file "/xi_output.dat". Then chaged the FTP server at receiver to 10.20.30.98. This resulted in creation of /xi_output.dat
Question:-
Though I got the desired result, I was unable to find the error from SXMB_MONI by myself.
I could manage to debug and find the sequence of actions, here it goes:-
tointerfacename->service->channel->file adapter->ftp mode
but there is no trace about why /xi_output.dat is not created via ftp (due to typo error in server name).
Please look at the log and advise why SXMB_MONI didn't report this error? or point me how to debug better.
<SAP:ToInterfaceName>mi_name_in</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>urn://file2file_2</SAP:ToInterfaceNamespace>
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">sevice</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">cc_in</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">File</SAP:AdapterName>
<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">AE</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">File</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0.0527</SAP:MessageProtocolVersion>
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">FTP</SAP:TransportProtocol>
<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />

Thanks. The error is exactly what I was looking for.
In RTW->CC->log
Error Attempt to process file failed with Error occurred while connecting to the FTP server "10:20:40:92:21": java.net.UnknownHostException: 10:20:40:92
Now RTW still has red for receiver communication channel with the note
"In the Last 4 Hours Server 0 50_40103 Communication channel is correctly configured and started "
I performed stop and start to the communication channel it results in red status. However it is creating the file without problems.
Any way to make communicaton channel green?

Sync/Async - JMS receiver comm. channel not processing

Similar Messages

Maybe you are looking for