Please do following to see if B instance is listening to the right ip:port.
1, *sh...@geronimo>** netstat -na|grep 1099* If everything is OK, you should see this *B_IP_address:1099 0.0.0.0:* LISTEN* or this *0.0.0.0:1099 0.0.0.0:* LISTEN* which means you instance B is listening to the right ip:port. Then, you can try the deployment again in machine A. You can also try to use ip address of B instead of B as hostname with deploy script. On Thu, Nov 26, 2009 at 12:03 AM, MDiamond <[email protected]> wrote: > > > > RunHua Chi wrote: > > > > If you want to deploy applications to B, then edit the value of > > RemoteDeployHostname in config-subsitutions.properties file on B. > > > > Then on A, use the deploy command like > > > > ./deploy.sh -host <ip of B> -u system -p manager deploy <application on > A> > > > > Yes, this is what I am doing and it doesn't work. I get the same error as > above. And this is with Geronimo-Tomcat. > -- > View this message in context: > http://old.nabble.com/Remote-Deployment%3A-Connection-Refused-tp26421415s134p26515354.html > Sent from the Apache Geronimo - Users mailing list archive at Nabble.com. > > -- Shawn
