Linux 64 bit

I tried the replacing license file but the same error. As a test we installed the program and Java on another server and just used the agent in trial mode same results test connection hangs and then fails. Firewall shows scheduler connection debog log empty as well as FTP amd Message logs for Linux, The good news is it was a 32 bit linux box so you were probably correct all along about it not being a 32 to 64 bit issue. So after that we installed it on another Linux server in trial mode the exact same way and it worked. At this point the Systems team asked that i just proceed with getting some phone support set up. Maybe its and installation issue, anyways please direct me in the right direction to escalate the issue and set up a call.

I will get a phone support for you, but I'm absolutely sure it is not going to help or speed anything up. The real issue is how to find the root cause or trace what is going on there and for that I need developers to provide some instructions or perhaps a troubleshooting or debugging utility. We are still working on that. Please wait.

Im not sure its going to help either but we are out of options we need to deploy a job scheduler in our production environment in the next couple months. We can see the packet being accepted by the agent the FTP session open and close and then nothing. We would like to try to resolve the issue and feel the product does everything we need but have problems troubleshooting it since Java handles the request and cannot see what the code is doing. Maybe a phone conference will help. It is something we have to resolve or we will have to look at other options and I personally dont want to do that, this product is as robust as i have found.

You are supposed to get a call from our sales people for the phone support option.

I just want you to know that we are working on a special build which can be used to dump more details to the debug log, not just top level calls and also dump more details about internal scheduler/agent communication. This should allow us to see where the buck stops.

I will notify you as soon as this build is ready and provide a download link. Thank you for your patience while we are trying to find a solution for this issue.

I got it WAHOOO
Here is the post on java Forums that helped point me in the right direction. Its the way the JAVA RMI handles the request and an issue with Red Hats local host file. I bet i seriously read Java forums for 6 hours straight. This is definitely something you might want to note in your install notes because unless you an expert in Java and Linux I dont know how long it would take someone with less determination to find what the problem is. Thanks again for all your patience

http://forum.java.sun.com/thread.jspa?threadID=5248747&tstart=0

WOW.... this is just outstanding. Thank you!

I wonder if the agent could do some kind of a sanity check on startup and validate that 127.0.01 maps to LocalHost.

Just for the record, our internal investigation lead to a conclusion that in this case the problem is not just in RMI, the agent doesn't call/use a remote registry, but for FTP based authentication it contacts the FTP daemon using "localhost" reference. So that if the localhost doesn't point to 127.0.0.1, the local FTP server cannot be found and as a result the user cannot be authenticated leading to refused connection. In the latest build we have replaced localhost references with explicit 127.0.0.1 references. Hope this will help in the future.