Description Michael OBrien 2009-12-02 12:48:07 EST

>The following weblogic.xml targets should not hardcode the server host name
Use the weblogic.host property in weblogic.properties - especially in the case that there is 2 network cards on the server.

    <target name="weblogic-start-nosleep"> 
        <wlserver fork="true" spawn="true" weblogichome="${weblogic.home}"
            dir="${weblogic.domain}" host="localhost" generateConfig="true" verbose="true"
    <target name="weblogic-stop">
        <wlserver fork="true" failonerror="false" weblogichome="${weblogic.home}"
            dir="${weblogic.domain}" host="localhost"

>should be
    <target name="weblogic-start-nosleep"> 
        <wlserver fork="true" spawn="true" weblogichome="${weblogic.home}"
            dir="${weblogic.domain}" host="${weblogic.host}" generateConfig="true" verbose="true"
    <target name="weblogic-stop">
        <wlserver fork="true" failonerror="false" weblogichome="${weblogic.home}"
            dir="${weblogic.domain}" host="${weblogic.host}"

>or we get
 [wldeploy] Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable;
 nested exception is:
 [wldeploy]     java.net.ConnectException: Connection refused: connect; No available router to destination]