December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5044) Upgrade HAL to 2.8.4

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5044?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5044. ---------------------------- > Upgrade HAL to 2.8.4 > -------------------- > > Key: WFLY-5044 > URL: https://issues.jboss.org/browse/WFLY-5044 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4651) Change default locking isolation of infinispan caches to READ_COMMITTED

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4651?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4651. ---------------------------- > Change default locking isolation of infinispan caches to READ_COMMITTED > ----------------------------------------------------------------------- > > Key: WFLY-4651 > URL: https://issues.jboss.org/browse/WFLY-4651 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Affects Versions: 9.0.0.CR1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > > This will allow concurrent read access to the session using our default configuration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4604) Smoke testsuite fails when running under security manager on JDK8

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4604?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4604. ---------------------------- > Smoke testsuite fails when running under security manager on JDK8 > ----------------------------------------------------------------- > > Key: WFLY-4604 > URL: https://issues.jboss.org/browse/WFLY-4604 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 9.0.0.CR1 > Environment: JDK 8 runtime > Reporter: Tomaz Cerar > Assignee: James Perkins > Fix For: 9.0.0.CR2, 10.0.0.Alpha1 > > > see http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=52198&tab=buil... > failed tests: > {noformat} > org.jboss.as.test.integration.jsp.JspTagTestCase.test > org.jboss.as.test.integration.web.jsp.taglib.external.ExternalTagLibTestCase.testExternalAndInternalTagLib > org.jboss.as.test.integration.web.jsp.taglib.external.ExternalTagLibTestCase.testExternalTagLibOnly > {noformat} > {noformat} > Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "accessDeclaredMembers")" in code source "(file:/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/web/target/jbossas/standalone/tmp/external-dependency-only.war/ <no signer certificates>)" of "org.apache.jasper.servlet.JasperLoader@1b8fd02") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:270) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:172) > at java.lang.Class.checkMemberAccess(Class.java:2348) > at java.lang.Class.getDeclaredConstructor(Class.java:2177) > at org.jboss.as.ee.component.ReflectiveClassIntrospector.createFactory(ReflectiveClassIntrospector.java:22) > at org.jboss.as.ee.component.ComponentRegistry.createInstanceFactory(ComponentRegistry.java:76) > at org.jboss.as.web.common.WebInjectionContainer.newInstance(WebInjectionContainer.java:67) > at org.wildfly.extension.undertow.deployment.UndertowJSPInstanceManager.newInstance(UndertowJSPInstanceManager.java:67) > at org.apache.jsp.test_jsp._jspx_meth_e_005ftest_005f0(test_jsp.java:83) > at org.apache.jsp.test_jsp._jspService(test_jsp.java:61) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5297) WildFly/IronJacamar 1.3.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5297?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5297. ---------------------------- > WildFly/IronJacamar 1.3.0.Final > ------------------------------- > > Key: WFLY-5297 > URL: https://issues.jboss.org/browse/WFLY-5297 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 10.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3590) Option to disable processing of authentication tokens on unsecured resources.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3590?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-3590. ---------------------------- > Option to disable processing of authentication tokens on unsecured resources. > ----------------------------------------------------------------------------- > > Key: WFLY-3590 > URL: https://issues.jboss.org/browse/WFLY-3590 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Environment: Oracle Java 1.8.0_05, Ubuntu 14.04 > Reporter: Harald Wellmann > Assignee: Stuart Douglas > Fix For: 10.0.0.Alpha3 > > > WildFly sends a basic authentication challenge and denies access when it shouldn't in the following simple setup: > {code:xml} > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>test</realm-name> > </login-config> > > <security-constraint> > <web-resource-collection> > <web-resource-name>all</web-resource-name> > <url-pattern>/hello</url-pattern> > </web-resource-collection> > <auth-constraint> > <role-name>USER</role-name> > </auth-constraint> > </security-constraint> > > <security-role> > <role-name>USER</role-name> > </security-role> > {code} > {{/hello}} is the only protected URL (mapped to a servlet), other URLs like {{/index.html}} are public. > When GETting /index.html with an (unneeded) basic authentication header, access is denied: > {noformat} > $ curl -v -u foo:bar http://localhost:8080/auth-basic/index.html > * Hostname was NOT found in DNS cache > * Trying 127.0.0.1... > * Connected to localhost (127.0.0.1) port 8080 (#0) > * Server auth using Basic with user 'foo' > > GET /auth-basic/index.html HTTP/1.1 > > Authorization: Basic Zm9vOmJhcg== > > User-Agent: curl/7.35.0 > > Host: localhost:8080 > > Accept: */* > > > < HTTP/1.1 401 Unauthorized > < Connection: keep-alive > * Authentication problem. Ignoring this. > < WWW-Authenticate: Basic realm="test" > < X-Powered-By: Undertow/1 > * Server WildFly/8 is not blacklisted > < Server: WildFly/8 > < Content-Type: text/html;charset=ISO-8859-1 > < Content-Length: 71 > < Date: Mon, 07 Jul 2014 17:28:25 GMT > < > * Connection #0 to host localhost left intact > <html><head><title>Error</title></head><body>Unauthorized</body></html> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4164) New JTS record types are not showing up in the CLI

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4164?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4164. ---------------------------- > New JTS record types are not showing up in the CLI > -------------------------------------------------- > > Key: WFLY-4164 > URL: https://issues.jboss.org/browse/WFLY-4164 > Project: WildFly > Issue Type: Enhancement > Components: CLI, Transactions > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 10.0.0.Alpha5 > > > We need to expose the new JTS record types in the tooling: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} > We need these because if a transaction ends up in a heuristic state we can't actually view this using the CLI even though the records are in the object store. This has the consequence that a transaction can remain in the object store indefinitely. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5112) After removing property empty properties tag left in xml cofiguration and server cannot run more.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5112?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5112. ---------------------------- > After removing property empty properties tag left in xml cofiguration and server cannot run more. > ------------------------------------------------------------------------------------------------- > > Key: WFLY-5112 > URL: https://issues.jboss.org/browse/WFLY-5112 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 10.0.0.Beta1 > Environment: Unsecured EAP 7.0.0 DR8 in standalone mode with standalone-full-ha profile. > Reporter: Patrik Cyprian > Assignee: Patrik Cyprian > Priority: Blocker > Fix For: 10.0.0.Beta2 > > > When in IIOP configuration is new property added and server is reloaded, then after removing property and reloading server, server cannot run more because of empty </properties> tag in xml configuration of profile. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4732) Potential race in test suite where ops can execute before server has reloaded

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4732?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4732. ---------------------------- > Potential race in test suite where ops can execute before server has reloaded > ----------------------------------------------------------------------------- > > Key: WFLY-4732 > URL: https://issues.jboss.org/browse/WFLY-4732 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.0.0.Alpha2 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3859) Improve ChannelInstanceResourceDefinition.addChannelProtocolMetricsRegistrationStep

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3859?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-3859. ---------------------------- > Improve ChannelInstanceResourceDefinition.addChannelProtocolMetricsRegistrationStep > ----------------------------------------------------------------------------------- > > Key: WFLY-3859 > URL: https://issues.jboss.org/browse/WFLY-3859 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 10.0.0.Beta1 > > > While debugging a test, I noticed this in the test's console output: > ERROR: WFLYCTL0013: Operation ("some_operation_name") failed - address: ([("subsystem" => "jgroups")]) - failure description: "WFLYCTL0216: Management resource '[(\"subsystem\" => \"jgroups\")]' not found" > Sep 16, 2014 9:29:35 AM org.jboss.as.controller.AbstractOperationContext executeStep > That "some_operation_name" visible to users isn't so good. > A simple fix is to use a more meaningful name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4720) DuplicateServiceException when adding a new FORK channel

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4720?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4720. ---------------------------- > DuplicateServiceException when adding a new FORK channel > -------------------------------------------------------- > > Key: WFLY-4720 > URL: https://issues.jboss.org/browse/WFLY-4720 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.0.CR1, 10.0.0.Alpha2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/channel=ee/fork=myfork:add > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.jgroups.factory.ee is already registered", > "rolled-back" => true > } > {noformat} > the problem is fixed in org.jboss.as.clustering.jgroups.subsystem.ForkAddHandler#installRuntimeServices -- 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