July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5117) Switch to version 5 of the management schema

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-5117?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-5117: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9079 (was: https://github.com/wildfly/wildfly/pull/8583) > Switch to version 5 of the management schema > -------------------------------------------- > > Key: WFLY-5117 > URL: https://issues.jboss.org/browse/WFLY-5117 > Project: WildFly > Issue Type: Task > Components: Domain Management, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: affects_elytron > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5136) Switch http-management-interface configurations to use http-upgrade enabled.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-5136?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-5136: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9079 (was: https://github.com/wildfly/wildfly/pull/8832) > Switch http-management-interface configurations to use http-upgrade enabled. > ---------------------------------------------------------------------------- > > Key: WFLY-5136 > URL: https://issues.jboss.org/browse/WFLY-5136 > Project: WildFly > Issue Type: Task > Components: Build System, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: affects_elytron > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6890) Add Weld SPI dependency to the transactions module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-6890?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on WFLY-6890: --------------------------------------- Fix pull request on Narayana WildFly clone: https://github.com/jbosstm/jboss-as/pull/47 > Add Weld SPI dependency to the transactions module > -------------------------------------------------- > > Key: WFLY-6890 > URL: https://issues.jboss.org/browse/WFLY-6890 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 10.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6890) Add Weld SPI dependency to the transactions module

by Gytis Trikleris (JIRA)

Gytis Trikleris created WFLY-6890: ------------------------------------- Summary: Add Weld SPI dependency to the transactions module Key: WFLY-6890 URL: https://issues.jboss.org/browse/WFLY-6890 Project: WildFly Issue Type: Task Components: Transactions Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 10.1.0.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6889) ArrayIndexOutOfBoundsException happens when Accept header is just a slash

by Dmitrii Tikhomirov (JIRA)

Dmitrii Tikhomirov created WFLY-6889: ---------------------------------------- Summary: ArrayIndexOutOfBoundsException happens when Accept header is just a slash Key: WFLY-6889 URL: https://issues.jboss.org/browse/WFLY-6889 Project: WildFly Issue Type: Bug Components: JSF Affects Versions: 10.0.0.Final Reporter: Dmitrii Tikhomirov Assignee: Dmitrii Tikhomirov Fix For: 10.1.0.CR1 Some clients send Accept header with just '/'. It causes ArrayIndexOutOfBoundsException as follows. {code} 2016-07-26 14:22:57,119 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (default task-15) Error Rendering View[/index.xhtml]: java.lang.ArrayIndexOutOfBoundsException: 0 at com.sun.faces.renderkit.RenderKitUtils.buildTypeArrayFromString(RenderKitUtils.java:913) at com.sun.faces.renderkit.RenderKitUtils.determineContentType(RenderKitUtils.java:563) at com.sun.faces.renderkit.RenderKitImpl.createResponseWriter(RenderKitImpl.java:260) at com.sun.faces.application.view.FaceletViewHandlingStrategy.createResponseWriter(FaceletViewHandlingStrategy.java:1193) at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:405) at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:134) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:659) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:285) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:264) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:175) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:802) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} This is fixed in the upstream as JAVASERVERFACES-4077 but not backported yet. https://java.net/jira/browse/JAVASERVERFACES-4077 https://github.com/javaserverfaces/mojarra/commit/14514cfe589cacad683f86a... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1676) read-attribute --node is badly handled

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1676?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-1676: ----------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1708 > read-attribute --node is badly handled > -------------------------------------- > > Key: WFCORE-1676 > URL: https://issues.jboss.org/browse/WFCORE-1676 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > read-attribute --node=interface=public namespaces should fail and fails > read-attribute namespaces --node=interface=public should fail and doesn't > read-attribute --node=interface=public init-address should succeed and succeeds > read-attribute init-address --node=interface=public should succeed and fails > This is due to some logic in place to retrieve the node value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1240) Allow to define an alternative JNDI name for the ManagedExecutorService

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1240: ----------------------------------- Summary: Allow to define an alternative JNDI name for the ManagedExecutorService Key: DROOLS-1240 URL: https://issues.jboss.org/browse/DROOLS-1240 Project: Drools Issue Type: Enhancement Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco At the moment the JNDI name of the ManagedExecutorService to be used inside a JEE container is hardcoded to the default one. It is required to make it configurable via System property. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6888) Fix bridge support for large messages

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6888?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-5437 to WFLY-6888: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-6888 (was: JBEAP-5437) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) (was: ActiveMQ) Affects Version/s: 10.0.0.Final (was: 7.0.1.CR2) > Fix bridge support for large messages > ------------------------------------- > > Key: WFLY-6888 > URL: https://issues.jboss.org/browse/WFLY-6888 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6888) Fix bridge support for large messages

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6888?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-6888: ------------------------------ Git Pull Request: (was: https://github.com/rh-messaging/jboss-activemq-artemis/pull/93) > Fix bridge support for large messages > ------------------------------------- > > Key: WFLY-6888 > URL: https://issues.jboss.org/browse/WFLY-6888 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2080) New Address which contains IP address and port

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2080?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2080: -------------------------------- More issues: if we create the address in an {{AddressGenerator}}, the bind_addr and bind_port are set (e.g. 127.0.0.1 and 7800). However, the port might change on connect time: e.g. if port 7800 is taken, 7801 will be taken, so the address should be 127.0.0.1:7801 instead of 127.0.0.1:7800! Perhaps {{AddressGenerator}} is not such a good idea and we need to use {{IpAddressUUID}} via a mechanism that's enabled/disabled in the transport and returns {{TP.getPhysicalAddress()}}... > New Address which contains IP address and port > ---------------------------------------------- > > Key: JGRP-2080 > URL: https://issues.jboss.org/browse/JGRP-2080 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0 > > > Currently, UUIDs are mapped to IpAddresses (InetAddress and port). The mappings are maintained in logical_address_cache in TP and populated via the discovery protocol. > If we encoded the IP address and port (6 bytes in IPv4, 18 bytes in IPv6) directly into the UUID, we would not have to maintain this cache anymore. At least not for IpAddresses, but still for UUID/logical_name mappings. > An {{IPv4UUID}} (credits to Neal Dillman) would look like this: > * 4 bytes: IPv4 address > * 2 bytes: port > * 12 bytes: random data (rest of the UUID) > When joining a cluster, the joiner would only need to discover the address of the coordinator and send a JOIN-REQ to it. The JOIN-RSP would contain the view, which contains all members, so the joiner has all addresses. Plus, the coord would also send a VIEW-CHANGE to all existing members, so they have the address of the new member, too. > When sending a unicast, the transport could simply extract the IpAddress from the first 6 bytes of the IPv4UUID to know the destination address. For multicasts, UDP is not an issue, and TCP would simply iterate over the current view and send the message to each member separately. > An IPv6UUID would need more than 16 bytes as it already needs 18 bytes for the address and the port. We might add another 6 bytes for uniqueness, to have a nice padding at 24 bytes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

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 July 2016