(File-)Adapter Logging

Hi,
I configured the file adapter as sender (polling on a ftp server on my local machine).
The log of the ftp server shows, that the adapter logged in and downloaded the specified file.
But I can't find the message in any monitoring components, neither in end-to-end monitoring, nor in the xml message monitor.
I can't find any logs concerning the file adapter on the J2EE Server. Is there any possibility to control the function of the file adapter ?
Thanks and best regards,
Linus

Hello,
There is an OSS Note (761921) that describes how to create a trace file for the XI Adapters (on the J2EE).
No need to explain it here. Let em know if you have problem with this note.
Regards,
Mustapha Zehana.

Similar Messages

OS commands from File adapter Trace logs?

Hi All,
I am running some UNIX OS commands from File adapter as showing in below Blog.
Problem is that in SXMB_MONI & in Runtime workbench I can not see any Trace logs written by those UNIX OS commands.
Even I am writing echo messages.
Runtime Workbench says only OS command file executed.
Please guide me where I can see OS trace if some OS command fails?
Any transaction code even at BASIS level exist?
Or the only other way round exist is I need to write log into some files.
/people/daniel.graversen/blog/2008/12/11/sftp-with-pi-the-openssh-way
I am using PI7.1.
Regards

I think no solution, other then writing ABAP code using RFC SXPG_COMMAND_EXECUTE and put log/trace in some table/application.

Where are the Adapter Log Files?

Hello All,
I have an message that just isn't being loaded by the receiving business system and I'd like to examine the receivers log files for additional details to help me debug the problem. I don't know where to look yet. Perhaps the group can offer it's collective advice.
Here's the details of the problem I'm tackling.....
I have a 3rd party system that's trying to send a purchase requisition to an SAP Business System via XI. The message is received by XI correctly. XI correctly performs the transformation and identifies the message interface and selects correct receiver for the message. XI communicates with the receiving business system via the appropriate communication channel.
The message "fails" in the receiving system with the following error:
HTTP server code 500 reason Internal Server Exception explanation Error parsing of SOAP header.
That's not particularly enlighting? What exactly about the SOAP header didn't the receiving system like? Perhaps if I could examine a log file on the receiving system, I could figure out what was preventing the message from being loaded.
A review of TCode SM21 and ST22 on the receiving system - show no errors
The message is being sent to an HTTP receiver channel on an SAP Business System. The URL being posted to looks something like this: http://host:port/sap/xi/engine?type=receiver
That's the URL for the local integration engine's pipeline on the receiving SAP business system, right? SXMB_MONI on the receiving system doesn't show an errors because the SOAP header could not be interpreted. What other log files would I examine on the receiver system to see an error in message parsing?
Thanks for your help! Points will be gladly awarded

Hi,
You can look into the Message Display Tool.
http://server:javaport/MessagingSystem/monitor/montior.jsp
This link will lead you to see the entire SOAP message that is actually sent out of XI and received by XI . You can also see the Adapter Log on this link.
Regards,
Bhavesh

Logging option on file adapter based JNDI

Hello,
While setting up a file adapter based JNDI, I notice under outbound connection, we have logging option where we have rotate logs based on size/time. Could someone please help me understand what does this refers to and how we can use that.
its under - Deployment -> File adapter -> Outbound connection -->"Select a JNDI created by you" -> Logging.
my JNDI, represent to a location where I am writing few specific log content in a text file. Can we handle(rotate) that based on this.
Pls advice.

Hi,
you need to create 40 channels if you have users
as dynamically you can only create:
File Name
Directory
File Type
File Encoding
Temporary Name Scheme for Target File Name
with FTP adapter
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

NFS File adapter donu00B4t generate log file.

Hello!
We have a problem with a File adapter. when adapter catch file, this one don´t archive this file into archive directory.
We have:
Processing mode: Archive.
Archive directory : /XIcom/INT181_GECAT/LOG
This directory is created correctly.
Someone can i help me. Thanks.
Best regards.

Hi ,
>>>NFS File adapter don´t generate log file
Do you mean you are not getting the processed files archived only when the file adapter set to NFS File system ?
Did you try same thing by setting File adapter as FTP ?
If you face same issue with File adpter set in FTP mode also then there is some issue with access to the folders.
Please check this ...
Regards,
Nanda
Message was edited by: Nanda kishore Reddy Narapu Reddy

File Adapter - special character in Filename

Hi,
i have a question concerning file adapter.
Scenario: we are polling files via file sender adapter (FTP).
Problem: if the filename contains a special character, an error is thrown with 'The System cannot find the file specified'
Scope: Special character in filename (not in payload)
Installed: XI 3.0 SP 19 on Linux
Questions:
- what FTP implementation does XI use?
- What do i have to check/upgrade to unicode?
- is it an OS problem or an Java problem or a XI problem?
- or is it not possible copiing files with special characters in filename?
Thank you very much in advance.
Michael

Hi Michael,
The file/FTP adapter supports both passive and active FTP data connection. You can select the data connection while configuring the adapter.
The file/FTP adapter follows specification RFC 959. The specification can be found on the Internet under www.ietf.org/rfc/rfc0959.txt.
For FAQs about the file/FTP adapter, see SAP Note 821267. Please note that you'll need an account to log in on service.sap.com.
Question: How are you specifiying the file name? i.e. Are you using placeholders, like ?, *, *.txt, etc ?
If there's a problem with the filenames, then it should be a problem in the JAVA implementation of the adapter I assume. So you could for instance build your own adapter extension to by-pass that problem.
Just for your information; I haven't encounter a problem with filenames in other projects.
Good luck!

Problem in sender file adapter

Hi all,
I have a sender file adapter using ftp with processing mode delete. But my input file is not getting deleted. In RWB, the adapter satus is green with msg processed sucessfully. I tried with a file name that is not available in the ftp folder, but still the adapter status is green with msg processed succesfully.
Help me debug this error.
Regards,
Jai Shankar.

Are you using Content conversion ?
If adapter monitoring is green, and shows processed successfully, then if you have any errors , you can see in the RWB->Message Monitoring->Audit Log (Message display Tool).
If there is no error, then try to do the cache refresh as I told. Ask Admin help for that. Restarting a Adapter engine may help you here/
Regards,
moorthy

Message File Adapter - XI Integration Server not arriving

