February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5566) org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5566?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-5566: -------------------------------------- XSite tests use 4 nodes but you configure num_initial_members=2... > org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed > -------------------------------------------------------------------------------- > > Key: WFLY-5566 > URL: https://issues.jboss.org/browse/WFLY-5566 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 10.0.0.CR2 > Reporter: Ivan Straka > Assignee: Dmitrii Tikhomirov > Labels: clustering_revalidate > > There is org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed failing with exception: > {code:java} > Error Message > expected:<500> but was:<200> > Stacktrace > java.lang.AssertionError: expected:<500> but was:<200> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed(XSiteSimpleTestCase.java:202) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3971) Jar Services in META-INF/services are not loaded from static modules

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3971?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-3971. ---------------------------------- Fix Version/s: 10.0.0.Final Resolution: Done > Jar Services in META-INF/services are not loaded from static modules > -------------------------------------------------------------------- > > Key: WFLY-3971 > URL: https://issues.jboss.org/browse/WFLY-3971 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.1.0.Final, 9.0.0.Final, 10.0.0.Alpha6 > Reporter: Tomas Repel > Assignee: Stuart Douglas > Fix For: 10.0.0.Final > > > If the web application (war) uses jar file from static module, the content of META-INF/services has no effect. If the jar is located inside WEB-INF/lib, services are loaded successfully. > Neither adding `Dependencies: my.module.name.com services` into MANIFEST.MF nor adding `services="import"` to jboss-deployment-structure.xml works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5969) io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents

by Matthew Casperson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5969?page=com.atlassian.jira.plugin.... ] Matthew Casperson edited comment on WFLY-5969 at 2/14/16 5:37 PM: ------------------------------------------------------------------ Interestingly, when I set the context-root in jboss-web.xml, all the links work as expected (i.e. http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml returns a 404). With the links below I have defined the following jboss-web.xml: {code} <jboss-web>  <context-root>wildfly-bug</context-root> </jboss-web> {code} * http://localhost:8080/wildfly-bug/static will browse as expected * http://localhost:8080/wildfly-bug/static/ will browse as expected * http://localhost:8080/wildfly-bug/static/static/data.xml returns a 404 * http://localhost:8080/wildfly-bug/static/data.xml will open the file as expected These tests were done against Wildfly 10 final was (Author: mcasperson): Interestingly, when I set the context-root in jboss-web.xml, all the links work as expected (i.e. http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml returns a 404). With the links below I have defined the following jboss-web.xml: {code} <jboss-web>  <context-root>wildfly-bug</context-root> </jboss-web> {code} * http://localhost:8080/wildfly-bug/static will browse as expected * http://localhost:8080/wildfly-bug/static/ will browse as expected * http://localhost:8080/wildfly-bug/static/static/data.xml returns a 404 * http://localhost:8080/wildfly-bug/static/data.xml will open the file as expected > io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents > ---------------------------------------------------------------------------------- > > Key: WFLY-5969 > URL: https://issues.jboss.org/browse/WFLY-5969 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Environment: MacOS with Java 8u65 > Reporter: Matthew Casperson > Assignee: Stuart Douglas > Attachments: Screen Shot 2016-01-11 at 11.24.34 am.png, Screen Shot 2016-01-11 at 11.24.41 am.png > > > The Untertow DefaultServlet exhibits some odd behaviour when it has been mapped to a subdirectory. > To see this behaviour, build the WAR file from the sample project at https://github.com/mcasperson/wildfly-default-servlet-bug. Deploy to WildFly 10 CR5, and open the link http://localhost:8080/wildfly-default-servlet-bug/static (note no slash on the end of the URL). You'll see the expected directory listing. > !Screen Shot 2016-01-11 at 11.24.41 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/ (note the slash on the end). You'll actually now be browsing the root directory of the application. > !Screen Shot 2016-01-11 at 11.24.34 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml (note the double static in the URL). You'll be able to open the XML file. This is not what I would have expected. > Now open http://localhost:8080/wildfly-default-servlet-bug/static/data.xml. You'll get a 404. I would have expected to be able to open the file using this URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5969) io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents

by Matthew Casperson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5969?page=com.atlassian.jira.plugin.... ] Matthew Casperson edited comment on WFLY-5969 at 2/14/16 5:34 PM: ------------------------------------------------------------------ Interestingly, when I set the context-root in jboss-web.xml, all the links work as expected (i.e. http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml returns a 404). With the links below I have defined the following jboss-web.xml: {code} <jboss-web>  <context-root>wildfly-bug</context-root> </jboss-web> {code} * http://localhost:8080/wildfly-bug/static will browse as expected * http://localhost:8080/wildfly-bug/static/ will browse as expected * http://localhost:8080/wildfly-bug/static/static/data.xml returns a 404 * http://localhost:8080/wildfly-bug/static/data.xml will open the file as expected was (Author: mcasperson): Interestingly, when I set the context-root in jboss-web.xml, all the links work as expected (i.e. http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml returns a 404). * http://localhost:8080/wildfly-bug/static will browse as expected * http://localhost:8080/wildfly-bug/static/ will browse as expected * http://localhost:8080/wildfly-bug/static/static/data.xml returns a 404 * http://localhost:8080/wildfly-bug/static/data.xml will open the file as expected > io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents > ---------------------------------------------------------------------------------- > > Key: WFLY-5969 > URL: https://issues.jboss.org/browse/WFLY-5969 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Environment: MacOS with Java 8u65 > Reporter: Matthew Casperson > Assignee: Stuart Douglas > Attachments: Screen Shot 2016-01-11 at 11.24.34 am.png, Screen Shot 2016-01-11 at 11.24.41 am.png > > > The Untertow DefaultServlet exhibits some odd behaviour when it has been mapped to a subdirectory. > To see this behaviour, build the WAR file from the sample project at https://github.com/mcasperson/wildfly-default-servlet-bug. Deploy to WildFly 10 CR5, and open the link http://localhost:8080/wildfly-default-servlet-bug/static (note no slash on the end of the URL). You'll see the expected directory listing. > !Screen Shot 2016-01-11 at 11.24.41 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/ (note the slash on the end). You'll actually now be browsing the root directory of the application. > !Screen Shot 2016-01-11 at 11.24.34 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml (note the double static in the URL). You'll be able to open the XML file. This is not what I would have expected. > Now open http://localhost:8080/wildfly-default-servlet-bug/static/data.xml. You'll get a 404. I would have expected to be able to open the file using this URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5969) io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents

by Matthew Casperson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5969?page=com.atlassian.jira.plugin.... ] Matthew Casperson commented on WFLY-5969: ----------------------------------------- Interestingly, when I set the context-root in jboss-web.xml, all the links work as expected (i.e. http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml returns a 404). * http://localhost:8080/wildfly-bug/static will browse as expected * http://localhost:8080/wildfly-bug/static/ will browse as expected * http://localhost:8080/wildfly-bug/static/static/data.xml still opens the xml file (this is an invalid path, so this is unexpected) * http://localhost:8080/wildfly-bug/static/data.xml will open the file as expected > io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents > ---------------------------------------------------------------------------------- > > Key: WFLY-5969 > URL: https://issues.jboss.org/browse/WFLY-5969 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Environment: MacOS with Java 8u65 > Reporter: Matthew Casperson > Assignee: Stuart Douglas > Attachments: Screen Shot 2016-01-11 at 11.24.34 am.png, Screen Shot 2016-01-11 at 11.24.41 am.png > > > The Untertow DefaultServlet exhibits some odd behaviour when it has been mapped to a subdirectory. > To see this behaviour, build the WAR file from the sample project at https://github.com/mcasperson/wildfly-default-servlet-bug. Deploy to WildFly 10 CR5, and open the link http://localhost:8080/wildfly-default-servlet-bug/static (note no slash on the end of the URL). You'll see the expected directory listing. > !Screen Shot 2016-01-11 at 11.24.41 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/ (note the slash on the end). You'll actually now be browsing the root directory of the application. > !Screen Shot 2016-01-11 at 11.24.34 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml (note the double static in the URL). You'll be able to open the XML file. This is not what I would have expected. > Now open http://localhost:8080/wildfly-default-servlet-bug/static/data.xml. You'll get a 404. I would have expected to be able to open the file using this URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5969) io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents

by Matthew Casperson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5969?page=com.atlassian.jira.plugin.... ] Matthew Casperson edited comment on WFLY-5969 at 2/14/16 5:32 PM: ------------------------------------------------------------------ Interestingly, when I set the context-root in jboss-web.xml, all the links work as expected (i.e. http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml returns a 404). * http://localhost:8080/wildfly-bug/static will browse as expected * http://localhost:8080/wildfly-bug/static/ will browse as expected * http://localhost:8080/wildfly-bug/static/static/data.xml returns a 404 * http://localhost:8080/wildfly-bug/static/data.xml will open the file as expected was (Author: mcasperson): Interestingly, when I set the context-root in jboss-web.xml, all the links work as expected (i.e. http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml returns a 404). * http://localhost:8080/wildfly-bug/static will browse as expected * http://localhost:8080/wildfly-bug/static/ will browse as expected * http://localhost:8080/wildfly-bug/static/static/data.xml still opens the xml file (this is an invalid path, so this is unexpected) * http://localhost:8080/wildfly-bug/static/data.xml will open the file as expected > io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents > ---------------------------------------------------------------------------------- > > Key: WFLY-5969 > URL: https://issues.jboss.org/browse/WFLY-5969 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Environment: MacOS with Java 8u65 > Reporter: Matthew Casperson > Assignee: Stuart Douglas > Attachments: Screen Shot 2016-01-11 at 11.24.34 am.png, Screen Shot 2016-01-11 at 11.24.41 am.png > > > The Untertow DefaultServlet exhibits some odd behaviour when it has been mapped to a subdirectory. > To see this behaviour, build the WAR file from the sample project at https://github.com/mcasperson/wildfly-default-servlet-bug. Deploy to WildFly 10 CR5, and open the link http://localhost:8080/wildfly-default-servlet-bug/static (note no slash on the end of the URL). You'll see the expected directory listing. > !Screen Shot 2016-01-11 at 11.24.41 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/ (note the slash on the end). You'll actually now be browsing the root directory of the application. > !Screen Shot 2016-01-11 at 11.24.34 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml (note the double static in the URL). You'll be able to open the XML file. This is not what I would have expected. > Now open http://localhost:8080/wildfly-default-servlet-bug/static/data.xml. You'll get a 404. I would have expected to be able to open the file using this URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5969) io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents

by Matthew Casperson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5969?page=com.atlassian.jira.plugin.... ] Matthew Casperson commented on WFLY-5969: ----------------------------------------- With the resolve-against-context-root option, I see the following behaviour: * http://localhost:8080/wildfly-default-servlet-bug/static will browse as expected * http://localhost:8080/wildfly-default-servlet-bug/static/ will browse as expected * http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml still opens the xml file (this is an invalid path, so this is unexpected) * http://localhost:8080/wildfly-default-servlet-bug/static/data.xml will open the file as expected > io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents > ---------------------------------------------------------------------------------- > > Key: WFLY-5969 > URL: https://issues.jboss.org/browse/WFLY-5969 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Environment: MacOS with Java 8u65 > Reporter: Matthew Casperson > Assignee: Stuart Douglas > Attachments: Screen Shot 2016-01-11 at 11.24.34 am.png, Screen Shot 2016-01-11 at 11.24.41 am.png > > > The Untertow DefaultServlet exhibits some odd behaviour when it has been mapped to a subdirectory. > To see this behaviour, build the WAR file from the sample project at https://github.com/mcasperson/wildfly-default-servlet-bug. Deploy to WildFly 10 CR5, and open the link http://localhost:8080/wildfly-default-servlet-bug/static (note no slash on the end of the URL). You'll see the expected directory listing. > !Screen Shot 2016-01-11 at 11.24.41 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/ (note the slash on the end). You'll actually now be browsing the root directory of the application. > !Screen Shot 2016-01-11 at 11.24.34 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml (note the double static in the URL). You'll be able to open the XML file. This is not what I would have expected. > Now open http://localhost:8080/wildfly-default-servlet-bug/static/data.xml. You'll get a 404. I would have expected to be able to open the file using this URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5566) org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed

