Troubleshoot > Troubleshooting and Limitations – Discovery Modules > Troubleshooting and Limitations – GlassFish Discovery

Troubleshooting and Limitations – GlassFish Discovery

This section describes troubleshooting and limitations for GlassFish discovery.

  • DFM can discover a J2EE application only when its .ear file is unzipped to a folder.
  • Sometimes the command line of the GlassFish process is too large, so it does not fit in to the appropriate field in the probe database while running Host Resources or Applications discovery. In such a case:
    1. Stop the probe.
    2. Open %DatafFlowProbeHome%/tools/dbscripts/create_netlinks_db_tables.sql.
    3. Change the size of cmdline for the Processes table from 4000 to 8000, or more if needed.
    4. Change the size of cmdline for the Applications table from 512 to 8000, or more if needed.
    5. Save the file.
    6. Run the clearProbeData.bat script.
    7. Start the probe.