Symptom
The PI tools - Integration Repository (ESR) and Integration Builder (IB) - are being attempted to be opened, but they are not opening.
From the Java WebStart Console trace (SAP note 1891480) the following error can be seen:
ERROR com.sap.aii.ib.clsif.login.EJBHomeFactory: MessageID=IBF.clntlib.<num>#Message server not available ms://<host>:<port>/P4
Thrown:
com.sap.aii.utilxi.misc.api.ReconnectRuntimeException: Cannot connect to server using message server: ms://<host>:<port>/P4
at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:704)
at com.sap.aii.ib.clsif.login.EJBHomeFactory.connect(EJBHomeFactory.java:481)
at com.sap.aii.ib.clsif.login.EJBHomeFactory.initRemoteFactory(EJBHomeFactory.java:142)
at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:227)
at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:146)
at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginController.doTrial(SplashLoginFrame.java:1150)
at com.sap.aii.ib.gui.login.SplashLoginFrame$StartupWaiter$1$1.run(SplashLoginFrame.java:975)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
...
Caused by: javax.naming.NamingException: Exception while trying to get InitialContext.
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:386)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:688)
...
Caused by: com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available profiles. Check if server is started, access point for the protocol is available, and IP/Host name is accessible on the network.
URL=ms://<host>:<port>/P4, protocol=P4(None), Reason: java.net.UnknownHostException: <host>;
at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:73)
at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:39)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:298)
...
Caused by: java.net.UnknownHostException: <host>
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(Unknown Source)
at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
at java.net.InetAddress.getAllByName0(Unknown Source)
at java.net.InetAddress.getAllByName(Unknown Source)
at java.net.InetAddress.getAllByName(Unknown Source)
at java.net.InetAddress.getByName(Unknown Source)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getInitialConnection(P4ObjectBrokerClientImpl.java:954)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getRemoteBroker(P4ObjectBrokerClientImpl.java:898)
at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:59)
...
Read more...
Environment
- PI Release Independent
- SAP NetWeaver
- SAP Process Integration
Product
Keywords
PI tools, Integration, Repository, Builder, ESR, IB, Open, Java WebStart Console, EJBHomeFactory, Message server not available, ms://, P4, ReconnectRuntimeException, Cannot connect, Server, Message Server, NamingException, InitialContext, DestinationException, Cannot establish connection, Profiles, Protocol, Inet6AddressImpl, lookupAllHostAddr, Native Method, InetAddress$2, Hosts, OS level, IP address, Fully Qualified Domain Name, FQDN, IPv4, IPv6, Djava, preferIPv4Stack, Parameter, JVM, Java configtool, Restart, Process Integration 7.0, PI 7.0, PI 7.01, PI 7.02, Process Integration 7.10, PI 7.10, Process Integration 7.11, PI 7.11, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.40, PI 7.40, PO 7.40, Process Orchestration 7.50, PI 7.50, PO 7.50, NetWeaver, XI, AEX , KBA , BC-XI-IBC , Integration Builder - Configuration , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.