March 2013 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-315: ------------------------------------------- One way would be to quickly merge this https://github.com/modcluster/mod_cluster/pull/12 to 1.2.x branch and make a 1.2.4 release. This change though is dropping entire HA mode -- which was never supported in EAP. > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Task > Reporter: James Perkins > Assignee: Paul Ferraro > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-315: ------------------------------------------- This is rather a peculiar situation, because master (1.2.3.Beta1) is older than 1.2.x branch. This issue is only fixed in master though and not in the tag (at least I dont see it): https://github.com/modcluster/mod_cluster/commits/1.2.3.Final > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Task > Reporter: James Perkins > Assignee: Paul Ferraro > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Jean-Frederic Clere closed MODCLUSTER-315. ------------------------------------------ Resolution: Done > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Task > Reporter: James Perkins > Assignee: Paul Ferraro > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-315: ------------------------------------------------ It is fixed since mod_cluster 1.2.3.Final. It is in AS 7.2.0.Final > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Task > Reporter: James Perkins > Assignee: Paul Ferraro > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by Dimitris Andreadis (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-315?page=com.atlassian.jira.pl... ] Dimitris Andreadis commented on MODCLUSTER-315: ----------------------------------------------- So is this essentially resolved? Which AS/EAP version is included? > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: MODCLUSTER-315 > URL: https://issues.jboss.org/browse/MODCLUSTER-315 > Project: mod_cluster > Issue Type: Task > Reporter: James Perkins > Assignee: Paul Ferraro > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-331) Add mod_cluster container SPI implementation for undertow

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-331?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-331: ------------------------------------------- What we needed and we added: * instance-id (jvmRoute) exposure https://github.com/undertow-io/undertow-subsystem/commit/f30ca17c79ee3720... * instance-id automagic configuration https://github.com/undertow-io/undertow-subsystem/commit/f30ca17c7 * expose servers and hosts https://github.com/undertow-io/undertow-subsystem/commit/11875594c7588320... > Add mod_cluster container SPI implementation for undertow > --------------------------------------------------------- > > Key: MODCLUSTER-331 > URL: https://issues.jboss.org/browse/MODCLUSTER-331 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 1.2.4.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-331) Add mod_cluster container SPI implementation for undertow

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-331?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-331 started by Radoslav Husar. > Add mod_cluster container SPI implementation for undertow > --------------------------------------------------------- > > Key: MODCLUSTER-331 > URL: https://issues.jboss.org/browse/MODCLUSTER-331 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 1.2.4.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-332) Add Engine.getExecutor() to container SPI

by Paul Ferraro (JIRA)

Paul Ferraro created MODCLUSTER-332: --------------------------------------- Summary: Add Engine.getExecutor() to container SPI Key: MODCLUSTER-332 URL: https://issues.jboss.org/browse/MODCLUSTER-332 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.2.3.Final Reporter: Paul Ferraro Assignee: Jean-Frederic Clere Fix For: 1.2.4.Final This is required to expose some mechanism to configure the STATUS interval. Currently, the web subsystem in AS7 has no mechanism to configure the background process period of the Engine. An Engine.getExecutor() container SPI method would allow the mod_cluster subsystem to configure its own executor to control this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-275) sticky session toggles randomly after the shutdown of the active node

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-275?page=com.atlassian.jira.pl... ] Radoslav Husar resolved MODCLUSTER-275. --------------------------------------- Resolution: Rejected As per last comment, this is not a bug. > sticky session toggles randomly after the shutdown of the active node > --------------------------------------------------------------------- > > Key: MODCLUSTER-275 > URL: https://issues.jboss.org/browse/MODCLUSTER-275 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.1.4.Final > Reporter: Christoph Gostner > Assignee: Paul Ferraro > Labels: clustering, jboss-as7, mod_cluster > > Sticky session randomly toggles between cluster node after the shutdown of the active node. > I'd expected that the session remains with one server only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-331) Add mod_cluster container SPI implementation for undertow

by Paul Ferraro (JIRA)

Paul Ferraro created MODCLUSTER-331: --------------------------------------- Summary: Add mod_cluster container SPI implementation for undertow Key: MODCLUSTER-331 URL: https://issues.jboss.org/browse/MODCLUSTER-331 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.2.3.Final Reporter: Paul Ferraro Assignee: Radoslav Husar Fix For: 1.2.4.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues March 2013