Com.sap.aii.messaging.adapter.trans.TransformException:'java.lang.NullPoint

Hi, This is Prasad
We are using 7.0 with SP15, i am using MTB module at receiver side ,we are getting following error.
Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.NullPointerException'; nested exception caused by: java.lang.NullPointerException
And we are passing following FCC Parameters
Transform.Class = com.sap.aii.messaging.adapter.Conversion
Transform.ContentType = text/xml;charset=utf-8
xml.Record.fieldFixedLengths
xml.Recordset.fieldSeparator
xml.conversionType= StructXML2Plain
xml.recordsetStructure = Recordset,Record
Please help me out ASAP

Hi Stefan,
I am a little bit confused with the parameter "Transform.ContentType".
According to your post it should be "TransformContentType" but the document has not yet been updated. At least when I search within SDN for the document I still get the old version with the dot.
In addition there is OSS note 1131655 from September 2008 (pretty new) and there SAP still refers to parameter "Transform.ContentType".
So, I assume the parameter with the dot is the correct one, right?
Klaus

Similar Messages

Jar file containing: com.sap.aii.messaging.adapter.Conversion package??

Hi! Gurus
Can you please let me know the name of the Jar/library file containing com.sap.aii.messaging.adapter.Conversion package.
Your help is greatly appreciated!!
Thank you,
Patrick

> Can you please let me know the name of the Jar/library file containing com.sap.aii.messaging.adapter.Conversion package.
aii_msg_runtime.jar
http://wiki.sdn.sap.com/wiki/display/XI/WheretogetthelibrariesforXI+development

Com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number

Experts,
My scenario is sync File to SOAP.
I am using File - bpm - soap - bpm - file.
I am trying to send a query to google in file with SOAP message and expecting a response back.
But in SOAP Adapter I am getting this error.
com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number
2008-04-05 07:49:31 Success Message successfully received by messaging system. Profile: XI URL: http://xibox:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2008-04-05 07:49:31 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
2008-04-05 07:49:31 Success Message successfully put into the queue.
2008-04-05 07:49:31 Success The message was successfully retrieved from the request queue.
2008-04-05 07:49:31 Success The message status set to DLNG.
2008-04-05 07:49:31 Success Delivering to channel: CC_SOAP_Google
2008-04-05 07:49:31 Success MP: entering
2008-04-05 07:49:31 Success MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2008-04-05 07:49:31 Success SOAP: request message entering the adapter with user J2EE_GUEST
2008-04-05 07:49:31 Error SOAP: call failed: com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number:
Could you pls tell me which piece I missed?
Regards,
AV.

I'm sending below SOAP message.
<?xml version='1.0' encoding='UTF-8'?>
<soap11:Envelope
 xmlns="urn:GoogleSearch"
 xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/">
<soap11:Body>
 <doGoogleSearch>
 
<key>1</key>
 <q>shrdlu winograd maclisp teletype</q>
 <start>0</start>
 <maxResults>10</maxResults>
 <filter>true</filter>
 <restrict></restrict>
 <safeSearch>false</safeSearch>
 <lr></lr>
 <ie>latin1</ie>
 <oe>latin1</oe>
 </doGoogleSearch>
</soap11:Body>
</soap11:Envelope>

Com.sap.aii.messaging.util.URI$MalformedURIException: no scheme

Hello Experts,
We are still configuring our XI in a RFC-XI-SOAP Scenario. We did all the Interface- and Message- Mapping, we configured our Business System and Business Services. But if we send a message from our R/3 4.6c system to the Web Service via the XI, we receive the following error messages: MP: exception caught with cause com.sap.aii.messaging.util.URI$MalformedURIException: no scheme. The error appears in the SOAP Adapter together with a com.sap.aii.af.ra.ms.api.RecoverableException with the message no scheme.
Does anyone know, why this error appears? What can we do to avoid this error?
Thanks for the answer! I appreciate every kind of answer.
Im looking forward to read your answers.
Best Regards
Philipp

Hello Bhavesh,
after we have checked the SOAP Receiver, we got the following exception:
ErrorCode: GENERAL ErrorText: com.sap.aii.af.ra.ms.api.DeliveryException: Connection timed out: connect.
Does this error show that we are through with our customizing?? Or is this still a problem on our xi??
Best Regards
Philipp

Replacement of com.sap.aii.messaging.lang.Binary; in PI7.11

Hi,
After upgrade to PI7.11 from XI3.0,I am trying to adapt an adapter module which uses following import statement:
import com.sap.aii.messaging.lang.Binary;
But I am not able to find the equivalent in PI7.11.
Can anyone please let me know.
Thanks.
Regards,
Shweta

import com.sap.aii.af.service.cpa.BinaryData worked.

Why "com.sunopsis.graphical.frame.j: Wrapped exception java.lang.NullPoint"

when click Model-><table>->control->error
com.sunopsis.graphical.frame.j: Wrapped exception java.lang.NullPointerException said:
 at com.sunopsis.graphical.frame.bl.c(bl.java)
 at com.sunopsis.graphical.r.p.b(p.java)
 at com.sunopsis.graphical.r.x.actionPerformed(x.java)
 at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
 at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
 at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
 at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
 at javax.swing.AbstractButton.doClick(Unknown Source)
 at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
 at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(Unknown Source)
 at java.awt.Component.processMouseEvent(Unknown Source)
 at java.awt.Component.processEvent(Unknown Source)
 at java.awt.Container.processEvent(Unknown Source)
 at java.awt.Component.dispatchEventImpl(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
 at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
 at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Window.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.run(Unknown Source)

faint!
it is ok again after restart

Unable to start service 'com.sap.aii.adapter.jms.svc'

Hi people,
After I have successfully deployed the external drivers jdbc/jms drivers on a PI 7.1 system trough JSPM using the com.sap.aii.adapter.lib.sda file but now the com.sap.aii.adapter.jms.svc and the com.sap.aii.adapter.jdbc.svc do not want to start up. When checking the log DefaulTrace log file I found the following error Reported reason: Service com.sap.aii.adapter.jms.svc is not loaded Any ideas on what the problem could be?

Hi people,
Thanks for all the ideas. I have followed all the notes and guides to prepare the SDA file ie editing the XML file and adding the JAR files.
The problem was that somewhere along the line the provider.xml file of the old aii_af_jmsproviderlib.sda and the new com.sap.aii.adapter.lib.sda file seeming ot "merged" during my struggles.
The provider.xml file of the SDA which I tried to uploaded had the two reference entries which actually belong to the old aii_af_jmsproviderlib.sda in as well as the correct reference entry. Once I removed these incorrect reference entries the services started up correctly.
I found the error mention above by firstly renaming the DefaultTrace_X.trc file and restarting the JAVA stack. I then stepped through each line of the newly created DefaultTrace_X.trc file from the top down and found the following entries:
1) Cannot resolve component library:sap.com/com.sap.aii.adapter.lib because referenced component Reference strong to library com.sap.aii.messaging.runtime not found#
2) Cannot resolve component service:sap.com/com.sap.aii.adapter.jdbc.svc because referenced component library:sap.com/com.sap.aii.adapter.lib not resolved#
3) Cannot resolve component service:sap.com/com.sap.aii.adapter.jms.svc because referenced component library:sap.com/com.sap.aii.adapter.lib not resolved#
In line line 1 I saw that it was referencing the com.sap.aii.messaging.runtime which seemed suspect. Luckily I still had the original SDA file and when comparing it to the uploaded SDA file I found the incorrect entry.
Thanks again for all the help

Error for package com.sap.aii.mapping.lookup

Hi All
I am writing a code for the DB lookup. When I import the package in the Message
Mapping (Advance Function) I am getting an Error.
C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map6af6f7d1335111dc9b51000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:3: package com.sap.aii.mapping.lookup does not exist
import com.sap.aii.mappingtool.tf3.;import com.sap.aii.mappingtool.tf3.rt.;import java.util.;import java.io.; import java.lang.reflect.;import com.sap.aii.mapping.lookup.; ^
C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map6af6f7d1335111dc9b51000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:57: cannot resolve symbol symbol : class Channel location: class com.sap.xi.tf._MM_File2JMS_ Channel channel = null;
C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map6af6f7d1335111dc9b51000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:58: cannot resolve symbol symbol : class DataBaseAccessor location: class com.sap.xi.tf._MM_File2JMS_ DataBaseAccessor accessor = null; ^
Thanks
Farooq.

