IBM Support

PM98297: Monitored directory starts application before it is expanded on node

Fixes are available

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During a monitored directory deployment, the application status
    is interpreted as  distribution complete before the application
    file has been expanded in the installedApps directory.
    Application start is then issued, which fails with the folowing
    sequence in the systemOut.log:
    [9/25/13 13:18:33:921 EDT] 00000016 AppManagement I
    CWLDD0048I: Event id 870480872-1. Application myapp is
    distributed completely.
    [9/25/13 13:18:34:811 EDT] 0000000b AppManagement I
    CWLDD0015I: Event id 870480872-1. Application myapp is
    installed successfully.
    [9/25/13 13:18:34:811 EDT] 0000000b AppManagement I
    CWLDD0020I: Event id 870480872-1. Starting application myapp...
    [9/25/13 13:18:34:843 EDT] 0000000b AdminHelper   A
    ADMN1008I: An attempt is made to start the mayapp application.
    (User ID =
    defaultWIMFileBasedRealm/server:Cell01_CellManager01_dmgr)
    ...
    [9/25/13 13:18:36:233 EDT] 0000000b AppManagement W
    ADMA0116W: Unable to start: myapp using:
    WebSphere:name=ApplicationManager,process=Server01,platform=prox
    y,node=Node01,version=8.0.0.6,type=ApplicationManager,mbeanIdent
    ifier=ApplicationManager,cell=Cell01,spec=1.0 exception is:
    javax.management.MBeanException: Exception thrown in
    RequiredModelMBean while trying to invoke operation
    startApplication
     at
    javax.management.modelmbean.RequiredModelMBean.invokeMethod(Requ
    iredModelMBean.java:1180)
     at
    javax.management.modelmbean.RequiredModelMBean.invoke(RequiredMo
    delMBean.java:984)
     at
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Def
    aultMBeanServerInterceptor.java:836)
     at
    com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.jav
    a:762)
     at
    com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.ja
    va:1335)
     ...
    Caused by: com.ibm.ws.exception.RuntimeWarning:
    com.ibm.ws.exception.ConfigurationWarning:
    org.eclipse.jst.j2ee.commonarchivecore.internal.exception.NoModu
    leFileException: A file does not exist for module element
    having uri: mymod-ejb.jar
     at
    com.ibm.ws.runtime.component.ApplicationMgrImpl.start(Applicatio
    nMgrImpl.java:2162)
     at
    com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(Compos
    itionUnitMgrImpl.java:445)
     ...
    Caused by: com.ibm.ws.exception.ConfigurationWarning:
    org.eclipse.jst.j2ee.commonarchivecore.internal.exception.NoModu
    leFileException: A file does not exist for module element
    having uri: mymod-ejb.jar
     at
    com.ibm.ws.runtime.component.ApplicationMgrImpl.initializeApplic
    ation(ApplicationMgrImpl.java:418)
     at
    com.ibm.ws.runtime.component.ApplicationMgrImpl.start(Applicatio
    nMgrImpl.java:2149)
     ...
    Caused by:
    org.eclipse.jst.j2ee.commonarchivecore.internal.exception.NoModu
    leFileException: A file does not exist for module element
    having uri: mymod-ejb.jar
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleRefIm
    pl.checkType(ModuleRefImpl.java:591)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleRefIm
    pl.initModuleFileFromEAR(ModuleRefImpl.java:167)
     ...
    
    Tracing on the deployment manager with trace string
    con.ibm.ws.management.dragdrop.*=all;AppMgmt=all will show:
    [9/25/13 13:18:33:921 EDT] 000000ee DistributionS >
    createCompletionEvent Entry
                                     bSuccess=true
                                     causeOfFailure=null
    [9/25/13 13:18:33:921 EDT] 000000ee DistributionS <
    createCompletionEvent Exit
    
    AppNotification:task=AppDistributionNode, taskStatus=Completed,
    subtask=, subtaskStatus=,
    taskProperties={AppDistributionAll=WebSphere:cell=Cell01,node=No
    de01,distribution=false,expansion=inprogress},
    taskMessage=ADMA5072I: Distribution status check completed for
    application myapp., causeOfFailure=<NULL>
    [9/25/13 13:18:33:921 EDT] 000000ee SchedulerImpl >
    propagateTaskEvent Entry
    [9/25/13 13:18:33:921 EDT] 000000ee AppManagement >
    sendJMXEvent Entry
    [9/25/13 13:18:33:921 EDT] 00000016 AppManagement >
    handleNotification Entry
    
    notification=javax.management.Notification[source=WebSphere:name
    =AppManagement,process=dmgr,platform=proxy,node=CellManager01,ve
    rsion=8.0.0.6,type=AppManagement,mbeanIdentifier=AppManagement,c
    ell=Cell01,spec=1.0][type=websphere.admin.appmgmt][message=],
    handBackObject=1171809019
    [9/25/13 13:18:33:921 EDT] 00000016 AppManagement 1
    handleNotification
                                     eventHandBack=1171809019
                                     handBack=1171809019
    [9/25/13 13:18:33:921 EDT] 00000016 AppManagement 3
    handleNotification
    
    eventTaskName=AppDistributionNode
                                     eventTaskStatus=Completed
    [9/25/13 13:18:33:921 EDT] 00000016 AppManagement I
    CWLDD0048I: Event id 870480872-1. Application myapp is
    distributed completely.
    

Local fix

  • Application can be manually started after the expansion into
    installedApps is complete.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server monitored directory application      *
    *                  deployment service.                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: An application deployed by the          *
    *                      monitored directory service fails to    *
    *                      start.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The monitored directory application service may attempt to
    start an application before it is fully deployed to all nodes.
    In that case the appplication may fail to be started by the
    service.
    

Problem conclusion

  • The code has been modifed to ensure that the application
    deployment is not still in progress on any targeted nodes when
    it is started.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.9, and 8.5.5.2.  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

    PM98297

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-02

  • Closed date

    2014-01-15

  • Last modified date

    2014-01-15

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022