Java Client log in error "ErrorMsg: AwE-5116 awtcpd error"

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

When logging into the Applications Manager Java client, the log in process may fail with the below error:

ErrorMsg: AwE-5116 awtcpd error
Details: MASTERNAME
awtcpd error : MASTERNAME : null
    at com.appworx.server.data.AxRmiServer.A(AxRmiServer.java:2598)
    at com.appworx.server.data.D$_B.doOperatorLogin(RemoteClientSocketManager.java:253)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.uc4.be.util.InvokeUtil.invoke(InvokeUtil.java:122)
    at com.appworx.util.InvokeRequest.invokeMethod(InvokeRequest.java:47)
    at com.appworx.server.data.B.A(ClientServices.java:150)
    at com.appworx.server.data.D$_A.doRun(RemoteClientSocketManager.java:171)
    at com.uc4.be.threading.AbstractWorker.run(AbstractWorker.java:367)
    at java.lang.Thread.run(Unknown Source)

This error generally means that Applications Manager master or RmiServer process is down or not running properly. Further review of the RmiServer logs is required to understand why the RmiServer stop functioning. 

Common errors that may be seen in the RmiServer log for the time of issue are below:

connCkr: AwE-9999
connCkr: SQL Error: 17002
connCkr: .AxOptions: NoErrorMsgProperties=false
ErrorMsg: AwE-9999 Internal error
Details: failed attempt at closing bad connection
java.sql.SQLRecoverableException: IO Error: Socket read timed out
    at oracle.jdbc.driver.T4CConnection.logoff(T4CConnection.java:857)
    at oracle.jdbc.driver.PhysicalConnection.close(PhysicalConnection.java:2498)
    at com.appworx.server.sql.AxConnection.closeIt(AxConnection.java:476)
    at com.appworx.server.sql.AxConnectionPool.A(AxConnectionPool.java:589)
    at com.appworx.server.sql.AxConnectionPool.B(AxConnectionPool.java:50)
    at com.appworx.server.sql.AxConnectionPool$_A.run(AxConnectionPool.java:798)
Caused by: oracle.net.ns.NetException: Socket read timed out
    at oracle.net.ns.Packet.receive(Packet.java:350)
    at oracle.net.ns.DataPacket.receive(DataPacket.java:105)
    at oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:305)
    at oracle.net.ns.NetInputStream.read(NetInputStream.java:249)
    at oracle.net.ns.NetInputStream.read(NetInputStream.java:171)
    at oracle.net.ns.NetInputStream.read(NetInputStream.java:89)
    at oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(T4CSocketInputStreamWrapper.java:123)
    at oracle.jdbc.driver.T4CSocketInputStreamWrapper.read(T4CSocketInputStreamWrapper.java:79)
    at oracle.jdbc.driver.T4CMAREngineStream.unmarshalUB1(T4CMAREngineStream.java:429)
    at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:397)
    at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257)
    at oracle.jdbc.driver.T4C7Ocommoncall.doOLOGOFF(T4C7Ocommoncall.java:59)
    at oracle.jdbc.driver.T4CConnection.logoff(T4CConnection.java:844)

 

ErrorMsg: AwE-5001 Database Query Error
Details: getConnection
    null
java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:743)
    at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:662)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:560)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at com.appworx.server.sql.AxConnectionPool.getConnection(AxConnectionPool.java:370)
    at com.appworx.server.sql.DBAccess.getConnection(DBAccess.java:1563)
    at com.appworx.server.sql.DBAccess.A(DBAccess.java:1470)
    at com.appworx.server.sql.DBAccess.getLoginConnection(DBAccess.java:1453)
    at com.appworx.server.sql.DBAccess.getProcedureData(DBAccess.java:1078)
    at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.uc4.be.util.InvokeUtil.invoke(InvokeUtil.java:122)
    at com.appworx.util.InvokeRequest.invokeMethod(InvokeRequest.java:47)
    at com.appworx.server.data.MasterSocketManager$_A.doRun(MasterSocketManager.java:360)
    at com.uc4.be.threading.AbstractWorker.run(AbstractWorker.java:367)
    at java.lang.Thread.run(Unknown Source)
Caused by: oracle.net.ns.NetException: The Network Adapter could not establish the connection
    at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:470)
    at oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:506)
    at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:595)
    at oracle.net.ns.NSProtocol.connect(NSProtocol.java:230)
    at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1452)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:496)
    ... 18 more
Caused by: java.net.ConnectException: Connection timed out: connect
    at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
    at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
    at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
    at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at oracle.net.nt.TcpNTAdapter.connect(TcpNTAdapter.java:161)
    at oracle.net.nt.ConnOption.connect(ConnOption.java:159)
    at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:428)
    ... 23 more

 

 

 

Environment

Applications Manager 9.4+

Cause

Error may indicate that a network or database issue occurred

Resolution

The Combination of errors documented in this article generally means that a network or database error may have occurred, and the connection to the database (the socket) timed out.

It is recommended to refer to the network and/or DBA team to review the time of errors and to check if there was any network or database issues during the time of reported errors

If needed, open a case with Support and upload the RmiServer debug logs covering the time of issue. In addition to confirming a network/database issue, Support may make make additional suggestions based on log findings.