August 2017 - jboss-jira - Jboss List Archives

[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)

8 years, 8 months

1
0
0 / 0

[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)

8 years, 8 months

1
0
0 / 0

[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 updated WFLY-9281: ------------------------------- Attachment: wf11-ra-error.txt > 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)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9281) Unable to remove an installed resource adapter

by John Huntley (JIRA)

John Huntley created WFLY-9281: ---------------------------------- Summary: 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 Running a :remove operation for a defined resource adapter fails with error WFLYCTL0123. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[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)

8 years, 8 months

1
0
0 / 0

[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: ---------------------------- Summary: LegacyPropertiesRealm should use spec passed into getCredential (was: Pass additional information to Elytron Realm getCredential method) > 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 > > 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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1348) Pass additional information to Elytron Realm getCredential method

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1348?page=com.atlassian.jira.plugin.s... ] Jan Kalina moved JBEAP-12905 to ELY-1348: ----------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-1348 (was: JBEAP-12905) Issue Type: Enhancement (was: Bug) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Realms (was: Security) Affects Version/s: 1.2.0.Beta1 (was: 7.1.0.DR11) > Pass additional information to Elytron Realm getCredential method > ----------------------------------------------------------------- > > 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 > > 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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1348) Pass additional information to Elytron Realm getCredential method

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1348?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1348: ---------------------------- Labels: security-realm (was: authentication eap7.1.0-to-prd http sasl security-realm) > Pass additional information to Elytron Realm getCredential method > ----------------------------------------------------------------- > > 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 > > 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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1717) Concurrency problems with enum constraints in MVEL

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1717?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1717: ------------------------------------- Sorry [~tzimanyi] but I'm missing the domain classes for the test case you pasted. Can you please add them? > Concurrency problems with enum constraints in MVEL > -------------------------------------------------- > > Key: DROOLS-1717 > URL: https://issues.jboss.org/browse/DROOLS-1717 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.2.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > Labels: concurrency > > Having a test case like this [1], it sometimes fails on > java.lang.RuntimeException: java.util.concurrent.ExecutionException: [Error: unable to resolve method using strict-mode: org.drools.compiler.integrationtests.facts.FactWithEnum.AnEnum()] > [Near : {... enumValue == AnEnum.SECOND ....}] > ... see here [2]. When using direct imports that are commented out in the pasted example, I see very rarely also a ClassCastException. See stacktrace here [3]. > Tested with mvel 2.2.8 on 6.5.x branch, 2.3.0 and 2.3.1 on master branch. > [1] https://gist.github.com/baldimir/d0f5f21d5b1a383887c5ebfb6013e5af > [2] https://gist.github.com/baldimir/da5c9cb23fab2eae1576948c8ca2a4c8 > [3] https://gist.github.com/baldimir/72eafe3909c21e25265cd3ee9a731d8e -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2061) TYPE_STRING does not handle unicode

by Cody Ebberson (JIRA)

[ https://issues.jboss.org/browse/JGRP-2061?page=com.atlassian.jira.plugin.... ] Cody Ebberson commented on JGRP-2061: ------------------------------------- Confirmed, this works for me. Appears fixed. Thanks! > TYPE_STRING does not handle unicode > ----------------------------------- > > Key: JGRP-2061 > URL: https://issues.jboss.org/browse/JGRP-2061 > Project: JGroups > Issue Type: Bug > Reporter: Cody Ebberson > Assignee: Bela Ban > Fix For: 4.0.6 > > > In several places throughout the org.jgroups.util.Util class, it is assumed that Strings are one byte per character. > For example, see objectToByteBuffer lines 561-567: > https://github.com/belaban/JGroups/blob/master/src/org/jgroups/util/Util.... > {code:java} > case TYPE_STRING: > String str=(String)obj; > int len=str.length(); > ByteBuffer retval=ByteBuffer.allocate(Global.BYTE_SIZE + len).put(TYPE_STRING); > for(int i=0; i < len; i++) > retval.put((byte)str.charAt(i)); > return retval.array(); > {code} > This code will incorrectly encode any String with non ASCII encoding. > There are several options to fix. You could use str.getBytes(StandardCharsets.UTF_8) to get a proper byte encoding, or you could use the existing TYPE_SERIALIZABLE code path. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2017