BARA - Failure uploading archive to server - UnknownHostException

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC BladeLogic Application Release Automation - Standard for WebSphere Business Applications


    APPLIES TO:

    BMC BladeLogic Application Release Automation - Standard for WebSphere Business Applications



    PROBLEM:

     

    Failure uploading archive to server - UnknownHostException
    ===========================
    Below are the errors seen in the phurnace.log file:

    22 Feb 2011 15:53:15 - DEBUG - (MBeanServerFacade.java:1676) - Saving ear archive F:\BMC ARA\BLAppRelease-8.1.0.******* InstallEAR\working\110222155254-0700\voice100.ear
    22 Feb 2011 15:53:35 - DEBUG - (MBeanServerFacade.java:1568) - Checking to see if application csbs exists.
    22 Feb 2011 15:53:35 - DEBUG - (MBeanServerFacade.java:1739) - Installing application csbs to path F:\BMC ARA\BLAppRelease-8.1.0.******* InstallEAR\working\110222155254-0700\voice100.ear
    Feb 22, 2011 3:54:19 PM com.ibm.ws.management.filetransfer.client.FileTransferClientImpl
    SEVERE: ADFS0112
    22 Feb 2011 15:54:19 - ERROR - (AbstractEngine.java:968) - Exception Name: WebSphere:Name=ABCDCell01,Type=Cell:Application
    22 Feb 2011 15:54:19 - ERROR - (AbstractEngine.java:969) - Exception Message: com.ibm.websphere.management.exception.AdminException: Failure uploading archive to server
    22 Feb 2011 15:54:19 - ERROR - (AbstractEngine.java:971) - Exception Class: com.phurnace.exception.PhurnaceException
    22 Feb 2011 15:54:19 - ERROR - (AbstractEngine.java:972) - Stack Trace:
    com.phurnace.exception.PhurnaceException: com.ibm.websphere.management.exception.AdminException: Failure uploading archive to server
    at com.phurnace.engine.websphere.MBeanServerFacade.installApplication(MBeanServerFacade.java:1756)
    at com.phurnace.mbeans.websphere.Application.install(Application.java:162)
    ~~
    Caused by:
    com.ibm.websphere.management.exception.AdminException: Failure uploading archive to server
    at com.ibm.websphere.management.application.AppManagementProxy.uploadArchive(AppManagementProxy.java:695)
    at com.ibm.websphere.management.application.AppManagementProxy.installApplication(AppManagementProxy.java:470)
    at com.phurnace.engine.websphere.MBeanServerFacade.installApplication(MBeanServerFacade.java:1745)
    ... 12 more
    Caused by:
    com.ibm.websphere.management.filetransfer.client.TransferFailedException: Upload retry limit exceeded for file F:\BMC ARA\BLAppRelease-8.1.0.******* InstallEAR\working\110222155254-0700\voice100.ear. Exception: java.net.UnknownHostException: ABCD
    at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.uploadFileInternal(FileTransferClientImpl.java:628)
    ~~
    at com.ibm.websphere.management.application.AppManagementProxy.uploadArchive(AppManagementProxy.java:681)
    ... 14 more
    Caused by:
    java.net.UnknownHostException: ABCD
    ~~
    at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.connectToServer(FileTransferClientImpl.java:2533)
    at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.uploadFileInternal(FileTransferClientImpl.java:533)
    ... 23 more
    22 Feb 2011 15:54:19 - INFO - (AbstractWebSphereEngine.java:1029) - Installing MBean AppPlacementController

    LP: BMC BladeLogic Application Release Automation - Standard for WebSphere Business Applications 8.1.00
    DR: BMC BladeLogic Application Release Automation - Standard 8.1.00

    Details: com.ibm.websphere.management.exception.AdminException: ADMA0176E: Application installation of csbs faild with PrivilegedActionException. Ear file path is C:\TEMP\voice100.ear.
    at com.ibm.ws.management.application.AppManagementImpl._installApplication(AppManagementImpl.java:305)

    AND

    com.ibm.websphere.management.exception.AdminException: ADMA0043E: C:\TEMP\voice100.ear does not exist for installation.

    C:\TEMP\voice100.ear is the correct source path
    But it looks like ARA tool is looking at this as the the install path... Should ARA know how to find the install path in WAS?

    WAS variables look like this;

    APP_INSTALL_ROOT ${USER_INSTALL_ROOT}/installedApps Node=ndm-ra01CellManagerNode01
    APP_INSTALL_ROOT ${USER_INSTALL_ROOT}/installedApps Node=tierljavabmc02Node01
    APP_INSTALL_ROOT ${USER_INSTALL_ROOT}/installedApps Node=tierljavabmc01Node01


    USER_INSTALL_ROOT /opt/WebSphere/AppServer/profiles/tierljavabmc02AppSv01 Node=tierljavabmc02Node01
    USER_INSTALL_ROOT /opt/WebSphere/AppServer/profiles/tierljavabmc01AppSv01 Node=tierljavabmc01Node01
    USER_INSTALL_ROOT /opt/WebSphere/DeploymentManager_cell_001/profiles/ndm-ra01Dmgr01 Node=ndm-ra01CellManagerNode01



    Issue Summary: PrivilegedActionException occurs when installing Application Deployment, AdminException: ADMA0043E occurs on same install stating that source EAR file cannot be found
     

     


    SOLUTION:

     

    Legacy ID:KA348728

    In the BARA Server Profile below are the infomration specified: 
    1. Hostname/IPAddress 
    2. SOAP Port 

    During Websphere Application deployment BARA calls the Websphere API and if the uploadApplicatin is set to true then Websphere returns a URL to which the file is uploaded. That URL is somewhat similar to https://WAS-Hostname:port/FileTransfer/******** 

    Depending on the target, if it is not-secure then the URL will be "http" and the port will be wc_adminhost (HTTP port of dmgr) and if it is secure then the URL would be "https" and the port will be wc_adminhost_secure (HTTPS port of DMGR). The WAS-Hostname is the same value that is given during the Profile creation. 

    It is possible for a Websphere Administrator to give a new-hostname (alias) during profile creation and then add that new-hostname (alias) to the local "hosts" file as an alias. By adding that in the "hosts" file it makes the Websphere instances to recognize the new-hostname (alias) locally and hence Websphere works fine. 

    When ARA tries to upload a file during app deployment then websphere will return the same new-hostname:port and ARA will not recognize this new-hostname (alias) (if it is not on the Websphere box). For this to work, the new-hostname (alias) has to be added to the "hosts" file of the ARA machine. 

    Locations of the "hosts" file: 
    UNIX : /etc/hosts 
    Windows: C:\Windows\System32\drivers\etc\hosts (where C drive is the Windows install drive). 

    Question: Why ara is looking for a different hostname when I have provided the IP/Hostname in the Serverprofle? 
    Answer: If your Websphere is configured on a different hostname/IP (alias) than the one in ServerProfile - BARA will not recognize if that alias is not set in the DNS. You will get below error messages during application deployment: 
    Exception Message: com.ibm.websphere.management.exception.AdminException: Failure uploading archive to server 
    Exception Class: com.phurnace.exception.PhurnaceException 
    ~~ 
    com.ibm.websphere.management.filetransfer.client.TransferFailedException: Upload retry limit exceeded for file F:\BMC ARA\BLAppRelease-8.1.0.******* InstallEAR\working\110222155254-0700\voice100.ear. Exception: java.net.UnknownHostException: ABCD 
    at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.uploadFileInternal(FileTransferClientImpl.java:628) 
    ~~ 
    Caused by: 
    java.net.UnknownHostException: ABCD 



    Related Products:  
       
    1. BMC BladeLogic Application Release Automation - Standard for WebSphere Business Applications

     


    Article Number:

    000090340


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles