Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4715

Write jvm information and path of derby.jar to derby.log

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Newcomer, Patch Available
    • Seen in production

    Description

      The bug is part of DERBY-1272. In production environment, derby.jar can be located different than the derbyclient.jar It can be easier if we have jvm version information and path of derby.jar are in the derby.log

      Attachments

        1. derby.log
          1 kB
          Lily Wei
        2. DERBY-4715-1.diff
          6 kB
          Lily Wei
        3. DERBY-4715-10.5_967304.diff
          20 kB
          Lily Wei
        4. DERBY-4715-10.6_967304.diff
          21 kB
          Lily Wei
        5. DERBY-4715-2.diff
          19 kB
          Lily Wei
        6. DERBY-4715-3.diff
          19 kB
          Lily Wei
        7. DERBY-4715-4.diff
          19 kB
          Lily Wei
        8. DERBY-4715-5.diff
          19 kB
          Lily Wei
        9. DERBY-4715-6.diff
          3 kB
          Lily Wei
        10. DERBY-4715-7.diff
          3 kB
          Lily Wei
        11. DERBY-4715-8.diff
          3 kB
          Lily Wei

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            lilywei Lily Wei
            lilywei Lily Wei
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment