IBM Support

PI05153: WASPOSTUPGRADE FAILS WHEN MIGRATING A NODE IN PLACE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When migrating a federated node in place, where both the old
    and the new WebSphere Application server installations use the
    same installation path on the host, WASPostUpgrade fails.
    WASPostUpgrade log shows:
    [10/24/2013 10:02:22:133 EEST]
    com.ibm.websphere.management.exception.ConnectorException:
    ADMC0016E: The system cannot create a SOAP connector to connect
    to host testhost at port 8880.
    com.ibm.ws.migration.utility.UpgradeException:
    com.ibm.websphere.management.exception.ConnectorException:
    ADMC0016E: The system cannot create a SOAP connector to connect
    to host testhost at port 8880.
    at
    com.ibm.ws.migration.postupgrade.Federated.DMgrConnectionInfo.in
    itializeAdminClient(DMgrConnectionInfo.java:359)
    at
    com.ibm.ws.migration.utility.ConfigRepositoryConnectionFederated
    Impl.getCorrectRepositoryForScenario(ConfigRepositoryConnectionF
    ederatedImpl.java:208)
    at
    com.ibm.ws.migration.utility.ConfigRepositoryConnectionFederated
    Impl.getConfigRepository(ConfigRepositoryConnectionFederatedImpl
    .java:172)
    at
    com.ibm.ws.migration.document.ConfigRepositoryDocumentCollection
    FederatedHelper.instantiateRepository(ConfigRepositoryDocumentCo
    llectionFederatedHelper.java:72)
    ...
    Caused by:
    com.ibm.websphere.management.exception.ConnectorException:
    ADMC0016E: The system cannot create a SOAP connector to connect
    to host testhost at port 8880.
    at
    com.ibm.websphere.management.AdminClientFactory.createAdminClien
    tPrivileged(AdminClientFactory.java:635)
    at
    com.ibm.websphere.management.AdminClientFactory.access$000(Admin
    ClientFactory.java:127)
    ...
    Caused by: java.lang.reflect.InvocationTargetException
    at
    sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
    Method)
    at
    sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeCons
    tructorAccessorImpl.java:56)
    ...
    Caused by:
    com.ibm.websphere.management.exception.ConnectorNotAvailableExce
    ption: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error
    opening socket: javax.net.ssl.SSLException: SSLSocketFactory is
    null. This can occur if
    javax.net.ssl.SSLSocketFactory.getDefault() is called to create
    a socket and javax.net.ssl.* properties are not set.;
    targetException=java.lang.IllegalArgumentException: Error
    opening socket: javax.net.ssl.SSLException: SSLSocketFactory is
    null. This can occur if
    javax.net.ssl.SSLSocketFactory.getDefault() is called to create
    a socket and javax.net.ssl.* properties are not set.]
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconne
    ct(SOAPConnectorClient.java:422)
    ....
    Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error
    opening socket: javax.net.ssl.SSLException: SSLSocketFactory is
    null. This can occur if
    javax.net.ssl.SSLSocketFactory.getDefault() is called to create
    a socket and javax.net.ssl.* properties are not set.;
    targetException=java.lang.IllegalArgumentException: Error
    opening socket: javax.net.ssl.SSLException: SSLSocketFactory is
    null. This can occur if
    javax.net.ssl.SSLSocketFactory.getDefault() is called to create
    a socket and javax.net.ssl.* properties are not set.]
    at
    org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPC
    onnection.java:475)
    ...
    [10/24/2013 10:02:22:135 EEST] MIGR0272E: The migration
    function cannot complete the command.
    
    Additional an ffdc file will be generated on the node with:
    [10/24/13 10:02:21:979 EEST]     FFDC
    Exception:java.io.IOException
    SourceId:com.ibm.ws.ssl.provider.AbstractJSSEProvider
    ProbeId:542
    Reporter:com.ibm.ws.ssl.provider.IBMJSSE2Provider@5210dda7
    java.io.IOException: Unable to verify MAC.
    at
    com.ibm.crypto.provider.PKCS12KeyStore.engineLoad(Unknown
    Source)
    at java.security.KeyStore.load(KeyStore.java:414)
    at
    com.ibm.ws.ssl.config.KeyStoreManager.getKeyStore(KeyStoreManage
    r.java:2209)
    ...
    
    The wrong keystore and trust files are being used when
    attempting to connect to the Deployment Manager.
    

Local fix

  • Save the following two files from the old WebSphere Application
    Server v8.0 install be prior to attempting a migration.
    <WAS_HOME>/profiles/<profile_name>/etc /key.p12
    <WAS_HOME>/profiles/<profile_name>/etc /trust.p12
    
    Then once the new WebSphere Application Sever v8.5.5 node has
    been created, but before WASPostUpgrade is executed, replace
    the existing files with the backed up files from the old
    WebSphere Application Server v8.0 version.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server performing a remote migration.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect keystore and truststore       *
    *                      files                                   *
    *                      are being used during a remote          *
    *                      migration, causing SOAP connection      *
    *                      problems.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When performing a remote migration, the WASPostUpgrade command
    could fail to create a SOAP connection.  The underlying problem
    of the SOAP connection failure is the use of incorrect
    keystore and truststore files.  This issue can only occur if
    the installation path of the new IBM WebSphere Application
    Server is the same as the installation path of the old IBM
    WebSphere Application Server.
    

Problem conclusion

  • The migration code has been updated to always use the keystore
    and truststore files collected in the migration backup
    directory.  Before, migration used the files found under the
    old install location when present, which could be incorrect.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.2 and 8.0.0.9.  Please refer to the Recommended
    Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI05153

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-30

  • Closed date

    2014-01-24

  • Last modified date

    2014-01-24

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI05153

Modified date: 24 January 2014


Translate this page: