February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6239) CLI: failure when adding a JNDI entry with default value containing a '$' at the end

by Valentin Maechler (JIRA)

[ https://issues.jboss.org/browse/WFLY-6239?page=com.atlassian.jira.plugin.... ] Valentin Maechler commented on WFLY-6239: ----------------------------------------- I guess by "escaping" you mean prefixing it with a "\", right? result: {code} [standalone@localhost:9990 /] /subsystem=naming/binding=java\:global\/my\/sample\/entry:add(binding-type=simple, type=java.lang.String, value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-\$}"){ "outcome" => "failed", "failure-description" => "WFLYCTL0370: Incomplete expression: ${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}", "rolled-back" => true}[standalone@localhost:9990 /] /subsystem=naming/binding=java\:global\/my\/sample\/entry:add(binding-type=simple, type=java.lang.String, value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$\}"){ "outcome" => "failed", "failure-description" => "WFLYCTL0370: Incomplete expression: ${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}", "rolled-back" => true} {code} May I ask you to try it on your side, please? ...and to provide the working example? > CLI: failure when adding a JNDI entry with default value containing a '$' at the end > ------------------------------------------------------------------------------------ > > Key: WFLY-6239 > URL: https://issues.jboss.org/browse/WFLY-6239 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 10.0.0.Final > Reporter: Valentin Maechler > Assignee: Alexey Loubyansky > > Can not add a JNDI / naming entry which contains a "$" sign at the end of its default value. > e.g. {code} > value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}" > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6239) CLI: failure when adding a JNDI entry with default value containing a '$' at the end

by Valentin Maechler (JIRA)

[ https://issues.jboss.org/browse/WFLY-6239?page=com.atlassian.jira.plugin.... ] Valentin Maechler edited comment on WFLY-6239 at 2/18/16 1:10 AM: ------------------------------------------------------------------ I guess by "escaping" you mean prefixing it with a "\", right? result: {code} [standalone@localhost:9990 /] /subsystem=naming/binding=java\:global\/my\/sample\/entry:add(binding-type=simple, type=java.lang.String, value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-\$}"){ "outcome" => "failed", "failure-description" => "WFLYCTL0370: Incomplete expression: ${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}", "rolled-back" => true}[standalone@localhost:9990 /] /subsystem=naming/binding=java\:global\/my\/sample\/entry:add(binding-type=simple, type=java.lang.String, value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$\}"){ "outcome" => "failed", "failure-description" => "WFLYCTL0370: Incomplete expression: ${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}", "rolled-back" => true} {code} (!)(?) *May I ask you to try it on your side, please? ...and to provide the working example?* was (Author: vmae): I guess by "escaping" you mean prefixing it with a "\", right? result: {code} [standalone@localhost:9990 /] /subsystem=naming/binding=java\:global\/my\/sample\/entry:add(binding-type=simple, type=java.lang.String, value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-\$}"){ "outcome" => "failed", "failure-description" => "WFLYCTL0370: Incomplete expression: ${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}", "rolled-back" => true}[standalone@localhost:9990 /] /subsystem=naming/binding=java\:global\/my\/sample\/entry:add(binding-type=simple, type=java.lang.String, value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$\}"){ "outcome" => "failed", "failure-description" => "WFLYCTL0370: Incomplete expression: ${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}", "rolled-back" => true} {code} May I ask you to try it on your side, please? ...and to provide the working example? > CLI: failure when adding a JNDI entry with default value containing a '$' at the end > ------------------------------------------------------------------------------------ > > Key: WFLY-6239 > URL: https://issues.jboss.org/browse/WFLY-6239 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 10.0.0.Final > Reporter: Valentin Maechler > Assignee: Alexey Loubyansky > > Can not add a JNDI / naming entry which contains a "$" sign at the end of its default value. > e.g. {code} > value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}" > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-897) Unable to authenticate in SPNEGO Login Module with NullPointerException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-897?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-897: -------------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1236606|https://bugzilla.redhat.com/show_bug.cgi?id=1236606] from POST to MODIFIED > Unable to authenticate in SPNEGO Login Module with NullPointerException > ----------------------------------------------------------------------- > > Key: SECURITY-897 > URL: https://issues.jboss.org/browse/SECURITY-897 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_2_3_6_Final > Environment: Red Hat JBoss EAP 6.3.2 > Reporter: Kunjan Rathod > Assignee: Chao Wang > Labels: jboss, jboss-as > Fix For: Negotiation_3_0_0_Final, Negotiation_2_3_11_Final > > > Description of problem: > The configuration with SPNEGO works fine, however from time to time the authentication fails with the following error: > ERROR (HTTP-341) [org.jboss.security.auth.spi.AbstractServerLoginModule] Unable to authenticate: java.lang.NullPointerException > at org.jboss.security.negotiation.spnego.SPNEGOLoginModule$AcceptSecContext.run(SPNEGOLoginModule.java:420) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:356) > Version-Release number of selected component (if applicable): > JBoss Security Negotiation 2.3.3.Final > How reproducible: > This happens very rarely (20 times in a day on a system where about 50 users are working) and it is extremely hard to reproduce. > Additional info: > At line 420 in [1], the GSSToken is null > ~~~~ > if (respToken != null) > { > NegotiationMessage response; > if (requestMessage instanceof KerberosMessage) > { > response = new KerberosMessage(Constants.KERBEROS_V5, respToken); > } > else > { > NegTokenTarg negTokenTarg = new NegTokenTarg(); > negTokenTarg.setResponseToken(respToken); > response = negTokenTarg; > } > ~~~~ > It looks like a GSSToken can be or is null, check the line#344 as follows:- > ~~~~~~~~~ > public Object run() > { > try > { > // The message type will have already been checked before this point so we know it is > // a SPNEGO message. > NegotiationMessage requestMessage = negotiationContext.getRequestMessage(); > // TODO - Ensure no way to fall through with gssToken still null. > byte[] gssToken = null; > if (requestMessage instanceof NegTokenInit) > { > ... > ~~~~~~~~~ > [1] : https://github.com/wildfly-security/jboss-negotiation/blob/2.3.3.Final/jb... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1398) RemotingHttpUpgradeService.SERVICE_NAME has a superfluous space

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1398: ---------------------------------------- Summary: RemotingHttpUpgradeService.SERVICE_NAME has a superfluous space Key: WFCORE-1398 URL: https://issues.jboss.org/browse/WFCORE-1398 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 2.1.0.CR1 Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 3.0.0.Alpha1 public static final ServiceName UPGRADE_SERVICE_NAME = ServiceName.JBOSS.append("remoting ", "remoting-http-upgrade-service"); Note the space in "remoting " -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1397) Boot errors and unmanageable server if http-interface resource's http-upgrade-enabled attribute != true

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1397: ---------------------------------------- Summary: Boot errors and unmanageable server if http-interface resource's http-upgrade-enabled attribute != true Key: WFCORE-1397 URL: https://issues.jboss.org/browse/WFCORE-1397 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 2.1.0.CR1 Reporter: Brian Stansberry Priority: Critical Fix For: 2.1.0.CR2 The https://github.com/wildfly/wildfly-core/pull/1360 work added a new XnioWorker service that the HTTP interface depends on, but for a standalone server it isn't installed unless http-upgrade-enabled == true. Otherwise you see this during boot: {code} 15:43:25,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("core-service" => "management"), ("management-interface" => "http-interface") ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [ "jboss.serverManagement.controller.management.http is missing [jboss.serverManagement.controller.management.worker]", "jboss.serverManagement.controller.management.http.shutdown is missing [jboss.remoting.management.channel.registry]" ]} 15:43:25,006 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "jmx"), ("remoting-connector" => "jmx") ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.jmx.remoting-connector-ref is missing [jboss.remoting.endpoint.management]"]} 15:43:25,031 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.remoting.endpoint.management (missing) dependents: [service jboss.jmx.remoting-connector-ref] service jboss.remoting.management.channel.registry (missing) dependents: [service jboss.serverManagement.controller.management.http.shutdown] service jboss.serverManagement.controller.management.worker (missing) dependents: [service jboss.serverManagement.controller.management.http] 15:43:25,127 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled 15:43:25,128 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled 15:43:25,128 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.0.0.GA (WildFly Core 2.0.12.Final-redhat-1) started (with errors) in 3493ms - Started 254 of 544 services (3 services failed or missing dependencies, 369 services are lazy, passive or on-demand) {code} The problem is org.jboss.as.server.operations.HttpManagementAddHandler doesn't install the service. The HC variant of HttpManagementAddHandler does. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1396) Delete GlobalOperationHandlers cruft about not register write-attribute handlers on ProcessType.DOMAIN_SERVER

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1396: ---------------------------------------- Summary: Delete GlobalOperationHandlers cruft about not register write-attribute handlers on ProcessType.DOMAIN_SERVER Key: WFCORE-1396 URL: https://issues.jboss.org/browse/WFCORE-1396 Project: WildFly Core Issue Type: Task Components: Domain Management Affects Versions: 2.1.0.CR1 Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 3.0.0.Alpha1 GlobalOperationHandlers.registerGlobalOperations has a block where it appears not to register handlers for write-attribute and undefine-attribute if the process type is ProcessType.DOMAIN_SERVER. But ProcessType.DOMAIN_SERVER is never the value passed as the param, so the block has no effect and if it ever took effect the server would not be properly manageable, since the HC sends over write-attribute and undefine-attribute ops. So delete it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6239) CLI: failure when adding a JNDI entry with default value containing a '$' at the end

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-6239?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky commented on WFLY-6239: ----------------------------------------- Have you tried escaping the $ at the end? > CLI: failure when adding a JNDI entry with default value containing a '$' at the end > ------------------------------------------------------------------------------------ > > Key: WFLY-6239 > URL: https://issues.jboss.org/browse/WFLY-6239 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 10.0.0.Final > Reporter: Valentin Maechler > Assignee: Alexey Loubyansky > > Can not add a JNDI / naming entry which contains a "$" sign at the end of its default value. > e.g. {code} > value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}" > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-937) Release JBoss Negotiation 2.3.11.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-937?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-937. --------------------------------------- Resolution: Done > Release JBoss Negotiation 2.3.11.Final > -------------------------------------- > > Key: SECURITY-937 > URL: https://issues.jboss.org/browse/SECURITY-937 > Project: PicketBox > Issue Type: Release > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_11_CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2948) Welcome file does not work for *.jsf

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2948?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2948: ----------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1256325|https://bugzilla.redhat.com/show_bug.cgi?id=1256325] from MODIFIED to ASSIGNED > Welcome file does not work for *.jsf > -------------------------------------- > > Key: WFLY-2948 > URL: https://issues.jboss.org/browse/WFLY-2948 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.0.0.Final > Reporter: Gulam Samdani > Assignee: Remy Maucherat > Priority: Minor > Fix For: 8.1.0.CR1, 8.1.0.Final > > > Welcome file does not work for *.jsf > -------------------------------------------------------- > same problem not exists in Wildfly Beta but wildfly 8 final /cr1 gives this error ... > > problem : > > http://localhost:8080/hello ------------------------------ NO works*** > @http://localhost:8080/hello/index.jsf ------------- it works fine > ======================================= > <welcome-file-list> > > <welcome-file>index.jsf</welcome-file> > > </welcome-file-list> > <servlet> > <servlet-name>Faces Servlet</servlet-name> > <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> > <load-on-startup>1</load-on-startup> > </servlet> > <servlet-mapping> > <servlet-name>Faces Servlet</servlet-name> > <url-pattern>*.jsf</url-pattern> > </servlet-mapping> > </web-app> > ------------------------------------------------- > Reproduce this error : > https://community.jboss.org/message/857300 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-937) Release JBoss Negotiation 2.3.11.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-937: ----------------------------------------- Summary: Release JBoss Negotiation 2.3.11.Final Key: SECURITY-937 URL: https://issues.jboss.org/browse/SECURITY-937 Project: PicketBox Issue Type: Release Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_3_11_CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016