Delivery Exception

Hi all,
I am trying to connect to Siebel server throuh iWay Siebel Adapter. It is showing following delivery exception in SXMB_MONI.
com.sap.aii.af.ra.ms.api.DeliveryException: IWAY AFJCA SAPXI cannot process the message via call. Location info is missing for the request
Could anybody help me to solve this issue?
Thanks & Regards,
sekhar

Hi Krishna,
Try this thread..
DeliveryException:: invalid content type for SOAP: TEXT/HTML
SSL Configuration on Visual Administrator (for XI Receiver Soap Adapter)
Web Services error message ! !??
Hope it helps you!
cheers,
Prashanth

Similar Messages

Anyone else have an iPhone 4 with 'Delivery Exception'

One of my 4 iPhone 4 orders is actually on a FedEx truck 'out for delivery', but it will not be delivered today because of a 'delivery exception'. It will stay on the truck until tomorrow, the official release date. Any else experiencing this??

Scratch that...
They still delivered it. I left a 'pre-sign' form and it was waiting for me at home. Hoping my other 3 orders get delivered tomorrow.

APARTMENT NUMBERS!! DELIVERY EXCEPTION!!

I live in a townhouse and DID enter my unit number on both of my orders. I just checked fedex (even though it says out for delivery, my OCD got the best of me) and good thing I did because it says there's a DELIVERY EXCEPTION for no unit number!
I called Fed Ex and they said they can't change it- verizon has to! So I called Verizon *611 and they've updated it, but it has to go to their shipping department and it can take 24-48 hours!!!!!!!!!!! She said it's usually faster, but that's what they have to say!! {word filter avoidance}
So, I'm going to give fed ex a check in about 1/2 hour and hopefully it'll update in time. Otherwise, guess I'll be SOL until I can get to the fedex location to pick it up! Ugh! SO ANGRY RIGHT NOW!!!
So if you had apartment # issues on your order, you may want to call fedex to make sure they have it and if not get on the horn to Verizon to update it ASAP.

cathied wrote:
I live in a townhouse and DID enter my unit number on both of my orders. I just checked fedex (even though it says out for delivery, my OCD got the best of me) and good thing I did because it says there's a DELIVERY EXCEPTION for no unit number!
I called Fed Ex and they said they can't change it- verizon has to! So I called Verizon *611 and they've updated it, but it has to go to their shipping department and it can take 24-48 hours!!!!!!!!!!! She said it's usually faster, but that's what they have to say!! FML!
So, I'm going to give fed ex a check in about 1/2 hour and hopefully it'll update in time. Otherwise, guess I'll be SOL until I can get to the fedex location to pick it up! Ugh! SO ANGRY RIGHT NOW!!!
So if you had apartment # issues on your order, you may want to call fedex to make sure they have it and if not get on the horn to Verizon to update it ASAP.
Thanks for the info and so sorry to hear about that...

How to Handle RFC delivery exception (rfcClientException) in XI?

I have a following scenario.
I have an outbound soap interface (sender) and inbound RFC(receiver). When the soap message is posted it goes to receiver where it has to execute the RFC. It tries to convert the XML to RFC and throws the following exception.
com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Date 'xxxx-xx-xx' has a wrong format at field CREAT_DATE: Unparseable date: "xxxx-xx-xx
I defined the fault message and attached it to the Inbound Interface. I also defined the mapping of receiver exception message to fault message. I am expecting a fault message back to sender which is not happening.
When I go to moni and try to look for the error in the response message I see the following.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Date 'xxxx-xx-xx' has a wrong format at field CREAT_DATE: Unparseable date: "xxxx-xx-xx"</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I am suspecting that since the fault message does not contain this structure it's not able to build it.
How do I handle such runtime exception and transfer it to sender system. Any help would be greatly apperciated.

I have the same problem. The error is as follows:
<?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>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Date '2006/04/09' has a wrong format at field INVALIDITYBEGIN: Unparseable date: "2006/04/09"</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Anyone have any idea, how should I resolve the data format issue?
Thanks

HTTP Response code 500 : Delivery Exception

Hello ,
i have following scenario WS(Client) <--> RFC. I am getting the following error :
Response code 500: File couldnot be posted.
Here are RWB data entries :
2006-03-13 09:45:52      Success      SOAP: request message leaving the adapter (call)
2006-03-13 09:45:52      Success      Application attempting to send an XI message synchronously using connection AFW.
2006-03-13 09:45:52      Success      Trying to put the message into the call queue.
2006-03-13 09:45:52      Success      Message successfully put into the queue.
2006-03-13 09:45:52      Success      The message was successfully retrieved from the call queue.
2006-03-13 09:45:52      Success      The message status set to DLNG.
2006-03-13 09:46:11      Error      Returning synchronous error notification to calling application: Received HTTP response code 500..
2006-03-13 09:46:11      Error      Transmitting the message using connection http://<XiServer>:8000/sap/xi/engine?type=entry failed, due to: Received HTTP response code 500..
//i changed here server name for internal reasons//
2006-03-13 09:46:11      Error      The message status set to FAIL.
2006-03-13 09:46:11      Error      Returning to application. Exception: Received HTTP response code 500.
2006-03-13 09:46:11      Error      SOAP: call failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500.
I did all the things i could do , tested soap service working fine, changed settings in sxmb_adm as well
Please suggest,
Vara

thanks sam,
Well i have the following error message in soap envelope:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
     <SOAP:Body>
          <SOAP:Fault>
               <faultcode>SOAP:Server</faultcode>
               <faultstring>failed to call the adapter engine</faultstring>
               <detail>
                    <s:SystemError
xmlns:s="http://sap.com/xi/WebService/xi2.0">
                         <context>XIAdapter</context>
                         <code>DeliveryException</code>
                         <text><![CDATA[
Please suggest :

Delivery Exception : Scenario File to WS

getting the following exception :
com.sap.aii.af.ra.ms.api.DeliveryException: Peer sent alert: Alert Fatal: illegal parameter
When communicating from file to Ws through BPM . Steps used in BPM :
Receive ( to receive file to deliver to BPM Type Async ; )
Send step Sync
Send step to deliver response to file.
Need help
Krishna

Hi Krishna,
Here is a similar thread..
Web Services error message ! !??
Please check it out..
cheers,
Prashanth

How to create outbound delivery except bapi BAPI_DELIVERYPROCESSING_EXEC

Hi,
I have a problem with bapi BAPI_DELIVERYPROCESSING_EXEC.
I use this bapi to create outbound delivery from delivery due list. But there is no shipping point as a parameter in this function module. So if there is two shipping point in a sales order, only one delivery is created for only one shipping point. How can I solve this problem.
Or Can I create outbound delivery from a sales order with using bapi ?
Thanks.

I think(It's strictly my opinion), if a suitable serial number profile is maintained in plant/material then this assignment should happen automatically!!
**You gotta refer to a functional consultant. I am not very sure..

Beware of iPhone 4S "Delivery Exceptions" from FedEx Today!

Hi there --
I'm a new iPhone 4S Verizon subscriber -- a refugee from AT&T.
If your iPhone hasn't arrive yet -- this could be the reason why:
http://urbansemiotic.com/2011/10/14/fedex-fs-ups-iphone-4s-delivery/
[fixed broken link]

The two iPhone 4S were just delivered.
It was my regular FedEx guy. He looked really worn out. He is always good to me, as I am to him, so I know he got here as fast as he could. He did say there were a lot of iPhones left to deliver.
Setting up the phones via iCloud backup was a breeze. Verizon activation was quick. Beautiful phones. Definitely worth the wait and the angst. SMILE!

RFC to SOAP Scenario -- Delivery Exception

Hi All,
I am working on RFC to SOAP scenario.
On executing a program in the SAP system, the system is throwing a dump stating "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML".
I feel that the error is because of the response not being sent back by the webservice. On executing the webservice independently, it is working fine i.e. sending back the response.
Can anyone suggest the possible reasons for this error and what needs to be done to rectify this?
Thanks,
Ravi Kiran

the return from the Web service must have been an HTML(may be an error page or something)...What kind of authorization does this WS look for ?
Pls check these threads...
SOAP Receiver Adapter Proxy Settings
Receiver SOAP Adapter Error: invalid content type for SOAP: TEXT/HTML

Receiver SOAP - Delivery Exception

Hi,
My scenario is RFC to SOAP.
The problem is in SOAP receiver adpater.
The url and all connection parameters are correct and the scenario is working fine.
But some times the response from SOAP service is like
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Software caused connection abort: recv failed; HTTP 200 OK</SAP:AdditionalText>
The SOAP server is running all the time.
Is it due to connection problem?
Any idea?
Thanks,
Uma
Message was edited by:
Uma Maheswari

I hope you have seen this blog for HTTP errors
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Exception Handling in JDBC Receiver

Hi,
We have a scenario WS to JDBC synchronous. If we inserting the same value we got the unique
constraint error in sxmb_moni level.But the WS response contains delivery exception error. But we
need the Actual error in the response.
How can get this?
Any suggestions..
Regards,
Prakasu

hi gabriel,
I think serializable use for sending data to the DB in a serialized queue.
AutoCommit used for when the data is inserted or updated in a Database it will commit the records.
Disconnect from database used for when our transactions over the chennel disconnect to the database.
But for my reuirement is when we inserted the same record or some varations in the record(like if DB have
the field (number) But we passed the value in Char) that time DB send a Application error response to the
XI server.
We are using WS to JDBC.
The error we can see in sxmb_moni.But the response of WS have simply "Delivery Exception system
error". So with out seeing the sxmb_Moni message we dont know the exact error.So we need the
"DB Application error" response in the WS response.
Thanks and Regards,
Prakasu

Delivery address house number listed twice?

So I just received my shipping notification for my iPhone 6, but the delivery address in Verizon's e-mail has my house number listed twice.
For example:
1325 1325 Sesame St.
Hollywood, CA 90210
I called FedEx and gave them the tracking number, but they said they did not have the address information yet.
Has anyone else seen this? I'm worried this will create a delivery exception and it won't deliver on Friday!
Thanks
-Jim

I have seen this and called verizon multiple times and been lied to every singl time! I had fedex tell a rep that they CAN change the address but verizon still didnt do it! the reps are full of ****

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.

New task record not getting created in BPM workspace.

Hi,
We have a BPM Process which has 2 roles. SKURequester and SKUChangeAnalyst.
When we initiate the flow , it opens up a screen and we populate data and click "SUBMIT".
It goes to ChangeAnalyst for approval.
It is working fine in Development Env.We could see a new task created for ChangeAnalyst once the requester SUBMIT's his task.
But in Test env, Once the requester submit's his task .It's not creating a task row for ChangeAnalyst in BPM workspace.
We verified the roles assigned to the user.Everything is same.
Repeatedly seeing the following error in LOGS.
Please help.
[2013-01-10T08:14:38.823-05:00] [soa_server1_1] [TRACE] [] [] [tid: [ACTIVE].ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: mudumbs1] [ecid: 0000Jk^aH_F9lZX_xt1FiW1GvUks000E9Q,0] [SRC_CLASS: oracle.bpel.services.workflow.client.config.ClientConfigurationUtil] [APP: OracleBPMWorkspace] [dcid: 8c22b87477b0f4ec:7ad8260b:13c21624156:-7ffd-000000000001a629] [SRC_METHOD: getClientConfiguration] WorkflowServiceClientContext: Cannot find client configuration file: wf_client_config.xml
[2013-01-10T08:14:41.684-05:00] [soa_server1_1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: orabpel.engine.pool-9.thread-15] [userId: mudumbs1] [ecid: 0000Jk^_u3x9lZX_xt1FiW1GvUks000E80,0:1054:100000592] [APP: soa-infra] [composite_name: SKUManagement] [component_name: CreateRequest] [component_instance_id: 23520007] [dcid: 8c22b87477b0f4ec:7ad8260b:13c21624156:-7ffd-000000000001a625] [composite_instance_id: 24141524] Database Adapter SKUManagement:Get_Site [ Get_Site_ptt::Get_SiteSelect(Get_SiteSelect_inputParameters,XxskuWizardResultsCollection) ] <oracle.tip.adapter.db.DBAdapterConstants getUniqueProcessIdentifier> Unique process identifier will be SKUManagement_default_SKUManagement_2_7_soa_1f700a1d_07c4_41ed_b74a_795a88fdc1c0_Get_Site[[
[2013-01-10T08:14:41.860-05:00] [soa_server1_1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: orabpel.engine.pool-9.thread-15] [userId: mudumbs1] [ecid: 0000Jk^_u3x9lZX_xt1FiW1GvUks000E80,0:1054:100000592] [APP: soa-infra] [composite_name: SKUManagement] [component_name: CreateRequest] [component_instance_id: 23520007] [dcid: 8c22b87477b0f4ec:7ad8260b:13c21624156:-7ffd-000000000001a625] [composite_instance_id: 24141524] Database Adapter SKUManagement:Get_Site [ Get_Site_ptt::Get_SiteSelect(Get_SiteSelect_inputParameters,XxskuWizardResultsCollection) ] <oracle.tip.adapter.db.ox.TopLinkXMLProjectInitializer initialize> Initializing toplink project for use by the database adapter.[[
[2013-01-10T08:14:42.496-05:00] [soa_server1_1] [ERROR] [] [oracle.soa.bpmn.engine] [tid: orabpel.engine.pool-9.thread-15] [userId: mudumbs1] [ecid: 0000Jk^_u3x9lZX_xt1FiW1GvUks000E80,0:1054:100000592] [APP: soa-infra] [composite_name: SKUManagement] [component_name: CreateRequest] [component_instance_id: 23520007] [dcid: 8c22b87477b0f4ec:7ad8260b:13c21624156:-7ffd-000000000001a625] [composite_instance_id: 24141524] <CubeEngine::handleWorkItem> This was an internal error. The flow was not generated correctly by the BPMN compiler. Root cause : null
[2013-01-10T08:14:42.497-05:00] [soa_server1_1] [ERROR] [] [oracle.soa.bpmn.system] [tid: orabpel.engine.pool-9.thread-15] [userId: mudumbs1] [ecid: 0000Jk^_u3x9lZX_xt1FiW1GvUks000E80,0:1054:100000592] [APP: soa-infra] [dcid: 8c22b87477b0f4ec:7ad8260b:13c21624156:-7ffd-000000000001a625] <BaseCubeSessionBean::logError > *Error while invoking bean "cube delivery": Exception not handled by the Collaxa Cube system.[[*
an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: "java.security.PrivilegedActionException: ORABPEL-02118
Variant not found.
The variable "ReRequesterUserTask_activity12_out" is not declared in the current scope. All variables must be declared in the scope before being accessed.
This was an internal error. The flow was not generated correctly by the BPMN compiler.
Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.security.Security.runAs(Security.java:61)
     at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
     at com.collaxa.cube.engine.CubeEngine._performActionAsSubject(CubeEngine.java:5423)
     at com.collaxa.cube.engine.CubeEngine._performCallbackPerformer(CubeEngine.java:5365)
     at com.collaxa.cube.engine.CubeEngine.callbackPerformer(CubeEngine.java:1249)
     at com.collaxa.cube.engine.delivery.DeliveryHelper.callbackPerformer(DeliveryHelper.java:636)
     at com.collaxa.cube.engine.delivery.DeliveryService.handleCallback(DeliveryService.java:1027)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleCallback(CubeDeliveryBean.java:392)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
     at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
     at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy243.handleCallback(Unknown Source)
     at oracle.bpm.bpmn.engine.ejb.impl.BPMNDeliveryBean_of8dk6_ICubeDeliveryLocalBeanImpl.handleCallback(BPMNDeliveryBean_of8dk6_ICubeDeliveryLocalBeanImpl.java:66)
     at com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMessageHandler.handle(CallbackDeliveryMessageHandler.java:47)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:82)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:619)
Caused by: ORABPEL-02118

Hi Juhi,
Go to transaction RZ20 and check out if the corresponding BAPI is executed. And also check the traces
Regards,
Kalyan

Problem in invoking the partner web service

Hi All,
I have a BPEL process which is compiling successfully and able to deploy in Oracle AS 10.1.3.1. But When I am trying to Initiate it thorws IndexOutOfBoundsException.
I am trying to invoke an operation in the partner service whose message have no part defined as below.
<wsdl:message name="NoPart_InputMessage" />
But I am sure that a message is allowed with out a part as per the WSI basic profile.
How can I invoke such kind of operation from my BPEL. Any thoughts ?
Thank you.

I can see the below exception in logs
<BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:546)
at java.util.ArrayList.get(ArrayList.java:321)
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.wrapInputParts(WSIFOperation_JaxRpc.java:2298)
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.getInputMessageValues(WSIFOperation_JaxRpc.java:2375)
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1622)
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1460)
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeRequestResponseOperation(WSIFOperation_JaxRpc.java:1182)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:431)
at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:416)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:202)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:736)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:371)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3271)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1697)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:184)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:269)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5244)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1083)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:530)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:333)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.evermind.server.ThreadState.runAs(ThreadState.java:622)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)

Delivery Exception

Similar Messages

Maybe you are looking for