IBM Support

JR46053: INFORMATION SERVER SERVICES TIER INSTALL ON WAS CLUSTER FAILED WITH ERROR: CDIIN5123E: ISFSERVICEADMINACTION FAILED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Information Server install of services tier on WAS cluster
    failed when deploying asb_prs.ear with the following error:
    
    Error The following exception has occurred:
    An error occurred trying to instantiate an object of the entry
    point client implementation
    "com.ascential.acs.security.auth.ejb.EJBAuthenticationService"
    2013-03-09T14:06:24.237, SEVERE:
    com.ibm.is.install.engine.runtime.InstallEngine
    com.ibm.is.install.exception.ActionException: CDIIN5123E:
    ISFServiceAdminAction failed: the process returned error code
    11:
     com.ascential.asb.util.invocation.EntryPointInstantiationExcept
    ion: An error occurred trying to instantiate an object of the
    entry point client implementation
    "com.ascential.acs.security.auth.ejb.EJBAuthenticationService"
        at
    com.ascential.asb.util.invocation.ejb.EJBServiceCreator.<init>(E
    JBServiceCreator.java:125)
        at
    com.ascential.acs.security.auth.ejb.EJBAuthenticationService.<in
    it>(EJBAuthenticationService.java:41)
        at
    com.ascential.acs.security.auth.JAASAuthenticationService.getAut
    hService(JAASAuthenticationService.java:439)
        at
    com.ascential.acs.security.auth.JAASAuthenticationService.loginI
    mpl(JAASAuthenticationService.java:418)
        at
    com.ascential.acs.security.auth.JAASAuthenticationService.login(
    JAASAuthenticationService.java:148)
        at
    com.ascential.acs.security.auth.client.AuthenticationService.doL
    oginImpl(AuthenticationService.java:866)
        at
    com.ascential.acs.security.auth.client.AuthenticationService.doL
    ogin(AuthenticationService.java:326)
        at
    com.ascential.asb.admin.service.tools.ServiceCommandCommon.authe
    nticate(ServiceCommandCommon.java:296)
        at
    com.ascential.asb.admin.service.tools.ServiceAdminCommand.handle
    Request(ServiceAdminCommand.java:465)
        at
    com.ascential.asb.admin.service.tools.ServiceAdminCommand.main(S
    erviceAdminCommand.java:562)
    Caused by: javax.naming.NameNotFoundException: Context:
    <cell_name>/clusters/<cluster_name>, name:
    ascential/acs/ejb/impl/AuthenticationService: First component
    in name ascential/acs/ejb/impl/AuthenticationService not found.
    [Root exception is
    org.omg.CosNaming.NamingContextPackage.NotFound:
    IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
        at
    com.ibm.ws.naming.jndicos.CNContextImpl.mapNotFoundException(CNC
    ontextImpl.java:4365)
        at
    com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j
    ava:1794)
        at
    com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j
    ava:1749)
        at
    com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.
    java:1500)
        at
    com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.jav
    a:637)
        at
    com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:165)
        at
    com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
        at
    javax.naming.InitialContext.lookup(InitialContext.java:436)
        at
    com.ascential.asb.util.invocation.ejb.EJBServiceCreator.<init>(E
    JBServiceCreator.java:120)
        ... 9 more
    

Local fix

  • If your application server is configured to auto start when
    ever the node agent restarts you may be running into this
    issue. This is not the default configuration and it can cause
    the application server to be started already at the time the
    install tries to start it. The work around is to configure the
    application server to only start when told to. In this way, it
    will not startup automatically when the node agent does and the
    installer's attempt to start the cluster will then start up the
    application server at the correct time after the core apps are
    deployed. To change this to the default setting instead:
    
       1. Log in to the WebSphere Integrated Solutions Console
       2. Navigate to Servers > Application servers > server_name
       3. Expand Java and Process Management and click on
    Monitoring Policy
       4. Change the Node restart state from RUNNING to STOPPED
       5. Click Apply
       6. Click Save to save the master configuration
    
    Stop the cluster, then stop the Node Agent. Next start the Node
    Agent again, this time the Application Server should not start
    up automatically. If that works, start the application server
    and now you are ready to resume the Information Server install.
    Resume the install by invoking the setup program in silent mode
    with the response file that was generated in their install
    interview.  Procedure for that is:
    
    1. Edit the response file (by default,
    /opt/IBM/InformationServer/response.txt) and replace the
    <CHANGE_TO_YOUR_PASSWORD> tokens with the appropriate actual
    passwords. This should include the WebSphere administrator
    password, the Information Server administrator password, the
    xmeta  password, etc.
    
    2. In the is-suite directory invoke the setup program with:
    
        ./setup -verbose -rsp full-path-of-response-file -uiMode
    silent
    
    -verbose will cause the log output to be echoed to the terminal
    window so you can watch the install's progress.  Without
    -verbose, you can run the install and then go to
    /tmp/ibm_is_logs and use tail -f to watch the logfile itself.
    

Problem summary

  • The cluster.jacl script needs to do a Ripple start rather than a
    plain start. A plain start causes the application servers to be
    restarted only if they are not already running. This causes the
    installation to fail if the cluster's node agents are configured
    to automatically start application servers when they themselves
    are brought up.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR46053

  • Reported component name

    INFO SRVR PLATF

  • Reported component ID

    5724Q3612

  • Reported release

    870

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-15

  • Closed date

    2013-04-25

  • Last modified date

    2013-04-25

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

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

Fix information

Applicable component levels

  • R910 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSZJPZ","label":"InfoSphere Information Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.7","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 October 2021