Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4067 ClientConnectionPoolDataSource.getPooledConnection and ClientXADataSource.getXAConnection ignore connection attributes
  3. DERBY-4070

Embedded and client data sources throw different exception when a connection attribute is badly formatted

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 10.4.2.1, 10.5.3.0, 10.6.1.0
    • 10.5.3.1, 10.6.1.0
    • JDBC, Network Client
    • None
    • Embedded/Client difference

    Description

      If a connection attribute is badly formatted, for instance if the attribute name is specified without a corresponding value, the embedded and the client data sources throw different exceptions:
      o XJ212: Invalid attribute syntax: bad
      o XJ028: The URL 'jdbc:derby://localhost:1527/wombat;bad' is not properly formed.

      Currently the only client data source affected is ClientDataSource, but the connection pool and XA data sources also have to deal with this issue when DERBY-4067 has been fixed.

      Attachments

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

          People

            kristwaa Kristian Waagan
            kristwaa Kristian Waagan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment