November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-343) lower messaging's min-large-message-size value in standalone-full.xml

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-343?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-343: ------------------------------ Fix Version/s: 9.0.0.Beta1 (was: 8.2.0.Final) > lower messaging's min-large-message-size value in standalone-full.xml > --------------------------------------------------------------------- > > Key: WFLY-343 > URL: https://issues.jboss.org/browse/WFLY-343 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 9.0.0.Beta1 > > > AS7's messaging subsystem defines 2 attributes: > journal-file-size => 10MiB > min-large-message-size => 100KiB > However, for startup performance issue, the standalone-full.xml sets the journal-file-size at 1OOKiB. This leads to issues since it's the same value than the min-large-message-size. > If we want to keep a low journal-file-size value in standalone-full.xml, the min-large-message-size must also bet set appropriately (eg 75KiB?) > For production use, however, we should suggest to the users to remove the journal-file-size and min-large-message-size from standalone-full.xml to use the default values (resp. 10MiB & 100KiB) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-261) Add way to properly parse JNDI urls in AS codebase

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-261?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-261: ------------------------------ Fix Version/s: 9.0.0.Beta1 (was: 8.2.0.Final) > Add way to properly parse JNDI urls in AS codebase > -------------------------------------------------- > > Key: WFLY-261 > URL: https://issues.jboss.org/browse/WFLY-261 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 9.0.0.Beta1 > > > This is a followup of AS7-2138. Original code, in case no URL context threw NamingException. The AS7-2138 introduced a fallback to NamingContext in case AS7 does not provide custom hack for url( like EJB ). However the fallback did not fail with NamingException in case it did not locate Context. This essentially made it go knee deep into AS7 service lookups, which hides real cause of failure. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2893) Determine cause of unreported test failures

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2893?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2893: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 8.2.0.Final) > Determine cause of unreported test failures > ------------------------------------------- > > Key: WFLY-2893 > URL: https://issues.jboss.org/browse/WFLY-2893 > Project: WildFly > Issue Type: Task > Components: Build System, Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 9.0.0.Beta1 > > > Identify the reason why the failing tests that needed https://github.com/wildfly/wildfly/commit/90643bc435a9ba439cf2988e5b7407d... to get working did not fail the build. Those tests were failing for 2.5 months. Fortunately it was just a test problem, not a broken feature. > They involved separate surefire executions. We want to avoid those, but sometimes they are needed to use different config files. We have separate executions in testsuite/integration/basic as well, covering a much broader scope, so if this kind of problem happened there as well we could have a big problem. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2620) Zero Timeout Stateful EJB Leak (clustered)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2620?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2620: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 8.2.0.Final) > Zero Timeout Stateful EJB Leak (clustered) > ------------------------------------------ > > Key: WFLY-2620 > URL: https://issues.jboss.org/browse/WFLY-2620 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.Beta1 > > > Stateful EJB instances are not removed from cache upon release, if the timeout is zero. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1895) Provide a "default" role for management users with no other role specified

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1895?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1895: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 8.2.0.Final) > Provide a "default" role for management users with no other role specified > -------------------------------------------------------------------------- > > Key: WFLY-1895 > URL: https://issues.jboss.org/browse/WFLY-1895 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Jakub Cechacek > Assignee: Emanuel Muckenhuber > Labels: rbac-filed-by-qa > Fix For: 9.0.0.Beta1 > > > Currently it seems that when using RBAC provider users with no defined role are unable to read domain model at all. Consequently logging into Admin Console leads to 500 error page. Similar errors in CLI. > In relation to this, it should be considered what is the expected behavior of unsecured management interface. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-465) Attribute check-for-live-server must set on live server to faillback

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-465?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-465: ------------------------------ Fix Version/s: 9.0.0.Beta1 (was: 8.2.0.Final) > Attribute check-for-live-server must set on live server to faillback > -------------------------------------------------------------------- > > Key: WFLY-465 > URL: https://issues.jboss.org/browse/WFLY-465 > Project: WildFly > Issue Type: Task > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Fix For: 9.0.0.Beta1 > > Attachments: standalone-full-ha-backup.xml, standalone-full-ha-live.xml > > > When there is live/backup pair with replicated journal then it should be sufficient to set attribute "check-for-live-server" in messaging subsystem only on backup to force backup server to shutdown when live server comes alive again. Problem is this won't happen. > Only when attribute "check-for-live-server" is set on live server then failback is successful (backup shutdown itself) > It's not well documented where "check-for-live-server" should be set in HornetQ project documentation: > http://docs.jboss.org/hornetq/2.3.0.CR1/docs/user-manual/html_single/inde... > This issue was hit with EAP 6.1.0.DR2 (HQ 2.3.0.CR1). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3619) XA END / un-enlist for database connection called before all persistence units have performed database updates

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3619?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3619: ------------------------------- Fix Version/s: (was: 8.2.0.Final) > XA END / un-enlist for database connection called before all persistence units have performed database updates > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3619 > URL: https://issues.jboss.org/browse/WFLY-3619 > Project: WildFly > Issue Type: Bug > Components: EJB, JCA, JPA / Hibernate, Transactions > Affects Versions: 8.0.0.Final > Environment: Windows 7 64-bit > JDK 1.8.0_05-b13 64-Bit > MS SQL Server 2012 database > Latest MS JDBC driver > XA datasource > Reporter: Andreas Liebscher > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 9.0.0.Beta1 > > Attachments: persistence.xml, server-9.0.0.Alpha1-SNAPHOT-trace.log, server-9.0.0.Alpha1-SNAPHOT.log, server-all-traces-full.log.gz, server-org-jboss-as-jpa.log, server.jca.log, server_MSSQL_Trace.log > > > While trying to port an EE application from JBoss5 to WF8 the following problem occurred: > EJBs (@Required) using JPA to do some data changes. > Some changes get already written to the database, others reside in the session cache. > After the top EJB call returns, a Hibernate Session flush is triggered in beforeCompletion. > Then more changes are flushed to the database, but I run in a reproduceable database locking problem. > After some time an update of a row fails with lock wait timeout. This row has been inserted prior during the EJB call. > There should be exactly one xa transaction active processing all data changes. > But the database shows two active session, one is an xa transaction with sessionId -2 (orphaned), the other session is a local transaction. > After analyzing all database communication with the help of the JDBC driver logging I found the following behaviour: > - a connection is enlisted and xa start called > - the same connection is used for several select / insert / update statements > - after return of the top EJB call on the same connection xa end and connection un-enlist is called > - the same connection is used for session flush (beforeCompletion) but with local transaction because the connection is no longer associated with the xa transaction, so locks can be expected. > Shouldn't xa end be called AFTER beforeCompletion / session flush!?! -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3602) Emit notifications for servers in domain mode

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3602?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3602: ------------------------------- Fix Version/s: (was: 8.2.0.Final) > Emit notifications for servers in domain mode > --------------------------------------------- > > Key: WFLY-3602 > URL: https://issues.jboss.org/browse/WFLY-3602 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 9.0.0.Beta1 > > > emit notifications related to server lifecycle in domain mode: > * server-started > * server-stopped > * server-restarted > * server-destroyed > * server-killed > These notifications should be emitted from the corresponding server-config resource (under /host=XXX/server-config=YYY) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3110) Don't copy the contents to all hosts when assigning a deployment to a server-group

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3110?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3110: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 8.2.0.Final) > Don't copy the contents to all hosts when assigning a deployment to a server-group > ---------------------------------------------------------------------------------- > > Key: WFLY-3110 > URL: https://issues.jboss.org/browse/WFLY-3110 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Fix For: 9.0.0.Beta1 > > > When assigning a deployment to a server-group it also copies the actual deployment contents to all hosts regardless of the whether the deployment is used locally or not. This should be changed that the contents are only retrieved if they are actually needed on a local server. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4083) Upgrade Infinispan to 6.0.3.Final

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4083?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4083: ------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 8.2.0.Final) > Upgrade Infinispan to 6.0.3.Final > --------------------------------- > > Key: WFLY-4083 > URL: https://issues.jboss.org/browse/WFLY-4083 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 8.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2014