January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5986) WFLYSRV0058: Additional resource root .. added via jboss-deployment-structure.xml does not exist when absolute path used

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-5986: ---------------------------------- Summary: WFLYSRV0058: Additional resource root .. added via jboss-deployment-structure.xml does not exist when absolute path used Key: WFLY-5986 URL: https://issues.jboss.org/browse/WFLY-5986 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 10.0.0.CR5 Reporter: Brad Maxwell Assignee: Jason Greene Using: {code} <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment> <resources> <resource-root path="/home/test/my.jar" /> </resources> </deployment> </jboss-deployment-structure> {code} It fails to locate the resource-root: {code} WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0058: Additional resource root /content/app1.war//home/test/my.jar added via jboss-deployment-structure.xml does not exist {code} Looks like src/main/java/org/jboss/as/server/deployment/module/descriptor/DeploymentStructureDescriptorParser.java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1277) Embed-server from CLI launch shows twice prompt string

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1277?page=com.atlassian.jira.plugi... ] Ståle Pedersen commented on WFCORE-1277: ---------------------------------------- ive pushed out a 0.66.3-SNAPSHOT, could you please try that? it fixes the issue when ive tested it locally. > Embed-server from CLI launch shows twice prompt string > ------------------------------------------------------ > > Key: WFCORE-1277 > URL: https://issues.jboss.org/browse/WFCORE-1277 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.5.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > {noformat} > When I launch an embed-server from CLI, it displays twice [standalone@embedded /] [standalone@embedded /] for the first time. > [wangc@dhcp-128-40 wildfly-10.0.0.Final-SNAPSHOT]$ sh bin/jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server > [standalone@embedded /] [standalone@embedded /] ls > core-service launch-type=EMBEDDED product-version=undefined > deployment management-major-version=4 profile-name=undefined > deployment-overlay management-micro-version=0 release-codename=Kenny > extension management-minor-version=0 release-version=2.0.5.Final > interface name=dhcp-128-40 running-mode=ADMIN_ONLY > path namespaces=[] schema-locations=[] > socket-binding-group organization=undefined server-state=running > subsystem process-type=Server suspend-state=RUNNING > system-property product-name=undefined uuid=8c4ede2f-8e14-48bf-9eaf-73947e23edcf > [standalone@embedded /] quit > {noformat} > This does not happen in 2.0.4.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5985) WFLYSRV0058: Additional resource root .. added via jboss-deployment-structure.xml does not exist when absolute path used

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-5985?page=com.atlassian.jira.plugin.... ] Brad Maxwell updated WFLY-5985: ------------------------------- Component/s: Server Description: Using: {code} <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment> <resources> <resource-root path="/home/test/my.jar" /> </resources> </deployment> </jboss-deployment-structure> {code} It fails to locate the resource-root: {code} WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0058: Additional resource root /content/app1.war//home/test/my.jar added via jboss-deployment-structure.xml does not exist {code} Looks like src/main/java/org/jboss/as/server/deployment/module/descriptor/DeploymentStructureDescriptorParser.java was: {code} <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment> <resources> <resource-root path="/home/test/my.jar" /> </resources> </deployment> </jboss-deployment-structure> {code} {code} WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0058: Additional resource root /content/app1.war//home/test/my.jar added via jboss-deployment-structure.xml does not exist {code} Affects Version/s: 10.0.0.CR5 > WFLYSRV0058: Additional resource root .. added via jboss-deployment-structure.xml does not exist when absolute path used > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-5985 > URL: https://issues.jboss.org/browse/WFLY-5985 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 10.0.0.CR5 > Reporter: Brad Maxwell > Assignee: Jason Greene > > Using: > {code} > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <deployment> > <resources> > <resource-root path="/home/test/my.jar" /> > </resources> > </deployment> > </jboss-deployment-structure> > {code} > It fails to locate the resource-root: > {code} > WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0058: Additional resource root /content/app1.war//home/test/my.jar added via jboss-deployment-structure.xml does not exist > {code} > Looks like src/main/java/org/jboss/as/server/deployment/module/descriptor/DeploymentStructureDescriptorParser.java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5441) Received unsolicited state from node X for segment Y of cache Z

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5441?page=com.atlassian.jira.plugin.... ] Radoslav Husar resolved WFLY-5441. ---------------------------------- Fix Version/s: 10.0.0.CR5 Resolution: Done Fix brought in by WFLY-5772. > Received unsolicited state from node X for segment Y of cache Z > --------------------------------------------------------------- > > Key: WFLY-5441 > URL: https://issues.jboss.org/browse/WFLY-5441 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR5 > Reporter: Richard Janík > Assignee: Radoslav Husar > Priority: Minor > Fix For: 10.0.0.CR5 > > > Hi, > we're occasionally seeing these warnings in the server logs: > {code} > [JBossINF] [0m[33m08:20:45,364 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t36) Received unsolicited state from node perf20 for segment 48 of cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar > ... > [JBossINF] [0m[33m08:21:02,793 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t22) Discarding received cache entries for segment 48 of cache dist because they do not belong to this node. > {code} > The warnings seem to be harmless. > This is the equivalent of https://bugzilla.redhat.com/show_bug.cgi?id=923789 which has been (with EAP6) followed by IllegalStateExceptions and has later been closed as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=922699. However, no IllegalStateExceptions occur with EAP7 and thus these two messages seem to be unrelated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1294) Alias in jboss-cli are not persistent

