July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1500) File attribute always replaces the file even if the values are equal

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1500?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1500: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 973450|https://bugzilla.redhat.com/show_bug.cgi?id=973450] from POST to MODIFIED > File attribute always replaces the file even if the values are equal > -------------------------------------------------------------------- > > Key: WFLY-1500 > URL: https://issues.jboss.org/browse/WFLY-1500 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Alpha2 > > > The value for the {{FILE}} attribute for file log handlers isn't properly checked when comparing bootstrap file value. With a file that is not appendable, the overwrite would overwrite bootstrapped logged data. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-291) Speed up clustering test suite using ARQ custom containers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-291?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-291: ---------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 972576|https://bugzilla.redhat.com/show_bug.cgi?id=972576] from ASSIGNED to MODIFIED > Speed up clustering test suite using ARQ custom containers > ---------------------------------------------------------- > > Key: WFLY-291 > URL: https://issues.jboss.org/browse/WFLY-291 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Test Suite > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Leveraging ARQ-850. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1553) Infinispan subsystem ignores cluster name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1553?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1553: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 975609|https://bugzilla.redhat.com/show_bug.cgi?id=975609] from POST to MODIFIED > Infinispan subsystem ignores cluster name > ----------------------------------------- > > Key: WFLY-1553 > URL: https://issues.jboss.org/browse/WFLY-1553 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Alpha1 > Reporter: Dennis Reed > Assignee: Paul Ferraro > Priority: Critical > Fix For: 8.0.0.Alpha3 > > > The Infinispan subsystem uses the name of the cache container as the cluster name, instead of the name configured in <transport cluster="foo"/>. > This is a critical issue when using a gossip router, as only the cluster name determines what nodes form a cluster. -- 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

1
0
0 / 0

[JBoss JIRA] (JGRP-1647) Use of Average for stats

by Bela Ban (JIRA)

Bela Ban created JGRP-1647: ------------------------------ Summary: Use of Average for stats Key: JGRP-1647 URL: https://issues.jboss.org/browse/JGRP-1647 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.4 Use Average to maintain average values instead of maintaining separate counters (e.g.) for number of values and totals. Average is faster and total can wrap around. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-52) Locally transmitted context data is not received

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-52?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-52: --------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 909804|https://bugzilla.redhat.com/show_bug.cgi?id=909804] from POST to MODIFIED > Locally transmitted context data is not received > ------------------------------------------------ > > Key: WFLY-52 > URL: https://issues.jboss.org/browse/WFLY-52 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Wouter De Borger > Assignee: jaikiran pai > Labels: ejb > Fix For: 8.0.0.Alpha1 > > > ContextData attached to request is not transmitted when LocalEJBReceiver is used. > org.jboss.as.ejb3.remote.LocalEJBReceiver:177 > context.setContextData(new HashMap<String, Object>()); > see also https://issues.jboss.org/browse/AS7-5021 -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1595) Possible race in jboss-invocation proxies resulting in NPE in initializer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1595?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1595: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 978603|https://bugzilla.redhat.com/show_bug.cgi?id=978603] from POST to MODIFIED > Possible race in jboss-invocation proxies resulting in NPE in initializer > ------------------------------------------------------------------------- > > Key: WFLY-1595 > URL: https://issues.jboss.org/browse/WFLY-1595 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 8.0.0.Alpha2 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha3 > > > jboss-invocation proxies use a thread local to pass information into the initializer, in most cases this works fine as long as only a single thread is attempting to define the class. It is possible for a different thread to load the class that the one that defines it. -- 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

1
0
0 / 0

[JBoss JIRA] (JBASMP-47) execute-commands on EAP6.1.0

by wiktorowski maximilien (JIRA)

wiktorowski maximilien created JBASMP-47: -------------------------------------------- Summary: execute-commands on EAP6.1.0 Key: JBASMP-47 URL: https://issues.jboss.org/browse/JBASMP-47 Project: JBoss AS Maven Plugins Issue Type: Bug Affects Versions: 7.4.Final Reporter: wiktorowski maximilien Assignee: James Perkins I'm trying to use execute-commands goal with EAP 6.1.0 and got : Failed to initialize CLI context: Failed to parse jboss-cli.xml: Unexpected element: resolve-parameter-values. CLI dependency should be updated: [INFO] Plugin Resolved: jboss-as-maven-plugin-7.4.Final.jar ..... [INFO] Plugin Dependency Resolved: jboss-as-cli-7.1.2.Final.jar -- 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

1
0
0 / 0

[JBoss JIRA] (JGRP-1637) Counters overflow

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1637?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1637 at 7/1/13 8:16 AM: -------------------------------------------------------- Another example prone to overflow are counters of the number of bytes sent/received. Investigate use of BigInteger. was (Author: belaban): Another example prone to overflow are counters of the number of bytes sent/received. Investigate use of BigInteger / BigLong (?) > Counters overflow > ----------------- > > Key: JGRP-1637 > URL: https://issues.jboss.org/browse/JGRP-1637 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.4 > > > We have some counters which might see a lot of increments. Investigate which counters are affected (and how) by a potential wraparound, e.g. longs wrap around at 2^63 and go negative. > For example, storing delivery times in nanoseconds and totalling that number could end up with an overflow as e.g. 2ms = 2000000ns, for 1 million msgs/sec would overflow in roughly 7 weeks ! That's the reason org.jgroups.util.Average was created: instead of totalling delivery time and the number of deliveries to compute avg delivery time, we only maintain a fixed array of delivery times, and its elements are randomly overwritten with new values, so we only keep the (more or less) most recent N values to compute the average. > Using a long for a message sequence number should not be an issue: even if we send 1 million messages / sec, we could send for roughly 290'000 years ! -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-878) Message-Driven Beans doesn't support DeliveryActive activation config property

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-878?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil updated WFLY-878: ----------------------------- Summary: Message-Driven Beans doesn't support DeliveryActive activation config property (was: Hornetq adapter doesn't implement ActivationConfigProperty DeliveryActive) > Message-Driven Beans doesn't support DeliveryActive activation config property > ------------------------------------------------------------------------------ > > Key: WFLY-878 > URL: https://issues.jboss.org/browse/WFLY-878 > Project: WildFly > Issue Type: Bug > Components: EE, EJB, JMS > Environment: Windows 64 bit > Reporter: Prasad Deshpande > Assignee: Jeff Mesnil > > I get this warning on AS7.1.1 console, seems that ActivationConfigProperty DeliveryActive is not implemented by hornetq-ra, could we please have it as earlier JMS implementation of JMS had it & application that were using it will fail with AS7 now..? > 16:04:30,794 WARN [org.jboss.ejb3] (MSC service thread 1-16) JBAS014105: ActivationConfigProperty DeliveryActive will be ignored since it is not allowed by resource adapter: hornetq-ra > Thanks, > Prasad -- 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

1
0
0 / 0

[JBoss JIRA] (JGRP-1637) Counters overflow

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1637?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1637: -------------------------------- Another example prone to overflow are counters of the number of bytes sent/received. Investigate use of BigInteger / BigLong (?) > Counters overflow > ----------------- > > Key: JGRP-1637 > URL: https://issues.jboss.org/browse/JGRP-1637 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.4 > > > We have some counters which might see a lot of increments. Investigate which counters are affected (and how) by a potential wraparound, e.g. longs wrap around at 2^63 and go negative. > For example, storing delivery times in nanoseconds and totalling that number could end up with an overflow as e.g. 2ms = 2000000ns, for 1 million msgs/sec would overflow in roughly 7 weeks ! That's the reason org.jgroups.util.Average was created: instead of totalling delivery time and the number of deliveries to compute avg delivery time, we only maintain a fixed array of delivery times, and its elements are randomly overwritten with new values, so we only keep the (more or less) most recent N values to compute the average. > Using a long for a message sequence number should not be an issue: even if we send 1 million messages / sec, we could send for roughly 290'000 years ! -- 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

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 July 2013