February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-544) Inconsistent handling of system properties.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-544?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-544: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1192467 > Inconsistent handling of system properties. > -------------------------------------------- > > Key: WFCORE-544 > URL: https://issues.jboss.org/browse/WFCORE-544 > Project: WildFly Core > Issue Type: Bug > Reporter: Emmanuel Hugonnet > > Description of problem: > Having a domain with a single server group and two eap hosts (all on localhost), following system property cause server to fail on startup: > <property name="org.jbpm.designer.perspective" value="${org.jbpm.designer.perspective:full}"/> > The problem occurs only in definition with possibility to override default value - <property name="X" value="${Y:default}"/>, where X = Y > Please see the error message in attached server log excerpt. > More interesting is the fact that the issue shows with domain mode only, standalone mode works with properties defined as above. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-544) Inconsistent handling of system properties.

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFCORE-544: ---------------------------------------- Summary: Inconsistent handling of system properties. Key: WFCORE-544 URL: https://issues.jboss.org/browse/WFCORE-544 Project: WildFly Core Issue Type: Bug Reporter: Emmanuel Hugonnet Description of problem: Having a domain with a single server group and two eap hosts (all on localhost), following system property cause server to fail on startup: <property name="org.jbpm.designer.perspective" value="${org.jbpm.designer.perspective:full}"/> The problem occurs only in definition with possibility to override default value - <property name="X" value="${Y:default}"/>, where X = Y Please see the error message in attached server log excerpt. More interesting is the fact that the issue shows with domain mode only, standalone mode works with properties defined as above. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2391) Wildfly caches content in exploded mode, breaking developer productivity

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-2391?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on WFLY-2391: ------------------------------------------- Stuart - is there a command line flag we can set to disable this caching completely when launching from jboss tools ? > Wildfly caches content in exploded mode, breaking developer productivity > ------------------------------------------------------------------------ > > Key: WFLY-2391 > URL: https://issues.jboss.org/browse/WFLY-2391 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.0.0.Beta1 > Environment: MacOSX with JBossTools 4.1.1.Beta1 > Reporter: Xavier Coulon > Assignee: Stuart Douglas > Priority: Critical > Fix For: 8.0.0.CR1 > > Attachments: jboss-as-kitchensink-html5-mobile.war.zip > > > While I was building a sample application with JBoss Tools 4.1.1.beta1 on WildFly 8.0.Beta1, I noticed that after a few minutes (or a few browser requests), the content of my index.html file seemed to be cached by the server, although I used the "exploded content" deployment mode (since I published the content using the WildFly Server Adapter in JBoss Tools). > > I checked the actual content of the index.html in the deployments folder and it contained the latest changes, which means that the JBoss Tools Server Adapter is doing its job well ;-) > I also tried to edit the index.html file directly in the deployments folder, and once again, I got no update in both Chrome and Firefox browsers. > > I checked in the "Network" tab of the browsers and could see that the server response for the index.html page had a "200 OK" status, which means that there's no browser caching involved. > I tried to get the index.html page with cUrl and got the same old version, which definitely excludes a browser caching issue. > At the end of the dat, this means that after a few changes, my browsers keep getting an old version of the deployed resources, which in turns means that I have to stop and restart the server to get the new content, and this is pretty bad in term of dev productivity. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2391) Wildfly caches content in exploded mode, breaking developer productivity

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2391?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-2391: -------------------------------------- I also tested locally, and it worked as expected. > Wildfly caches content in exploded mode, breaking developer productivity > ------------------------------------------------------------------------ > > Key: WFLY-2391 > URL: https://issues.jboss.org/browse/WFLY-2391 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.0.0.Beta1 > Environment: MacOSX with JBossTools 4.1.1.Beta1 > Reporter: Xavier Coulon > Assignee: Stuart Douglas > Priority: Critical > Fix For: 8.0.0.CR1 > > Attachments: jboss-as-kitchensink-html5-mobile.war.zip > > > While I was building a sample application with JBoss Tools 4.1.1.beta1 on WildFly 8.0.Beta1, I noticed that after a few minutes (or a few browser requests), the content of my index.html file seemed to be cached by the server, although I used the "exploded content" deployment mode (since I published the content using the WildFly Server Adapter in JBoss Tools). > > I checked the actual content of the index.html in the deployments folder and it contained the latest changes, which means that the JBoss Tools Server Adapter is doing its job well ;-) > I also tried to edit the index.html file directly in the deployments folder, and once again, I got no update in both Chrome and Firefox browsers. > > I checked in the "Network" tab of the browsers and could see that the server response for the index.html page had a "200 OK" status, which means that there's no browser caching involved. > I tried to get the index.html page with cUrl and got the same old version, which definitely excludes a browser caching issue. > At the end of the dat, this means that after a few changes, my browsers keep getting an old version of the deployed resources, which in turns means that I have to stop and restart the server to get the new content, and this is pretty bad in term of dev productivity. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2391) Wildfly caches content in exploded mode, breaking developer productivity

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/WFLY-2391?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on WFLY-2391: ----------------------------------- I just tested this in JBossTools and it seems to work as [~swd847] says for wf8.2: when using an external firefox, it seems to refresh within the 2 seconds limit. In JBT, using the embedded browser, however, the browser can sometimes not refresh properly or show outdated content when using the 'run on server' action. See https://issues.jboss.org/browse/JBIDE-18685 for our bug on that issue, or the underlying eclipse bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=448933 > Wildfly caches content in exploded mode, breaking developer productivity > ------------------------------------------------------------------------ > > Key: WFLY-2391 > URL: https://issues.jboss.org/browse/WFLY-2391 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.0.0.Beta1 > Environment: MacOSX with JBossTools 4.1.1.Beta1 > Reporter: Xavier Coulon > Assignee: Stuart Douglas > Priority: Critical > Fix For: 8.0.0.CR1 > > Attachments: jboss-as-kitchensink-html5-mobile.war.zip > > > While I was building a sample application with JBoss Tools 4.1.1.beta1 on WildFly 8.0.Beta1, I noticed that after a few minutes (or a few browser requests), the content of my index.html file seemed to be cached by the server, although I used the "exploded content" deployment mode (since I published the content using the WildFly Server Adapter in JBoss Tools). > > I checked the actual content of the index.html in the deployments folder and it contained the latest changes, which means that the JBoss Tools Server Adapter is doing its job well ;-) > I also tried to edit the index.html file directly in the deployments folder, and once again, I got no update in both Chrome and Firefox browsers. > > I checked in the "Network" tab of the browsers and could see that the server response for the index.html page had a "200 OK" status, which means that there's no browser caching involved. > I tried to get the index.html page with cUrl and got the same old version, which definitely excludes a browser caching issue. > At the end of the dat, this means that after a few changes, my browsers keep getting an old version of the deployed resources, which in turns means that I have to stop and restart the server to get the new content, and this is pretty bad in term of dev productivity. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4280) Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed

by Juan Hernández (JIRA)

[ https://issues.jboss.org/browse/WFLY-4280?page=com.atlassian.jira.plugin.... ] Juan Hernández commented on WFLY-4280: -------------------------------------- Note that in the attached binary .jar file I replaced {{@Valid}} with {{@NotNull}}, the result is the same. > Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed > --------------------------------------------------------------------------------------- > > Key: WFLY-4280 > URL: https://issues.jboss.org/browse/WFLY-4280 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final, 8.2.0.Final > Environment: Fedora 21, OpenJDK 1.8.0_25-b18. > Reporter: Juan Hernández > Assignee: Scott Marlow > Attachments: hv-861-1.0-SNAPSHOT.jar, hv-861.tar.gz > > > The version of Hibernate Validator included in WildFly 8.1 and 8.2 throws an {{ArrayIndexOutOfBounds}} exception when deploying some applications. This is already reported in the Hibernate Validator JIRA: > https://hibernate.atlassian.net/browse/HV-861 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4280) Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed

by Juan Hernández (JIRA)

[ https://issues.jboss.org/browse/WFLY-4280?page=com.atlassian.jira.plugin.... ] Juan Hernández updated WFLY-4280: --------------------------------- Attachment: hv-861-1.0-SNAPSHOT.jar The binary .jar file, generated with the compiler from the Oracle JDK 7. > Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed > --------------------------------------------------------------------------------------- > > Key: WFLY-4280 > URL: https://issues.jboss.org/browse/WFLY-4280 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final, 8.2.0.Final > Environment: Fedora 21, OpenJDK 1.8.0_25-b18. > Reporter: Juan Hernández > Assignee: Scott Marlow > Attachments: hv-861-1.0-SNAPSHOT.jar, hv-861.tar.gz > > > The version of Hibernate Validator included in WildFly 8.1 and 8.2 throws an {{ArrayIndexOutOfBounds}} exception when deploying some applications. This is already reported in the Hibernate Validator JIRA: > https://hibernate.atlassian.net/browse/HV-861 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4280) Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed

by Juan Hernández (JIRA)

[ https://issues.jboss.org/browse/WFLY-4280?page=com.atlassian.jira.plugin.... ] Juan Hernández commented on WFLY-4280: -------------------------------------- This is what I'm using: {noformat} # wget http://download.jboss.org/wildfly/8.2.0.Final/wildfly-8.2.0.Final.zi # md5sum wildfly-8.2.0.Final.zip 86a51782581b90db44958a0ee7002c14 wildfly-8.2.0.Final.zip {noformat} The result is the same. > Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed > --------------------------------------------------------------------------------------- > > Key: WFLY-4280 > URL: https://issues.jboss.org/browse/WFLY-4280 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final, 8.2.0.Final > Environment: Fedora 21, OpenJDK 1.8.0_25-b18. > Reporter: Juan Hernández > Assignee: Scott Marlow > Attachments: hv-861.tar.gz > > > The version of Hibernate Validator included in WildFly 8.1 and 8.2 throws an {{ArrayIndexOutOfBounds}} exception when deploying some applications. This is already reported in the Hibernate Validator JIRA: > https://hibernate.atlassian.net/browse/HV-861 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-258) DigestAuthenticator generates duplicate nonces

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-258?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-258: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1188744|https://bugzilla.redhat.com/show_bug.cgi?id=1188744] from POST to MODIFIED > DigestAuthenticator generates duplicate nonces > ---------------------------------------------- > > Key: JBWEB-258 > URL: https://issues.jboss.org/browse/JBWEB-258 > Project: JBoss Web > Issue Type: Bug > Affects Versions: JBossWeb-2.1.12.GA, JBossWeb-7.0.16.GA, JBossWeb-7.2.0.Alpha3 > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > Attachments: 21x.diff, 70x.diff, 72x.diff > > > DigestAuthenticator currently generates nonces as a hash of the client's remote ip, the current time at generation time, and an internal server key. With high concurrent load in a scenario where many clients show a single ip (such as behind a loadbalancer/proxy), then it is very easy for DigestAuthenticator to give out duplicate nonces when they are generated at the same time. > This then leads to authentication failues as counts for the duplicate nonces get out of whack. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4280) Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed

by Juan Hernández (JIRA)

[ https://issues.jboss.org/browse/WFLY-4280?page=com.atlassian.jira.plugin.... ] Juan Hernández commented on WFLY-4280: -------------------------------------- Forgot to say that I'm not using a modified WildFly, just what is available in the web site. I downloaded it some time ago, will download it again now, just in case. > Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed > --------------------------------------------------------------------------------------- > > Key: WFLY-4280 > URL: https://issues.jboss.org/browse/WFLY-4280 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final, 8.2.0.Final > Environment: Fedora 21, OpenJDK 1.8.0_25-b18. > Reporter: Juan Hernández > Assignee: Scott Marlow > Attachments: hv-861.tar.gz > > > The version of Hibernate Validator included in WildFly 8.1 and 8.2 throws an {{ArrayIndexOutOfBounds}} exception when deploying some applications. This is already reported in the Hibernate Validator JIRA: > https://hibernate.atlassian.net/browse/HV-861 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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