January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7491) joiner attribute of concatenating-principal-decoder (Elytron subsystem) is marked as nillable but can not be

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7491?page=com.atlassian.jira.plugin.... ] Jan Kalina reopened WFLY-7491: ------------------------------ Reopening, still not possible to unset attribute. (with new controller version?) Probably will need to remove default value, which is automatically passed instead of setting null. > joiner attribute of concatenating-principal-decoder (Elytron subsystem) is marked as nillable but can not be > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-7491 > URL: https://issues.jboss.org/browse/WFLY-7491 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Kotek > Assignee: Jan Kalina > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > *Issue description:* > After having undefined the {{joiner}} attribute of {{concatenating-principal-decoder}} in Elytron subsystem, the server does not start. The {{joiner}} attribute is declared as {{"nillable" => true}} in CLI, but can not be -- see _Steps to Reproce_ that results in > {noformat} > 14:50:29,357 ERROR [org.jboss.as.controller] (Controller Boot Thread) > OPVDX001: Validation error in standalone-elytron.xml =========================== > 346: <permission class-name="org.wildfly.security.auth.permission.LoginPermission"/> > 347: </constant-permission-mapper> > 348: <concatenating-principal-decoder name="concatPrincDecoder"> > ^^^^ 'concatenating-principal-decoder' is missing one or more required attributes > All of the following are required: joiner > 349: <principal-decoder name="constPrincDecoder"/> > 350: <principal-decoder name="constPrincDecoder"/> > 351: </concatenating-principal-decoder> > The underlying error message was: > > ParseError at [row,col]:[348,17] > > Message: WFLYCTL0133: Missing required attribute(s): joiner > ================================================================================ > 14:50:29,357 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143) > at org.jboss.as.server.ServerService.boot(ServerService.java:355) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:302) > at java.lang.Thread.run(Thread.java:745) > 14:50:29,358 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {noformat} > The {{joiner}} attribute has {{use="required"}} in _wildfly-elytron_1_0.xsd_. > *Suggestions for improvement:* > In case it makes sense to have no joiner, the joiner should not be required. (There could be reasonable cases.) Otherwise, the CLI {{joiner}} attribute should be declared as {{"nillable" => false}}. > The XSD {{joiner}} attribute should have defined {{default="."}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6011) Remote branch of a transaction gets rolled back incorrectly.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6011?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-6011: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1298161, https://bugzilla.redhat.com/show_bug.cgi?id=1301676, https://bugzilla.redhat.com/show_bug.cgi?id=1411287 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1298161, https://bugzilla.redhat.com/show_bug.cgi?id=1301676) > Remote branch of a transaction gets rolled back incorrectly. > ------------------------------------------------------------- > > Key: WFLY-6011 > URL: https://issues.jboss.org/browse/WFLY-6011 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Jason Greene > Assignee: David Lloyd > > The use case is as follow: > Client makes a call to a bean on server-1 > bean (server-1) inserts a row into table-1 > bean (server-1) calls to a bean on server-2 > bean (server-2) inserts a row into table-2 > bean (server-2) goes to sleep for 3 minutes > periodic recovery (server-1) flags the remote branchof the transaction (on server-2) as in doubt and rolls it back. > (server-1 log) > {noformat} > 11:53:37,991 TRACE [com.arjuna.ats.arjuna] (Periodic Recovery) RecoveryXids _whenFirstSeen toRecover no RecoveryOnlyEJBXAResource{receiverContext=EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@322f7790, receiver=Remoting connection EJB receiver [connection=Remoting connection <2c1ab3f6>,channel=jboss.ejb,nodename=server2]}, transactionOriginNodeIdentifier='server1'} 1452599607985 === 1452599617991 > 11:53:37,991 DEBUG [com.arjuna.ats.jta] (Periodic Recovery) Have 1 Xids to recover on this pass. > 11:53:37,992 DEBUG [com.arjuna.ats.jta] (Periodic Recovery) No record found for < formatId=131077, gtrid_length=35, bqual_length=43, tx_uid=0:ffffc0a80164:-fa2e9db:5694e833:2c, node_name=server1, branch_uid=0:ffffc0a80164:-fa2e9db:5694e833:39, subordinatenodename=server2, eis_name=unknown eis name > > 11:53:37,992 DEBUG [com.arjuna.ats.jta] (Periodic Recovery) XAResourceOrphanFilter com.arjuna.ats.internal.jta.recovery.arjunacore.JTATransactionLogXAResourceOrphanFilter voted ABSTAIN > 11:53:37,993 DEBUG [com.arjuna.ats.jta] (Periodic Recovery) node name of < formatId=131077, gtrid_length=35, bqual_length=43, tx_uid=0:ffffc0a80164:-fa2e9db:5694e833:2c, node_name=server1, branch_uid=0:ffffc0a80164:-fa2e9db:5694e833:39, subordinatenodename=server2, eis_name=unknown eis name > is server1 > 11:53:37,993 DEBUG [com.arjuna.ats.jta] (Periodic Recovery) XAResourceOrphanFilter com.arjuna.ats.internal.jta.recovery.arjunacore.JTANodeNameXAResourceOrphanFilter voted ROLLBACK > 11:53:37,993 DEBUG [com.arjuna.ats.jta] (Periodic Recovery) subordinate node name of < formatId=131077, gtrid_length=35, bqual_length=43, tx_uid=0:ffffc0a80164:-fa2e9db:5694e833:2c, node_name=server1, branch_uid=0:ffffc0a80164:-fa2e9db:5694e833:39, subordinatenodename=server2, eis_name=unknown eis name > is server2 > 11:53:37,993 DEBUG [com.arjuna.ats.jta] (Periodic Recovery) Checking whether Xid < formatId=131077, gtrid_length=35, bqual_length=43, tx_uid=0:ffffc0a80164:-fa2e9db:5694e833:2c, node_name=server1, branch_uid=0:ffffc0a80164:-fa2e9db:5694e833:39, subordinatenodename=server2, eis_name=unknown eis name > exists in ObjectStore. > 11:53:37,993 DEBUG [com.arjuna.ats.jta] (Periodic Recovery) Looking for 0:ffffc0a80164:-fa2e9db:5694e833:2c and /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA > 11:53:37,993 INFO [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016013: Rolling back < formatId=131077, gtrid_length=35, bqual_length=43, tx_uid=0:ffffc0a80164:-fa2e9db:5694e833:2c, node_name=server1, branch_uid=0:ffffc0a80164:-fa2e9db:5694e833:39, subordinatenodename=server2, eis_name=unknown eis name > > {noformat} > (server-2 log) > {noformat} > 11:53:37,997 TRACE [com.arjuna.ats.jta] (EJB default - 5) TransactionImple.getStatus: javax.transaction.Status.STATUS_ACTIVE > 11:53:37,998 TRACE [com.arjuna.ats.arjuna] (EJB default - 5) BasicAction::phase2Abort() for action-id 0:ffffc0a80164:-41fcd6d0:5694e85a:34 > 11:53:37,998 TRACE [com.arjuna.ats.arjuna] (EJB default - 5) BasicAction::doAbort (XAResourceRecord < resource:XAResourceWrapperImpl@3de8e444[xaResource=org.jboss.jca.adapters.jdbc.xa.XAManagedConnection@6440856e pad=false overrideRmValue=false productName=PostgreSQL productVersion=9.4.1 jndiName=java:jboss/datasources/testJBossDS], txid:< formatId=131077, gtrid_length=35, bqual_length=43, tx_uid=0:ffffc0a80164:-fa2e9db:5694e833:2c, node_name=server1, branch_uid=0:ffffc0a80164:-41fcd6d0:5694e85a:3e, subordinatenodename=server2, eis_name=java:jboss/datasources/testJBossDS >, heuristic: TwoPhaseOutcome.FINISH_OK, product: PostgreSQL/9.4.1, jndiName: java:jboss/datasources/testJBossDS com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@32ff4c6d >) > 11:53:37,998 TRACE [com.arjuna.ats.jta] (EJB default - 5) XAResourceRecord.topLevelAbort for XAResourceRecord < resource:XAResourceWrapperImpl@3de8e444[xaResource=org.jboss.jca.adapters.jdbc.xa.XAManagedConnection@6440856e pad=false overrideRmValue=false productName=PostgreSQL productVersion=9.4.1 jndiName=java:jboss/datasources/testJBossDS], txid:< formatId=131077, gtrid_length=35, bqual_length=43, tx_uid=0:ffffc0a80164:-fa2e9db:5694e833:2c, node_name=server1, branch_uid=0:ffffc0a80164:-41fcd6d0:5694e85a:3e, subordinatenodename=server2, eis_name=java:jboss/datasources/testJBossDS >, heuristic: TwoPhaseOutcome.FINISH_OK, product: PostgreSQL/9.4.1, jndiName: java:jboss/datasources/testJBossDS com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@32ff4c6d >, record id=0:ffffc0a80164:-41fcd6d0:5694e85a:3f > 11:53:37,998 TRACE [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$MyXaMCF] (EJB default - 5) Unlock: HeldByCurrentThread: Yes, Locked: Yes, HoldCount: 1, QueueLength: 0 > 11:53:37,998 TRACE [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$MyXaMCF] (EJB default - 5) Owner: Thread[EJB default - 5,5,EJB default] > 11:53:37,999 TRACE [com.arjuna.ats.arjuna] (EJB default - 5) BasicAction::doAbort() result for action-id (0:ffffc0a80164:-41fcd6d0:5694e85a:34) on record id: (0:ffffc0a80164:-41fcd6d0:5694e85a:3f) is (TwoPhaseOutcome.FINISH_OK) node id: (server2) > 11:53:37,999 TRACE [com.arjuna.ats.arjuna] (EJB default - 5) BasicAction::updateState() for action-id 0:ffffc0a80164:-41fcd6d0:5694e85a:34 > 11:53:37,999 TRACE [com.arjuna.ats.jta] (EJB default - 5) SynchronizationImple.afterCompletion > {noformat} > bean (server-2) wake up > bean (server-1) updates the row in table-1 > at this point the parent transaction gets committed without an error > {noformat} > 11:55:31,104 TRACE [com.arjuna.ats.arjuna] (EJB default - 3) BasicAction::removeChildThread () action 0:ffffc0a80164:-fa2e9db:5694e833:2c removing TSThread:1 > 11:55:31,104 TRACE [com.arjuna.ats.arjuna] (EJB default - 3) BasicAction::removeChildThread () action 0:ffffc0a80164:-fa2e9db:5694e833:2c removing TSThread:1 result = true > 11:55:31,104 TRACE [com.arjuna.ats.arjuna] (EJB default - 3) TransactionReaper::remove ( BasicAction: 0:ffffc0a80164:-fa2e9db:5694e833:2c status: ActionStatus.COMMITTED ) > {noformat} > client call ends > When I look at the table in the database I see a row in table-1 but no row in table-2. I would expect to see both tables empty. > When I switch to JTS and run the same use case it all works as expected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7859) jbossws-cxf-resources is still using wildfly1000 classifier, move to wildfly1100

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-7859?page=com.atlassian.jira.plugin.... ] Alessio Soldano moved JBEAP-8156 to WFLY-7859: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7859 (was: JBEAP-8156) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web Services (was: Web Services) Affects Version/s: (was: 7.1.0.DR10) > jbossws-cxf-resources is still using wildfly1000 classifier, move to wildfly1100 > -------------------------------------------------------------------------------- > > Key: WFLY-7859 > URL: https://issues.jboss.org/browse/WFLY-7859 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Alessio Soldano > Assignee: Alessio Soldano > > jbossws-cxf-resources is still using wildfly1000 classifier, move to wildfly1100. > https://github.com/wildfly/wildfly/blob/master/pom.xml#L5779 > https://github.com/wildfly/wildfly/blob/master/feature-pack/pom.xml#L491 > https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6400) Elytron integration with resource adapters subsystem

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-6400?page=com.atlassian.jira.plugin.... ] Stefano Maestri reassigned WFLY-6400: ------------------------------------- Assignee: Flavia Rainone (was: Stefano Maestri) > Elytron integration with resource adapters subsystem > ---------------------------------------------------- > > Key: WFLY-6400 > URL: https://issues.jboss.org/browse/WFLY-6400 > Project: WildFly > Issue Type: Feature Request > Components: JCA, Security > Reporter: Darran Lofthouse > Assignee: Flavia Rainone > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6394) Elytron integration with JCA subsystem

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-6394?page=com.atlassian.jira.plugin.... ] Stefano Maestri reassigned WFLY-6394: ------------------------------------- Assignee: Flavia Rainone (was: Stefano Maestri) > Elytron integration with JCA subsystem > -------------------------------------- > > Key: WFLY-6394 > URL: https://issues.jboss.org/browse/WFLY-6394 > Project: WildFly > Issue Type: Feature Request > Components: JCA, Security > Reporter: Darran Lofthouse > Assignee: Flavia Rainone > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6391) Elytron integration with datasources subsystem

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-6391?page=com.atlassian.jira.plugin.... ] Stefano Maestri reassigned WFLY-6391: ------------------------------------- Assignee: Flavia Rainone (was: Stefano Maestri) > Elytron integration with datasources subsystem > ---------------------------------------------- > > Key: WFLY-6391 > URL: https://issues.jboss.org/browse/WFLY-6391 > Project: WildFly > Issue Type: Feature Request > Components: JCA, Security > Reporter: Darran Lofthouse > Assignee: Flavia Rainone > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2160) Incorrect JBOSS_HOME warning in vault.sh

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2160?page=com.atlassian.jira.plugi... ] Romain Pelisse reassigned WFCORE-2160: -------------------------------------- Assignee: Romain Pelisse (was: Tomaz Cerar) > Incorrect JBOSS_HOME warning in vault.sh > ---------------------------------------- > > Key: WFCORE-2160 > URL: https://issues.jboss.org/browse/WFCORE-2160 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 3.0.0.Alpha16 > Reporter: Dennis Reed > Assignee: Romain Pelisse > Priority: Minor > > vault.sh has an incorrect check to make sure JBOSS_HOME is set correctly. > SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd` > if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then > The check will always fail because of the incorrect "/..", which should be removed. > The incorrect value is only used for printing the "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." log, and appears to have been around since at least EAP 6.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7779) ReAuth does not work with Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7779?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7779: ---------------------------------- Ok, adding *elytron-legacy-test-fails* label. > ReAuth does not work with Elytron > --------------------------------- > > Key: WFLY-7779 > URL: https://issues.jboss.org/browse/WFLY-7779 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Darran Lofthouse > Labels: elytron-legacy-test-fails > > Following way of change identity from servlet does not work: > {code:java} > LoginContext lc = getCLMLoginContext(username, password); > lc.login(); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7779) ReAuth does not work with Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7779?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7779: ----------------------------- Labels: elytron-legacy-test-fails (was: ) > ReAuth does not work with Elytron > --------------------------------- > > Key: WFLY-7779 > URL: https://issues.jboss.org/browse/WFLY-7779 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Darran Lofthouse > Labels: elytron-legacy-test-fails > > Following way of change identity from servlet does not work: > {code:java} > LoginContext lc = getCLMLoginContext(username, password); > lc.login(); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7778) Remoting identity propagation does not work with Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7778?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7778: ----------------------------- Labels: elytron-legacy-test-fails (was: ) > Remoting identity propagation does not work with Elytron > -------------------------------------------------------- > > Key: WFLY-7778 > URL: https://issues.jboss.org/browse/WFLY-7778 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > Labels: elytron-legacy-test-fails > > Even througth succesful obtaining LoginContext, identity is not propagated in EJB call. > Identity is unauthorized on server side. > *Remoting does not work because it is not implemented yet* - this issue created primary for tests ignore issue reference. > Often error message: > {code:java} > SaslException: Authentication failed: all available authentication mechanisms failed: > JBOSS-LOCAL-USER: Server rejected authentication > DIGEST-MD5: Server rejected authentication] > at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:110) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 January 2017