October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-130) Upgrade Woodstox

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-130?page=com.atlassian.jira.plugin... ] David Lloyd resolved WFCORE-130. -------------------------------- Assignee: David Lloyd Fix Version/s: (was: 1.0.0.CR1) Resolution: Won't Fix This is not necessary with WFCORE-147 which contains a suitable workaround. > Upgrade Woodstox > ---------------- > > Key: WFCORE-130 > URL: https://issues.jboss.org/browse/WFCORE-130 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > > Upgrade Woodstox to a version which contains a fix for https://jira.codehaus.org/browse/WSTX-305 . -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1264) Create a test to get notifications when hosts join/leave a domain

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1264?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-1264: ---------------------------------------- The domain controller itself doesn't provide remote notifications of hosts joining and leaving a domain, so I don't see how there can be an arquillian based test of it. QE, please clarify the requirements. > Create a test to get notifications when hosts join/leave a domain > ----------------------------------------------------------------- > > Key: WFLY-1264 > URL: https://issues.jboss.org/browse/WFLY-1264 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Andrew Rubinger > Assignee: Panagiotis Sotiropoulos > > Should be implemented by using the mechanism provided by AS7-1415, injection of the ManagementClient into the test. Verify this is working to fulfill the feature request from QE to get notifications on hosts joining/leaving the Domain. May depend upon the presence of an AS7 Domain Controller Container. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3945) Upgrade WildFly Core to 1.0.0.Alpha9

by David Lloyd (JIRA)

David Lloyd created WFLY-3945: --------------------------------- Summary: Upgrade WildFly Core to 1.0.0.Alpha9 Key: WFLY-3945 URL: https://issues.jboss.org/browse/WFLY-3945 Project: WildFly Issue Type: Component Upgrade Reporter: David Lloyd Assignee: Jason Greene Fix For: 9.0.0.Beta1 Dependent issue for all issues which need a WFCORE upgrade to continue. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3882) Add a function at ManagementClient that returns the hosts that are included in the domain.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3882?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-3882: ---------------------------------------- There needs to be justification for this requirement. The WFLY-1264 request isn't one, as that is asking for notifications, not a query. > Add a function at ManagementClient that returns the hosts that are included in the domain. > ------------------------------------------------------------------------------------------ > > Key: WFLY-3882 > URL: https://issues.jboss.org/browse/WFLY-3882 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > A function is needed at ManagementClient which returns the hosts that are currently in the domain. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-144) Update JBoss Threads

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-144?page=com.atlassian.jira.plugin... ] David Lloyd updated WFCORE-144: ------------------------------- Description: Update to a version which includes JBTHR-30 (2.2.0.Beta1). (was: Update to a version which includes JBTHR-30.) > Update JBoss Threads > -------------------- > > Key: WFCORE-144 > URL: https://issues.jboss.org/browse/WFCORE-144 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > > Update to a version which includes JBTHR-30 (2.2.0.Beta1). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1226) Add connection listener and timestamp to leak detector pool

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1226?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1226. ------------------------------------ Resolution: Done > Add connection listener and timestamp to leak detector pool > ----------------------------------------------------------- > > Key: JBJCA-1226 > URL: https://issues.jboss.org/browse/JBJCA-1226 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.29.Final, 1.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1226) Add connection listener and timestamp to leak detector pool

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1226: -------------------------------------- Summary: Add connection listener and timestamp to leak detector pool Key: JBJCA-1226 URL: https://issues.jboss.org/browse/JBJCA-1226 Project: IronJacamar Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.29.Final, 1.2.0.Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-852) Broken Links on JBoss.org

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-852?page=com.atlassian.jira.plug... ] Stefan Guilhen resolved SECURITY-852. ------------------------------------- Resolution: Done Twitter link has been removed (PicketBox project doesn't have a twitter account) and the remaining links have been updated. > Broken Links on JBoss.org > ------------------------- > > Key: SECURITY-852 > URL: https://issues.jboss.org/browse/SECURITY-852 > Project: PicketBox > Issue Type: Bug > Reporter: Daniel Coughlin > Assignee: Stefan Guilhen > > The following broken link is currently listed against this project on www.jboss.org/projects. > http://twitter.com/picketbox - Twitter Link > http://community.jboss.org/en/jbossas/picketbox?view=discussions - User Forum > http://community.jboss.org/en/jbossas/picketbox?view=discussions - Community > http://community.jboss.org/en/jbossas/picketbox?view=documents - KnowledgeBase > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3943) There is no testing of the messaging subsystem integration with the JGroups subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3943?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-3943: ---------------------------------------- Merging a fix for WFLY-3805 will require some form of integration testing, JIRA for which is WFLY-3943. > There is no testing of the messaging subsystem integration with the JGroups subsystem > ------------------------------------------------------------------------------------- > > Key: WFLY-3943 > URL: https://issues.jboss.org/browse/WFLY-3943 > Project: WildFly > Issue Type: Task > Components: JMS > Affects Versions: 9.0.0.Alpha1 > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Priority: Critical > > HornetQServerAdd and HornetQServerService have integration with the JGroups subsystem in order to add a dependency on a ChannelFactory for use with broadcast and discovery groups. But it seems there is no testing of this integration. > Looks like it's currently broken. That problem is likely a clustering bug, as there was a recent major change in this area, and this works in the 6.x branch. > This JIRA is about the fact lack of testing that would have caught the bug. Also, https://github.com/wildfly/wildfly/pull/6725 passed the testsuite with a code change that was binary incompatible with the version of HQ that was integrated at the time. > I'll file a separate issue for the problem I'm referring to. To reproduce it change the bg-group1 element in standalone-full-ha.xml to replace the socket-binding element with the following: > {code} > <jgroups-stack>udp</jgroups-stack> > <jgroups-channel>hq-bg</jgroups-channel> >  > {code} > At boot this appears in the logs: > {code} > 10:00:58,707 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging"), > ("hornetq-server" => "default") > ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.jgroups.stack.udp]"]} > 10:00:58,930 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.jgroups.stack.udp (missing) dependents: [service jboss.messaging.default] > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3944) Broken integration between messaging subsystem and jgroups subsystem

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-3944: -------------------------------------- Summary: Broken integration between messaging subsystem and jgroups subsystem Key: WFLY-3944 URL: https://issues.jboss.org/browse/WFLY-3944 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Brian Stansberry Assignee: Paul Ferraro Priority: Critical The integration between messaging and jgroups is currently broken. My guess is this was due to recent changes in clustering. To reproduce it change the bg-group1 element in standalone-full-ha.xml to replace the socket-binding element with the following: {code} <jgroups-stack>udp</jgroups-stack> <jgroups-channel>hq-bg</jgroups-channel>  {code} At boot this appears in the logs: {code} 10:00:58,707 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "messaging"), ("hornetq-server" => "default") ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.jgroups.stack.udp]"]} 10:00:58,930 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.jgroups.stack.udp (missing) dependents: [service jboss.messaging.default] {code} WFLY-3943 is about the lack of testing of this integration, -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 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 October 2014