September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3894) Can't login JAAS secured management interfaces with --admin-only

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3894?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3894: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146238 > Can't login JAAS secured management interfaces with --admin-only > ---------------------------------------------------------------- > > Key: WFLY-3894 > URL: https://issues.jboss.org/browse/WFLY-3894 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.0.Alpha1 > Reporter: Chris Dolphy > Assignee: Brian Stansberry > Attachments: standalone.xml > > > After configuring JAAS security for management realm, when I start JBoss with `bin/standalone.sh --admin-only', I can't login to the management web console. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3894) Can't login JAAS secured management interfaces with --admin-only

by Chris Dolphy (JIRA)

[ https://issues.jboss.org/browse/WFLY-3894?page=com.atlassian.jira.plugin.... ] Chris Dolphy updated WFLY-3894: ------------------------------- Description: After configuring JAAS security for management realm, when I start JBoss with `bin/standalone.sh --admin-only', I can't login to the management web console. was: Setup JAAS security domain for management realm and when I start JBoss with `bin/standalone.sh --admin-only', I can't login to the management web console. > Can't login JAAS secured management interfaces with --admin-only > ---------------------------------------------------------------- > > Key: WFLY-3894 > URL: https://issues.jboss.org/browse/WFLY-3894 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.0.Alpha1 > Reporter: Chris Dolphy > Assignee: Brian Stansberry > Attachments: standalone.xml > > > After configuring JAAS security for management realm, when I start JBoss with `bin/standalone.sh --admin-only', I can't login to the management web console. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3894) Can't login JAAS secured management interfaces with --admin-only

by Chris Dolphy (JIRA)

[ https://issues.jboss.org/browse/WFLY-3894?page=com.atlassian.jira.plugin.... ] Chris Dolphy updated WFLY-3894: ------------------------------- Attachment: standalone.xml > Can't login JAAS secured management interfaces with --admin-only > ---------------------------------------------------------------- > > Key: WFLY-3894 > URL: https://issues.jboss.org/browse/WFLY-3894 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.0.Alpha1 > Reporter: Chris Dolphy > Assignee: Brian Stansberry > Attachments: standalone.xml > > > Setup JAAS security domain for management realm and when I start JBoss with `bin/standalone.sh --admin-only', I can't login to the management web console. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3894) Can't login JAAS secured management interfaces with --admin-only

by Chris Dolphy (JIRA)

Chris Dolphy created WFLY-3894: ---------------------------------- Summary: Can't login JAAS secured management interfaces with --admin-only Key: WFLY-3894 URL: https://issues.jboss.org/browse/WFLY-3894 Project: WildFly Issue Type: Bug Components: Domain Management Affects Versions: 9.0.0.Alpha1 Reporter: Chris Dolphy Assignee: Brian Stansberry Attachments: standalone.xml Setup JAAS security domain for management realm and when I start JBoss with `bin/standalone.sh --admin-only', I can't login to the management web console. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3893) JacORB compatibility subsystem

by Tomasz Adamski (JIRA)

Tomasz Adamski created WFLY-3893: ------------------------------------ Summary: JacORB compatibility subsystem Key: WFLY-3893 URL: https://issues.jboss.org/browse/WFLY-3893 Project: WildFly Issue Type: Feature Request Components: IIOP Reporter: Tomasz Adamski Assignee: Tomasz Adamski Create jacorb compatibility subsystem which will be able to parse jacorb subsystem configuration, map it to iiop-openjdk configuration, and (if possible) emulate jacorb subsystem using iiop-openjdk subsystem. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-124) The yes/no checking in add-user converts the users input to lower case but not the translated values.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-124?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-124: ------------------------------------------------ Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 901193|https://bugzilla.redhat.com/show_bug.cgi?id=901193] from ASSIGNED to POST > The yes/no checking in add-user converts the users input to lower case but not the translated values. > ----------------------------------------------------------------------------------------------------- > > Key: WFCORE-124 > URL: https://issues.jboss.org/browse/WFCORE-124 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha9 > > > The end result is if the translated value contains upper case characters the users input will not match, as an example for German ja and Ja - whatever the user inputs it will be converted to 'ja' but is always compared to 'Ja'. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-610) drools-worker-2 thread blocked and the main program blocks

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-610?page=com.atlassian.jira.plugin... ] Mario Fusco commented on DROOLS-610: ------------------------------------ Nathalie, for what I can see from the stack you attached, the deadlock is caused by the fact that you're misusing drools. In particular drools-worker-2.PNG shows that you're invoking a fireAllRules inside the execution of a drools consequence. For what I know this doesn't make any sense and I cannot see a valid reason for doing this, even because if a consequence is firing it means that you're already inside a fireAllRules. Please let me know if you have a use case that requires to do this, so we could discuss it. Otherwise I'll close this ticket as invalid. Cheers, Mario > drools-worker-2 thread blocked and the main program blocks > ---------------------------------------------------------- > > Key: DROOLS-610 > URL: https://issues.jboss.org/browse/DROOLS-610 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Environment: linux > Reporter: Nathalie ravenel > Assignee: Mario Fusco > Attachments: blocked.PNG, drools-worker-2.PNG, main thread.PNG, pool-1-thread1.PNG > > > Running our program, we got some deadlock on one thread (drools-worker-2). We investigated the problem using java memory control. The thread is blocked and the program also. The stack traces was registered for the different threads. The last trace for the thread was : org.drools.core.common.SynchronizedLeftTuplesSets.takeAll. > There are 1111 Blocked count on one DeadLock on the thread. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-611) Support type-safe metadata for fact and rules

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-611: ------------------------------------- Summary: Support type-safe metadata for fact and rules Key: DROOLS-611 URL: https://issues.jboss.org/browse/DROOLS-611 Project: Drools Issue Type: Feature Request Reporter: Davide Sottara Assignee: Mark Proctor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-611) Support type-safe metadata for facts and rules

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-611?page=com.atlassian.jira.plugin... ] Davide Sottara updated DROOLS-611: ---------------------------------- Summary: Support type-safe metadata for facts and rules (was: Support type-safe metadata for fact and rules) > Support type-safe metadata for facts and rules > ---------------------------------------------- > > Key: DROOLS-611 > URL: https://issues.jboss.org/browse/DROOLS-611 > Project: Drools > Issue Type: Feature Request > Reporter: Davide Sottara > Assignee: Mark Proctor > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.... ] David Lloyd resolved WFLY-3189. ------------------------------- Fix Version/s: 9.0.0.Beta1 Resolution: Done > Error validating jboss-ejb3.xml. > -------------------------------- > > Key: WFLY-3189 > URL: https://issues.jboss.org/browse/WFLY-3189 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Environment: WildFly 8.0.0.Final > Reporter: shinzey shinzey > Assignee: David Lloyd > Fix For: 9.0.0.Beta1 > > Attachments: p.patch > > > I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error: > {noformat} > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33] > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37] > src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39] > {noformat} > The jboss-ejb3.xml is quite simple: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <jboss:ejb-jar version="3.1" impl-version="2.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns:s="urn:security:1.1" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd > http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd"> > <assembly-descriptor> > <s:security> > <ejb-name>*</ejb-name> > <s:security-domain>testsd</s:security-domain> > </s:security> > </assembly-descriptor> > </jboss:ejb-jar> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2014