We have configured a file adapter to read a file. According to the audit log the file is successfully read and converted to XML; however, the message is never posted to XI. We have checked to make sure that no XI* users are locked and we have bounced the server.
The following error message is listed in the audit log:
Transmitting the message to endpoint http://kansbwul01:50000/sap/xi/engine/entry?action=execute using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server.
The following is the application log:
#1.5#0003BA54D61900190000000C000030E60003EEAAD1138641#1106842349700#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######3e38f290707e11d996610003ba54d619#SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###The running MCF with GUID will be stopped now#1#8fa37160707811d995b00003ba54d619#
#1.5#0003BA54D619001900000014000030E60003EEAAD16F4730#1106842355713#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######3e38f290707e11d996610003ba54d619#SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was stopped successfully.#1#8fa37160707811d995b00003ba54d619#
#1.5#0003BA54D619006000000009000030E60003EEAAD1A4DD9D#1106842359225#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Clustering##com.sap.aii.af.ra.ms.runtime.MessagingSystem.reassignMessages(String, String[])#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.MessagingSystem#Java###Could not redistribute messages due to #1#LockingManager must be initialized before usage.#
#1.5#0003BA54D6190040000000000000316A0003EEAAD9D40B8C#1106842496535#/Applications/ExchangeInfrastructure/AdapterFramework/Services/SecurityService##com.sap.aii.af.security.MessageSecurityServiceFrame.MessageSecurityServiceFrame.start()#######SAPEngine_System_Thread[impl:5]_24##0#0#Info#1#com.sap.aii.af.security.MessageSecurityServiceFrame#Java###QUEUE_CONNECTION_FACTORY: , ERROR_QUEUE: , QUEUE: , JARM_PREFIX: , JARM_USER: , JARM_ENABLED: .#6#jmsfactory/default/QueueConnectionFactory#jmsqueues/default/MessageSecurityErrorQueue#jmsqueues/default/MessageSecurityQueue#XI:Security:#XISecurityUser#false#
#1.5#0003BA54D619004A000000060000316A0003EEAADD1ABF82#1106842551500#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'c5a6ccb89b113e8c92474a4aa0df5858': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#
#1.5#0003BA54D619004A000000080000316A0003EEAADD1AC8F6#1106842551503#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Delivery Exception for guid'96f35561-707e-11d9-a16c-0003ba54d619' - non recoverable error, retry anyway#
#1.5#0003BA54D619004A0000000A0000316A0003EEAADD1ACE8D#1106842551504#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Channel CDWExtFile: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available. - continue processing#
#1.5#0003BA54D6190011000000FD0000316A0003EEAADF49F9C7#1106842588150#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.SpiManagedConnectionFactory()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Plain###This SPIManagedConnectionFactory has the GUID: cc6372c0-707e-11d9-ca96-0003ba54d619#
#1.5#0003BA54D6190011000001030000316A0003EEAADF4ADA00#1106842588207#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.start()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID is started now. (,)#3#cc6372c0707e11d9ca960003ba54d619#com.sap.engine.services.deploy.server.ApplicationLoader@5293b95#cc6372c0707e11d9ca960003ba54d619#
#1.5#0003BA54D6190011000001090000316A0003EEAADF4AEA33#1106842588211#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.start()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was started successfully.#1#cc6372c0707e11d9ca960003ba54d619#
#1.5#0003BA54D6190051000000040000316A0003EEAAE1DFB940#1106842631518#/Applications/ExchangeInfrastructure/Repository#sap.com/com.sap.xi.repository#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0####e63e40d0707e11d9b8020003ba54d619#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "REPOSITORY" ok.#
#1.5#0003BA54D6190054000000170000316A0003EEAAE4BA42E1#1106842679394#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector#J2EE_ADMIN#339####02bf9dd0707f11d9b9830003ba54d619#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D619004C000000080000316A0003EEAAE692D9D6#1106842710366#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0##kansbwul01.erc.ge.com_LB1_148575#Guest#d8164a70707e11d9a3490003ba54d619#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "DIRECTORY" ok.#
#1.5#0003BA54D619004D000000040000316A0003EEAAEB3DF548#1106842788689#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.server.util.BasicJMSClient#WSHAUN#466#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb6000ffffff90]###43ec08c0707f11d99f8b0003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.aii.ib.server.util.BasicJMSClient#Plain###TopicConnectionFactory not found#
#1.5#0003BA54D619004D000000050000316A0003EEAAEB3E07B0#1106842788693#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.server.util.BasicJMSClient#WSHAUN#466#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb6000ffffff90]###43ec08c0707f11d99f8b0003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.aii.ib.server.util.BasicJMSClient#Plain###Exception during JMS startup for topic "SYNCHRONIZED_CACHE"
Thrown:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/jms/topic/xi/TopicConnectionFactory.
 at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:258)
 at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:621)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
 at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
 at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
 at javax.naming.InitialContext.lookup(InitialContext.java:347)
 at javax.naming.InitialContext.lookup(InitialContext.java:347)
 at com.sap.aii.ib.server.util.BasicJMSClient.initJmsResources(BasicJMSClient.java:77)
 at com.sap.aii.ib.server.util.BasicJMSClient.init(BasicJMSClient.java:54)
 at com.sap.aii.ib.server.util.BasicJMSClient.<init>(BasicJMSClient.java:48)
 at com.sap.aii.ib.server.util.ClusterSyncedCache.<init>(ClusterSyncedCache.java:41)
 at com.sap.aii.ib.server.cpa.AdapterMDCache.<clinit>(AdapterMDCache.java:27)
 at com.sap.aii.ib.sbeans.misc.MiscServicesBean.getAdapterMetadata(MiscServicesBean.java:226)
 at com.sap.aii.ib.sbeans.misc.MiscServicesRemoteObjectImpl10.getAdapterMetadata(MiscServicesRemoteObjectImpl10.java:2028)
 at com.sap.aii.ib.sbeans.misc.MiscServicesRemoteObjectImpl10p4_Skel.dispatch(MiscServicesRemoteObjectImpl10p4_Skel.java:284)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
