[jboss-jira] [JBoss JIRA] (WFLY-9681) Deleting ExampleDS Leaves Remnants in standalone.xml
Chris Giddings (JIRA)
issues at jboss.org
Wed Jan 17 09:41:00 EST 2018
[ https://issues.jboss.org/browse/WFLY-9681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13520175#comment-13520175 ]
Chris Giddings commented on WFLY-9681:
--------------------------------------
[~jaikiran], The error posted (from StackOverflow) is not my own, but mine is nearly identical.
For the WAR file I'm attempting to deploy myself, yes. Rather prolifically.
I'm currently running a POC to transition our applications from Tomcat 8 to Wildfly (11 Final) for easier cluster and HA management.
> Deleting ExampleDS Leaves Remnants in standalone.xml
> ----------------------------------------------------
>
> Key: WFLY-9681
> URL: https://issues.jboss.org/browse/WFLY-9681
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 11.0.0.Final
> Reporter: Chris Giddings
> Assignee: Stefano Maestri
> Priority: Minor
> Labels: JDBC
>
> h2. SUMMARY
> When initially installing Wildfly 11.0.0 Final, the installation comes pre-configured with a datasource labeled "Example DS".
> When this datasource is deleted, some configuration for it remains in the standalone.xml file for the standalone server mode.
> h2. WORKAROUND
> Removing this configuration manually and restarting Wildfly in standalone mode resolves the issue. (I tested by searching for "ExampleDS" as a string match in vi and deleting the one line the match found)
> h2. BUG JUSTIFICATION
> # I would expect anything labeled as "Example" to be deleted by an administrator in most environments
> # I would expect deleted items to be fully removed upon deletion so remnant configuration couldn't cause issues with unrelated deployments (i.e. deployments which don't specifically require the deleted item)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list