[JBoss JIRA] (WFLY-5427) If used journal object store (AMQ Artemis journal) directory is named HornetqObjectStore
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5427?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5427:
-------------------------------
Fix Version/s: 12.0.0.Alpha1
(was: 11.0.0.Final)
> If used journal object store (AMQ Artemis journal) directory is named HornetqObjectStore
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-5427
> URL: https://issues.jboss.org/browse/WFLY-5427
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 10.0.0.CR2
> Reporter: Ondra Chaloupka
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 12.0.0.Alpha1
>
>
> Directory of transaction object store is named {{standalone/data/tx-object-store/HornetqObjectStore}}. The WFLY 10 does not use HornetQ object store but it uses ActiveMQ Artemis object store. That's same for the Transaction subsystem.
> The journal dirctory should be renamed to {{JournalObjectStore}} or something similar.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-5265) Use WildFly Common for null param checks
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5265?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5265:
-------------------------------
Fix Version/s: 12.0.0.Alpha1
(was: 11.0.0.Final)
> Use WildFly Common for null param checks
> ----------------------------------------
>
> Key: WFLY-5265
> URL: https://issues.jboss.org/browse/WFLY-5265
> Project: WildFly
> Issue Type: Task
> Reporter: David Lloyd
> Assignee: David Lloyd
> Priority: Minor
> Fix For: 12.0.0.Alpha1
>
>
> For each module, do the following:
> * Locate any/all null param check methods in the log msg
> * Replace them with calls to org.wildfly.common.Assert#checkNotNullParam or related method as needed
> * Replace the old null param check method with a comment that reserves the ID and shows that it was previously used for that purpose
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-5141) Custom operation for setting of process-id-*
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5141?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5141:
-------------------------------
Fix Version/s: 12.0.0.Alpha1
(was: 11.0.0.Final)
> Custom operation for setting of process-id-*
> --------------------------------------------
>
> Key: WFLY-5141
> URL: https://issues.jboss.org/browse/WFLY-5141
> Project: WildFly
> Issue Type: Feature Request
> Components: Transactions
> Affects Versions: 10.0.0.Beta1
> Reporter: Ondra Chaloupka
> Assignee: Amos Feng
> Priority: Minor
> Labels: ux
> Fix For: 12.0.0.Alpha1
>
>
> When you want to set generation of process-id-* - either as uuid or as socket id the way to set it and set it back is inconsistent. In one direction you need to use composite operation in other direction you can't use it.
> All this is discussed in jiras WFLY-2623 and WFLY-5126
> As result of discussion https://issues.jboss.org/browse/WFLY-2623#comment-13100037 this issue is raised.
> It would be much better for user to have single way how to do this switching and custom operation could solve this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-5551) Formalize ejb clustering modules into a proper subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5551?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5551:
-------------------------------
Fix Version/s: 12.0.0.Alpha1
(was: 11.0.0.Final)
> Formalize ejb clustering modules into a proper subsystem
> --------------------------------------------------------
>
> Key: WFLY-5551
> URL: https://issues.jboss.org/browse/WFLY-5551
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 10.0.0.CR3
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 12.0.0.Alpha1
>
>
> Currently, the coupling between the ejb3 subsystem and the modules required for the distributed cache is very loose.
> Consequently, misconfiguration (e.g. a missing "ejb" cache-container) can prevent deployment from succeeding without an adequate explanation.
> The subsystem would define the requisite cache-container, exposed as a capability.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-5550) Formalize web session clustering modules into a proper subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5550?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5550:
-------------------------------
Fix Version/s: 12.0.0.Alpha1
(was: 11.0.0.Final)
> Formalize web session clustering modules into a proper subsystem
> ----------------------------------------------------------------
>
> Key: WFLY-5550
> URL: https://issues.jboss.org/browse/WFLY-5550
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 10.0.0.CR3
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 12.0.0.Alpha1
>
>
> Currently, the coupling between the undertow subsystem and the modules required for distributed web session manager and single sign-on manager support is very loose.
> Consequently, misconfiguration (e.g. a missing "web" cache-container) can prevent deployment from succeeding without an adequate explanation.
> The subsystem would define the requisite cache-container, exposed as a capability.
> This subsystem would exposes a number of profiles, containing the configuration traditionally specified in jboss-web.xml, as well as the cache configuration to use (specified by cache-container + cache name). jboss-web.xml would only need to reference a profile by name, or, if unspecified, use the default profile.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months