April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1452) SEQUENCER goes wrong when members fail simultaneously

by David Hotham (JIRA)

David Hotham created JGRP-1452: ---------------------------------- Summary: SEQUENCER goes wrong when members fail simultaneously Key: JGRP-1452 URL: https://issues.jboss.org/browse/JGRP-1452 Project: JGroups Issue Type: Bug Affects Versions: 3.0.9 Reporter: David Hotham Assignee: Bela Ban Consider the case where current view is [A, B, C, D], and A and B both die more or less simultaneously. C will now try to broadcast the new view [C, D]. But if SEQUENCER is in the stack this goes wrong: SEQUENCER on C doesn't yet know that it is coordinator and tries to forward to either A or B. The change of view gets stuck. The problem looks to be in handleSuspect(). This assumes that there is at most one suspect, removes that from the list of members, and figures that whoever is left will be the new coordinator. But this fails in the case just described. IMHO it's a mistake for SEQUENCER to try and duplicate the work that the GMS layer does in the new view. I'm currently trying a fix that removes handleSuspect() from SEQUENCER altogether, and instead pays attention to TMP_VIEW events. This seems to be working, I think. David -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
7
0 / 0

[JBoss JIRA] (AS7-4242) Reduce testsuite memory footprint

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-4242: -------------------------------------- Summary: Reduce testsuite memory footprint Key: AS7-4242 URL: https://issues.jboss.org/browse/AS7-4242 Project: Application Server 7 Issue Type: Task Components: Test Suite Reporter: Rostislav Svoboda Assignee: Ondrej Zizka Fix For: 7.1.2.Final Try to investigate testsuite for possible "memory leaks" / unnecessary memory consumption. For inspiration take a look at JBWS-3455 commits, maybe some of Alessio's changes can be applied to AS TS too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1577) Require at least maven 2.0.9

by Carlo de Wolf (JIRA)

Require at least maven 2.0.9 ---------------------------- Key: EJBTHREE-1577 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1577 Project: EJB 3.0 Issue Type: Feature Request Components: build Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 1.0.0-Beta7 Because a bug in Maven with the ordering of the class path, you need at least version 2.0.9. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] (AS7-4052) Update OSGi susbsystem docs in the AS71 wiki

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4052: ----------------------------------- Summary: Update OSGi susbsystem docs in the AS71 wiki Key: AS7-4052 URL: https://issues.jboss.org/browse/AS7-4052 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.1.1.Final Please revisit/update [OSGi subsystem configuration|https://docs.jboss.org/author/display/AS71/OSGi+subsystem+c...]. It is quite out of date. Some coverage is [here|https://docs.jboss.org/author/display/JBOSGI/Application+Server+Inte...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
5
0 / 0

[JBoss JIRA] (AS7-4077) Unexpected attribute 'ca-certificate-file' encountered

by Michal Babacek (JIRA)

Michal Babacek created AS7-4077: ----------------------------------- Summary: Unexpected attribute 'ca-certificate-file' encountered Key: AS7-4077 URL: https://issues.jboss.org/browse/AS7-4077 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Michal Babacek Assignee: Paul Ferraro I've wanted to verify the [AS7-3869] (*[pull 1723|https://github.com/jbossas/jboss-as/pull/1723]*) with the current jboss-as *master* and the following configuration in *standalone-ha.xml*: {code:lang=xml} <subsystem xmlns="urn:jboss:domain:modcluster:1.0"> <mod-cluster-config advertise-socket="modcluster"> <ssl ca-certificate-file="/tmp/hudson/Client/client-keystore.jsk" certificate-key-file="/tmp/hudson/Client/client-keystore.jsk" password="tomcat" /> </mod-cluster-config> </subsystem> {code} throws the undermentioned error on startup: {noformat} 06:43:39,873 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA 06:43:40,063 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA 06:43:40,122 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final-SNAPSHOT "Thunder" starting 06:43:41,001 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT] at org.jboss.as.server.ServerService.boot(ServerService.java:266) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[358,13] Message: JBAS014788: Unexpected attribute 'ca-certificate-file' encountered at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:104) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT] at org.jboss.as.modcluster.ModClusterSubsystemXMLReader_1_0.parseSSL(ModClusterSubsystemXMLReader_1_0.java:199) at org.jboss.as.modcluster.ModClusterSubsystemXMLReader_1_0.parseModClusterConfig(ModClusterSubsystemXMLReader_1_0.java:134) at org.jboss.as.modcluster.ModClusterSubsystemXMLReader_1_0.readElement(ModClusterSubsystemXMLReader_1_0.java:107) at org.jboss.as.modcluster.ModClusterSubsystemXMLReader_1_0.readElement(ModClusterSubsystemXMLReader_1_0.java:86) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:894) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT] at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:330) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:127) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:100) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT] ... 3 more 06:43:41,016 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. 06:43:41,028 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.1.Final-SNAPSHOT "Thunder" stopped in 6ms {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] (AS7-4095) mod_cluster AdvertiseListenerImpl does not take multicast-port setting into account

