October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3948) Extract JGroups ChannelFactory and ServiceName factories into separate module

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-3948: ---------------------------------- Summary: Extract JGroups ChannelFactory and ServiceName factories into separate module Key: WFLY-3948 URL: https://issues.jboss.org/browse/WFLY-3948 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 9.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro Modules that wish to create JGroups channels currently need to import the entire jgroups subsystem module just to reference a ChannelFactory and generate the appropriate ServiceNames. These should reside in a separate module from the extension. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-116) Correct or remove usage of finalize in LoggerNode

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-116?page=com.atlassian.jira.plugin... ] Jason Greene closed LOGMGR-116. ------------------------------- Fix Version/s: (was: 1.4.4.Final) (was: 1.5.4.Final) Resolution: Won't Fix Ah fair enough. I'll close it as won't fix then. > Correct or remove usage of finalize in LoggerNode > ------------------------------------------------- > > Key: LOGMGR-116 > URL: https://issues.jboss.org/browse/LOGMGR-116 > Project: JBoss Log Manager > Issue Type: Task > Reporter: Jason Greene > Assignee: James Perkins > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-116) Correct or remove usage of finalize in LoggerNode

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-116?page=com.atlassian.jira.plugin... ] David Lloyd commented on LOGMGR-116: ------------------------------------ The API itself makes certain contracts in terms of finalization. Like for example if I get a logger, set a level on it, and then log a message, I am not guaranteed that the logger will retain the level setting for the duration of the log call (though in general, it probably will, because there are locks etc. all over the place) because the API specifies that "It is important to note that the Logger returned by one of the getLogger factory methods may be garbage collected at any time if a strong reference to the Logger is not kept." > Correct or remove usage of finalize in LoggerNode > ------------------------------------------------- > > Key: LOGMGR-116 > URL: https://issues.jboss.org/browse/LOGMGR-116 > Project: JBoss Log Manager > Issue Type: Task > Reporter: Jason Greene > Assignee: James Perkins > Fix For: 1.4.4.Final, 1.5.4.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-116) Correct or remove usage of finalize in LoggerNode

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-116?page=com.atlassian.jira.plugin... ] Jason Greene commented on LOGMGR-116: ------------------------------------- Do you have any sort of guarantee that LoggerNode is held past all desired usage of it (e.g. log calls)? If not then the main issue, aside from the potential finalizer thread stall, is you could lose log messages. > Correct or remove usage of finalize in LoggerNode > ------------------------------------------------- > > Key: LOGMGR-116 > URL: https://issues.jboss.org/browse/LOGMGR-116 > Project: JBoss Log Manager > Issue Type: Task > Reporter: Jason Greene > Assignee: James Perkins > Fix For: 1.4.4.Final, 1.5.4.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3947) Incorrect EJB Calendar Based Timeouts

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-3947: ------------------------------------- Summary: Incorrect EJB Calendar Based Timeouts Key: WFLY-3947 URL: https://issues.jboss.org/browse/WFLY-3947 Project: WildFly Issue Type: Bug Components: EJB Reporter: Eduardo Martins Assignee: Eduardo Martins EJB3 CalendarBasedTimeout computes incorrects timeouts due to bad Calendar time fields manipulation, specially on DST. A couple of examples: 1) Timezone: "Europe/Lisbon" Schedule Expression: any day at 1h30m Start: 2013/03/31 03h30m First timeout currently is 2h30m 2) Timezone: "Australia/Lord_Howe" Schedule Expression: any day at 2h20m, 2h40m, 3h20m, 3h40m Start: 2013/10/06 02h41m First timeout currently is 3h50m -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-116) Correct or remove usage of finalize in LoggerNode

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-116?page=com.atlassian.jira.plugin... ] David Lloyd commented on LOGMGR-116: ------------------------------------ This finalize is designed to behave equivalently to the JUL version. So far this usage has not been observed to actually cause any issues with the finalizer thread - it could conceivably do so in a case where you have a hierarchy of loggers that is hundreds of levels deep and exponential in breadth, but the simple massive number of objects that such a case would create would be a far larger factor. I think it should be kept as-is unless a problem is observed, at which time a dedicated cleanup thread should be used instead. > Correct or remove usage of finalize in LoggerNode > ------------------------------------------------- > > Key: LOGMGR-116 > URL: https://issues.jboss.org/browse/LOGMGR-116 > Project: JBoss Log Manager > Issue Type: Task > Reporter: Jason Greene > Assignee: James Perkins > Fix For: 1.4.4.Final, 1.5.4.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBVFS-198) Correct or remove usage of finalize in VFS, TempDir, and TempFileProvider

by Jason Greene (JIRA)

Jason Greene created JBVFS-198: ---------------------------------- Summary: Correct or remove usage of finalize in VFS, TempDir, and TempFileProvider Key: JBVFS-198 URL: https://issues.jboss.org/browse/JBVFS-198 Project: JBoss VFS Issue Type: Task Reporter: Jason Greene Assignee: Tomaz Cerar Fix For: 3.2.8.Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-116) Correct or remove usage of finalize in LoggerNode

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-116?page=com.atlassian.jira.plugin... ] Jason Greene commented on LOGMGR-116: ------------------------------------- Note that it according to a comment this usage could potentially stall the finalizer thread(s). If it can stall it should be a task executed in another thread. The only exception is a monitor acquire on the finalize method itself, this does not incur a lock due to a JLS rule that an object is not finalizable if it aquires a monitor that is actively locked > Correct or remove usage of finalize in LoggerNode > ------------------------------------------------- > > Key: LOGMGR-116 > URL: https://issues.jboss.org/browse/LOGMGR-116 > Project: JBoss Log Manager > Issue Type: Task > Reporter: Jason Greene > Assignee: James Perkins > Fix For: 1.4.4.Final, 1.5.4.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-116) Correct or remove usage of finalize in LoggerNode

by Jason Greene (JIRA)

Jason Greene created LOGMGR-116: ----------------------------------- Summary: Correct or remove usage of finalize in LoggerNode Key: LOGMGR-116 URL: https://issues.jboss.org/browse/LOGMGR-116 Project: JBoss Log Manager Issue Type: Task Reporter: Jason Greene Assignee: James Perkins Fix For: 1.4.4.Final, 1.5.4.Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3749) Upgrade to Remoting 4.0.5.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3749?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-3749. ------------------------------------ Resolution: Duplicate Issue > Upgrade to Remoting 4.0.5.Final > ------------------------------- > > Key: WFLY-3749 > URL: https://issues.jboss.org/browse/WFLY-3749 > Project: WildFly > Issue Type: Component Upgrade > Components: Remoting > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

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 October 2014