ESI: getResponse: failed to get response: rc = 10 Internal server error 500

If you get these errors in Plugin logs

ERROR: ServerIOTimeout fired. Time out 60. retry count 0. serverIOTimeoutRetry -1, retry YES, rc 10

The above error is due to low value of ServerIOtimeOut.

ServerIOtimeOut plugin property explanation from IBM:
The ServerIOTimeout attribute of a server element enables the plug-in to set a time out value, in seconds, for sending requests to and reading responses from the application server.
If you set the ServerIOTimeout attribute to a positive value, this attempt to contact the server ends when the timeout occurs. However, the server is not considered to be down and future requests are still sent to the server on which the timeout occurred..
If you set the ServerIOTimeout attribute to a negative value, the server is considered to be down whenever a timeout occurs, and no future requests are sent to the server on which the timeout occurred.
  If a value is not set for the ServerIOTimeout attribute, the plug-in, by default, uses blocked I/O to write requests to and read responses from the application server, and does not time out the TCP connection. For example, you might specify the following setting:

For example, you might specify the following setting:

<Server Name="server1" ServerIOTimeout=300>

In this situation, if an application server stops responding to requests, the plug-in waits 300 seconds (5 minutes) before timing out the TCP connection. Setting the ServerIOTimeout attribute to a reasonable value enables the plug-in to time out the connection sooner, and transfer requests to another application server when possible.
When selecting a value for this attribute, remember that sometimes it might take a couple of minutes for an application server to process a request. Setting the value of the ServerIOTimeout attribute too low could cause the plug-in to send a false server error response to the client.

Important: The ServerIOTimeout limits the amount of time the plug-in will wait for each individual read or write operation to return. ServerIOTimeout does not represent a timeout for the overall request.

 

 

Increase the ServerIOtimeout value  to solve the above issue.

 

 

Viewing activity log using showlog command

GO to $profile_root/bin

Use the below command to conver binary activity log to viewable one.

./showlog.sh  <activity.log path>  <path where you wanted to place new log>

ex:./showlog.sh ./logsactivity.log    /tmp/activity.log

SRVE0255E: A WebGroup/Virtual Host to handle /ibm/console has not been defined

The above error will be there in SystemOut logs when admin console of Websphere is not able to access.The reason is isclite.ear might be corrupted or manul port change would have caused the issue.

To solve the issue please reinstall isclite.ear using the below commands

Uninstall :

$profile_root/bin/wsadmin.sh -lang jython -f deployConsole.py remove






Install:
 $profile_root/bin/wsadmin.sh -lang jython -f deployConsole.py install

Caused by: com.ibm.websphere.wim.exception.WIMSystemException: CWWIM4520E The 'javax.naming.NamingException: [LDAP: error code 80 - Other]

If the above error is seen in Sysout logs of WAS please check LDAP is up and running fine.

80

LDAP_OTHER

Indicates an unknown error condition. This is the default value for NDS error codes which do not map to other LDAP error codes

java.sql.SQLNonTransientException: [jcc][t4][2043][11550][4.3.111] Exception java.net.ConnectException:

If you get this error while doing a test connection to a datasource.Please check the connection
telnet servername port

If it failed as connection refused then the port is not opened .