Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6259946

JPLIS: Validate Boot-Class-Path attribute before adding agent JAR to application class path

    XMLWordPrintable

    Details

      Description

      Viswadeep Veguru wrote:

      > Hi Alan,
      > I have a question question / suggestion.
      >
      > What I could see here is. When I said add this jar file in BootStrapClassPath, It throws me warnning and agent will continue to execute.
      >
      > Why not we validate jar file first and attach the agent.
      >
      > Reason is
      >
      > 1) This messages comes on ( console or log) of Target (Application), So Tool doesn;t have any clue. What's happening.
      >
      > 2) If My agent start's using any of this jar file class, Then It will endup in throwing NoClassDefFoundError on Target (console or log).
      >
      > Because, We don;t have any way to send back warnings.
      >
      >
      >
      > <Target Console>
      > WARNING: ./ver1.0/AOD009005Agent.jar not added to bootstrap class loader search: Illegal argument or not JAR file
      > </Tatget Console>


      Yes, it is a warning - the agent's JAR file is added to the application class path before we process the Boot-Class-Path attribute. We could do some minimal validation of the Boot-Class-Path attribute to catch configuration problems early - for example check that the file exists and is a JAR file. It's possible that we still fail later but the chances are much reduced.

      -Alan
      ###@###.### 2005-04-22 09:18:54 GMT

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            alanb Alan Bateman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: