Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6157

Connection URL ignored for SQL Server datasource

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 10.0.0.Final
    • None
    • None

    Description

      The connection-url for a datasource is being ignored (or more likely, getting lost somewhere) when using WildFly with the Microsoft SQL Server JDBC driver. No matter what I specify as the connection-url (even something obviously invalid like "foobar"), the driver always ends up using the defaults that are baked into it.

      The same driver worked fine on WildFly 10 CR2 (and many earlier versions), so some change between then and 10 Final has caused a regression.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-6200 connection-url is required even when not used

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7018 Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-6198 When a datasource has no connection-properties and its driver has defined datasource-class a warning should be issued

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jgreene@redhat.com Jason Greene
              rdicroce Richard DiCroce (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: