March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2562) NullPointerException when removing configuration history

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2562?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2562: ---------------------------------------- Assignee: Ken Wills (was: Brian Stansberry) > NullPointerException when removing configuration history > -------------------------------------------------------- > > Key: WFCORE-2562 > URL: https://issues.jboss.org/browse/WFCORE-2562 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Dennis Reed > Assignee: Ken Wills > > org.jboss.as.controller.persistence.ConfigurationFile#deleteRecursively is missing error checking. > If an I/O error occurs while listing the directory contents (file permission error/etc) it still tries to use the listing and gets a NullPointerException. > This method is used while removing old configuration history directories during boot, and the NullPointerException causes the EAP boot to abort. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1034) Allow HTTP authentication mechanisms to use Status 500 / Internal Server Error

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1034?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1034: ---------------------------------- Description: Some mechanisms are unable to operate correctly due to internal errors / configuration issues. When this happens they should be able to provide a responder which sets the status code to 500. However if other mechanisms can respond they should and the 500 be dropped. > Allow HTTP authentication mechanisms to use Status 500 / Internal Server Error > ------------------------------------------------------------------------------ > > Key: ELY-1034 > URL: https://issues.jboss.org/browse/ELY-1034 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta34 > > > Some mechanisms are unable to operate correctly due to internal errors / configuration issues. > When this happens they should be able to provide a responder which sets the status code to 500. However if other mechanisms can respond they should and the 500 be dropped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1034) Allow HTTP authentication mechanisms to use Status 500 / Internal Server Error

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1034: ------------------------------------- Summary: Allow HTTP authentication mechanisms to use Status 500 / Internal Server Error Key: ELY-1034 URL: https://issues.jboss.org/browse/ELY-1034 Project: WildFly Elytron Issue Type: Enhancement Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta34 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8455) Upgrade HAL to 2.9.6.Final

by Harald Pehl (JIRA)

