IBM Support

PI46612: Server dump command fails when a Java dump file cannot be found.

Fixes are available

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.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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.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

  • When a user runs the server dump command and requests Java
dumps (such as thread, heap or system dumps) to be acquired
(ex: server dump myServer --include=thread,heap,system ), if
one or more of the requested Java dump files could not be
found, it will result in an error message such as the
following:

CWWKE0018E: An exception occurred while launching the
runtime environment: java.lang.IllegalArgumentException: The
source does not exist.
java.lang.IllegalArgumentException: The source does not
exist.
at
com.ibm.ws.kernel.boot.archive.FileEntryConfig.(FileEntryCon
fig.java:39)
at
com.ibm.ws.kernel.boot.internal.commands.DumpProcessor.creat
eDumpConfigs(DumpProcessor.java:138)
at
com.ibm.ws.kernel.boot.internal.commands.DumpProcessor.execu
te(DumpProcessor.java:58)
at
com.ibm.ws.kernel.boot.internal.commands.ServerDumpPackager.
packageServerDumps(ServerDumpPackager.java:356)
at
com.ibm.ws.kernel.boot.internal.commands.ServerDumpPackager.
packageDump(ServerDumpPackager.java:192)
at
com.ibm.ws.kernel.boot.internal.commands.ProcessControlHelpe
r.dump(ProcessControlHelper.java:315)
at
com.ibm.ws.kernel.boot.Launcher.handleActions(Launcher.java:
282)
at
com.ibm.ws.kernel.boot.Launcher.createPlatform(Launcher.java
:120)
 at com.ibm.ws.kernel.boot.Launcher.main(Launcher.java:55)
at
com.ibm.ws.kernel.boot.cmdline.EnvCheck.main(EnvCheck.java:6
1)
at
com.ibm.ws.kernel.boot.cmdline.EnvCheck.main(EnvCheck.java:3
7)

This error occurs because the client dump process cannot
find one or more of the requested Java dumps.  It results in
the server dump archive not getting created at all.  One way
to workaround this issue is to request a Java dump manually
(using server javadump myServer
--include=thread,heap,system) and once the dump is completed
and the output is in the server directory, then run the
server dump command without any additional parameters (i.e.
server dump myServer).

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty Profile - Command Line       *
*                  Tools                                       *
****************************************************************
* PROBLEM DESCRIPTION: Server dump command fails when a Java   *
*                      dump file cannot be found.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a user runs the server dump command and requests Java dumps
(such as thread, heap or system dumps) to be acquired (ex:
server dump myServer --include=thread,heap,system ), if one or
more of the requested Java dump files could not be found, it
will result in an error message such as the following:

CWWKE0018E: An exception occurred while launching the runtime
environment: java.lang.IllegalArgumentException: The source does
not exist.
java.lang.IllegalArgumentException: The source does not exist.
 at
com.ibm.ws.kernel.boot.archive.FileEntryConfig.(FileEntryConfig.
java:39)
 at
com.ibm.ws.kernel.boot.internal.commands.DumpProcessor.createDum
pConfigs(DumpProcessor.java:138)
 at
com.ibm.ws.kernel.boot.internal.commands.DumpProcessor.execute(D
umpProcessor.java:58)
 at
com.ibm.ws.kernel.boot.internal.commands.ServerDumpPackager.pack
ageServerDumps(ServerDumpPackager.java:356)
 at
com.ibm.ws.kernel.boot.internal.commands.ServerDumpPackager.pack
ageDump(ServerDumpPackager.java:192)
 at
com.ibm.ws.kernel.boot.internal.commands.ProcessControlHelper.du
mp(ProcessControlHelper.java:315)
 at
com.ibm.ws.kernel.boot.Launcher.handleActions(Launcher.java:282)
at
com.ibm.ws.kernel.boot.Launcher.createPlatform(Launcher.java:120
)
 at com.ibm.ws.kernel.boot.Launcher.main(Launcher.java:55)
 at
com.ibm.ws.kernel.boot.cmdline.EnvCheck.main(EnvCheck.java:61)
 at
com.ibm.ws.kernel.boot.cmdline.EnvCheck.main(EnvCheck.java:37)

This error occurs because the client dump process cannot find
one or more of the requested Java dumps.  It results in the
server dump archive not getting created at all.  One way to
workaround this issue is to request a Java dump manually (using
server javadump myServer --include=thread,heap,system) and once
the dump is completed and the output is in the server directory,
then run the server dump command without any additional
parameters (i.e. server dump myServer).

    



Problem conclusion


    

  • The fix for this APAR ensures that the server dump will still
proceed in the event that a Java dump file could not be located.
The command line tool will output the location that it expected
to find the Java dump.

The fix for this APAR is currently targeted for inclusion in fix
pack 8.5.5.7.  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
    PI46612
    • 

  • Reported component name
    WAS LIBERTY COR
    • 

  • Reported component ID
    5725L2900
    • 

  • Reported release
    855
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2015-08-11
    • 

  • Closed date
    2015-08-17
    • 

  • Last modified date
    2015-08-17
    • 





    

  • 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
    WAS LIBERTY COR
    • 

  • Fixed component ID
    5725L2900
    • 



Applicable component levels


    

  • R855  PSY
       UP
    • 








      
              
                            

              

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

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            28 April 2022
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback