OpenJPA
  1. OpenJPA
  2. OPENJPA-2236

Trace of connection info can cause class transform/enhancement to fail

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.1, 2.3.0
    • Fix Version/s: 1.2.3, 2.2.1, 2.3.0
    • Component/s: jdbc
    • Labels:
      None

      Description

      While transforming persistent classes, if a specific DBDictionary is not provided, OpenJPA attempts to detect and set up a dictionary. Within this process, DBDictionary.connectedConfiguration() is called (to determine the DB type) when a connection is obtained. If trace is enabled, information about the connection is traced. I hit a case where one of the methods that is called on the connection to gather trace data threw an exception, resulting in classes not being enhanced. The simple (but not always possible) workaround is to specify the db dictionary type. Regardless, a trace point should not cause a catastrophic failure.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Jeremy Bauer
            Reporter:
            Jeremy Bauer
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development