[JBoss JIRA] (WFLY-13121) jgroups channel protocol read-resource error with include-runtime
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13121?page=com.atlassian.jira.plugi... ]
Radoslav Husar reassigned WFLY-13121:
-------------------------------------
Component/s: (was: Management)
Assignee: Radoslav Husar (was: Brian Stansberry)
[~brian.stansberry] [~jdenise] This is almost certainly a clustering issue, the problem only appears to happen when there is no application deployed.
> jgroups channel protocol read-resource error with include-runtime
> ------------------------------------------------------------------
>
> Key: WFLY-13121
> URL: https://issues.redhat.com/browse/WFLY-13121
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 19.0.0.Beta2
> Reporter: Jean Francois Denise
> Assignee: Radoslav Husar
> Priority: Major
>
> Start standlone-ha.xml
> /subsystem=jgroups/channel=ee/protocol=UDP:read-resource(include-runtime
> Client:
> {
> "outcome" => "failed",
> "rolled-back" => true
> }
> Server:
> 12:01:32,541 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("subsystem" => "jgroups"),
> ("channel" => "ee"),
> ("protocol" => "UDP")
> ]) - failure description: "newValue is null"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13121) jgroups channel protocol read-resource error with include-runtime
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13121?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13121:
----------------------------------
Affects Version/s: 19.0.0.Beta2
> jgroups channel protocol read-resource error with include-runtime
> ------------------------------------------------------------------
>
> Key: WFLY-13121
> URL: https://issues.redhat.com/browse/WFLY-13121
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 19.0.0.Beta2
> Reporter: Jean Francois Denise
> Assignee: Radoslav Husar
> Priority: Major
>
> Start standlone-ha.xml
> /subsystem=jgroups/channel=ee/protocol=UDP:read-resource(include-runtime
> Client:
> {
> "outcome" => "failed",
> "rolled-back" => true
> }
> Server:
> 12:01:32,541 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("subsystem" => "jgroups"),
> ("channel" => "ee"),
> ("protocol" => "UDP")
> ]) - failure description: "newValue is null"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13126) Refactor EJB client affinity processing
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13126?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz updated WFLY-13126:
---------------------------------------
Summary: Refactor EJB client affinity processing (was: jboss-ejb-client affinity refactor)
> Refactor EJB client affinity processing
> ---------------------------------------
>
> Key: WFLY-13126
> URL: https://issues.redhat.com/browse/WFLY-13126
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Reporter: Cheng Fang
> Assignee: Richard Achmatowicz
> Priority: Major
> Labels: EAP-CD20
>
> Refactor of jboss-ejb-client internal operation: change the way in which proxy affinity (an object that decides on which node invocation should be performed) is determined. Instead of calculating it on client side we would let server set the affinity when necessary and propagate it to the client.
> This refactor is supposed to reduce the complexity of jboss-ejb-client code and as a result, make it significantly easier to maintain. Richard has prepared a comprehensive document describing the suggested modifications: https://mojo.redhat.com/docs/DOC-1204767
> Parallelly, the test suite has to be refactored to make it compatible with the new algorithm and to provide broad coverage of jboss-ejb-client operation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13126) jboss-ejb-client affinity refactor
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-13126?page=com.atlassian.jira.plugi... ]
Cheng Fang moved EAP7-1450 to WFLY-13126:
-----------------------------------------
Project: WildFly (was: JBoss EAP Planning for version 7 and above)
Key: WFLY-13126 (was: EAP7-1450)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0)
Component/s: EJB
(was: EJB)
EAP PT Pre-Checked (PC): (was: TODO)
Target Release: (was: 7.4.0.GA)
EAP PT Community Docs (CD): (was: TODO)
EAP PT Product Docs (PD): (was: New)
EAP PT Test Dev (TD): (was: TODO)
EAP PT Docs Analysis (DA): (was: TODO)
EAP PT Test Plan (TP): (was: TODO)
EAP PT Analysis Document (AD): (was: TODO)
> jboss-ejb-client affinity refactor
> ----------------------------------
>
> Key: WFLY-13126
> URL: https://issues.redhat.com/browse/WFLY-13126
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Reporter: Cheng Fang
> Assignee: Richard Achmatowicz
> Priority: Major
> Labels: EAP-CD20
>
> Refactor of jboss-ejb-client internal operation: change the way in which proxy affinity (an object that decides on which node invocation should be performed) is determined. Instead of calculating it on client side we would let server set the affinity when necessary and propagate it to the client.
> This refactor is supposed to reduce the complexity of jboss-ejb-client code and as a result, make it significantly easier to maintain. Richard has prepared a comprehensive document describing the suggested modifications: https://mojo.redhat.com/docs/DOC-1204767
> Parallelly, the test suite has to be refactored to make it compatible with the new algorithm and to provide broad coverage of jboss-ejb-client operation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFCORE-4854) Layers for application and management core security realms
by Jean Francois Denise (Jira)
Jean Francois Denise created WFCORE-4854:
--------------------------------------------
Summary: Layers for application and management core security realms
Key: WFCORE-4854
URL: https://issues.redhat.com/browse/WFCORE-4854
Project: WildFly Core
Issue Type: Enhancement
Components: Build System
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
Today core-security-realms contains both realms in the form of feature-groups. By introducing 2 layers for each realm, core-security-realms could then depend optionally on them. being optional, one could exclude security realms.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months