cancel
Showing results for 
Search instead for 
Did you mean: 

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

roger_alluivall
Participant
0 Kudos

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 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 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

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Roger,

we also experience the same issue and would be very keen to understand how you resolved this problem.

Many thanks.

Dieter

roger_alluivall
Participant
0 Kudos

Could anybody explain me how I have to configure JMS Receiver Adapter to access Websphere Application Server queues (not MQ!!)?

roger_alluivall
Participant
0 Kudos

Fixed!

js2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Roger, can you please share how you resolved the issue? Others are following your post and it competely defeats the purpose of having SCN if you are going to ask for help then withhold the solution. Disappointing how much this happens on scn!