Hey satish I am getting same Error:
C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map7801d381335311dc8660000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:3: package com.sap.aii.mapping.lookup does not exist import com.sap.aii.mappingtool.tf3.;import com.sap.aii.mappingtool.tf3.rt.;import java.util.;import java.io.; import java.lang.reflect.;import com.sap.aii.mapping.lookup.;import java.io.*; ^ C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map7801d381335311dc8660000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:57: cannot resolve symbol symbol : class Channel location: class com.sap.xi.tf._MM_File2JMS_ Channel channel = null; ^ C:/usr/sap/SXI/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map7801d381335311dc8660000c2967ead8/source/com/sap/xi/tf/_MM_File2JMS_.java:58: cannot resolve symbol symbol : class DataBaseAccessor location: class com.sap.xi.tf._MM_File2JMS_ DataBaseAccessor accessor = null; ^ 3 errors

When i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

when i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

Hi, Michal
I have read your Weblog. It makes sense to me. Thanks a lot for your help! However, I still have some questions and listed them as following. Could you please help to answer them?
Q1: I am new to SAP-XI. So I have no idea about TCODE-SXMB_ADM. Could you introduce more details about it?
Q2: The XI system I am using is running on SAP-ICC's machine. The tools I can use are:
1.Builder for Integration Repository
2.Builder for Integration Configuration
3.System Landscape Directory
4.Runtime Workbench
5.Administration System (for Repository, Directory, Runtime)
Please note that I do not have a complete control on this SAP-XI. Do you think whether or not I can set the timeout parameter by following the instructions provided in your Weblog?
For more details about my SAP-XI, please access the following Web page:
http://iccxi.sap.com:58000/rep/support/admin/index.html
Q3: The following messages are extracted from the SAP-XI. Wish they are hepful to solving my problem.
2006-06-19 05:12:16 Success The message was successfully received by the messaging system. Profile: XI URL: http://iccxi.sap.com:58000/MessagingSystem/receive/AFW/XI
2006-06-19 05:12:16 Success Using connection AFW. Trying to put the message into the request queue.
2006-06-19 05:12:16 Success Message successfully put into the queue.
2006-06-19 05:12:16 Success The message was successfully retrieved from the request queue.
2006-06-19 05:12:16 Success The message status set to DLNG.
2006-06-19 05:12:16 Success Delivering to channel: ValidationRequestHandlerServiceChannel
2006-06-19 05:12:16 Success SOAP: request message entering the adapter
2006-06-19 05:12:37 Success SOAP: call failed
2006-06-19 05:12:37 Error SOAP: error occured: java.net.ConnectException: Connection timed out: connect
2006-06-19 05:12:37 Error Exception caught by adapter framework: Connection timed out: connect
Thanks
Menghua Li

Where can I find the Java Document of com.sap.aii.af.ra.ms.api.Message

Com.sap.aii.af.ra.ms.api.Message is class that would be used in Adapter Module development, but I found I can't find the document of it in neither Adapter Module related document nor XI Mapping related document.
Anyone can help me?

YiNing,
Did you check this link,
http://help.sap.com/saphelp_nw04/helpdata/en/87/3ef4403ae3db12e10000000a155106/content.htm
Does it help? Also did you look into the Java Docs Section,
https://help.sap.com/javadocs/index.html
Regards
Bhavesh

Another SOAP Sender adapter "com.sap.aii.af.mp.module.ModuleException" erro

I am working on a synchronous scenario SOAP <-> XI <-> RFC.
This worked fine, when I run it without SOAP adapter, direct via XI Pipeline.
Now I want to use the SOAP sender adapter, but get the error as described below this post.
As this is a real new XI installation, some patches or updates might be required to make it work. Or some adapter modules ?
Any suggestions on how to solve this problem will be rewarded.
What worries me a bit is the line " " in the error description.
Extra info: I use SoapSonar as a test webservice client. The error is the message as received in te test client.
<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ModuleUnknownException</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/645_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#9 $)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hi Chandravadhana,
The colon should be there :
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
Regards
Suraj

Com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc don't start

Hello,
In order to configure JMS Receiver Adapter to access Websphere Application Server 7.0, I have recently deployed file com.sap.aii.adapter.lib.sca with the following libraries:
com.sap.aii.adapter.lib_api.jar
com.ibm.ws.ejb.thinclient_7.0.0.jar
com.ibm.ws.orb_7.0.0.jar
com.ibm.ws.sib.client.thin.jms_7.0.0.jar
com.ibm.ws.runtime.jar
javax.j2ee.jms.jar
The communication channel can reach the queue but when I send a message it fails because services sap.com/com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc are not started.
Checking dev_server0 file I found the following error.
==============================================================================================
Service com.sap.aii.adapter.jdbc.svc start ================= ERROR =================
com.sap.engine.frame.ServiceException: Could not obtain an initial context due to a communication failure. Since no provider
URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make sure that any
bootstrap address information in the URL is correct and that the target name server is running. Possible causes other than
an incorrect bootstrap address or unavailable name server include the network environment and workstation network configurati
on.
at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:151)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make
sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible caus
es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,
port=2809 vmcid: 0x4942f000 minor code: 3586 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:100)
... 6 more
Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,port=2809 vmcid: 0x4942f0
00 minor code: 3586 completed: No
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:425)
at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:436)
at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:187)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:120)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:209)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
... 16 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:522)
at java.net.Socket.connect(Socket.java:470)
at java.net.Socket.<init>(Socket.java:367)
at java.net.Socket.<init>(Socket.java:180)
at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:270)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
... 28 more
Service com.sap.aii.adapter.jms.svc start ================= ERROR =================
com.sap.engine.frame.ServiceRuntimeException: Could not obtain an initial context due to a communication failure. Since no pr
ovider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make sure t
hat any bootstrap address information in the URL is correct and that the target name server is running. Possible causes othe
r than an incorrect bootstrap address or unavailable name server include the network environment and workstation network conf
iguration.
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:171)
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.start(AdapterServiceFrameImpl.java:125)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make
sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible caus
es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5) vmcid: 0x4942f000 minor co
de: 775 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:163)
... 7 more
Caused by: org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5) vmcid: 0x4942f000 minor code: 775 completed: No
at com.ibm.rmi.iiop.Connection.checkEstablished(Connection.java:3091)
at com.ibm.rmi.iiop.Connection.send(Connection.java:2145)
at com.ibm.rmi.iiop.Connection._locate(Connection.java:463)
at com.ibm.rmi.iiop.Connection.locate(Connection.java:439)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
... 17 more
==============================================================================================
Could anyone tell me why is trying to connect to "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService"? Do I have to configure a default provider URL for SAP PI server? If so, where I configure it? Any help will be appreciated.
Thank you in advance.
Roger Allué i Vall

Hi Roger,
we also experience the same issue and would be very keen to understand how you resolved this problem.
Many thanks.
Dieter

JSPM SPS13 Problem : com.sap.aii.adapter.axis.app

Hello all,
For the PI 7.00 SP10 server we have applied a SP13 patch .All the Java patches are applied except SAP_XIAF we are gettting an error :
Error: Aborted: development component 'com.sap.aii.adapter.axis.app'/'sap.com'/'SAP AG'/'7.0013.20071224120620.0000'/'1', grouped by software component 'SAP_XIAF'/'sap.com'/'SAP AG'/'1000.7.00.13.4.20071226125540''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot register EarLoader for application sap.com/com.sap.aii.adapter.axis.app..
Log File ::::::::
Info: Begin of log messages of the target system:
08/02/10 08:48:06 - ***********************************************************
08/02/10 08:48:08 - Start updating EAR file...
08/02/10 08:48:08 - start-up mode is lazy
08/02/10 08:48:10 - EAR file updated successfully for 1292ms.
08/02/10 08:48:10 - Start deploying ...
08/02/10 08:48:11 - EAR file uploaded to server for 526ms.
08/02/10 08:48:14 - ERROR: Not deployed. Deploy Service returned ERROR:
 java.rmi.RemoteException: Cannot register EarLoader for application sap.com/com.sap.aii.adapter.axis.app..
 Reason: null; nested exception is:
 java.lang.NullPointerException
 at java.lang.Throwable.<init>(Throwable.java:194)
 at java.lang.Exception.<init>(Exception.java:41)
 at java.io.IOException.<init>(IOException.java:40)
 at java.rmi.RemoteException.<init>(RemoteException.java:71)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:204)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:0)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:117)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:119)
 Caused by: java.lang.NullPointerException
 at com.sap.engine.lib.util.HashMapObjectObject.get(HashMapObjectObject.java:601)
 at com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(LoadContextImpl.java:537)
 at com.sap.engine.core.classload.impl0.LoadContextImpl.registerReference(LoadContextImpl.java:296)
 at com.sap.engine.core.service630.container.LoadContextWrapper.registerReference(LoadContextWrapper.java:54)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.registerEARloader(DeployServiceImpl.java:2101)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:230)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
 ... 9 more
 For detailed information see the log file of the Deploy Service.