by Alexis Hassler (JIRA)

Alexis Hassler created WFCORE-1294: -------------------------------------- Summary: Alias in jboss-cli are not persistent Key: WFCORE-1294 URL: https://issues.jboss.org/browse/WFCORE-1294 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 2.0.5.Final Reporter: Alexis Hassler Assignee: Alexey Loubyansky Alias are supposed to be persistent in Aesh, but it fails due to a bug. This bug has been fix in Aesh but after version 0.66.2. see https://issues.jboss.org/browse/AESH-341 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5985) WFLYSRV0058: Additional resource root .. added via jboss-deployment-structure.xml does not exist when absolute path used

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-5985: ---------------------------------- Summary: WFLYSRV0058: Additional resource root .. added via jboss-deployment-structure.xml does not exist when absolute path used Key: WFLY-5985 URL: https://issues.jboss.org/browse/WFLY-5985 Project: WildFly Issue Type: Bug Reporter: Brad Maxwell Assignee: Jason Greene {code} <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment> <resources> <resource-root path="/home/test/my.jar" /> </resources> </deployment> </jboss-deployment-structure> {code} {code} WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0058: Additional resource root /content/app1.war//home/test/my.jar added via jboss-deployment-structure.xml does not exist {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5962) ServletContainerInitializers from jboss-deployment-structure.xml module dependencies are not invoked

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5962?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5962: ----------------------------------------------- Aaron Ogburn <aogburn(a)redhat.com> changed the Status of [bug 1297877|https://bugzilla.redhat.com/show_bug.cgi?id=1297877] from ASSIGNED to POST > ServletContainerInitializers from jboss-deployment-structure.xml module dependencies are not invoked > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-5962 > URL: https://issues.jboss.org/browse/WFLY-5962 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Reporter: Aaron Ogburn > Assignee: Stuart Douglas > Attachments: WFLY5962test.zip > > > If a module includes a ServletContainerInitializer, that ServletContainerInitializer is not invoked for any applications that include the module in its jboss-deployment-structure.xml module dependencies. It looks like the ServletContainerInitializerDeploymentProcessor only checks server provided dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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: ----------------------------------------- I was running it on MacOS with Java 8u65. > 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, 3 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 updated WFLY-5969: ------------------------------------ Environment: MacOS with Java 8u65 > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1293) SocketBindingManager.createMulticast/DatagramSocket(...) variants needed for unbound sockets

by Paul Ferraro (JIRA)

Paul Ferraro created WFCORE-1293: ------------------------------------ Summary: SocketBindingManager.createMulticast/DatagramSocket(...) variants needed for unbound sockets Key: WFCORE-1293 URL: https://issues.jboss.org/browse/WFCORE-1293 Project: WildFly Core Issue Type: Bug Components: Server Affects Versions: 2.0.5.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Blocker Fix For: 2.0.6.Final In order to modify the SO_REUSEADDR option of a multicast or datagram socket, the socket must be unbound - otherwise the behavior is undefined. See: http://docs.oracle.com/javase/8/docs/api/java/net/DatagramSocket.html#set... To support this (as required for JGroups 3.6.7.Final), SocketBindingManager needs methods to create unbound datagram/multicast sockets. The current methods that accept a SocketAddress throw an ISE when a null address is used. Setting priority to blocker to encourage inclusion into 2.0.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 January 2016