Home General

Unable to establish a connection with WEM 10.5 through APIs

Hello Everyone

We are getting below error while trying to establish a connection with WEM10.5 instance. Please advice on the resolution if anyone has faced similar issue.

Error

------------------------------------------

com.vignette.authn.AuthnException: 01/21/2021 20:40:05:278, Error 11 (IOError), Message 003-003-0014: Destination t3://myserver2016:27110 is unreachable.

at com.vignette.authn.AuthnException.getOne(AuthnException.java:160)

at com.vignette.authn.AuthnException.getOne(AuthnException.java:134)

at com.vignette.authn.WLContextAuthentication.loginUser(WLContextAuthentication.java:85)

at com.vignette.authn.BaseAuthentication.login(BaseAuthentication.java:67)

at com.vignette.authn.BEAAuthentication.login(BEAAuthentication.java:19)

at com.vignette.authn.LoginMgr.updateLogin(LoginMgr.java:128)

at com.vignette.authn.LoginMgr.login(LoginMgr.java:108)

at WEM.ConnectingWEM.main(ConnectingWEM.java:26)

Nested exception is:

java.net.ConnectException: t3://myserver2016:27110: Bootstrap to: myserver2016/192.168.13.128:27110' over: 't3' got an error or timed out

at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)

at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)

at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:165)

at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)

at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)

at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)

at weblogic.jndi.Environment.getContext(Environment.java:315)

at weblogic.jndi.Environment.getContext(Environment.java:285)

at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)

at java.naming/javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:719)

at java.naming/javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305)

at java.naming/javax.naming.InitialContext.init(InitialContext.java:236)

at java.naming/javax.naming.InitialContext.<init>(InitialContext.java:208)

at com.vignette.authn.WLContextAuthentication.loginUser(WLContextAuthentication.java:68)

at com.vignette.authn.BaseAuthentication.login(BaseAuthentication.java:67)

at com.vignette.authn.BEAAuthentication.login(BEAAuthentication.java:19)

at com.vignette.authn.LoginMgr.updateLogin(LoginMgr.java:128)

at com.vignette.authn.LoginMgr.login(LoginMgr.java:108)

at WEM.ConnectingWEM.main(ConnectingWEM.java:26)

Caused by: java.rmi.ConnectException: Bootstrap to: myserver2016/192.168.13.128:27110' over: 't3' got an error or timed out

at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)

at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:260)

at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)

at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)

at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)

... 19 more


Nested exception is:

java.net.ConnectException: t3://myserver2016:27110: Bootstrap to: myserver2016/192.168.13.128:27110' over: 't3' got an error or timed out

at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)

at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)

at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:165)

at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)

at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)

at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)

at weblogic.jndi.Environment.getContext(Environment.java:315)

at weblogic.jndi.Environment.getContext(Environment.java:285)

at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)

at java.naming/javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:719)

at java.naming/javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305)

at java.naming/javax.naming.InitialContext.init(InitialContext.java:236)

at java.naming/javax.naming.InitialContext.<init>(InitialContext.java:208)

at com.vignette.authn.WLContextAuthentication.loginUser(WLContextAuthentication.java:68)

at com.vignette.authn.BaseAuthentication.login(BaseAuthentication.java:67)

at com.vignette.authn.BEAAuthentication.login(BEAAuthentication.java:19)

at com.vignette.authn.LoginMgr.updateLogin(LoginMgr.java:128)

at com.vignette.authn.LoginMgr.login(LoginMgr.java:108)

at WEM.ConnectingWEM.main(ConnectingWEM.java:26)

Caused by: java.rmi.ConnectException: Bootstrap to: myserver2016/192.168.13.128:27110' over: 't3' got an error or timed out

at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)

at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:260)

at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)

at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)

at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)

... 19 more

---------------------------------

Code Used

----------------------------------

AuthnBundle authn = new AuthnBundle();

authn.setHost("myserver2016");

authn.setPort("27110");

authn.setUsername("user");

authn.setPassword("password");

LoginMgr loginMgr = new LoginMgr();

try {

loginMgr.login(authn);

System.out.println("connected.");

} catch (AuthnException e) {

e.printStackTrace();

}

Comments

  • edited January 28

    Check the Norskale Infrastructure Service in the Windows services console and to make sure it is running. If it is stopped, then start it. Then attempt to connect the WEM admin console again and monitor that the service does not stop again.

    Configure the service Recovery to "Restart the Service" for the First, Second and Subsequent failures. mysubwaycard

    If the service is stopped again, we need to find out what is causing the service to stop.

  • Hi Mariane

    Thanks for responding. We do not see any such services in our server. Also all the WEM services are up and running and we are able to access the system through browser. The error is happening only when we run the above code in the server.

    Thanks,

    Manu

  • Qutubuddin SaifuddinQutubuddin Saifuddin Senior Architect EM

    Please look at local firewall rules for your Windows server. Looks you need some local rules.

  • edited February 2

    Create a full backup of the WEM database and then run the following query on the SQL server where the WEM database is hosted.


    FaceTime PC

  • Yes, it looks like a firewall block.

    We did disable the the windows firewall service and enabled the ports 27001 and 27110 for both inbound and outbound traffic, however still facing the same issue. Also the TELNET to these ports from the server seems to be working as well.

Sign In or Register to comment.