[JBoss JIRA] (WFLY-6123) Infinispan subsystem XSD doesn't document all possible values of <transaction mode="...">
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6123?page=com.atlassian.jira.plugin.... ]
Radoslav Husar reassigned WFLY-6123:
------------------------------------
Assignee: Radoslav Husar (was: Paul Ferraro)
> Infinispan subsystem XSD doesn't document all possible values of <transaction mode="...">
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-6123
> URL: https://issues.jboss.org/browse/WFLY-6123
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Ladislav Thon
> Assignee: Radoslav Husar
>
> The XSD for the Infinispan subsystem ({{jboss-as-infinispan_4_0.xsd}}) says the following about {{<transaction mode="...">}}:
> bq. Sets the cache transaction mode to one of NONE, NON_XA, NON_DURABLE_XA, FULL_XA.
> However, the enum {{org.jboss.as.clustering.infinispan.subsystem.TransactionMode}} has the following values:
> - {{NONE}}
> - {{BATCH}}
> - {{NON_XA}}
> - {{NON_DURABLE_XA}}
> - {{FULL_XA}}
> I.e., the {{BATCH}} value is missing from the documentation. Interestingly, {{BATCH}} is also used in the default config for all the {{web}} and {{ejb}} caches.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6118) EJB subsystem adds a capability but does not remove it in remove handler
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-6118?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-6118:
-----------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/8649
> EJB subsystem adds a capability but does not remove it in remove handler
> ------------------------------------------------------------------------
>
> Key: WFLY-6118
> URL: https://issues.jboss.org/browse/WFLY-6118
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, EJB
> Affects Versions: 10.0.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 10.1.0.Final
>
>
> EJB3SubsystemAdd adds capability org.wildfly.ejb3.clustered.singleton but then EJB3SubsystemRemove does not remove it.
> This breaks use cases where the subsystem is repeatedly added, particularly a cycle of
> /profile=foo:clone(to-profile=bar)
> ... make some adjustments to bar
> ... oops, screwed up on those adjustments, lets start over!
> /profile=bar:remove
> /profile=foo:clone(to-profile=bar)
> The last step will fail with:
> {code}
> [Host Controller] &#27;[33m&#27;[0m&#27;[31m12:05:13,818 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("add") failed - address: ([&#27;[0m
> [Host Controller] &#27;[31m ("profile" => "clone"),&#27;[0m
> [Host Controller] &#27;[31m ("subsystem" => "ejb3")&#27;[0m
> [Host Controller] &#27;[31m]): java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.ejb3.clustered.singleton' is already registered in context 'profile=clone'.&#27;[0m
> [Host Controller] &#27;[31m at org.jboss.as.controller.CapabilityRegistry.registerCapability(CapabilityRegistry.java:146)&#27;[0m
> [Host Controller] &#27;[31m at org.jboss.as.controller.OperationContextImpl.registerCapability(OperationContextImpl.java:1430)&#27;[0m
> [Host Controller] &#27;[31m at org.jboss.as.controller.OperationContextImpl.registerCapability(OperationContextImpl.java:1417)&#27;[0m
> [Host Controller] &#27;[31m at org.jboss.as.ejb3.subsystem.EJB3SubsystemAdd.recordCapabilitiesAndRequirements(EJB3SubsystemAdd.java:178)&#27;[0m
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFCORE-1354) Cannot clone a profile with a remoting subsystem but no io subsystem
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1354?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1354:
-------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1407
> Cannot clone a profile with a remoting subsystem but no io subsystem
> --------------------------------------------------------------------
>
> Key: WFCORE-1354
> URL: https://issues.jboss.org/browse/WFCORE-1354
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Remoting
> Affects Versions: 2.0.10.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 2.1.0.CR2
>
>
> The remoting subsystem added a requirement for the new io subsystem's worker capability, but it has special logic such that the requirement is only added if an endpoint resource is configured. So, legacy configs (pre-io) won't have that resource, so there is no requirement.
> This breaks down in the case of the profile 'clone' op, as a placeholder resource we add for the endpoint (to allow reads of the default endpoint config data) ends up getting 'described' and added by the cloning process. So that added resource triggers an unmet requirement for the io worker:
> {code}
> [domain@localhost:9990 /] /profile=default:clone(to-profile=test)
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYCTL0369: Required capabilities are not available:
> org.wildfly.io.worker.default in context 'profile=test'; There are no known registration points which can provide this capability."},
> "rolled-back" => true
> }
> {code}
> I'm not sure how to deal with this; some sort of marker is needed to disable 'describing' that placeholder resource.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFCORE-1340) Store "host ignore" data in the domain wide model
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1340?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1340:
-------------------------------------
Fix Version/s: 2.1.0.CR2
(was: 3.0.0.Alpha1)
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1407
> Store "host ignore" data in the domain wide model
> -------------------------------------------------
>
> Key: WFCORE-1340
> URL: https://issues.jboss.org/browse/WFCORE-1340
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 2.1.0.CR2
>
>
> Including an EAP 6.x slave in a mixed domain managed by a WF 10 / EAP 7 DC is overly difficult operationally because potentially numerous host configurations need to be manually updated whenever new server groups and profiles are added.
> An issue with managing mixed domains is the need for the slave's host.xml to include configuration of what domain-wide content should be ignored. This isn't nice as it requires modifying potentially many host configs when new domain-wide content is added (e.g. new server groups or profiles that the legacy slaves won't understand.)
> Core 2 / Full 10 are better in this regard as they allow "ignore-unused-configuration" where stuff is auto-ignored. But this still has weaknesses:
> 1) The "ignore-unused-configuration" logic is slave-side and is not present in EAP 6.x slaves. So for those slaves manual configuration is the only option.
> 2) Extensions are not covered, so new extensions in later releases may need to be manually configured.
> Idea here is to include config for host-ignores in the domain-wide model, for use by the DC. It's in the domain-wide model, not the DC's host.xml, to ensure that any backup HC has the latest data. The concept will be referred to as a "host-exclude" because what is happening in this case is not the slave ignoring some resources, it's the DC excluding them from the slave's view.
> Proposed structure:
> Resources are at address /host-exclude=*
> Attributes are:
> * management-major-version
> * management-minor-version
> * management-micro-version
> * host-release
> These identify the category of slave to which host-ignore data should be applied when a matching slave registers. The first 3 attributes identify the *core management API version* of the slave (not its release version.) The last is a user-friendly *alternative* to the first 3 and is an enum identifying well known releases (e.g. EAP6.2, EAP6.3, EAP6.4, WildFly10.0) from which the api versions can be derived.
> If management-micro-version is undefined, the meaning is the config applies to all releases of the given major/minor version, excluding any for which a config with a micro version specified is also present. Not specifying a micro is expected to be the norm. The "slave-release" enums will be for minors.
> In addition to the above scoping attributes, the following attributes will be supported:
> * ignored-extensions
> * active-server-groups
> * active-socket-binding-groups
> The ignored-extensions attribute is a list of extension names the resources for which (/extension=X) should be treated as ignored by the target hosts.
> The active-server-groups attribute is a list of server groups names the members of which should be treated as *not* ignored by the target hosts. These are the groups used by the host's servers. The server-group and related profile and socket-binding-group resources will not be ignored; all others of these types will be ignored. This is the same data that a core 2 / WF 10 slave sends when it registers. This JIRA just provides a different mechanism for making the data known to the DC.
> The active-socket-binding-groups attribute is only meaningful if active-server-groups is set, and it only needs to be set if the set of socket-binding-groups associated with the groups listed in active-socket-binding-groups is not the complete set of sbgs needed on server's running the legacy release. This can happen is the server-config element for some servers overrides the normal socket-binding-group specified in the server-group config and specifies some different sbg. This is expected to be an edge case.
>
> Adding a new group to active-server-groups will not cause existing slave HCs to get new data sent to them. The slave will need to reconnect to get new data.
> Changing the profile or socket-binding-group associated with a group listed in active-server-groups will not cause existing slave HCs to get new data sent to them. The slave will need to reconnect to get new data.
> There is other data that could be included in these resources, e.g. fine grained "exclude" information matching what can be configured in host.xml, but that is out of scope for this first cut, and may never be added if there is no clear demand.
> A WildFly Core 2 or later slave will send its ignore-unused-configuration setting when it registers. If this is set to 'true', the DC will not use any of the domain wide active-server-groups and active-socket-binding-groups data in its handling of that slave. That setting means the slave is taking responsibility for informing the DC of what should server-groups, profiles and socket-binding-groups be ignored. Mixing this WFCORE-1340 functionality into that creates too much complication. However, the domain-wide 'ignored-extensions' data *will* be used for the slave.
> An EAP 6.x slave can't set ignore-unused-configuration, so there is no confusion for that use case, which is the primary one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFCORE-1353) Cannot clone or ad-hoc describe legacy extensions
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1353?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1353:
-------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1407
> Cannot clone or ad-hoc describe legacy extensions
> -------------------------------------------------
>
> Key: WFCORE-1353
> URL: https://issues.jboss.org/browse/WFCORE-1353
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.10.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 2.1.0.CR2
>
>
> Trying to clone a profile that includes legacy extensions results in this failure (which is buried and not properly reported, but that's a different problem):
> WFLYCTL0309: Legacy extension 'org.jboss.as.web' is not supported on servers running this version. The extension is only supported for use by hosts running a previous release in a mixed-version managed domain
> It's created by UnsupportedSubsystemDescribeHandler.
> That failure made some sense when the only use of the 'describe' op was by an HC launching a domain server, but now 'describe' is also an impl detail of the 'clone' op, and describe may also be executed independently by users.
> We need to distinguish the server launch case from other uses and only fail in the former.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-4840) Deprecated element cluster-passivation-store from ejb subsystem does not work
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4840?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-4840 at 2/4/16 9:12 AM:
--------------------------------------------------------------
The way it currently works is you configure one or the other, not both and no aliases. So the old configuration still works. So you remove one and the other such as and note that you need to restart inbetween these changes as the services will be stick around since its reload required.
{noformat}
[standalone@localhost:9990 /] /subsystem=ejb3/passivation-store=infinispan:remove
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:add
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb.cache.factory.distributable.infinispan is already registered",
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}
[standalone@localhost:9990 /] :reload
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:add
{"outcome" => "success"}
{noformat}
was (Author: rhusar):
The way it currently works is you configure one or the other, not both and no aliases. So the old configuration still works. So you remove one and the other such as
{noformat}
[standalone@localhost:9990 /] /subsystem=ejb3/passivation-store=infinispan:remove
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:add
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb.cache.factory.distributable.infinispan is already registered",
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}
[standalone@localhost:9990 /] :reload
{noformat}
> Deprecated element cluster-passivation-store from ejb subsystem does not work
> -----------------------------------------------------------------------------
>
> Key: WFLY-4840
> URL: https://issues.jboss.org/browse/WFLY-4840
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Ondřej Chaloupka
> Assignee: Radoslav Husar
>
> There is a mismatch in behaviour of deprecated element {{cluster-passivation-store}} under {{ejb}} subsystem.
> When element is deprecated still it should work and only prints warning that it's deprecated.
> {code}
> [standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:read-resource()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"ejb3\"),
> (\"cluster-passivation-store\" => \"infinispan\")
> ]' not found",
> "rolled-back" => true
> }
> {code}
> but
> {code}
> [standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:add()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb.cache.factory.distributable.infinispan is already registered",
> "rolled-back" => true
> }
> {code}
> _A note:_ the element {{cluster-passivation-store}} was replaced by {{passivation-store}} which works fine
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-4840) Deprecated element cluster-passivation-store from ejb subsystem does not work
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4840?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-4840:
--------------------------------------
The way it currently works is you configure one or the other, not both and no aliases. So the old configuration still works. So you remove one and the other such as
{noformat}
[standalone@localhost:9990 /] /subsystem=ejb3/passivation-store=infinispan:remove
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:add
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb.cache.factory.distributable.infinispan is already registered",
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}
[standalone@localhost:9990 /] :reload
{noformat}
> Deprecated element cluster-passivation-store from ejb subsystem does not work
> -----------------------------------------------------------------------------
>
> Key: WFLY-4840
> URL: https://issues.jboss.org/browse/WFLY-4840
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Ondřej Chaloupka
> Assignee: Radoslav Husar
>
> There is a mismatch in behaviour of deprecated element {{cluster-passivation-store}} under {{ejb}} subsystem.
> When element is deprecated still it should work and only prints warning that it's deprecated.
> {code}
> [standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:read-resource()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"ejb3\"),
> (\"cluster-passivation-store\" => \"infinispan\")
> ]' not found",
> "rolled-back" => true
> }
> {code}
> but
> {code}
> [standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:add()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb.cache.factory.distributable.infinispan is already registered",
> "rolled-back" => true
> }
> {code}
> _A note:_ the element {{cluster-passivation-store}} was replaced by {{passivation-store}} which works fine
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6127) JPA specification - section 7.6.4.1 - Violation?
by Mazen Mahmoud (JIRA)
Mazen Mahmoud created WFLY-6127:
-----------------------------------
Summary: JPA specification - section 7.6.4.1 - Violation?
Key: WFLY-6127
URL: https://issues.jboss.org/browse/WFLY-6127
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 9.0.2.Final
Reporter: Mazen Mahmoud
Assignee: Scott Marlow
Priority: Minor
SPEC: If a component is called and the JTA transaction is propagated into that component:
If there is a persistence context of type SynchronizationType.UNSYNCHRONIZED
associated with the JTA transaction and the target component specifies a persistence context of type SynchronizationType.SYNCHRONIZED, the IllegalStateException is thrown by the container
We have a stateful session bean (SFB1) / PC: TRANSACTION/UNSYNCHRONIZED)
stateful session bean (SFB2) / PC: TRANSACTION/SYNCHRONIZED)
SFB1 method M1 (REQUIRED) calls SFB2 Method 2 (REQUIRED):
PC is propagated from SFB1 to SFB2 without any exception.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months