#1.5#0003BA54D6190004000000060000316A0003EEAAED036F71#1106842818407#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D6190004000000120000316A0003EEAAED1F56F6#1106842820236#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D61900040000001E0000316A0003EEAAED2014BF#1106842820285#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D61900040000002A0000316A0003EEAAED20EE43#1106842820341#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D6190004000000360000316A0003EEAAED21A105#1106842820386#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D6190004000000420000316A0003EEAAED2268E0#1106842820438#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D61900040000004E0000316A0003EEAAED233205#1106842820489#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D61900040000005A0000316A0003EEAAED23EDCB#1106842820537#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D6190004000000660000316A0003EEAAED249350#1106842820580#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
#1.5#0003BA54D6190051000000090000316A0003EEAAF39F13CA#1106842929271#/Applications/ExchangeInfrastructure/IntegrationServer#sap.com/com.sap.xi.services#com.sap.aii.ib.core.applcomp.ApplicationComponent#XIDIRUSER#526####97b7c160707f11d9837b0003ba54d619#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "RUNTIME" ok.#
#1.5#0003BA54D619003C0000000C0000316A0003EEAAFD1B729D#1106843088417#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Queue##com.sap.aii.af.ra.ms.runtime.ListenerFinder.run()#J2EE_GUEST#0####b4a1c0b1707e11d98d600003ba54d619#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.ListenerFinder#Java###Message listener could not be created for connection after attempts.#3#localejbs/TestListener#test#10#
#1.5#0003BA54D6190058000000050000316A0003EEAB27D41690#1106843805160#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector#J2EE_ADMIN#635####a1c95a40708111d9887c0003ba54d619#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
The following is the trace file:
#1.5#0003BA54D6190000000000140000316A0003EEAAD72107D8#1106842451248#com.sap.engine.core.service630.container.ReferenceResolver##com.sap.engine.core.service630.container.ReferenceResolver#######Thread[Thread-1,5,main]##0#0#Error##Plain###Component com.sap.aii.af.security has a hard reference to service com.sap.aii.af.service.cpa with manual startup mode.#
#1.5#0003BA54D6190036000000000000316A0003EEAAD94B1302#1106842487558#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
#1.5#0003BA54D6190036000000010000316A0003EEAAD94C908B#1106842487656#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************** CCMS CONNECTOR (System) **************#
#1.5#0003BA54D6190036000000020000316A0003EEAAD94C936D#1106842487657#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
#1.5#0003BA54D6190036000000030000316A0003EEAAD94C9621#1106842487657#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###Tracelevel: 0#
#1.5#0003BA54D6190036000000040000316A0003EEAAD94E292D#1106842487760#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
#1.5#0003BA54D6190036000000050000316A0003EEAAD94F65F2#1106842487842#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###******* Java Monitoring API - Version ********#1#1.8.8#
#1.5#0003BA54D6190036000000060000316A0003EEAAD9525DA5#1106842488036#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
#1.5#0003BA54D6190036000000070000316A0003EEAAD9547512#1106842488173#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Host: , OS: , JDK: .#3#kansbwul01.erc.ge.com#SunOS_sparcv9_5.9#1.4.2_06#
#1.5#0003BA54D6190036000000080000316A0003EEAAD95490A6#1106842488180#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###Calculated library path: /global/usr/sap/LB1/DVEBMGS00/j2ee/cluster/server0/bin/ext/com.sap.mona.api#
#1.5#0003BA54D6190036000000090000316A0003EEAAD954A29A#1106842488185#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###System.load [2] /global/usr/sap/LB1/DVEBMGS00/j2ee/os_libs/libjmon.so#
#1.5#0003BA54D61900360000000A0000316A0003EEAAD95617BA#1106842488280#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Version of JNI library: .#1#3.12 Non-Unicode Version#
#1.5#0003BA54D61900360000000B0000316A0003EEAAD9562000#1106842488283#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Java tracelevel set to .#1#Error#
#1.5#0003BA54D61900360000000C0000316A0003EEAAD9577C95#1106842488372#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Connected () to segment (), , .#5#attach#0#read/write#system mode#40000000 bytes#
#1.5#0003BA54D6190009000000010000316A0003EEAAD97D6C04#1106842490858#com.sap.aii.af.ra.ms.impl.core.queue.Queue##com.sap.aii.af.ra.ms.impl.core.queue.Queue.run()#######SAPEngine_System_Thread[impl:5]_73##0#0#Error##Java###Failed to retrieve message from MessageStore for queue .#2#aef38c80-707d-11d9-a639-0003ba54d619(OUTBOUND)#AFWSend#
#1.5#0003BA54D6190014000000020000316A0003EEAAD988D5C9#1106842491606#com.sap.aii.af.ra.ms.impl.core.queue.Queue##com.sap.aii.af.ra.ms.impl.core.queue.Queue.run()#######SAPEngine_System_Thread[impl:5]_28##0#0#Error##Java###Failed to retrieve message from MessageStore for queue .#2#ea9f3be0-707c-11d9-834f-0003ba54d619(OUTBOUND)#AFWSend#
#1.5#0003BA54D619003F000000000000316A0003EEAAD9CFB274#1106842496250#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://kansbwul01:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.lb1.kansbwul01), due to: HTTP 503: Service Unavailable#
#1.5#0003BA54D619003F000000010000316A0003EEAAD9D09295#1106842496307#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###Confirmation handling failed, due to: #1#Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Service Unavailable#
#1.5#0003BA54D6190046000000000000316A0003EEAAD9E5FAD6#1106842497710#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setCurrentNodeID(int)#######SAPEngine_System_Thread[impl:5]_43##0#0#Info#1#/Version#Plain###Current node set to 1485750#
#1.5#0003BA54D6190046000000010000316A0003EEAAD9E62B77#1106842497723#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setEnvironmentState(int)#######SAPEngine_System_Thread[impl:5]_43##0#0#Info#1#/Version#Plain###Environment state set to : ENV_INCOMPLETE#
#1.5#0003BA54D6190049000000000000316A0003EEAAD9F40CB0#1106842498632#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
#1.5#0003BA54D6190049000000010000316A0003EEAAD9FB0888#1106842499090#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
#1.5#0003BA54D6190049000000020000316A0003EEAAD9FB3838#1106842499102#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
#1.5#0003BA54D6190049000000030000316A0003EEAAD9FB61D0#1106842499113#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
#1.5#0003BA54D6190009000000020000316A0003EEAADA5386CF#1106842504889#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######9998abd0707e11d9cd270003ba54d619#SAPEngine_System_Thread[impl:5]_73##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server#http://kansbwul01:50000/sap/xi/engine/entry?action=execute#
#1.5#0003BA54D6190014000000030000316A0003EEAADA542AB7#1106842504931#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######99afb640707e11d9a86c0003ba54d619#SAPEngine_System_Thread[impl:5]_28##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server#http://kansbwul01:50000/sap/xi/engine/entry?action=execute#
#1.5#0003BA54D619004D000000000000316A0003EEAADAF321D0#1106842515349#com.sap.aii.proxy.xiruntime.web.TransportServlet#sap.com/com.sap.xi.proxyserver#com.sap.aii.proxy.xiruntime.web.TransportServlet.init(...)#J2EE_GUEST#0####a1006c50707e11d99ea30003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Info##Plain###Initialized#
#1.5#0003BA54D619004D000000010000316A0003EEAADAF32B88#1106842515352#com.sap.aii.proxy.xiruntime.web.TransportServlet#sap.com/com.sap.xi.proxyserver#com.sap.aii.proxy.xiruntime.web.TransportServlet.init(...)#J2EE_GUEST#0####a1006c50707e11d99ea30003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Info##Plain###Registered with Adapter Framework Monitor#
#1.5#0003BA54D6190055000000010000316A0003EEAADCAC81FD#1106842544275#com.sap.pmi.io.HttpPostThread##com.sap.pmi.io.HttpPostThread######b1f90ee0707e11d9c4300003ba54d619#Thread[Thread-42,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain###Error sending PMI records to http://kansbwul01:8000/sap/bc/sapi_gate, HTTP response: 404Not found. Please check the HTTP destination "pmistore".#
#1.5#0003BA54D619004A000000050000316A0003EEAADD1ABD1C#1106842551499#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'c5a6ccb89b113e8c92474a4aa0df5858': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#
#1.5#0003BA54D619004A000000070000316A0003EEAADD1AC765#1106842551502#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Delivery Exception for guid'96f35561-707e-11d9-a16c-0003ba54d619' - non recoverable error, retry anyway#
#1.5#0003BA54D619004A000000090000316A0003EEAADD1ACD22#1106842551504#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CDWExtFile: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available. - continue processing#
#1.5#0003BA54D619004A0000000C0000316A0003EEAADD1B3AEE#1106842551532#com.sap.engine.services.ts##com.sap.engine.services.ts#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java#ts_0021##Thread is not associated with any transaction context.##
#1.5#0003BA54D619004A0000000D0000316A0003EEAADD1B41AE#1106842551533#com.sap.engine.services.ts##com.sap.engine.services.ts#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ts.exceptions.BaseIllegalStateException: Thread is not associated with any transaction context.
 at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.rollback(TransactionManagerImpl.java:441)
 at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1756)
 at com.sap.aii.adapter.file.File2XI.run(File2XI.java:1007)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
#1.5#0003BA54D6190011000000790000316A0003EEAADDAE5C4B#1106842561174#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.xi.ibresources factory name: jms/topic/xi/TopicConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D61900110000007A0000316A0003EEAADDAFCE2B#1106842561269#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: jms/topic/xi/TopicConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D61900110000007C0000316A0003EEAADDAFE340#1106842561274#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.xi.ibresources factory name: jms/queue/xi/QueueConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D61900110000007D0000316A0003EEAADDB040CB#1106842561298#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: jms/queue/xi/QueueConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000B20000316A0003EEAADE6877ED#1106842573371#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.aii.af.ispeak.app factory name: ISPXAConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000B30000316A0003EEAADE68A1E8#1106842573382#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: ISPXAConnectionFactory loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000C10000316A0003EEAADE837B81#1106842575141#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setEnvironmentState(int)######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Environment state set to : ENV_COMPLETE#
#1.5#0003BA54D6190011000000C20000316A0003EEAADE83D50E#1106842575164#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.initialize()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Looked up factory : com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl@6cbd9138#
#1.5#0003BA54D6190011000000C30000316A0003EEAADE83D78C#1106842575165#com.sap.aii.af.protocol.ispeak.j2ee.services.ISPStartupService##com.sap.aii.af.protocol.ispeak.j2ee.services.ISPStartupService.onAllAppStart()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Calling onServerStart on ISPClusterContext...#
#1.5#0003BA54D6190011000000E60000316A0003EEAADF147D24#1106842584644#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.ip.me.insttool factory name: InstToolTopicFactoryCreateEmptyImage loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000E70000316A0003EEAADF14A82D#1106842584655#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: InstToolTopicFactoryCreateEmptyImage loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000E90000316A0003EEAADF14B7A3#1106842584659#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.ip.me.insttool factory name: InstToolTopicFactoryFinishImage loader does not exist: . Using default class loader!!!#
#1.5#0003BA54D6190011000000EA0000316A0003EEAADF14DC56#1106842584669#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: InstToolTopicFactoryFinishImage loader does not exist: . Using default class loader!!!#

