AppSync: The AppSync GUI will not work and presents: " HTTP 403 forbidden " following an upgrade of AppSync.

           

   Article Number:     498434                                   Article Version: 3     Article Type:    Break Fix 
   

 


Product:

 

AppSync,AppSync 3.1,AppSync 3.0

 

Issue:

 

 

Following an upgrade of AppSync, the GUI will not load and presents the following error:   
        

      HTTP 403 forbidden   
   
    The upgrade actually failed despite reporting that it was successful, due to one of the AppSync Ports being in use during the upgrade.   
   
    Where xxxx is the userid used to perform the upgrade, the Setup.log for the upgrade located in C:\Users\xxxx\AppData will show:   
        
      04-04-2017 14:26:27.468 Command.run(): C:\Users\xxxx\AppData\Local\Temp\482499.tmp\executeScriptTmp0.bat:stdout [Deployment of archway-ear.ear failed]   
   
    The System event log will show the following error during the upgrade timeframe:   
        
      04/04/2017 02:26:22 PM Warning       ServerName. 4227    Tcpip                            TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.   
   
    The AppSync Services will start after the upgrade, as seen in services, however the following will be found in the server.log:    
        
      04-04-2017 14:26:41.609 ERROR [Controller Boot Thread] [org.jboss.as.controller.management-operation] [] [] WFLYCTL0013: Operation ("add") failed - address: ([        
            ("subsystem" => "undertow"),        
            ("server" => "default-server"),        
            ("http-listener" => "default")        
        ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.listener.default" => "org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener        
            Caused by: java.net.BindException: Address already in use: bind"}}
   
                                                             

 

 

Cause:

 

 

The cause was another process using an AppSync port.   
    The netstat -anbo output showed Macafee using one of the AppSync ports as seen here:   
        

      TCP 0.0.0.0:8085 0.0.0.0:0 LISTENING 1192 [macmnsvc.exe]        
        TCP [::]:8085 [::]:0 LISTENING 1192 [macmnsvc.exe] 
   
   
   
        
   
                                                                

 

 

Resolution:

 

 

In this specific situation, Macafee was uninstalled and then the upgrade was performed and the AppSync GUI was functional.   
    Other methods to ensure Macafee is not using the AppSync ports may provide a valid resolution as well.   
   
    The AppSync ports are:   

         
  •         CAS_PORT=8444      
  •      
  •         HTTP_PORT=8085      
  •      
  •         HTTPS_PORT=8445      
  •      
  •         TOMCAT_PORT=8015      
  •