December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3414) Symbolic links inside deployed ear/war are not followed by web server

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/AS7-3414?page=com.atlassian.jira.plugin.s... ] Jean-Frederic Clere commented on AS7-3414: ------------------------------------------ metadata 7.0.7.Final is available. > Symbolic links inside deployed ear/war are not followed by web server > --------------------------------------------------------------------- > > Key: AS7-3414 > URL: https://issues.jboss.org/browse/AS7-3414 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.2.0.Alpha1 > Environment: Fedora 16 > Reporter: Ronen Angluster > Assignee: Navin Surtani > Fix For: No Release > > > when creating a symbolic link inside a deployed ear/war the symbolic link's target is not followed when > accessing it from a web browser > i.e. > in jboss-as/standalone/deplyoment/somedomain.ear/files we created a symbolic link named "version.js" > which points to /usr/share/something/version.js > the target file (/usr/share/...) is accessible by all (chmod'd to 777) and is readable by the jboss-as user which runs > the Jboss application server. > when accessing http://domain:8080/something/files/version.js we get an 404 error, seems like the file is not found by > the server. > when placing the file instead of symbolic link, the file is accessible and all is well -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1554) FD: monitor stops after reconnecting a channel

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1554?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1554: --------------------------- Fix Version/s: 3.2.5 > FD: monitor stops after reconnecting a channel > ---------------------------------------------- > > Key: JGRP-1554 > URL: https://issues.jboss.org/browse/JGRP-1554 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.2.5, 3.3 > > > When reconnecting a channel, the monitor task on the FD's task is not running. The test is FdMonitorTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6154) Expression support inconsistency

by Heiko Braun (JIRA)

Heiko Braun created AS7-6154: -------------------------------- Summary: Expression support inconsistency Key: AS7-6154 URL: https://issues.jboss.org/browse/AS7-6154 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.2.0.CR1 Although some subsystem declare support for expression on certain attributes, they actually don't support it. As en example see datasources > pool > max-pool-size. The DMR description says it supports expressions on this attribute: {noformat} "max-pool-size" => { "type" => INT, "description" => "The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool", "expressions-allowed" => true, "nillable" => true, "default" => 20, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {noformat} But then writing an expression value yields an exception {noformat} Request [ERROR] { [ERROR] "operation" => "composite", [ERROR] "address" => [], [ERROR] "steps" => [{ [ERROR] "address" => [ [ERROR] ("profile" => "full"), [ERROR] ("subsystem" => "datasources"), [ERROR] ("data-source" => "ExampleDS") [ERROR] ], [ERROR] "operation" => "write-attribute", [ERROR] "name" => "max-pool-size", [ERROR] "value" => expression "${pool:15}" [ERROR] }] [ERROR] } {noformat} {noformat} 08:48:23,965 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 5) JBAS014616: Operation ("write-attribute") failed - address: ([ ("subsystem" => "datasources"), ("data-source" => "ExampleDS") ]) - failure description: "JBAS014688: Wrong type for value. Expected [INT] but was EXPRESSION" {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6154) Expression support inconsistency

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6154?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6154: ----------------------------- Description: Although some subsystem declare support for expression on certain attributes, they actually don't support it. As en example see datasources > pool > max-pool-size. The DMR description says it supports expressions on this attribute: {noformat} "max-pool-size" => { "type" => INT, "description" => "The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool", "expressions-allowed" => true, "nillable" => true, "default" => 20, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {noformat} But then writing an expression value yields an exception {noformat} Request [ERROR] { [ERROR] "operation" => "composite", [ERROR] "address" => [], [ERROR] "steps" => [{ [ERROR] "address" => [ [ERROR] ("profile" => "full"), [ERROR] ("subsystem" => "datasources"), [ERROR] ("data-source" => "ExampleDS") [ERROR] ], [ERROR] "operation" => "write-attribute", [ERROR] "name" => "max-pool-size", [ERROR] "value" => expression "${pool:15}" [ERROR] }] [ERROR] } {noformat} {noformat} 08:48:23,965 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 5) JBAS014616: Operation ("write-attribute") failed - address: ([ ("subsystem" => "datasources"), ("data-source" => "ExampleDS") ]) - failure description: "JBAS014688: Wrong type for value. Expected [INT] but was EXPRESSION" {noformat} was: Although some subsystem declare support for expression on certain attributes, they actually don't support it. As en example see datasources > pool > max-pool-size. The DMR description says it supports expressions on this attribute: {noformat} "max-pool-size" => { "type" => INT, "description" => "The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool", "expressions-allowed" => true, "nillable" => true, "default" => 20, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {noformat} But then writing an expression value yields an exception {noformat} Request [ERROR] { [ERROR] "operation" => "composite", [ERROR] "address" => [], [ERROR] "steps" => [{ [ERROR] "address" => [ [ERROR] ("profile" => "full"), [ERROR] ("subsystem" => "datasources"), [ERROR] ("data-source" => "ExampleDS") [ERROR] ], [ERROR] "operation" => "write-attribute", [ERROR] "name" => "max-pool-size", [ERROR] "value" => expression "${pool:15}" [ERROR] }] [ERROR] } {noformat} {noformat} 08:48:23,965 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 5) JBAS014616: Operation ("write-attribute") failed - address: ([ ("subsystem" => "datasources"), ("data-source" => "ExampleDS") ]) - failure description: "JBAS014688: Wrong type for value. Expected [INT] but was EXPRESSION" {noformat} > Expression support inconsistency > -------------------------------- > > Key: AS7-6154 > URL: https://issues.jboss.org/browse/AS7-6154 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 7.2.0.CR1 > > > Although some subsystem declare support for expression on certain attributes, they actually don't support it. > As en example see datasources > pool > max-pool-size. > The DMR description says it supports expressions on this attribute: > {noformat} > "max-pool-size" => { > "type" => INT, > "description" => "The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool", > "expressions-allowed" => true, > "nillable" => true, > "default" => 20, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > {noformat} > But then writing an expression value yields an exception > {noformat} > Request > [ERROR] { > [ERROR] "operation" => "composite", > [ERROR] "address" => [], > [ERROR] "steps" => [{ > [ERROR] "address" => [ > [ERROR] ("profile" => "full"), > [ERROR] ("subsystem" => "datasources"), > [ERROR] ("data-source" => "ExampleDS") > [ERROR] ], > [ERROR] "operation" => "write-attribute", > [ERROR] "name" => "max-pool-size", > [ERROR] "value" => expression "${pool:15}" > [ERROR] }] > [ERROR] } > {noformat} > {noformat} > 08:48:23,965 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 5) JBAS014616: Operation ("write-attribute") failed - address: ([ > ("subsystem" => "datasources"), > ("data-source" => "ExampleDS") > ]) - failure description: "JBAS014688: Wrong type for value. Expected [INT] but was EXPRESSION" > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6154) Inconsistent expression support

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6154?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6154: ----------------------------- Summary: Inconsistent expression support (was: Expression support inconsistency) > Inconsistent expression support > ------------------------------- > > Key: AS7-6154 > URL: https://issues.jboss.org/browse/AS7-6154 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 7.2.0.CR1 > > > Although some subsystem declare support for expression on certain attributes, they actually don't support it. > As en example see datasources > pool > max-pool-size. > The DMR description says it supports expressions on this attribute: > {noformat} > "max-pool-size" => { > "type" => INT, > "description" => "The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool", > "expressions-allowed" => true, > "nillable" => true, > "default" => 20, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > {noformat} > But then writing an expression value yields an exception > {noformat} > Request > [ERROR] { > [ERROR] "operation" => "composite", > [ERROR] "address" => [], > [ERROR] "steps" => [{ > [ERROR] "address" => [ > [ERROR] ("profile" => "full"), > [ERROR] ("subsystem" => "datasources"), > [ERROR] ("data-source" => "ExampleDS") > [ERROR] ], > [ERROR] "operation" => "write-attribute", > [ERROR] "name" => "max-pool-size", > [ERROR] "value" => expression "${pool:15}" > [ERROR] }] > [ERROR] } > {noformat} > {noformat} > 08:48:23,965 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 5) JBAS014616: Operation ("write-attribute") failed - address: ([ > ("subsystem" => "datasources"), > ("data-source" => "ExampleDS") > ]) - failure description: "JBAS014688: Wrong type for value. Expected [INT] but was EXPRESSION" > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1554) FD: monitor stops after reconnecting a channel

by Bela Ban (JIRA)

Bela Ban created JGRP-1554: ------------------------------ Summary: FD: monitor stops after reconnecting a channel Key: JGRP-1554 URL: https://issues.jboss.org/browse/JGRP-1554 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.3 When reconnecting a channel, the monitor task on the FD's task is not running. The test is FdMonitorTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6153) Fix styles for pages

by Heiko Braun (JIRA)

Heiko Braun created AS7-6153: -------------------------------- Summary: Fix styles for pages Key: AS7-6153 URL: https://issues.jboss.org/browse/AS7-6153 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 see core > logging > handler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6100) Support expressions for non-string attributes

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6100?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6100: ----------------------------- Summary: Support expressions for non-string attributes (was: Support expression for boolean attributes) Description: boolean attributes and numeric values are currently not supported due to the nature of their input type (was: it currently uses checkbox input types) > Support expressions for non-string attributes > --------------------------------------------- > > Key: AS7-6100 > URL: https://issues.jboss.org/browse/AS7-6100 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.2.0.CR1 > > > boolean attributes and numeric values are currently not supported due to the nature of their input type -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6100) Support expression for boolean attributes

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6100?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6100: ----------------------------- Description: it currently uses checkbox input types (was: it currently uses checkbox inout types) > Support expression for boolean attributes > ----------------------------------------- > > Key: AS7-6100 > URL: https://issues.jboss.org/browse/AS7-6100 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.2.0.CR1 > > > it currently uses checkbox input types -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6134) Problem reassigning server to different group

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6134: ----------------------------- Issue Type: Bug (was: Feature Request) > Problem reassigning server to different group > --------------------------------------------- > > Key: AS7-6134 > URL: https://issues.jboss.org/browse/AS7-6134 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Emanuel Muckenhuber > Fix For: 7.2.0.CR1 > > > I cannot reassign a (stopped) server to a different group if the domain has two members -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 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 December 2012