The problem was the Pipeline URL for the integration server.
http://<server>:50000/sap/xi/engine/entry?action=execute
is the defective URL.
Once we logged into SLD and selected the business system for the integration server we change the pipeline URL to the following
http://<server>:8000/sap/xi/engine?type=entry
we then restarted the J2EE server and it worked fine.

File Adapter in OSB 11g

Hi
I am using a File Adapter created to read a file using OSB 11.1.1.3.0. But after i publish that osb project, i am getting the below warning and file is not been polled by the proxy.
####<Feb 23, 2011 10:08:30 AM IST> <Warning> <JCA_FRAMEWORK_AND_ADAPTER> <wipro-e16351a68> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <dcc2d8a908de630a:59887477:12e50cc23d3:-7ff2-0000000000000084> <1298435910015> <BEA-000000> <PollWork::run exiting, Worker thread will die>
After 600 secs i could see StuckThread error in server.
####<Feb 23, 2011 10:15:01 AM IST> <Error> <WebLogicServer> <wipro-e16351a68> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <dcc2d8a908de630a:59887477:12e50cc23d3:-7ff2-0000000000000092> <1298436301203> <BEA-000337> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "601" seconds working on the request "weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl@dd20cd", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
 java.lang.Object.wait(Native Method)
 oracle.tip.adapter.file.inbound.FilesToProcess.dequeueToProcess(FilesToProcess.java:101)
 oracle.tip.adapter.file.inbound.ProcessWork.run(ProcessWork.java:269)
 weblogic.work.ContextWrap.run(ContextWrap.java:41)
 weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Please help what is going wrong in my approach.
Thanks,
Sesha

I even tired creating a new WM thread and assigned to this proxy.
I have chosen MaxThreadsConstraint option with Maximum of 5 concurrent thread.
Also i have enabled Ignore Stuck Threads in that WM thread.
Now i dont see any thread stuck in the server log, but sametime the file is not been picked by the Proxy which means the error is suppressed alone from displaying in logs..
Thanks,
Sesha

