[JBoss JIRA] (WFLY-9281) Unable to remove an installed resource adapter
by John Huntley (JIRA)
[ https://issues.jboss.org/browse/WFLY-9281?page=com.atlassian.jira.plugin.... ]
John Huntley commented on WFLY-9281:
------------------------------------
>From my reading of the source code I suspect that the problem is a result of the code changes introduced by WFCORE-2849 and that org.jboss.as.connector.subsystems.resourceadapters.RaRemove.java now needs an update around line 156. I did a search of this Jira project but was unable to find any other tickets referring to RaRemove that are current.
> Unable to remove an installed resource adapter
> ----------------------------------------------
>
> Key: WFLY-9281
> URL: https://issues.jboss.org/browse/WFLY-9281
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 11.0.0.CR1
> Reporter: John Huntley
> Assignee: Stefano Maestri
> Attachments: wf11-ra-error.txt
>
>
> Running a :remove operation for a defined resource adapter fails with error WFLYCTL0123.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (WFLY-9282) UserTransaction should be lazy to allow node selection (loadbalancing) even if the invocations stick to one node
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created WFLY-9282:
--------------------------------------
Summary: UserTransaction should be lazy to allow node selection (loadbalancing) even if the invocations stick to one node
Key: WFLY-9282
URL: https://issues.jboss.org/browse/WFLY-9282
Project: WildFly
Issue Type: Enhancement
Components: EJB
Environment: Remote client EJB invocation
Reporter: Wolf-Dieter Fink
Assignee: David Lloyd
It should be possible to lookup a UserTransaction from a node or a cluster and call .begin() with starting the Transaction lazy until the first EJB invocation.
The invocation will implicit begin the transaction and all invocation are sticky to that node.
This is to spread the load across several server instances if there is no running transaction but keep the transaction sticky to the first selected node.
It prevents from a strong affinity to one instance via URI affinity or the necessity to define the node for the UserTransaction upfront.
The sticiness is because of issues with persistence like JPA as here the server is not really 'stateless' as the session of EntityManager can decide to not flush the changed data to the underlying database which can cause issues if the transaction will continued on a different instance if the client invoke EJB's multiple times.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (WFLY-9281) Unable to remove an installed resource adapter
by John Huntley (JIRA)
[ https://issues.jboss.org/browse/WFLY-9281?page=com.atlassian.jira.plugin.... ]
John Huntley commented on WFLY-9281:
------------------------------------
My result from running the attached script file is:
C:\tools\wildfly-11.0.0.CR1\bin>jboss-cli --connect --file=C:\Users\jhuntley\Desktop\wf11-ra-error.txt
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0123: Stage RUNTIME is not valid for context process type HOST_CONTROLLER"},
"rolled-back" => true
}
Press any key to continue . . .
> Unable to remove an installed resource adapter
> ----------------------------------------------
>
> Key: WFLY-9281
> URL: https://issues.jboss.org/browse/WFLY-9281
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 11.0.0.CR1
> Reporter: John Huntley
> Assignee: Stefano Maestri
> Attachments: wf11-ra-error.txt
>
>
> Running a :remove operation for a defined resource adapter fails with error WFLYCTL0123.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ELY-1348) LegacyPropertiesRealm should use spec passed into getCredential
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1348?page=com.atlassian.jira.plugin.s... ]
Jan Kalina updated ELY-1348:
----------------------------
Description: As suggested in JBEAP-8700 comments, when DIGEST mechanism and plain-text properties realm used, realm should use digest realm name from HTTP mechanism - which is already passed into getCredential method but ignored by properties-realm yet. (was: There should be a possibility to retrieve additional information (e.g. Digest Realm name) in the realms when calling {{getCredential}} method. Currently such info has to be provided (duplicated) in the realm configuration.
This issue is created as follow up for JBEAP-6003. See [this comment|https://issues.jboss.org/browse/JBEAP-6003?focusedCommentId=13359...] with HipChat discussion.
)
> LegacyPropertiesRealm should use spec passed into getCredential
> ---------------------------------------------------------------
>
> Key: ELY-1348
> URL: https://issues.jboss.org/browse/ELY-1348
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Realms
> Affects Versions: 1.2.0.Beta1
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Labels: security-realm
>
> As suggested in JBEAP-8700 comments, when DIGEST mechanism and plain-text properties realm used, realm should use digest realm name from HTTP mechanism - which is already passed into getCredential method but ignored by properties-realm yet.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months