January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4254) Symbolic links within web applications do not work

by Kris Iyer (JIRA)

[ https://issues.jboss.org/browse/WFLY-4254?page=com.atlassian.jira.plugin.... ] Kris Iyer updated WFLY-4254: ---------------------------- Description: Symbolic Linking under exploded web-apps to files and/or directories outside the web-app do not work. Here is what I tried under an exploded war: <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" version="8.0"> <symbolic-linking-enabled>true</symbolic-linking-enabled> </jboss-web> Does not follow links and results in a 404. HTTP/?.? 404 Not Found Connection: keep-alive X-Powered-By: Undertow/1 Server: WildFly/8 was: symbolic Linking under exploded web-apps to files and/or directories outside the web-app do not work. Here is what I tried under an exploded war: <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" version="8.0"> <symbolic-linking-enabled>true</symbolic-linking-enabled> </jboss-web> Does not follow links and results in a 404. HTTP/?.? 404 Not Found Connection: keep-alive X-Powered-By: Undertow/1 Server: WildFly/8 > Symbolic links within web applications do not work > -------------------------------------------------- > > Key: WFLY-4254 > URL: https://issues.jboss.org/browse/WFLY-4254 > Project: WildFly > Issue Type: Feature Request > Components: Web (JBoss Web), Web (Undertow) > Affects Versions: 8.2.0.Final > Reporter: Kris Iyer > Assignee: Remy Maucherat > > Symbolic Linking under exploded web-apps to files and/or directories outside the web-app do not work. > Here is what I tried under an exploded war: > <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" > version="8.0"> > <symbolic-linking-enabled>true</symbolic-linking-enabled> > </jboss-web> > Does not follow links and results in a 404. > HTTP/?.? 404 Not Found > Connection: keep-alive > X-Powered-By: Undertow/1 > Server: WildFly/8 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4253) CredentialIdentityFactory.NULL_IDENTITY does not get initialized and causes NullPointerExceptions

by Rostyslav Smirnov (JIRA)

Rostyslav Smirnov created WFLY-4253: --------------------------------------- Summary: CredentialIdentityFactory.NULL_IDENTITY does not get initialized and causes NullPointerExceptions Key: WFLY-4253 URL: https://issues.jboss.org/browse/WFLY-4253 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 8.2.0.Final Environment: Java 1.8.0_25 Reporter: Rostyslav Smirnov Assignee: Darran Lofthouse org.jboss.security.identity.extensions.CredentialIdentityFactory.NULL_IDENTITY does not get initialized to an empty identity due to initialization method returning a reference to NULL_IDENTITY, which has not initialized yet, resulting in null pointer. This causes NullPointerException in org.jboss.security.SecurityContextUtil.clearIdentities() and org.jboss.security.SecurityContextUtil.getIdentities() methods. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-128) RFC 5843 additional hash types for Digest authentication, applied to SASL

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-128?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-128. ----------------------------- Fix Version/s: 1.0.0.Alpha1 (was: 1.0.0.Beta1) Resolution: Done This was merged on Dec 18 (fc3f9d8b00c9512f26). > RFC 5843 additional hash types for Digest authentication, applied to SASL > ------------------------------------------------------------------------- > > Key: ELY-128 > URL: https://issues.jboss.org/browse/ELY-128 > Project: WildFly Elytron > Issue Type: Enhancement > Components: SASL > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.0.0.Alpha1 > > > http://tools.ietf.org/html/rfc5843 specifies three additional SHA-based digest schemes. Apply these to SASL. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4252) Pagination don't work on the Data Source Metrics web console.

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-4252?page=com.atlassian.jira.plugin.... ] Jesper Pedersen reassigned WFLY-4252: ------------------------------------- Assignee: Heiko Braun (was: Jason Greene) Component/s: Web Console > Pagination don't work on the Data Source Metrics web console. > ------------------------------------------------------------- > > Key: WFLY-4252 > URL: https://issues.jboss.org/browse/WFLY-4252 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.2.0.Final > Environment: RedHat 6.4, WildFly 8.2.Final, Java 1.7.0_65, Firefox 34.0 and Google Chrome 39.0.2171.95 > Reporter: Kleber Rocha > Assignee: Heiko Braun > Attachments: wildfly_8.1.png, wildfly_8.2.png > > > On the WildFly Tweek Management, when you go to the page "Data Source Metrics", the table where show list of data sources, do not display pagination, like the page "JDBC Datasources", this is a problem, because I have 8 data sources, and I only can see 5 of these data sources. I cannot view metrics of the others data sources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4252) Pagination don't work on the Data Source Metrics web console.

by Kleber Rocha (JIRA)

