[JBoss JIRA] (WFLY-13026) Upgrade jboss-ejb-client to 4.0.29.Final
by Tomasz Adamski (Jira)
[ https://issues.redhat.com/browse/WFLY-13026?page=com.atlassian.jira.plugi... ]
Tomasz Adamski updated WFLY-13026:
----------------------------------
Description:
[http://github.com/jerel/<project>/commit/479ebe3cf0d21335f0b3675e5e21a3b50af2e717|Prep 4.0.28.Final]
[http://github.com/jerel/<project>/commit/a9e94e1366420b75d05da6f6e444f040eee5f260|Next is 4.0.29.Final]
[http://github.com/jerel/<project>/commit/0fc3e1e5e40fec0a16982b3be1a31093c00fa43d|[EJBCLIENT-364] Standalone EJB-over-HTTP invocation]
[http://github.com/jerel/<project>/commit/1d41329eb450c52f36aa007f97c63fd605f6148e|Merge pull request #446 from tadamski/EJBCLIENT-364]
[http://github.com/jerel/<project>/commit/1539c2c2f194db0b2b4b8ca0d0d7ff467e8cafa3|[EJBCLIENT-361] DiscoveryEJBClientInterceptor: static blacklisting destinations after RequestSendFailedException]
[http://github.com/jerel/<project>/commit/4545f0149c1dd13d1a431d21322e5fed8d5b385f|Merge pull request #450 from tadamski/EJBCLIENT-361]
[http://github.com/jerel/<project>/commit/533f42fe21024422b59d7a82500a5038dff2f1de|EJBClientInvocationContext: log exception on the first interceptor only]
[http://github.com/jerel/<project>/commit/4ae2faae1e0dfc3c4c75f1e86f070dfa3eba8660|Prep 4.0.29.Final]
was:
<li> <a href="http://github.com/jerel/<project>/commit/479ebe3cf0d21335f0b3675e5e21a3b50af2e717">view commit •</a> Prep 4.0.28.Final</li>
<li> <a href="http://github.com/jerel/<project>/commit/a9e94e1366420b75d05da6f6e444f040eee5f260">view commit •</a> Next is 4.0.29.Final</li>
<li> <a href="http://github.com/jerel/<project>/commit/0fc3e1e5e40fec0a16982b3be1a31093c00fa43d">view commit •</a> [EJBCLIENT-364] Standalone EJB-over-HTTP invocation</li>
<li> <a href="http://github.com/jerel/<project>/commit/1d41329eb450c52f36aa007f97c63fd605f6148e">view commit •</a> Merge pull request #446 from tadamski/EJBCLIENT-364</li>
<li> <a href="http://github.com/jerel/<project>/commit/1539c2c2f194db0b2b4b8ca0d0d7ff467e8cafa3">view commit •</a> [EJBCLIENT-361] DiscoveryEJBClientInterceptor: static blacklisting destinations after RequestSendFailedException</li>
<li> <a href="http://github.com/jerel/<project>/commit/4545f0149c1dd13d1a431d21322e5fed8d5b385f">view commit •</a> Merge pull request #450 from tadamski/EJBCLIENT-361</li>
<li> <a href="http://github.com/jerel/<project>/commit/533f42fe21024422b59d7a82500a5038dff2f1de">view commit •</a> EJBClientInvocationContext: log exception on the first interceptor only</li>
<li> <a href="http://github.com/jerel/<project>/commit/4ae2faae1e0dfc3c4c75f1e86f070dfa3eba8660">view commit •</a> Prep 4.0.29.Final</li>
> Upgrade jboss-ejb-client to 4.0.29.Final
> ----------------------------------------
>
> Key: WFLY-13026
> URL: https://issues.redhat.com/browse/WFLY-13026
> Project: WildFly
> Issue Type: Component Upgrade
> Components: EJB
> Reporter: Tomasz Adamski
> Assignee: Tomasz Adamski
> Priority: Major
>
> [http://github.com/jerel/<project>/commit/479ebe3cf0d21335f0b3675e5e21a3b50af2e717|Prep 4.0.28.Final]
> [http://github.com/jerel/<project>/commit/a9e94e1366420b75d05da6f6e444f040eee5f260|Next is 4.0.29.Final]
> [http://github.com/jerel/<project>/commit/0fc3e1e5e40fec0a16982b3be1a31093c00fa43d|[EJBCLIENT-364] Standalone EJB-over-HTTP invocation]
> [http://github.com/jerel/<project>/commit/1d41329eb450c52f36aa007f97c63fd605f6148e|Merge pull request #446 from tadamski/EJBCLIENT-364]
> [http://github.com/jerel/<project>/commit/1539c2c2f194db0b2b4b8ca0d0d7ff467e8cafa3|[EJBCLIENT-361] DiscoveryEJBClientInterceptor: static blacklisting destinations after RequestSendFailedException]
> [http://github.com/jerel/<project>/commit/4545f0149c1dd13d1a431d21322e5fed8d5b385f|Merge pull request #450 from tadamski/EJBCLIENT-361]
> [http://github.com/jerel/<project>/commit/533f42fe21024422b59d7a82500a5038dff2f1de|EJBClientInvocationContext: log exception on the first interceptor only]
> [http://github.com/jerel/<project>/commit/4ae2faae1e0dfc3c4c75f1e86f070dfa3eba8660|Prep 4.0.29.Final]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFLY-13026) Upgrade jboss-ejb-client to 4.0.29.Final
by Tomasz Adamski (Jira)
[ https://issues.redhat.com/browse/WFLY-13026?page=com.atlassian.jira.plugi... ]
Tomasz Adamski updated WFLY-13026:
----------------------------------
Description:
<li> <a href="http://github.com/jerel/<project>/commit/479ebe3cf0d21335f0b3675e5e21a3b50af2e717">view commit •</a> Prep 4.0.28.Final</li>
<li> <a href="http://github.com/jerel/<project>/commit/a9e94e1366420b75d05da6f6e444f040eee5f260">view commit •</a> Next is 4.0.29.Final</li>
<li> <a href="http://github.com/jerel/<project>/commit/0fc3e1e5e40fec0a16982b3be1a31093c00fa43d">view commit •</a> [EJBCLIENT-364] Standalone EJB-over-HTTP invocation</li>
<li> <a href="http://github.com/jerel/<project>/commit/1d41329eb450c52f36aa007f97c63fd605f6148e">view commit •</a> Merge pull request #446 from tadamski/EJBCLIENT-364</li>
<li> <a href="http://github.com/jerel/<project>/commit/1539c2c2f194db0b2b4b8ca0d0d7ff467e8cafa3">view commit •</a> [EJBCLIENT-361] DiscoveryEJBClientInterceptor: static blacklisting destinations after RequestSendFailedException</li>
<li> <a href="http://github.com/jerel/<project>/commit/4545f0149c1dd13d1a431d21322e5fed8d5b385f">view commit •</a> Merge pull request #450 from tadamski/EJBCLIENT-361</li>
<li> <a href="http://github.com/jerel/<project>/commit/533f42fe21024422b59d7a82500a5038dff2f1de">view commit •</a> EJBClientInvocationContext: log exception on the first interceptor only</li>
<li> <a href="http://github.com/jerel/<project>/commit/4ae2faae1e0dfc3c4c75f1e86f070dfa3eba8660">view commit •</a> Prep 4.0.29.Final</li>
> Upgrade jboss-ejb-client to 4.0.29.Final
> ----------------------------------------
>
> Key: WFLY-13026
> URL: https://issues.redhat.com/browse/WFLY-13026
> Project: WildFly
> Issue Type: Component Upgrade
> Components: EJB
> Reporter: Tomasz Adamski
> Assignee: Tomasz Adamski
> Priority: Major
>
> <li> <a href="http://github.com/jerel/<project>/commit/479ebe3cf0d21335f0b3675e5e21a3b50af2e717">view commit •</a> Prep 4.0.28.Final</li>
> <li> <a href="http://github.com/jerel/<project>/commit/a9e94e1366420b75d05da6f6e444f040eee5f260">view commit •</a> Next is 4.0.29.Final</li>
> <li> <a href="http://github.com/jerel/<project>/commit/0fc3e1e5e40fec0a16982b3be1a31093c00fa43d">view commit •</a> [EJBCLIENT-364] Standalone EJB-over-HTTP invocation</li>
> <li> <a href="http://github.com/jerel/<project>/commit/1d41329eb450c52f36aa007f97c63fd605f6148e">view commit •</a> Merge pull request #446 from tadamski/EJBCLIENT-364</li>
> <li> <a href="http://github.com/jerel/<project>/commit/1539c2c2f194db0b2b4b8ca0d0d7ff467e8cafa3">view commit •</a> [EJBCLIENT-361] DiscoveryEJBClientInterceptor: static blacklisting destinations after RequestSendFailedException</li>
> <li> <a href="http://github.com/jerel/<project>/commit/4545f0149c1dd13d1a431d21322e5fed8d5b385f">view commit •</a> Merge pull request #450 from tadamski/EJBCLIENT-361</li>
> <li> <a href="http://github.com/jerel/<project>/commit/533f42fe21024422b59d7a82500a5038dff2f1de">view commit •</a> EJBClientInvocationContext: log exception on the first interceptor only</li>
> <li> <a href="http://github.com/jerel/<project>/commit/4ae2faae1e0dfc3c4c75f1e86f070dfa3eba8660">view commit •</a> Prep 4.0.29.Final</li>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFCORE-255) jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-255:
--------------------------------------
I can see where it's an RFE for sure then. When I filed this I wasn't quite sure of the intentions and I likely should have asked, but that was almost 6 years ago so I can't really remember all the details :)
I do recall the changes when I looked back in October were not simple. I was hoping it was as simple as just looking if those were set with {{boot-time=true}} and allowing them. That was a rather naive hope though in hindsight.
I'll go ahead and change this to a feature request. There may not be a new API needed and nothing user facing should be changed with the exception of documentation.
> jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFCORE-255) jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-255:
---------------------------------
Issue Type: Feature Request (was: Bug)
> jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFCORE-255) jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-255:
-----------------------------------------
It was intentional. It's just a limitation because we can't do everything and chose not to implement support for this.
Perhaps it's just an Enhancement instead of a Feature Request, if there is no new API, just that existing resources will accept values they would not have before.
But, I suspect that is not the case, or if it is the case the appropriate work to do it correctly, i.e. analysis, test coverage and docs is basically the same as a feature so might as well handle it as such.
For example, system properties can be set at numerous levels, but for these properties some levels likely are wrong. That all has to be analyzed and documented and perhaps it means the configuration style to use for this is not system properties but is something else that we can properly restrict.
> jboss.server.base.dir, jboss.server.config.dir and jboss.server.log.dir should also be allowed to be set as a system-property resource or overridden via JAVA_OPTS or the launch-command.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-255
> URL: https://issues.redhat.com/browse/WFCORE-255
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: domain-mode, downstream_dependency
>
> The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property.
> These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}.
> The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state.
> {code}
> [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log")
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
>
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line",
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
> These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months