No application machine is available to service any funcationality in DBA domain

After a recent clone of OTM loosely based on method described in http://otm62.blogspot.com, when we brought up the services, the following message appeared on accessing the OTM URL:

Error found handling the request.
No application machine is available to service any funcationality in DBA domain.

glog.exception.log was showing this error:

OTMActivationThread]
2012-06-28 13:36:25.728 0       Error   Exception       Server t3://otmapp1.example.com:9001 is not responding
  3:09 PM
[OTMActivationThread]
2012-06-28 13:36:53.804 0       Error   Exception       Could not notify APPSERVER2 of APPSERVER2 activation
[OTMActivationThread]
2012-06-28 13:39:07.491 306049  Error   Exception       cause.QueryFoundNoRecords
  3:09 PM


After going through the contents of glog.properties of both nodes, the cluster tables app_server, app_machine, app_server_machine for many hours, I noticed that the port number was incorrect in the MACHINE_URL column of app_machine. 

SQL> select MACHINE_URL from app_machine;

MACHINE_URL
--------------------------------------------------------------------------------
t3://otmapp1.example.com:9001
t3://otmapp2.example.com:9001 
It had the apache port 9001, instead of the weblogic port 7001

So I updated app_machine table to change it to:

MACHINE_URL
--------------------------------------------------------------------------------
t3://otmapp1.example.com:7001
t3://otmapp2.example.com:7001

After correcting this, the services came up and we were able to login without issues.