Need help with a simple process with FTP Adapter and File Adapter

I am trying out a simple BPEL process that gets a file in opaque mode from a FTP server using a FTP adapter and writes it to the local file system using a File Adapter. However, the file written is always empty (zero bytes). I then tried out the FTPDebatching sample using the same FTP server JNDI name and this work fine surprisingly. I also verified by looking at the FTP server logs that my process actually does hit the FTP server and seems to list the files based on the filtering condition - but it does not issue any GET or RETR commands to actually get the files. I am suspecting that the problem could be in the Receive, Assign or Invoke activities, but I am not able identify what it is.
I can provide additional info such as the contents of my bpel and wsdl files if needed.
Would appreciate if someone can help me with this at the earliest.
Thanks
Jay

persiandude wrote:
Topic: Need help with if, else, and which statements and loops.
How would I display 60 < temp. <= 85 in java
System.out.println("60 < temp. <= 85 in java");
another question is how do I ask a question like want to try again (y/n) after a output and asking that everytime I type in yes after a output and terminate when saying No.Sun's [basic Java tutorial|http://java.sun.com/docs/books/tutorial/]
Sun's [New To Java Center|http://java.sun.com/learning/new2java/index.html].Includes an overview of what Java is, instructions for setting up Java, an intro to programming (that includes links to the above tutorial or to parts of it), quizzes, a list of resources, and info on certification and courses.
[http://javaalmanac.com|http://javaalmanac.com]. A couple dozen code examples that supplement [The Java Developers Almanac|http://www.amazon.com/exec/obidos/tg/detail/-/0201752808?v=glance].
jGuru. A general Java resource site. Includes FAQs, forums, courses, more.
JavaRanch. To quote the tagline on their homepage: "a friendly place for Java greenhorns." FAQs, forums (moderated, I believe), sample code, all kinds of goodies for newbies. From what I've heard, they live up to the "friendly" claim.
Bruce Eckel's [Thinking in Java|http://mindview.net/Books/DownloadSites] (Available online.)
Joshua Bloch's [Effective Java|http://www.amazon.com/Effective-Java-2nd-Joshua-Bloch/dp/0321356683/ref=pd_bbs_1?ie=UTF8&s=books&qid=1214349768&sr=8-1]
Bert Bates and Kathy Sierra's [Head First Java|http://www.amazon.com/exec/obidos/tg/detail/-/0596004656?v=glance].
James Gosling's [The Java Programming Language|http://www.bookpool.com/sm/0321349806].

Problem with FIle Adapter

Hi
We r facing typical problem with file adapter.
Lets say there are 30 files to be processed by placing an copy in arichive folder by file adapter based on pooling
parameters.
All the 30 files are picked up and we can see the copies in archive folder.
But when we go to RWB and check the audit log,
there we could see only 25 files , the 5 files are missing.
no trace found therre about the 5 files.
This is happening only some times and not to all the files placed in the FTP. Later when the same file is placed back from the Archive folder to the Source folder, the file is being picked and processed succesfully.
unfortunately this is happening on Production server
Any pointers which could trouble shoot this issue.
Regards
shekar chandra

Hi,
Couple of thing which you can try....
1. Use EOIO QoS and check if you still face the issue.
Is some program or application writing files to the directory? If yes I would recommend the use of a temporary name to write the files and then rename them.
Sometimes when an external application connects via FTP and transfers the files...
The file could be picked up by the adapter poll even before the transfer of data is done.
Which is why you will find that the file is archived but there is no xml message created for the same in the Integration engine.
Try increasing the poll interval. This helps sometimes.
Regards,
Sidharth

Receiver File Adapter:Variable substitution :FATAL ERROR

HI all
as per the previous thread :
Receiver File Name Variable Substitution :payload: Fatal Error
in our idoc to file sceanrio, we are using simple graphical mapping.
for dynamic file name , variable field is at Target message type,So on using Variable substitution, again the error is same :
SAXException while parsing XML payload: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) .
Our XI Component version : 2004
WAS 6.4 SP 15
Thanks
AR

Ashutosh,
There is nothing to do with your mapping programs. Its the mistake in ur reciever file adapter configuration for variable substitution.I asked u whether u changed message mapping in order to implement the UDF!!
Did u tried checking the audit log. Ok just to see where u are going wrong, instead of using Payload :... in Variable substitution use Message:..... and give some interface name so that to check whether the file is created with Interface name.
Juz give a try!!!
Best regards
raj.

