Deployment issue with updating properties file

In part of deployment, along with ear file we have copied properties file in application path and deployed the application on weblogic server. Post deployment, application status in weblogic console is also active. But other applications not able to communicate with this application.

We found the following errors in weblogic logs
=============================================================================
java.io.IOException: Cannot bind to URL: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://10.*6.146.17:7280: Destination unreachable; nested exception is:
        java.net.ConnectException: Connection refused; No available router to destination]
        at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804)
        at javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.java:555)
        at weblogic.management.mbeanservers.internal.MBeanServerServiceBase.stop(MBeanServerServiceBase.java:233)
        at weblogic.management.mbeanservers.runtime.internal.RuntimeServerService.stop(RuntimeServerService.java:283)
        at weblogic.management.mbeanservers.internal.MBeanServerServiceBase.halt(MBeanServerServiceBase.java:247)
        at weblogic.t3.srvr.ServerServicesManager.haltInternal(ServerServicesManager.java:504)
        at weblogic.t3.srvr.ServerServicesManager.halt(ServerServicesManager.java:336)
        at weblogic.t3.srvr.T3Srvr.shutdown(T3Srvr.java:1120)
        at weblogic.t3.srvr.T3Srvr.forceShutdown(T3Srvr.java:1024)
        at weblogic.t3.srvr.ServerRuntime.forceShutdown(ServerRuntime.java:349)
        at weblogic.server.RemoteLifeCycleOperationsImpl.forceShutdown(RemoteLifeCycleOperationsImpl.java:57)
        at weblogic.server.RemoteLifeCycleOperationsImpl_WLSkel.invoke(Unknown Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
        at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
        at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
============================================================================

During deployment, it is trying to load the properties file. As IP address(10.*6.146.17) is mentioned wrong, it has loaded the wrong ip. Because this application is not able to communicate with other applications.
===================================================
Loading properties from property file - /granite.properties
GraniteProperties, props = APPLICATIONID=1, password=*****, AG1Model=CS-ASR-903-PAR, servername=10.*6.**6.*7, OM_SOAP_ACTION=woResponse, TRANSACTIONID=*****, CIENA=Ciena Transport Installation,Ciena Transport Logistic, database=*****, host=***, ALU_FTTX=ALU FTTX Installation,ALU FTTX Logistic, APIKEY=***, ALU_TRANSPORT=ALU Transport Installation,ALU Transport Logistic
===================================================

We have later updated the properties file with the correct ip(10.*6.146.172) and stopped weblogic server. Cleared the cache and started the weblogic server. Now this application is able to communicate properly with other applications.