December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1625) WebConsole: Ability to mock different roles

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1625?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1625: ----------------------------- Fix Version/s: 9.0.0.Final > WebConsole: Ability to mock different roles > ------------------------------------------- > > Key: WFLY-1625 > URL: https://issues.jboss.org/browse/WFLY-1625 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3696) Security domain configuration doesn't allow empty or missing login-module-stack

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3696?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3696: ----------------------------- Fix Version/s: 9.0.0.Final > Security domain configuration doesn't allow empty or missing login-module-stack > ------------------------------------------------------------------------------- > > Key: WFLY-3696 > URL: https://issues.jboss.org/browse/WFLY-3696 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 9.0.0.Final > > > https://bugzilla.redhat.com/show_bug.cgi?id=901075 description: > project_key: JBPAPP6 > Adding a security domain with JASPI authentication fails if there is no (or is empty) login-module-stack. It should be possible to add custom ServerAuthModule, which doesn't use JAAS login modules. > {code:xml} > <security-domain name="jmx-console" cache-type="default"> > <authentication-jaspi> >  > <login-module-stack name="lm-stack"> > <login-module code="UsersRoles" flag="required"/> > </login-module-stack> > <auth-module code="org.jboss.example.CustomServerAuthModule" flag="required"> > <module-option name="option1" value="value1" /> > </auth-module> > </authentication-jaspi> > </security-domain> > {code} > It should be possible to remove here the login-module-stack element. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4112) Update Wildfly JDF Stacks (BOM) for 8.2.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4112?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4112: ----------------------------- Fix Version/s: 9.0.0.Final > Update Wildfly JDF Stacks (BOM) for 8.2.0.Final > ----------------------------------------------- > > Key: WFLY-4112 > URL: https://issues.jboss.org/browse/WFLY-4112 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 8.2.0.Final > Reporter: Cody Lerum > Assignee: Eduardo Martins > Fix For: 9.0.0.Final > > > The JDF stacks haven't been updated for Wildfly 8.2.0.Final > This creates an issue for users wishing to keep the provided impl versions in sync with their project for debugging purposes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1534) HAL Release Stream 1.5.4.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1534?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1534: ----------------------------- Fix Version/s: 9.0.0.Final > HAL Release Stream 1.5.4.Final > ------------------------------ > > Key: WFLY-1534 > URL: https://issues.jboss.org/browse/WFLY-1534 > Project: WildFly > Issue Type: Task > Components: Web Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1834) Missing dependency for JDBC adapters module

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1834?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1834: ----------------------------- Fix Version/s: 9.0.0.Final > Missing dependency for JDBC adapters module > ------------------------------------------- > > Key: WFLY-1834 > URL: https://issues.jboss.org/browse/WFLY-1834 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.0.0.Alpha3 > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Priority: Minor > Fix For: 9.0.0.Final > > > The jdbcadapters module needs an explicit dependency on ironjacamar.impl in order to allow all shipped recovery plugins to operate. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1343) Undertow: Cannot read filter and error-handler resources

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1343?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1343: ----------------------------- Fix Version/s: 9.0.0.Final > Undertow: Cannot read filter and error-handler resources > -------------------------------------------------------- > > Key: WFLY-1343 > URL: https://issues.jboss.org/browse/WFLY-1343 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Heiko Braun > Assignee: Stuart Douglas > Fix For: 9.0.0.Final > > > {noformat} > [standalone@localhost:9999 /] /subsystem=undertow/configuration=filter:read-resource > { > "outcome" => "failed", > "failure-description" => "JBAS014807: Management resource '[ > (\"subsystem\" => \"undertow\"), > (\"configuration\" => \"filter\") > ]' not found", > "rolled-back" => true, > "response-headers" => {"process-state" => "reload-required"} > } > {noformat} > {noformat} > [standalone@localhost:9999 /] /subsystem=undertow/configuration=error-handler:read-resource > { > "outcome" => "failed", > "failure-description" => "JBAS014807: Management resource '[ > (\"subsystem\" => \"undertow\"), > (\"configuration\" => \"error-handler\") > ]' not found", > "rolled-back" => true, > "response-headers" => {"process-state" => "reload-required"} > } > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1470) Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM)

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1470?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1470: ----------------------------- Fix Version/s: 9.0.0.Final > Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-1470 > URL: https://issues.jboss.org/browse/WFLY-1470 > Project: WildFly > Issue Type: Task > Reporter: Carlo de Wolf > Assignee: Jason Greene > Priority: Critical > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2773) ClientConfigurationImpl should not translate IP address to host name

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2773?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2773: ----------------------------- Fix Version/s: 9.0.0.Final > ClientConfigurationImpl should not translate IP address to host name > -------------------------------------------------------------------- > > Key: WFLY-2773 > URL: https://issues.jboss.org/browse/WFLY-2773 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Jan Martiska > Assignee: Jan Martiska > Fix For: 9.0.0.Final > > > When creating a ModelControllerClient and passing in an IP address, ClientConfigurationImpl internally translates it to a host name, like here: > {noformat} > public static ModelControllerClientConfiguration create(final InetAddress address, final int port) { > return new ClientConfigurationImpl(address.getHostName(), port, null, null, null, createDefaultExecutor(), true, null); > } > {noformat} > Later on, when the client connects, it is translated via DNS back to an IP address. This is not only unnecessary, but in some situations, it is wrong. > Consider a Windows machine having two IP addresses ,A and B, on one network interface, where only A is pointed at by a DNS record. > - Run AS testsuite and pass it the address B as the node0 property, AS will bind itself to this address. > - Now when a test creates a ModelControllerClient using IP address B, the address B will get translated to the host name, even though B is not in the DNS. The resolving works this way on a Windows machine. > - During the connection, the host name will get resolved by DNS to address A and the test will try to connect through address A. The connection will be refused, or worse, might connect to another instance on the same machine. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3689) Ability to specify a resource adapter reference in jboss-ejb3.xml without the ear name

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3689?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3689: ----------------------------- Fix Version/s: 9.0.0.Final > Ability to specify a resource adapter reference in jboss-ejb3.xml without the ear name > -------------------------------------------------------------------------------------- > > Key: WFLY-3689 > URL: https://issues.jboss.org/browse/WFLY-3689 > Project: WildFly > Issue Type: Enhancement > Components: EJB, JCA > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Minor > Fix For: 9.0.0.Final > > > Resource adapters can be packaged inside an EAR file. With the current set up it is necessary to specify the EAR name when referencing it jboss-ejb3.xml file. > Extension is needed that would allow to avoid adding the EAR name all together for the resource adapter. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1149) Naming lookup intermittently fails on IBM JDK due to org.jboss.remoting3.NotOpenException: Endpoint is not open.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1149?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1149: ----------------------------- Fix Version/s: 9.0.0.Final > Naming lookup intermittently fails on IBM JDK due to org.jboss.remoting3.NotOpenException: Endpoint is not open. > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1149 > URL: https://issues.jboss.org/browse/WFLY-1149 > Project: WildFly > Issue Type: Bug > Components: Naming, Test Suite > Environment: IBM JDK 6 (build 20110203_074623) > IBM JDK 7 (build 20120809_118929) > Reporter: Ivo Studensky > Assignee: Jason Greene > Fix For: 9.0.0.Final > > Attachments: endpoint_is_not_open_2012-11-26.xml, failed_with_status_cancelled_2012-11-26.xml, test_output_with_trace_logging_in_EndpointCache.xml > > > RemoteNamingTestCase intermittently fails when running on IBM JDK. According to logs the remoting channel had been closed before the endpoint tried to connect to it. Unfortunately, when I was trying to debug this issue the tests always nicely passed. > test.log snippet: > {noformat} > 13:16:31,115 DEBUG [org.xnio.nio] (Remoting "config-based-naming-client-endpoint" read-1) Started channel thread 'Remoting "config-based-naming-client-endpoint" read-1', selector sun.nio.ch.EPollSelectorImpl@345642e1 > 13:16:31,115 DEBUG [org.xnio.nio] (Remoting "config-based-naming-client-endpoint" write-1) Started channel thread 'Remoting "config-based-naming-client-endpoint" write-1', selector sun.nio.ch.EPollSelectorImpl@1dc68cf2 > 13:16:31,121 DEBUG [org.jboss.naming.remote.client.InitialContextFactory] (main) jboss.naming.client.connect.options. has the following options {org.xnio.Options.SASL_POLICY_NOPLAINTEXT=>false} > 13:16:31,191 ERROR [org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1] (Remoting "config-based-naming-client-endpoint" task-1) Channel end notification received, closing channel Channel ID d1f17196 (outbound) of Remoting connection fd3dcedc to /127.0.0.1:4447 > 13:16:31,204 DEBUG [org.jboss.naming.remote.client.HaRemoteNamingStore] (main) Failed to connect to server remote://127.0.0.1:4447: org.jboss.remoting3.NotOpenException: Endpoint is not open > at org.jboss.remoting3.EndpointImpl.resourceUntick(EndpointImpl.java:182) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:261) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105) > at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:179) > at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:117) > at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:223) > at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79) > at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83) > at javax.naming.InitialContext.lookup(InitialContext.java:422) > at org.jboss.as.test.integration.naming.remote.simple.RemoteNamingTestCase.testRemoteLookup(RemoteNamingTestCase.java:74) > {noformat} > server.log snippet: > {noformat} > 13:16:31,025 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "test.jar" > 13:16:31,163 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "thinkpax" task-3) Channel Opened - Channel ID 51f17196 (inbound) of Remoting connection b9da2788 to /127.0.0.1:46866 > 13:16:31,176 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "thinkpax" task-4) Chosen version 0x01 > 13:16:31,189 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "thinkpax" read-1) Channel Channel ID 51f17196 (inbound) of Remoting connection b9da2788 to /127.0.0.1:46866 closed. > 13:16:31,193 INFO [org.jboss.as.naming] (Remoting "thinkpax" task-1) JBAS011806: Channel end notification received, closing channel Channel ID 51f17196 (inbound) of Remoting connection b9da2788 to null > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017