December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1066) Parametr -Djboss.domain.log.dir does not have effect on HP-UX when directory does not exist

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1066?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-1066: ----------------------------------------- Assignee: ehsavoie Hugonnet (was: Tomaz Cerar) > Parametr -Djboss.domain.log.dir does not have effect on HP-UX when directory does not exist > ------------------------------------------------------------------------------------------- > > Key: WFCORE-1066 > URL: https://issues.jboss.org/browse/WFCORE-1066 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.0.0.CR7 > Reporter: Ondřej Chaloupka > Assignee: ehsavoie Hugonnet > Priority: Minor > > If you run container in domain mode with explicitly specified log directory (by parameter {{jboss.domain.log.dir}}) then such settings does not take any effect if directory does not exist before server startup. This issue can be seen only on HP-UX (hpux jdk). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5716) Wrong handling of request context for remote EJB calls

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-5716?page=com.atlassian.jira.plugin.... ] Martin Kouba updated WFLY-5716: ------------------------------- Fix Version/s: 10.0.0.CR5 > Wrong handling of request context for remote EJB calls > ------------------------------------------------------ > > Key: WFLY-5716 > URL: https://issues.jboss.org/browse/WFLY-5716 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, EJB > Affects Versions: 9.0.0.Final, 10.0.0.CR4 > Reporter: Ste Gr > Assignee: Martin Kouba > Fix For: 10.0.0.CR5 > > Attachments: wfly5716.zip > > > Two applications deployed to Wildfly. The first one provides a singleton remote ejb which uses request scoped beans (in this case a RESOURCE_LOCAL entity manager manged by a CDI producer/disposer, but +all+ request scoped beans are affected). The second application uses that EJB to get some data only accessible by the first application. > A request is made to the second app from a browser. The app will get the remote EJB and invokes two methods on it. The first method produces the entity manager, accesses the database and returns the result. The entity manager will be disposed again. The second method won't produce a new entity manager but tries to re-use the one from the previous invokation. This fails as the entity manager was disposed. > If the same use-case is made using the first app everythings works as desired. But it doesn't look right (or the request context is joined because it is the same application). It produces the the entity manager on the first invocation and closes it as soon as the whole request made from the browser is completed. Thats why the second invokation has a valid entity manager to work with. > I don't know the spec but: > - either the first EJB invokation from second app to first app is not allowed to dispose the request context (all the request scoped beans) > - or each invokation must get its own request context (entity manager must be produced and disposed again). > I've made a [stackoverflow thread|http://stackoverflow.com/q/33826720/1741604] which shows some code examples. > (JBoss AS 7.1.3.Final is also affected but it is not available in 'affected version/s') -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5814) Upgrade Weld to 2.3.2.Final

by Martin Kouba (JIRA)

