[JBoss JIRA] (WFLY-4379) Always expose <transaction-support> for resource adapters
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4379?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-4379:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Always expose <transaction-support> for resource adapters
> ---------------------------------------------------------
>
> Key: WFLY-4379
> URL: https://issues.jboss.org/browse/WFLY-4379
> Project: WildFly
> Issue Type: Task
> Components: JCA
> Reporter: Jesper Pedersen
> Assignee: Stefano Maestri
> Priority: Critical
> Fix For: 10.0.0.Alpha3
>
>
> The <transaction-support> setting for resource adapters should always be exposed in the DMR model - e.g. no "undefined".
> If the value isn't explicit defined by the deployment, then it will be obtained from the metadata repository of the archive in question.
> This also makes it clear that <xa-pool> is used for XATransaction deployments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4378) Infinispan/JGroups subsystem check for and correct diffs in the default config we ship vs. what we persist
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4378?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-4378:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Infinispan/JGroups subsystem check for and correct diffs in the default config we ship vs. what we persist
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4378
> URL: https://issues.jboss.org/browse/WFLY-4378
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 10.0.0.Alpha3
>
>
> https://github.com/wildfly/wildfly/pull/7184#issuecomment-75439059
> Brian:
> {quote}Semi-tangent: could you guys check for and correct diffs in the default config we ship vs. what we persist? E.g.
> 1) Start a new server running standalone-full-ha.xml
> 2) Use cli to add a system prop (just to force persistence)
> 3) Diff standalone-full-ha.xml vs standalone/configuration/standalone_xml_history/standalone-full-ha.initial.xml
> There shouldn't be changes other than the added system prop. Any changes mean either our default configs are wrong or the marshalling is wrong. Both should match xsd. I did this for another reason a couple weeks ago and saw some changes in the clustering subsystems. Perhaps this PR fixes the problem, but I have a feeling I saw something else besides this.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4435) Booting profile with infinispan/jgroups pre-3_0 subsystems fails with "Resource ... cannot be created until all ancestor resources have been added"
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4435?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-4435:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Booting profile with infinispan/jgroups pre-3_0 subsystems fails with "Resource ... cannot be created until all ancestor resources have been added"
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4435
> URL: https://issues.jboss.org/browse/WFLY-4435
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
> Fix For: 9.0.0.CR2, 10.0.0.Alpha3
>
>
> The same problem happens when attempting to use 2_0 version of these subsystems in current configuration.
> {noformat}
> [Host Controller] [0m[0m15:33:41,155 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version![0m
> [Host Controller] [0m[0m15:33:41,161 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute default-clustered-sfsb-cache is deprecated, and it might be removed in future version![0m
> [Host Controller] [0m[31m15:33:41,174 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([[0m
> [Host Controller] [31m ("profile" => "full-ha"),[0m
> [Host Controller] [31m ("subsystem" => "jgroups"),[0m
> [Host Controller] [31m ("channel" => "server")[0m
> [Host Controller] [31m]) - failure description: "WFLYCTL0175: Resource [[0m
> [Host Controller] [31m (\"profile\" => \"full-ha\"),[0m
> [Host Controller] [31m (\"subsystem\" => \"jgroups\")[0m
> [Host Controller] [31m] does not exist; a resource at address [[0m
> [Host Controller] [31m (\"profile\" => \"full-ha\"),[0m
> [Host Controller] [31m (\"subsystem\" => \"jgroups\"),[0m
> [Host Controller] [31m (\"channel\" => \"server\")[0m
> [Host Controller] [31m] cannot be created until all ancestor resources have been added"[0m
> [Host Controller] [31m[0m[31m15:33:41,183 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.[0m
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (WFLY-4431) IJ020017: Invalid archive
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-4431?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-4431:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> IJ020017: Invalid archive
> --------------------------
>
> Key: WFLY-4431
> URL: https://issues.jboss.org/browse/WFLY-4431
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Jesper Pedersen
> Assignee: Stefano Maestri
> Priority: Critical
> Fix For: 10.0.0.Alpha3
>
>
> {noformat}
> wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/tmp/vfs/temp/temp146a05eee4929397/content-167c9962bff9f1b5/contents/
> {noformat}
> is shown as path, where as
> {noformat}
> wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/tmp/vfs/temp/temp146a05eee4929397/content-167c9962bff9f1b5/content
> {noformat}
> should be used, or the .rar archive should be expanded into the directory
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month