by Ivan Straka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5566?page=com.atlassian.jira.plugin.... ] Ivan Straka commented on WFLY-5566: ----------------------------------- I have taken some investigation and I have found out, that this test is failing only when TCPGOSSIP is configured to be used. IMHO all instances are configured to use TCPGOOSSIP, therefore they all make cluster. So the cache is replicated. I assume this is the reason, why the test fails. Can you confirm this? > org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed > -------------------------------------------------------------------------------- > > Key: WFLY-5566 > URL: https://issues.jboss.org/browse/WFLY-5566 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 10.0.0.CR2 > Reporter: Ivan Straka > Assignee: Dmitrii Tikhomirov > Labels: clustering_revalidate > > There is org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed failing with exception: > {code:java} > Error Message > expected:<500> but was:<200> > Stacktrace > java.lang.AssertionError: expected:<500> but was:<200> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed(XSiteSimpleTestCase.java:202) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6097) Error response handling from bean validation ignores Accept header

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/WFLY-6097?page=com.atlassian.jira.plugin.... ] Ron Sigal commented on WFLY-6097: --------------------------------- RESTEASY-1264 is closed. > Error response handling from bean validation ignores Accept header > ------------------------------------------------------------------ > > Key: WFLY-6097 > URL: https://issues.jboss.org/browse/WFLY-6097 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.Final > Environment: Mac OS X El Captain > java version "1.8.0_66" > Java(TM) SE Runtime Environment (build 1.8.0_66-b17) > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode) > Reporter: Renann Prado > Assignee: Weinan Li > Attachments: delivery-optimization-ear-1.0.Final.ear > > > Basically I have a very simple application that has request validation in the REST endpoints. > According to the documentation of RESTEasy, I should get a JSON error response if I put "application/json" in Accept header in the request. > https://docs.jboss.org/resteasy/docs/3.0.13.Final/userguide/html/Validati... > The mentioned feature worked just fine in Wildfly 9.0.2.Final. Now, however, it doesn't. > I have tried to upgrade the dependencies in the pom.xml to use dependencies from Wildfly 10.0.0.Final, but still no luck. Though the attached application deploys just fine in Wildfly 9.0.2.Final and Wildfly 10.0.0.Final. > In WF 9.0.2.Final I used to get the below error *JSON* > {code:json} > { > "exception": null, > "fieldViolations": [], > "propertyViolations": [], > "classViolations": [], > "parameterViolations": [{ > "constraintType": "PARAMETER", > "path": "registerLogisticsNetwork.arg0.name", > "message": "may not be null", > "value": "" > }], > "returnValueViolations": [] > } > {code} > In WF 10.0.0.Final I get this: > {code} > [PARAMETER] > [registerLogisticsNetwork.arg0.name] > [may not be null] > [] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6206) org.jboss.metadata.ejb.spec.EntityBeanMetaData still needs to be setup for later isEntity check, to avoid ISE on ejbType==null

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-6206: ------------------------------------ Summary: org.jboss.metadata.ejb.spec.EntityBeanMetaData still needs to be setup for later isEntity check, to avoid ISE on ejbType==null Key: WFLY-6206 URL: https://issues.jboss.org/browse/WFLY-6206 Project: WildFly Issue Type: Bug Components: EJB Reporter: Stuart Douglas Assignee: Stuart Douglas [http://pastebin.test.redhat.com/348470] shows the exception that we are getting from various different TCK tests. I recreated the failure locally with the com/sun/ts/tests/ejb30/misc/metadataComplete/appclient2ejbjars tests. The first ISE was on this bean: [https://svn.devel.redhat.com/repos/jboss-tck/tck7/trunk/src/com/sun/ts/te... Looks like we need to set the bean type for this test, so that the [https://github.com/wildfly/wildfly/pull/8674/files#diff-eda1b9555b6e171eb...] check for entity beans will not throw an ISE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

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