Martin Kouba created WFLY-5814: ---------------------------------- Summary: Upgrade Weld to 2.3.2.Final Key: WFLY-5814 URL: https://issues.jboss.org/browse/WFLY-5814 Project: WildFly Issue Type: Component Upgrade Components: CDI / Weld Reporter: Martin Kouba Assignee: Martin Kouba Fix For: 10.0.0.CR5 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5813) Quick redeploy vulnerable to CacheRegistry entry loss

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-5813: ---------------------------------- Summary: Quick redeploy vulnerable to CacheRegistry entry loss Key: WFLY-5813 URL: https://issues.jboss.org/browse/WFLY-5813 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR4 Reporter: Paul Ferraro Assignee: Paul Ferraro On deploy, CacheRegistry adds its local entry to the cache, and on undeploy removes it entry. However, we use a topology change listener to remove entries for crashed members (since these nodes will not have removed their local entry). However, since the listener is triggered asynchronously, it is possible that the topology change fired in response to an undeploy execute *after* the redeployed CacheRegistry starts - which would cause erroneous removal of the local entry that was added. This manifests itself as an intermittent failure of the RegistryTestCase as seen in this PR: https://github.com/wildfly/wildfly/pull/8465 Not surprisingly, this issue only surfaces in the windoze runs, which, according to [~ctomc], execute faster than the linux runs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1196) Read resource of deployment with faulty datasource fails

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1196?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-5807 to WFCORE-1196: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1196 (was: WFLY-5807) Component/s: Domain Management (was: Domain Management) Affects Version/s: 2.0.4.Final (was: 10.0.0.CR4) > Read resource of deployment with faulty datasource fails > -------------------------------------------------------- > > Key: WFCORE-1196 > URL: https://issues.jboss.org/browse/WFCORE-1196 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.4.Final > Reporter: Harald Pehl > Assignee: Tomaz Cerar > > For the setup see HAL-1006. Reading the deployments of a server which contains a deployment with a faulty datasource, yields an undefined result: > {code} > /host=master/server=server-one:read-children-resources(child-type=deployment,recursive=true,include-runtime=true) > { > "outcome" => "success", > "result" => undefined, > "failure-description" => undefined > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5807) Read resource of deployment with faulty datasource fails

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5807?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-5807: --------------------------------- Assignee: Tomaz Cerar (was: Brian Stansberry) > Read resource of deployment with faulty datasource fails > -------------------------------------------------------- > > Key: WFLY-5807 > URL: https://issues.jboss.org/browse/WFLY-5807 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 10.0.0.CR4 > Reporter: Harald Pehl > Assignee: Tomaz Cerar > > For the setup see HAL-1006. Reading the deployments of a server which contains a deployment with a faulty datasource, yields an undefined result: > {code} > /host=master/server=server-one:read-children-resources(child-type=deployment,recursive=true,include-runtime=true) > { > "outcome" => "success", > "result" => undefined, > "failure-description" => undefined > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5811) Clustering performance regression in scenarios with ASYNC cache used

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5811?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-5811. ------------------------------ Resolution: Rejected It is easy to misinterpret ASYNC performance results. These graphs do not indicate a performance regression. On the contrary, the DIST_ASYNC ejbremote stress tests show equivalent performance, while the DIST_ASYNC session stress test indicate a welcome, but expected performance improvement. > Clustering performance regression in scenarios with ASYNC cache used > -------------------------------------------------------------------- > > Key: WFLY-5811 > URL: https://issues.jboss.org/browse/WFLY-5811 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Michal Vinkler > Assignee: Paul Ferraro > > Our clustering write-heavy stress tests show a performance drop of 7.0.0.ER2 bits compared to 6.4.0 bits, when using ASYNC cache. > Compare these results: > stress-ejbremote-dist-async > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > stress-ejbremote-repl-async > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > stress-ejbservlet-repl-async > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > stress-session-repl-async > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > stress-session-dist-async > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > Also, load scenarios, which use a stable load of 4000 sessions are affected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5683) Default jgroups thread pool keep-alive times are much too small

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5683?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-5683. -------------------------------- Verified downstream. > Default jgroups thread pool keep-alive times are much too small > --------------------------------------------------------------- > > Key: WFLY-5683 > URL: https://issues.jboss.org/browse/WFLY-5683 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Labels: clustering_performance > Fix For: 10.0.0.CR5 > > > This looks like a unit problem. e.g. 60 sec instead of 60 msec. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1195) Name for wildcard resources should be configurable in parser

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-1195: ----------------------------------- Summary: Name for wildcard resources should be configurable in parser Key: WFCORE-1195 URL: https://issues.jboss.org/browse/WFCORE-1195 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Affects Versions: 2.0.4.Final Reporter: Tomaz Cerar Assignee: Tomaz Cerar Currently attribute do distinguish between resource names is always "name" this should be configurable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5698) Remove duplicate keys from clustering LocalDescriptions.properties

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5698?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-5698. -------------------------------- > Remove duplicate keys from clustering LocalDescriptions.properties > ------------------------------------------------------------------ > > Key: WFLY-5698 > URL: https://issues.jboss.org/browse/WFLY-5698 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > Fix For: 10.0.0.CR5 > > > Violates properties file structure, adds unnecessar translations, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2015