Overwriting the File in File Adapter

Hi All,
I hav a module processor (in Receiver file Adapter)which checks the existence of the file by name DOWN.flg befor writing the file by the same name at the same location. if the file already exists, then it has to wait until another system deletes (as per the requirement). if not, it has to write the file. I had done this successfully with an FTP receiver. but when i'm moving the same functionality to the local drive(now the receiver is a local directory on the XI Server), then i'm getting the following error.
Error:Attempt to process file failed with java.lang.Exception: Overwriting file '/cpe/data/DEV/XI_/IN/APD/Commander/DOWN.flg' not allowed due to configuration flag
Error:
Exception caught by adapter framework: Overwriting file '/cpe/data/DEV/XI_/IN/APD/Commander/DOWN.flg' not allowed due to configuration flag
these are the errors which i found in the audit log. i din't check the overwrite Existing File option in the Receiver adapter.Can anyone help me out in resolving this.
Anyhelp wud b greately apprecited...
Thnx in Advance.

Hello Jayakrishnan,
Thank you very much for the tip, actualy it was very tricky, since the overwrite existing file option is not possible in the "append" mode on my XI version (SP12). THis is what we have done :
- modify the communication channel to "create" mode and check the "overwrite existing file option".
- activate it
- chanche back to the "append" mode
- activate it again
And then it works !
Thanks for your help
Guislain

Receiver file adapter not responding

Hi guys,
I have 2 interfaces in XI development system that make use of receiver file adapter in order to receive some .txt files. Although these communication channels used to work until yesterday, for some strange reason they stopped functioning, but only in development system. However, I cannot see any error in Runtime Workbench (Communication channel monitoring), it's status is "correctly configured and started" and has a green sign. But, when I sent a file from sender adapter, it is sent correctly, but it never gets received from receiver communication channel.
There is no error in SXMB_MONI either.
In XI production system, the same interfaces are functioning well.
Any ideas?
Best Regards
--Evaggelos

Hi Amit,
I went into Message Monitoring for this interface and I can see all the messages for the last 24 hours that should be written into a file that have status "to be delivered".
When I go into Details -->Audit Log for a single message:
2007-06-13 11:49:33 Success Processing child message of multi-message with message ID ff896d50-198a-11dc-cdfa-00145e694b16
2007-06-13 11:49:33 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-06-13 11:49:33 Success Message successfully put into the queue.
And in Message Data there is the following information:
Status To Be Delivered
Repeatable Yes
Cancelable Yes
Error Category
Error Code
Start 13.06.2007 11:49:33
End
Sender Party
Sender Service TPBS_GR
Receiver Party
Receiver Service TPBS_GR
Interface http://famar.gr:LoyaltyDataMNSToSRS
MI_LoyaltyDataMNSToGR_IB
Quality of Service Exactly Once
Message b2685674-7626-5141-bfa1-13155ad0d25a
Reference
Conversation ID
Serialization Context
Direction INBOUND
Message Type Recv
Profile XI
Connection File_http://sap.com/xi/XI/System
Transport HTTP
End Point http://fmgralxi01:50000/MessagingSystem/receive/AFW/XI
Authorization
Sequential Number 0
Number of Retries 3
Failed 0
Retries 300000
Valid to
Persist Until 13.07.2007 11:49:33
Schedule Time 13.06.2007 11:49:33

Error while using module in receiver file adapter??

Hi,
I am using user defined module(for converting EBCDIC type of data to ASCII type of data) in receiver file adapter, while running the module it is giving erors in audit log
Exception caught by adapter framework: class com.sap.aii.af.mp.module.ModuleLocalHomeImpl0_0 can not be casted to ModuleLocalHome or SModuleLocalHome
MP: exception caught with cause java.lang.ClassCastException: class com.sap.aii.af.mp.module.ModuleLocalHomeImpl0_0 can not be casted to ModuleLocalHome or SModuleLocalHome
Please help.
Thanks.
Madhusudhan.

hi ....Stephan
now we are getting the below exceptions in the message disply tool audit log
Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.Exception.
MP: exception caught with message null
Thanks,
Madhusudhan.

(File-)Adapter Logging

Similar Messages

Maybe you are looking for