December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5758) Getting [Management resource '[(\"subsystem\" => \"undertow\")]' not found] when removing ressources from Undertow

by Montpa Pasteur (JIRA)

[ https://issues.jboss.org/browse/WFLY-5758?page=com.atlassian.jira.plugin.... ] Montpa Pasteur commented on WFLY-5758: -------------------------------------- Doesn't fix the problem. > Getting [Management resource '[(\"subsystem\" => \"undertow\")]' not found] when removing ressources from Undertow > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-5758 > URL: https://issues.jboss.org/browse/WFLY-5758 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.x.x TBD > Environment: Wildfly 8.2.1 on SUSE Linux 11.1 and Solaris 11 > Reporter: Montpa Pasteur > Assignee: Alexey Loubyansky > Priority: Minor > > When trying remove more that one resource from Undertow using the CLI, I am getting this message: *[Management resource '[(\"subsystem\" => \"undertow\")]' not found*] > This doesn't happen all time, it looks like random. Adding a sleep between the CLI command helps some time. > I get this problem when trying to remove http request header configuration and when trying to remove static ressource serving configuration(location, file handler, filter ..) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-994) Improve extensibility of drools extension in KIE Server

by Maciej Swiderski (JIRA)

Maciej Swiderski created DROOLS-994: --------------------------------------- Summary: Improve extensibility of drools extension in KIE Server Key: DROOLS-994 URL: https://issues.jboss.org/browse/DROOLS-994 Project: Drools Issue Type: Enhancement Components: kie server Affects Versions: 6.3.0.Final Reporter: Maciej Swiderski Assignee: Edson Tirelli Currently Drools extension in KIE Server expects data in String format that then are transformed into object representation via marshallers. While this is completely ok for REST and JMS it might be a limitation when other type of transports are required - socket communication with binary data, Apache Mina, Netty, etc Current solution should be improved to allow direct use of rule service that will be responsible for: - finding ksession to use - executing commands - returning results such service should be then wrapped with implementation that deal with given transport like REST and JMS based on string payload and marshaller. Custom implementation could then decide how to deal with different types of data handling and directly call the rule execution service to avoid sting based transformation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-994) Improve extensibility of drools extension in KIE Server

by Maciej Swiderski (JIRA)

[ https://issues.jboss.org/browse/DROOLS-994?page=com.atlassian.jira.plugin... ] Maciej Swiderski reassigned DROOLS-994: --------------------------------------- Assignee: Maciej Swiderski (was: Edson Tirelli) > Improve extensibility of drools extension in KIE Server > ------------------------------------------------------- > > Key: DROOLS-994 > URL: https://issues.jboss.org/browse/DROOLS-994 > Project: Drools > Issue Type: Enhancement > Components: kie server > Affects Versions: 6.3.0.Final > Reporter: Maciej Swiderski > Assignee: Maciej Swiderski > > Currently Drools extension in KIE Server expects data in String format that then are transformed into object representation via marshallers. While this is completely ok for REST and JMS it might be a limitation when other type of transports are required - socket communication with binary data, Apache Mina, Netty, etc > Current solution should be improved to allow direct use of rule service that will be responsible for: > - finding ksession to use > - executing commands > - returning results > such service should be then wrapped with implementation that deal with given transport like REST and JMS based on string payload and marshaller. Custom implementation could then decide how to deal with different types of data handling and directly call the rule execution service to avoid sting based transformation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5765) Data source connection-properties is defined as an attribute and a sub-resource

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-5765?page=com.atlassian.jira.plugin.... ] Jesper Pedersen reassigned WFLY-5765: ------------------------------------- Assignee: Stefano Maestri (was: Jesper Pedersen) > Data source connection-properties is defined as an attribute and a sub-resource > ------------------------------------------------------------------------------- > > Key: WFLY-5765 > URL: https://issues.jboss.org/browse/WFLY-5765 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: James Perkins > Assignee: Stefano Maestri > Priority: Critical > > The {{subsystem=datasource/data-source=*}} resource has a {{connection-properties}} attribute and a {{connection-properties}} sub-resource. Since DMR is a tree structure each child must have a unique key. Since the parent resource has a {{connection-properties}} attribute and sub-resource with a {{read-resource}} operation you will only get one of the values. > Also writing to the {{connection-properties}} attribute fails to marshal the XML since marshaller expects the value to look something like > {code} > { "key" => { "value" => "real-value" } } > {code} > But the resource definition expects > {code} > { "key" => "real-value" } > {code} > The attribute does not appear to be in EAP 6.4. It is however in WildFly 8.x and 9.x. Some further research should be done, but the attribute could likely be removed. Not having the attribute would also be more consistent with XA data sources. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5769) If development mode enabled register ProbeExtension also for non-web deployments

by Martin Kouba (JIRA)

Martin Kouba created WFLY-5769: ---------------------------------- Summary: If development mode enabled register ProbeExtension also for non-web deployments Key: WFLY-5769 URL: https://issues.jboss.org/browse/WFLY-5769 Project: WildFly Issue Type: Task Components: CDI / Weld Reporter: Martin Kouba Assignee: Martin Kouba Currently, the extension is only registered for web deployments. However, Weld Probe also supports JMX. See also {{org.jboss.as.weld.deployment.processors.DevelopmentModeProcessor}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5769) If development mode enabled register ProbeExtension also for non-web deployments

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-5769?page=com.atlassian.jira.plugin.... ] Martin Kouba updated WFLY-5769: ------------------------------- Affects Version/s: 10.0.0.CR4 > If development mode enabled register ProbeExtension also for non-web deployments > -------------------------------------------------------------------------------- > > Key: WFLY-5769 > URL: https://issues.jboss.org/browse/WFLY-5769 > Project: WildFly > Issue Type: Task > Components: CDI / Weld > Affects Versions: 10.0.0.CR4 > Reporter: Martin Kouba > Assignee: Martin Kouba > > Currently, the extension is only registered for web deployments. However, Weld Probe also supports JMX. See also {{org.jboss.as.weld.deployment.processors.DevelopmentModeProcessor}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 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: ----------------------------------------------- Dmitrii Tikhomirov <dtikhomi(a)redhat.com> changed the Status of [bug 1256325|https://bugzilla.redhat.com/show_bug.cgi?id=1256325] from POST 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 (JBoss Web) > 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)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-203) Add OAuth2 SASL Mechanism

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-203?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-203: --------------------------- Description: See https://tools.ietf.org/html/rfc7628. (was: See https://tools.ietf.org/html/draft-ietf-kitten-sasl-oauth-21.) > Add OAuth2 SASL Mechanism > ------------------------- > > Key: ELY-203 > URL: https://issues.jboss.org/browse/ELY-203 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 2.0.0.Alpha1 > > > See https://tools.ietf.org/html/rfc7628. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5768) Unable to exclude root context (/) via excluded-contexts in mod_cluster subsystem

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-5768: ------------------------------------ Summary: Unable to exclude root context (/) via excluded-contexts in mod_cluster subsystem Key: WFLY-5768 URL: https://issues.jboss.org/browse/WFLY-5768 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR4 Reporter: Radoslav Husar Assignee: Radoslav Husar {noformat}[standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=excluded-contexts,value="ROOT,/"{noformat} but no luck {noformat} mod_cluster/1.3.2.Alpha1-SNAPSHOT Auto Refresh show DUMP output show INFO output Node localhost (ajp://127.0.0.1:8009): Enable Contexts Disable Contexts Stop Contexts Balancer: syrah-cluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 26,Ttl: 60000000,Status: OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 77 Virtual Host 1: Contexts: /clusterbench-passivating, Status: ENABLED Request: 0 Disable Stop /, Status: ENABLED Request: 0 Disable Stop Aliases: localhost default-host {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5767) Fix reference to removed enable-welcome-root in welcome content

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-5767: ------------------------------------ Summary: Fix reference to removed enable-welcome-root in welcome content Key: WFLY-5767 URL: https://issues.jboss.org/browse/WFLY-5767 Project: WildFly Issue Type: Bug Components: Documentation, Web (Undertow) Affects Versions: 10.0.0.CR4 Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Trivial No more! - <p class="note">To replace this page set "enable-welcome-root" to false in your server configuration and deploy - your own war with / as its context path.</p> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2015