Unable to login to admin ui in AEM Forms 6.5 JEE

Hi @bibhu_bikash_na ,

Please confirm if this is Cluster/standalone Environment.

If this Cluster Setup,

a) Please confirm which caching mechanism we are using 

> TCP

> UDP

b) There should not be any time difference between the Cluster Nodes

c) Share the Error that you are getting in the logs when trying to login to /adminui

Regards

Sameer Dhawan

Hi Sameer,

Thanks for your quick response. It's an un-clustered server. We are getting the below error while we try to login.

####<Apr 5, 2021 1:54:32,790 AM EDT> <Error> <com.adobe.idp.docmanager.service.DocumentManagerServiceImpl> <rpc15030.corp.ncr.com> <DEV63> <purgeDeletionLoop> <<anonymous>> <BEA1-10430FC818DB69C13B23> <8038c75e-fa71-4021-b6fd-d077a31f0725-00000008> <1617602072790> <[severity-value: 8] [rid: 0:145] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <Error in batch-delete!
java.lang.RuntimeException: java.sql.SQLException: Attempt to set connection harvestable to false but the connection is already closed.

Caused By: java.sql.SQLException: Attempt to set connection harvestable to false but the connection is already closed.

Thanks,

Bibhu.

@bibhu_bikash_na 

Based on the log[0] shared, please check the value of "enable Test Connections On Reserve" under Admin Console -> Navigate to the Data Source's Configuration -> Connection Pool -> (Advanced) -> check "Test Connections On Reserve"

Restart the node/admin server and monitor for any further issues. 

[0] - ... Caused By: java.sql.SQLException: Attempt to set connection harvestable to false but the connection is already closed.

Hi @pulkit_jain_ 

We have made the required changes suggested by you and will keep you informed on the errors. We are also getting below error in the server logs as well intermittently as well.

####<Apr 6, 2021 1:01:47,706 AM EDT> <Error> <com.adobe.service.J2EEConnectionFactoryManagerPeerImpl> <rpc15032.corp.ncr.com> <AEM65> <[ACTIVE] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-2A74CE0E532C58315DF7> <cc5e9581-738e-4615-88c5-7184e8db49c4-00000007> <1617685307706> <[severity-value: 8] [rid: 0:134:1:3] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <ALC-BMC-001-001: Unexpected exception while getting connection
org.omg.CORBA.COMM_FAILURE: Attempt to send message on closed socket vmcid: 0x0 minor code: 0 completed: No

Caused By: java.io.EOFException: Attempt to send message on closed socket

Thanks,

Bibhu.

@bibhu_bikash_na  I don't see any new reports of this issue so please confirm, if the issue is resolved. Otherwise, please raise a support ticket to discuss the issue over a screen share session.

Regarding the other issue reported, error msg points to WebLogic level socket connection timeout exception which needs to be increased incrementally.

- In console: click server, then protocols tab, then general sub-tab, then in advanced options try to increment Idle Connection Timeout parameter (ideally its 65 let's make it 100) and also try boosting all of these timeouts in WebLogic:

1) Stuckthead timeout

2) message timeout

3) output timeout

4) JTA timeout.