08/02/10 08:48:14 - ***********************************************************
Feb 10, 2008 8:48:15 AM Info: End of log messages of the target system.
Feb 10, 2008 8:48:15 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Feb 10, 2008 8:48:15 AM Error: Aborted: development component 'com.sap.aii.adapter.axis.app'/'sap.com'/'SAP AG'/'7.0013.20071224120620.0000'/'1', grouped by software component 'SAP_XIAF'/'sap.com'/'SAP AG'/'1000.7.00.13.4.20071226125540''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot register EarLoader for application sap.com/com.sap.aii.adapter.axis.app..
Reason: null; nested exception is:
* java.lang.NullPointerException*
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Feb 10, 2008 8:48:15 AM Info: Starting to save the repository
Feb 10, 2008 8:48:18 AM Info: Finished saving the repository
Feb 10, 2008 8:48:18 AM Info: Starting: Update: Selected software component 'SAP_XIAF'/'sap.com'/'SAP AG'/'1000.7.00.13.4.20071226125540''/'1' updates currently deployed software component 'SAP_XIAF'/'sap.com'/'SAP AG'/'1000.7.00.10.3.20070321093500''/'0'.
Feb 10, 2008 8:48:18 AM Error: Aborted: software component 'SAP_XIAF'/'sap.com'/'SAP AG'/'1000.7.00.13.4.20071226125540''/'1':
Failed deployment of SDAs:
development component 'com.sap.aii.adapter.axis.app'/'sap.com'/'SAP AG'/'7.0013.20071224120620.0000'/'1' : aborted
Feb 10, 2008 8:48:22 AM Error: -
At least one of the Deployments failed -
Any idea how to resolve this issue
Thanks,
GangaPrasad

Hello Prasad,
Seems like this one is similar to the other post from you. I responded in that one :
XIAF and XITOOLS packages depend on XIAFC package. It is first recommended you first upgrade XIAFC to the latest one if already not done.
After this, try to deploy the XIAF and XITOOLS.
Please also check SAP Note 1028961 .
Hope that helps !
Regards,
Snehal

Call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException

hello
I am running an interface RFC2WS sync and recieve this message in the RFC. the message does not get out of the XI and rich the target (WS).
the XI been upgraded lately, and I think this might be the cuase to the problem, becuase the interface been worked before, and still working in PROD environment as is.
what could be the problem and how can I start investigate it to find the problem?
this is what the SAP recieves
call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException
Thanks
Kfir

Hi Kfir,
just check in RWB, in component monitoring, the status of integration server and adapter engine.......if it is red, then ask your basis guys to remove that error................just check your comm channels, i think your comm channels are in error, if they are just edit them, save and activate them again..........i think then your this issue will be resolved.'
Regards,
Rajeev Gupta

File to RFC - error while processing message to remote system:com.sap.aii.

Hi
i m working on File to RFC scenario. the records are getting displayed in sender CC and receiver CC. But in receiver CC i m also getting the following error:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
It was working fine few hours earlier but showing this error now. i was giving a SUBMIT program , but stopped that now.
But still facing the same problem. and in SXMB_MONI its showing recorded for Outbound processing.
could anyone help.

Hi
I am Facing Following Error When I am trying to call SAP Screen through JCO.jar
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user
Please Guide Whethere it is possible to call SAP screen Through JCO.jar ot NOT
Please HELP if it is possible to Call SAP screen through JCO.jar with step and Code
Thanks
Vivek

Com.sap.aii.messaging.adapter.trans.TransformException:'java.lang.NullPoint

Similar Messages

Maybe you are looking for