Harald Pehl created WFLY-8455: --------------------------------- Summary: Upgrade HAL to 2.9.6.Final Key: WFLY-8455 URL: https://issues.jboss.org/browse/WFLY-8455 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2582) jboss-cli.bat script is unable to start on Windows, if JBOSS_HOME folder contains '!' character

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2582?page=com.atlassian.jira.plugi... ] Jean-Francois Denise moved JBEAP-9918 to WFCORE-2582: ----------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2582 (was: JBEAP-9918) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: CLI) Affects Version/s: (was: 7.1.0.DR15) Affects Testing: (was: Regression) > jboss-cli.bat script is unable to start on Windows, if JBOSS_HOME folder contains '!' character > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-2582 > URL: https://issues.jboss.org/browse/WFCORE-2582 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > jboss-cli.bat script is unable to start on Windows, if JBOSS_HOME folder contains '!' character, if '!' character is not at the end of the name of JBOSS_HOME folder. > jboss-cli.bat script is unable to start on Windows if JBOSS_HOME ends with exclamation mark, but it is covered by JBEAP-249 > {noformat} > C:\Users\Administrator\playground\7.1.0.DR15\jboss!eap\bin>jboss-cli.bat > The system cannot find the path specified. > The system cannot find the path specified. > Could not locate "C:\Users\Administrator\playground\7.1.0.DR15\jbosseap\bin\jboss-modules.jar". > Please check that you are in the bin directory when running this script. > Press any key to continue . . . > C:\Users\Administrator\playground\7.1.0.DR15\jboss!eap\bin>jboss-cli.bat > {noformat} > * This issue is caused by JBEAP-9699 > *Workaround:* > Rename JBOSS_HOME folder -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2581) There isn't possible change value for given alias in Credential Store over CLI.

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2581?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-2581: ----------------------------------------- Assignee: ehsavoie Hugonnet (was: Peter Skopek) > There isn't possible change value for given alias in Credential Store over CLI. > ------------------------------------------------------------------------------- > > Key: WFCORE-2581 > URL: https://issues.jboss.org/browse/WFCORE-2581 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta11 > Reporter: Hynek Švábek > Assignee: ehsavoie Hugonnet > Priority: Critical > > There isn't possible change value for given alias in Credential Store over CLI. > I expected something like this > {code} > /subsystem=elytron/credential-store=credStore/alias=entryAlias:update(secret-value=newSecretValue) > {code} > Write-attribute operation doesn't work too. Operation pass but any changes are not propagated to Credential Store. > {code} > /subsystem=elytron/credential-store=credStore/alias=entryAlias:write-attribute(name="secret-value" value="newSecretValue") > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2581) There isn't possible change value for given alias in Credential Store over CLI.

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2581?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet moved ELY-676 to WFCORE-2581: ----------------------------------------------- Project: WildFly Core (was: WildFly Elytron) Key: WFCORE-2581 (was: ELY-676) Component/s: Security (was: Credential Store) Affects Version/s: 3.0.0.Beta11 (was: 1.1.0.Beta10) > There isn't possible change value for given alias in Credential Store over CLI. > ------------------------------------------------------------------------------- > > Key: WFCORE-2581 > URL: https://issues.jboss.org/browse/WFCORE-2581 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta11 > Reporter: Hynek Švábek > Assignee: Peter Skopek > Priority: Critical > > There isn't possible change value for given alias in Credential Store over CLI. > I expected something like this > {code} > /subsystem=elytron/credential-store=credStore/alias=entryAlias:update(secret-value=newSecretValue) > {code} > Write-attribute operation doesn't work too. Operation pass but any changes are not propagated to Credential Store. > {code} > /subsystem=elytron/credential-store=credStore/alias=entryAlias:write-attribute(name="secret-value" value="newSecretValue") > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2577) ModelOnlyResourceDefinition does not expose a constructor that takes a Parameters object.

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2577?page=com.atlassian.jira.plugi... ] Radoslav Husar reassigned WFCORE-2577: -------------------------------------- Assignee: Radoslav Husar > ModelOnlyResourceDefinition does not expose a constructor that takes a Parameters object. > ----------------------------------------------------------------------------------------- > > Key: WFCORE-2577 > URL: https://issues.jboss.org/browse/WFCORE-2577 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Radoslav Husar > Priority: Minor > > It's better to wire up resource definitions using Parameters so we should support it for this one too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8449) EJB contextData not sent back to client in response

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ] Kabir Khan reopened WFLY-8449: ------------------------------ > EJB contextData not sent back to client in response > --------------------------------------------------- > > Key: WFLY-8449 > URL: https://issues.jboss.org/browse/WFLY-8449 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Labels: ejb > Fix For: 11.0.0.Alpha1 > > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8451) org.wildfly.clustering.web.session.IdentifierExternalizerTestCase#toHex fails on JDK9 b162

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8451?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-8451: -------------------------------------- Needs some sort of `-addmods java.xml.bind` at the moment. > org.wildfly.clustering.web.session.IdentifierExternalizerTestCase#toHex fails on JDK9 b162 > ------------------------------------------------------------------------------------------ > > Key: WFLY-8451 > URL: https://issues.jboss.org/browse/WFLY-8451 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > testHex(org.wildfly.clustering.web.session.IdentifierExternalizerTestCase) Time elapsed: 0.008 sec <<< ERROR! > java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:533) > at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:186) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:476) > at org.wildfly.clustering.web.IdentifierExternalizer$3.writeObject(IdentifierExternalizer.java:74) > at org.wildfly.clustering.web.IdentifierExternalizer$3.writeObject(IdentifierExternalizer.java:71) > at org.wildfly.clustering.web.session.IdentifierExternalizerTestCase.test(IdentifierExternalizerTestCase.java:97) > at org.wildfly.clustering.web.session.IdentifierExternalizerTestCase.testHex(IdentifierExternalizerTestCase.java:61) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 March 2017