by Michal Babacek (JIRA)

Michal Babacek created AS7-4095: ----------------------------------- Summary: mod_cluster AdvertiseListenerImpl does not take multicast-port setting into account Key: AS7-4095 URL: https://issues.jboss.org/browse/AS7-4095 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Michal Babacek Assignee: Michal Babacek The undermentioned configuration: {code:lang=xml} +++ <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> +++ <socket-binding name="modcluster" port="0" multicast-address="224.0.1.105" multicast-port="6666"/> +++ </socket-binding-group> +++ {code} does not affect the actual port the mod_cluster is looking for advertisement: {code} 05:11:22,295 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-4) Listening to proxy advertisements on 224.0.1.105:23364 {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
4
0 / 0

[JBoss JIRA] (AS7-4098) mod_cluster subsystem does not take proxy-list attribute into account

by Michal Babacek (JIRA)

Michal Babacek created AS7-4098: ----------------------------------- Summary: mod_cluster subsystem does not take proxy-list attribute into account Key: AS7-4098 URL: https://issues.jboss.org/browse/AS7-4098 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Michal Babacek Assignee: Paul Ferraro With the AS7 current master *{color:green}89daec9{color}*, the following configuration: {code:lang=xml} <subsystem xmlns="urn:jboss:domain:modcluster:1.0"> <mod-cluster-config proxy-list="perf05:8888"> <ssl password="tomcat" certificate-key-file="/tmp/Client/client-keystore.jsk" ca-certificate-file="/tmp/Client/client-keystore.jsk"/> </mod-cluster-config> </subsystem> {code} leads to the default, "advertising enabled" behaviour (e.g. might be related to [AS7-4095]): {noformat} [JBoss] 07:10:12,426 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-4) Initializing mod_cluster 1.2.0.Final [JBoss] 07:10:12,473 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-4) Listening to proxy advertisements on 224.0.1.105:23364 {noformat}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] (AS7-2764) Show configured / effective bind address of a server

by Wolf-Dieter Fink (Created) (JIRA)

Show configured / effective bind address of a server ---------------------------------------------------- Key: AS7-2764 URL: https://issues.jboss.org/browse/AS7-2764 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.1.0.Beta1, 7.1.0.Alpha1 Reporter: Wolf-Dieter Fink Assignee: Heiko Braun The bind address of a server can be dedicated configured for each server of a host controller. This should be reflected by the management console. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] (AS7-4464) EJB3 deployment metrics missing

by Stefan Negrea (JIRA)

Stefan Negrea created AS7-4464: ---------------------------------- Summary: EJB3 deployment metrics missing Key: AS7-4464 URL: https://issues.jboss.org/browse/AS7-4464 Project: Application Server 7 Issue Type: Enhancement Reporter: Stefan Negrea The following metrics are missing from AS7 EJB3 subsystem from deployment when compared to AS5 exposed metrics: Stateless Session Bean Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB Stateful Session Bean Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB Cache Size - Cache Size Passivated Count - Passivated Count Total Size - Total Size -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1684) Add configuration setting that allows an extended persistence context to be propagated even if there is no JTA transaction

by Scott Marlow (JIRA)

Add configuration setting that allows an extended persistence context to be propagated even if there is no JTA transaction --------------------------------------------------------------------------------------------------------------------------- Key: AS7-1684 URL: https://issues.jboss.org/browse/AS7-1684 Project: Application Server 7 Issue Type: Feature Request Components: JPA / Hibernate Affects Versions: 7.0.0.Beta2 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.1.0.Beta1 Earlier versions of AS, allowed an extended persistence context (XPC) to propagate, even if no JTA transaction was active during use of the XPC. With the recent fix to AS7-1663, using an XPC outside of a JTA transaction and then invoking a transactional entity manager inside of a JTA transaction, will not propagate the XPC into the new transaction. Add a domain default setting that allows the (not used in a JTA transaction) XPC to propagate into the new transaction (on behalf of a transactional entity manager). This will only happen if the XPC is active in the call stack. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
5
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 April 2012