[ https://issues.jboss.org/browse/WFLY-4252?page=com.atlassian.jira.plugin.... ] Kleber Rocha updated WFLY-4252: ------------------------------- Attachment: wildfly_8.2.png Screenshot on WildFly 8.2 where the pagination do not works. > Pagination don't work on the Data Source Metrics web console. > ------------------------------------------------------------- > > Key: WFLY-4252 > URL: https://issues.jboss.org/browse/WFLY-4252 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.2.0.Final > Environment: RedHat 6.4, WildFly 8.2.Final, Java 1.7.0_65, Firefox 34.0 and Google Chrome 39.0.2171.95 > Reporter: Kleber Rocha > Assignee: Heiko Braun > Attachments: wildfly_8.1.png, wildfly_8.2.png > > > On the WildFly Tweek Management, when you go to the page "Data Source Metrics", the table where show list of data sources, do not display pagination, like the page "JDBC Datasources", this is a problem, because I have 8 data sources, and I only can see 5 of these data sources. I cannot view metrics of the others data sources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4252) Pagination don't work on the Data Source Metrics web console.

by Kleber Rocha (JIRA)

[ https://issues.jboss.org/browse/WFLY-4252?page=com.atlassian.jira.plugin.... ] Kleber Rocha updated WFLY-4252: ------------------------------- Attachment: wildfly_8.1.png Screenshot on WildFly 8.1 where the pagination works. > Pagination don't work on the Data Source Metrics web console. > ------------------------------------------------------------- > > Key: WFLY-4252 > URL: https://issues.jboss.org/browse/WFLY-4252 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Environment: RedHat 6.4, WildFly 8.2.Final, Java 1.7.0_65, Firefox 34.0 and Google Chrome 39.0.2171.95 > Reporter: Kleber Rocha > Assignee: Jason Greene > Attachments: wildfly_8.1.png > > > On the WildFly Tweek Management, when you go to the page "Data Source Metrics", the table where show list of data sources, do not display pagination, like the page "JDBC Datasources", this is a problem, because I have 8 data sources, and I only can see 5 of these data sources. I cannot view metrics of the others data sources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4252) Pagination don't work on the Data Source Metrics web console.

by Kleber Rocha (JIRA)

Kleber Rocha created WFLY-4252: ---------------------------------- Summary: Pagination don't work on the Data Source Metrics web console. Key: WFLY-4252 URL: https://issues.jboss.org/browse/WFLY-4252 Project: WildFly Issue Type: Bug Affects Versions: 8.2.0.Final Environment: RedHat 6.4, WildFly 8.2.Final, Java 1.7.0_65, Firefox 34.0 and Google Chrome 39.0.2171.95 Reporter: Kleber Rocha Assignee: Jason Greene On the WildFly Tweek Management, when you go to the page "Data Source Metrics", the table where show list of data sources, do not display pagination, like the page "JDBC Datasources", this is a problem, because I have 8 data sources, and I only can see 5 of these data sources. I cannot view metrics of the others data sources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-297) HC should remember the 'run' state of the server instances after crash or shutdown

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-297?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-297: ----------------------------------------- Unfortunately the proposed approach will make starting/stopping servers unavailable to the Operator role when RBAC is enabled. This is because these ops will now need to modify persistent configuration (the auto-start attribute) and an Operator will not be allowed to do that. Even if the 'set-auto-start-on-start-stop' flag were false and the actual modification is unnecessary, the metadata describing these ops will now need to describe them as r-w, with the result that the data we provide to tools (i.e. web console) stating whether the op is available to a role will say the ops are not available to Operator. With the likely effect that the tools will no longer offer them. > HC should remember the 'run' state of the server instances after crash or shutdown > ---------------------------------------------------------------------------------- > > Key: WFCORE-297 > URL: https://issues.jboss.org/browse/WFCORE-297 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Wolf-Dieter Fink > Assignee: Emmanuel Hugonnet > Labels: EAP, todo > > The host controller should save which server is currently up and running. This would allow the host controller to bring up all previously running instances on a restart. > The idea is to support the same behavior that other application server (i.e WebLogic) supports. > If a server is started or stopped during the lifetime of the DC/HC it should be in the same state after shutdown the DC/HC or a system crash. > This can be achieved by an optional flag 'set-auto-start-on-start-stop' where the default is false which is the current behaviour. > If set to true, a start of the server instance will set auto-start=true and a stop auto-start=false. > If the server should not be started after a crash for any reason, this can be simple done by setting auto-start=false within the configuration, after starting the server the flag will be set b/c of the 'set-auto-start-on-start-stop' flag. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3966) Allow soapFaults to be returned for HTTP_BAD_REQUEST are per SOAP 1.2 spec

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3966?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3966: ----------------------------------------------- Jan Blizňák <jbliznak(a)redhat.com> changed the Status of [bug 1151526|https://bugzilla.redhat.com/show_bug.cgi?id=1151526] from ON_QA to ASSIGNED > Allow soapFaults to be returned for HTTP_BAD_REQUEST are per SOAP 1.2 spec > -------------------------------------------------------------------------- > > Key: WFLY-3966 > URL: https://issues.jboss.org/browse/WFLY-3966 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Alpha1 > Reporter: Mustafa Musaji > Assignee: Bartosz Baranowski > Attachments: SAAJ-74.patch > > > SOAP 1.2 spec says that HTTP 400 should return a soapFault error. At the moment the code only returns SoapFault for HTTP 500 which is wrong. > The issue is recorded in the SAAJ JIRA: https://java.net/jira/browse/SAAJ-74 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4251) @DependsOn not adherent to Java EE 7 spec

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/WFLY-4251?page=com.atlassian.jira.plugin.... ] Matteo Mortari commented on WFLY-4251: -------------------------------------- Thank you very much for your prompt feedback, and accurate answers! Have a nice day, MM > @DependsOn not adherent to Java EE 7 spec > ----------------------------------------- > > Key: WFLY-4251 > URL: https://issues.jboss.org/browse/WFLY-4251 > Project: WildFly > Issue Type: Bug > Components: EE, EJB > Affects Versions: 8.2.0.Final > Reporter: Matteo Mortari > Priority: Minor > Attachments: 20150114.wildfly82_dependson.zip > > > *Premise*: actually, I'm leveraging this misalignment for implementing a functionality; however, I don't believe is correct behavior accordingly to Java EE 7 specs, hence reporting it. > h5. Executive summary > With reference to attached reproducer, and example scenario below; the {{@DependsOn}} annotation on wildfly 8.2.0.Final works also against Stateless EJB, but accordingly to Java EE 7 specs {{@DependsOn}} annotation: > {quote} > Used to express an initialization dependency between singleton components. > {quote} > h5. Detailed description > Assume you have a {{@Singleton}} and while on {{@PreDestroy}} you need to persist some entities, which are normally done through a Stateless EJB serving as a "Controller"/"DAO", example: > {code:java} > @Singleton > @Startup > //@DependsOn(value={"AStatelessEJB"}) > public class SingletonEJB { > private static final Logger LOG = LoggerFactory.getLogger(SingletonEJB.class); > > @EJB > private AStatelessEJB sl; > > @PostConstruct > public void init() { > LOG.info("SingletonEJB is here."); > } > > @PreDestroy > public void shutdown() { > LOG.info("SingletonEJB is about to shutdown..."); > sl.dummyPersist(); // line #30 > } > } > {code} > with the {{@DependsOn}} annotation currently commented, and where: > {code:java} > @Stateless(name="AStatelessEJB", mappedName="AStatelessEJB") > public class AStatelessEJB { > private static final Logger LOG = LoggerFactory.getLogger(AStatelessEJB.class); > > public void dummyPersist() { > LOG.info("called dummyPersist()."); > } > } > {code} > just for simulating a "controller"/"DAO" example as a Stateless EJB. > Invoking wildfly shutdown will produce the following stacktrace: > {noformat} > 19:26:34,570 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 98671ms - Started 347 of 399 services (107 services are lazy, passive or on-demand) > 19:26:45,136 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017535: Unregistered web context: /wildfly82-dependson > ... > 19:26:45,213 INFO [com.acme.wildfly82_dependson.SingletonEJB] (ServerService Thread Pool -- 24) SingletonEJB is about to shutdown... > ... > 19:26:45,213 ERROR [org.jboss.as.ejb3.invocation] (ServerService Thread Pool -- 24) JBAS014134: EJB Invocation failed on component AStatelessEJB for method public void com.acme.wildfly82_dependson.AStatelessEJB.dummyPersist(): org.jboss.as.ejb3.component.EJBComponentUnavailableException: > JBAS014559: Invocation cannot proceed as component is shutting down > ... > at com.acme.wildfly82_dependson.AStatelessEJB$$$view2.dummyPersist(Unknown Source) [classes:] > at com.acme.wildfly82_dependson.SingletonEJB.shutdown(SingletonEJB.java:30) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_05] > {noformat} > However, with the annotation un-commented and active: > {noformat} > 19:21:44,713 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 109462ms - Started 347 of 399 services (107 services are lazy, passive or on-demand) > ... > 19:22:17,908 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017535: Unregistered web context: /wildfly82-dependson > 19:22:17,971 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017532: Host default-host stopping > ... > 19:22:18,017 INFO [com.acme.wildfly82_dependson.SingletonEJB] (ServerService Thread Pool -- 68) SingletonEJB is about to shutdown... > 19:22:18,033 INFO [com.acme.wildfly82_dependson.AStatelessEJB] (ServerService Thread Pool -- 68) called dummyPersist(). > ... > 19:22:18,236 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment wildfly82-dependson.war (runtime-name: wildfly82-dependson.war) in 334ms > {noformat} > But I'm puzzled because as stated above the Java EE specs javadoc describe the {{@DependsOn}} annotation as _Used to express an initialization dependency between singleton components._ , therefore although I'm happy it actually works, I'm puzzled about the misalignments, hence reporting it. > h5. Conclusions > I have the following questions, please? > * Can you clarify if this is the correct or intended behavior of the annotation on Wildfly? > * In the case the implementation of this annotation will be put in future release to adhere strictly to the Java EE 7 specs, what should be the correct way to implement the above scenario, in an alternative way? > (If this instead will not be modified, in other words the Wildfly implementation of the annotation will be more wide than the JavaEE 7 specs, then I got nothing to do as the application is already working and sorry for this report, but I thought worthy to mention). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 2015