December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6134) problem reassigning server to different group

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6134: ----------------------------- Component/s: Domain Management (was: Console) it's not a console problem, hence re-assign to brian > problem reassigning server to different group > --------------------------------------------- > > Key: AS7-6134 > URL: https://issues.jboss.org/browse/AS7-6134 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 7.2.0.CR1 > > > I cannot reassign a (stopped) server to a different group if the domain has two members -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1552) UFC: not needed if we have a TCP transport

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1552?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1552: --------------------------- Fix Version/s: 3.3 > UFC: not needed if we have a TCP transport > ------------------------------------------ > > Key: JGRP-1552 > URL: https://issues.jboss.org/browse/JGRP-1552 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.3 > > > Unicast Flow Control (UFC) is not really needed if we run over a TCP transport. > TODO: > - Remove UFC from all configs that have TCP (or TCP_NIO) as transport > - UFC now issues an INFO message if it discovers it's running over TCP -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1552) UFC: not needed if we have a TCP transport

by Bela Ban (JIRA)

Bela Ban created JGRP-1552: ------------------------------ Summary: UFC: not needed if we have a TCP transport Key: JGRP-1552 URL: https://issues.jboss.org/browse/JGRP-1552 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Unicast Flow Control (UFC) is not really needed if we run over a TCP transport. TODO: - Remove UFC from all configs that have TCP (or TCP_NIO) as transport - UFC now issues an INFO message if it discovers it's running over TCP -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1552) UFC: not needed if we have a TCP transport

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1552?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1552. ---------------------------- Resolution: Done > UFC: not needed if we have a TCP transport > ------------------------------------------ > > Key: JGRP-1552 > URL: https://issues.jboss.org/browse/JGRP-1552 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > > Unicast Flow Control (UFC) is not really needed if we run over a TCP transport. > TODO: > - Remove UFC from all configs that have TCP (or TCP_NIO) as transport > - UFC now issues an INFO message if it discovers it's running over TCP -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6134) problem reassigning server to different group

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-6134: ---------------------------------- The same op nested within a composite op fails: {noformat} [INFO] { [INFO] "operation" => "composite", [INFO] "address" => [], [INFO] "steps" => [{ [INFO] "operation" => "write-attribute", [INFO] "address" => [ [INFO] ("host" => "slave1-with-a-very-lomng-name"), [INFO] ("server-config" => "backup1") [INFO] ], [INFO] "name" => "group", [INFO] "value" => "production" [INFO] }] [INFO] } {noformat} > problem reassigning server to different group > --------------------------------------------- > > Key: AS7-6134 > URL: https://issues.jboss.org/browse/AS7-6134 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.2.0.CR1 > > > I cannot reassign a (stopped) server to a different group if the domain has two members -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6134) problem reassigning server to different group

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-6134: ---------------------------------- seems to work in an atomic operation: {noformat} [domain@localhost:9999 server-config=backup1] :write-attribute(name=group,value=staging) { "outcome" => "success", "result" => undefined, "server-groups" => undefined } {noformat} > problem reassigning server to different group > --------------------------------------------- > > Key: AS7-6134 > URL: https://issues.jboss.org/browse/AS7-6134 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.2.0.CR1 > > > I cannot reassign a (stopped) server to a different group if the domain has two members -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-932) Replace header names and protocol names with IDs

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-932?page=com.atlassian.jira.plugin.s... ] Bela Ban updated JGRP-932: -------------------------- Fix Version/s: 2.10 Affects Version/s: (was: 2.10) > Replace header names and protocol names with IDs > ------------------------------------------------ > > Key: JGRP-932 > URL: https://issues.jboss.org/browse/JGRP-932 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 2.10 > > > We currently use strings as header names. Since a header has to have a magic number, we can replace strings with shorts. A short is always 2 bytes and we don't need to send (potentially long) names around. > A message would then have a Headers hashmap of shorts and Headers. A protocol would also have to be able to catch its own headers, e.g. by creating a method getId(). UDP.getId() might return 56, which is the value in jg-magic-map.xml for TpHeader. > This will solve https://jira.jboss.org/jira/browse/JGRP-872. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-932) Replace header names and protocol names with IDs

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-932?page=com.atlassian.jira.plugin.s... ] Bela Ban commented on JGRP-932: ------------------------------- Hi Bhupesh, Multiplexer was deprecated a long time ago, and finally removed in 3.0, and I don't support 2.12.x any longer. I recommend you upgrade to a 3.2 release. > Replace header names and protocol names with IDs > ------------------------------------------------ > > Key: JGRP-932 > URL: https://issues.jboss.org/browse/JGRP-932 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 2.10 > > > We currently use strings as header names. Since a header has to have a magic number, we can replace strings with shorts. A short is always 2 bytes and we don't need to send (potentially long) names around. > A message would then have a Headers hashmap of shorts and Headers. A protocol would also have to be able to catch its own headers, e.g. by creating a method getId(). UDP.getId() might return 56, which is the value in jg-magic-map.xml for TpHeader. > This will solve https://jira.jboss.org/jira/browse/JGRP-872. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-932) Replace header names and protocol names with IDs

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-932?page=com.atlassian.jira.plugin.s... ] Bela Ban updated JGRP-932: -------------------------- Fix Version/s: (was: 2.10) Affects Version/s: 2.10 > Replace header names and protocol names with IDs > ------------------------------------------------ > > Key: JGRP-932 > URL: https://issues.jboss.org/browse/JGRP-932 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.10 > Reporter: Bela Ban > Assignee: Bela Ban > > We currently use strings as header names. Since a header has to have a magic number, we can replace strings with shorts. A short is always 2 bytes and we don't need to send (potentially long) names around. > A message would then have a Headers hashmap of shorts and Headers. A protocol would also have to be able to catch its own headers, e.g. by creating a method getId(). UDP.getId() might return 56, which is the value in jg-magic-map.xml for TpHeader. > This will solve https://jira.jboss.org/jira/browse/JGRP-872. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6146) Solder doesn't work with 7.1.3 and 7.2.0.alpha1-SNAPSHOT

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created AS7-6146: --------------------------------------- Summary: Solder doesn't work with 7.1.3 and 7.2.0.alpha1-SNAPSHOT Key: AS7-6146 URL: https://issues.jboss.org/browse/AS7-6146 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1 Reporter: Juergen Zimmermann Assignee: Stuart Douglas Attachments: testcase.zip The attached testcase results in a NPE in a JBoss Solder class when it is deployed to 7.1.3.Final and also to 7.2.0.alpha1-SNAPSHOT. It works fine with 7.1.2.Final. Just do a "mvn package jboss-as:deploy" to invoke the testcase. The testcase is preconfigured for 7.1.3. To switch to 7.1.2 or 7.2.0.alpha1 the related property is in the beginning of pom.xml I'm not sure whether the issue is related to Weld (1.1.8 inside JBoss 7.1.2, 1.1.9 inside JBoss 7.1.3, 1.1.10 inside JBoss 7.2) or whether the issue is related to Solder. Anyway, this issue prevents an upgrade from JBoss 7.1.2. The stacktrace in the JBoss console: ... INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] Wrapping InjectionTarget to set field values: test.ArticleController ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.deployment.unit."test.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: Exception 0 : org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: Exception 0 : java.lang.NullPointerException at org.jboss.solder.bean.generic.GenericBeanExtension.registerGenericBeanObserverMethod(GenericBeanExtension.java:378) at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213) at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:117) at org.jboss.weld.event.TransactionalObserverNotifier.notifyObserver(TransactionalObserverNotifier.java:44) at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:85) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:75) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:60) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:38) at org.jboss.weld.bootstrap.events.ProcessObserverMethodImpl.fire(ProcessObserverMethodImpl.java:45) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:76) at org.richfaces.cdi.push.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:42) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:360) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:40) at org.jboss.weld.bootstrap.events.ProcessObserverMethodImpl.fire(ProcessObserverMethodImpl.java:45) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:76) at org.richfaces.cdi.push.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:42) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:360) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- 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

13 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 2012