[JBoss JIRA] (WFLY-10257) Cannot add non-anonymous entries to authentication configuration via console
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-10257?page=com.atlassian.jira.plugin... ]
David Lloyd resolved WFLY-10257.
--------------------------------
Fix Version/s: 13.0.0.Beta1
Resolution: Done
The new web console does fix the issue; I am able to add an authentication configuration. Thanks!
> Cannot add non-anonymous entries to authentication configuration via console
> ----------------------------------------------------------------------------
>
> Key: WFLY-10257
> URL: https://issues.jboss.org/browse/WFLY-10257
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Reporter: David Lloyd
> Assignee: Harald Pehl
> Priority: Critical
> Fix For: 13.0.0.Beta1
>
>
> If you try to add an authentication configuration which includes an authentication-name (i.e. is not anonymous), you get an error because the "anonymous" attribute is present even though it is not valid due to the use of alternatives.
> This appears to be a realization of a more general problem handling alternative attribute sets.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (AG-69) Pool-less mode
by Jesper Pedersen (JIRA)
Jesper Pedersen created AG-69:
---------------------------------
Summary: Pool-less mode
Key: AG-69
URL: https://issues.jboss.org/browse/AG-69
Project: Agroal
Issue Type: Feature Request
Components: pool
Reporter: Jesper Pedersen
Assignee: Luis Barreiro
In scenarios where multiple pools access the same data source instance you may end up in a situation where the combined number of max-pool-size is greater than the maximum number of connections in the data source.
Introduce a pool-less mode, where the underlying connection is closed upon return to the pool if the pool size is greater than min-pool-size.
This will allow you to configure Agroal to
{{.mode("pool-less").minSize(0).maxSize(1)}}
that only use 1 connection that is returned upon close. This is especially useful for service-mesh scenarios where each service is short-lived, and process one transaction.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-3758) :start-servers operation can start servers when the host is in admin-only mode
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3758?page=com.atlassian.jira.plugi... ]
Yeray Borges moved WFLY-10267 to WFCORE-3758:
---------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-3758 (was: WFLY-10267)
Component/s: Domain Management
(was: Domain Management)
Affects Version/s: (was: 12.0.0.Final)
> :start-servers operation can start servers when the host is in admin-only mode
> ------------------------------------------------------------------------------
>
> Key: WFCORE-3758
> URL: https://issues.jboss.org/browse/WFCORE-3758
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Yeray Borges
> Assignee: Yeray Borges
>
> If a Host Controler is reloaded or started in admin-only mode, it is possible to start the servers using {{:start-servers}} operation. It is problematic when the user reloads the Host Controller without restarting the servers and tries to start the servers afterwards.
> By definition, when the host controller is started in admin-only, it will not start any server. Indeed, if the user tries to start a single server using {{/host=master/server-config=server-one:start}} an error is correctly reported:
> {code:xml}
> [domain@localhost:9990 /] /host=master/server-config=server-one:start
> {
> "outcome" => "failed",
> "failure-description" => "WFLYHC0048: Cannot start servers when the Host Controller running mode is ADMIN_ONLY",
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-3758) start-servers operation can start servers when the host is in admin-only mode
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3758?page=com.atlassian.jira.plugi... ]
Yeray Borges updated WFCORE-3758:
---------------------------------
Summary: start-servers operation can start servers when the host is in admin-only mode (was: :start-servers operation can start servers when the host is in admin-only mode)
> start-servers operation can start servers when the host is in admin-only mode
> -----------------------------------------------------------------------------
>
> Key: WFCORE-3758
> URL: https://issues.jboss.org/browse/WFCORE-3758
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Yeray Borges
> Assignee: Yeray Borges
>
> If a Host Controler is reloaded or started in admin-only mode, it is possible to start the servers using {{:start-servers}} operation. It is problematic when the user reloads the Host Controller without restarting the servers and tries to start the servers afterwards.
> By definition, when the host controller is started in admin-only, it will not start any server. Indeed, if the user tries to start a single server using {{/host=master/server-config=server-one:start}} an error is correctly reported:
> {code:xml}
> [domain@localhost:9990 /] /host=master/server-config=server-one:start
> {
> "outcome" => "failed",
> "failure-description" => "WFLYHC0048: Cannot start servers when the Host Controller running mode is ADMIN_ONLY",
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10267) :start-servers operation can start servers when the host is in admin-only mode
by Yeray Borges (JIRA)
Yeray Borges created WFLY-10267:
-----------------------------------
Summary: :start-servers operation can start servers when the host is in admin-only mode
Key: WFLY-10267
URL: https://issues.jboss.org/browse/WFLY-10267
Project: WildFly
Issue Type: Bug
Components: Domain Management
Affects Versions: 12.0.0.Final
Reporter: Yeray Borges
Assignee: Yeray Borges
If a Host Controler is reloaded or started in admin-only mode, it is possible to start the servers using {{:start-servers}} operation. It is problematic when the user reloads the Host Controller without restarting the servers and tries to start the servers afterwards.
By definition, when the host controller is started in admin-only, it will not start any server. Indeed, if the user tries to start a single server using {{/host=master/server-config=server-one:start}} an error is correctly reported:
{code:xml}
[domain@localhost:9990 /] /host=master/server-config=server-one:start
{
"outcome" => "failed",
"failure-description" => "WFLYHC0048: Cannot start servers when the Host Controller running mode is ADMIN_ONLY",
"rolled-back" => true
}
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10258) Prevent enlisting additional resources on EJB caller side in case of server side @RequiresNew
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-10258?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-10258:
------------------------------------
[~ochaloup] Hmm good points. I wonder if there's some way we could improve it though. What if we proactively delisted the resource with TMSUCCESS before prepare begins? Will the TM still try to include it in commit processing?
> Prevent enlisting additional resources on EJB caller side in case of server side @RequiresNew
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-10258
> URL: https://issues.jboss.org/browse/WFLY-10258
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 12.0.0.Final
> Reporter: Jörg Bäsner
>
> Scenario:
> - server-1 (intermediary)
> -- Running standalone profile
> -- Has a remote-outbound-connection pointing at server-2 through server-2's public IP address
> -- Intermediary bean need to lookup the Target bean in server-2 and also inject the {{TransactionManager}}
> -- Intermediary bean need to enlist a _dummy_ XAResource
> - server-2 (target)
> -- disable {{JBOSS-LOCAL-USER}} auth
> -- Target bean needs to be annotated with {{@REQUIRES_NEW}} (important)
> - Standalone EJB client invokes an intermediary bean server-1, which as a result invokes target bean on server-2.
> The _dummy_ XAResource should log in the {{commit}} method whether one-phase optimization is being used like:
> {code}
> @Override
> public void commit(Xid arg0, boolean onePhaseOptim) throws XAException {
> logger.info("-- Committing in the client resource. One-phase optimisation is: " + onePhaseOptim + " --"
> + (onePhaseOptim ? "" : " -> TWO-PHASE COMMIT !!!"));
> }
> {code}
> In this scenario it is expected that the one-phase optimization is being used!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years