February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-390) Eliminate the threads subsystem

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-390?page=com.atlassian.jira.plugin.sy... ] Tomaz Cerar updated AS7-390: ---------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.3.0.Alpha1) > Eliminate the threads subsystem > ------------------------------- > > Key: AS7-390 > URL: https://issues.jboss.org/browse/AS7-390 > Project: Application Server 7 > Issue Type: Task > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 7.1.0.CR1 > > > The threads subsystem should be eliminated, and instead the individual consuming subsystems should utilize common code from the jboss-as-threads module to define and manage thread pools within their own configuration models. > Subtasks for affected subsystems. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-724) Vault created through 7.2.0_Alpha not compatible with 7.1.1_Final

by Anil Saldhana (JIRA)

[ https://issues.jboss.org/browse/SECURITY-724?page=com.atlassian.jira.plug... ] Anil Saldhana reassigned SECURITY-724: -------------------------------------- Assignee: Peter Skopek (was: Anil Saldhana) Peter - can you investigate and tell us all the interoperability problems we have here? > Vault created through 7.2.0_Alpha not compatible with 7.1.1_Final > ------------------------------------------------------------------ > > Key: SECURITY-724 > URL: https://issues.jboss.org/browse/SECURITY-724 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Interoperability > Reporter: subh aym > Assignee: Peter Skopek > > Created a security vault through security jars of JBoss AS 7.2.0-Alpha which is scriptable. But the same vault could not be used in JBoss 7.1.1-Final release. > How can the vault be created through script, working for JBoss 7.1 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-23) Debugging rules impossible

by Marc Dzaebel (JIRA)

[ https://issues.jboss.org/browse/DROOLS-23?page=com.atlassian.jira.plugin.... ] Marc Dzaebel commented on DROOLS-23: ------------------------------------ This might be one of the first experiences of any new user. > Debugging rules impossible > -------------------------- > > Key: DROOLS-23 > URL: https://issues.jboss.org/browse/DROOLS-23 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5 > Environment: Eclipse Juno, Windows 8 > Reporter: Marc Dzaebel > Assignee: Mark Proctor > > Create Drools Project, set breakpoint, debug as Drools Application > --> No debug -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-23) Debugging rules impossible

by Marc Dzaebel (JIRA)

Marc Dzaebel created DROOLS-23: ---------------------------------- Summary: Debugging rules impossible Key: DROOLS-23 URL: https://issues.jboss.org/browse/DROOLS-23 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.5 Environment: Eclipse Juno, Windows 8 Reporter: Marc Dzaebel Assignee: Mark Proctor Create Drools Project, set breakpoint, debug as Drools Application --> No debug -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6392) standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/AS7-6392?page=com.atlassian.jira.plugin.s... ] Tom Fonteyne updated AS7-6392: ------------------------------ Workaround Description: remove the "if $linux" and matching "fi" for CygWin use. Not to be removed in general! (was: remove the "if $linux" and matching "fi") > standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN > --------------------------------------------------------------------------------------------------------- > > Key: AS7-6392 > URL: https://issues.jboss.org/browse/AS7-6392 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > > There is a check on linux, so a cygwin system will not execute this block: > if $linux; then > # consolidate the server and command line opts > CONSOLIDATED_OPTS="$JAVA_OPTS $SERVER_OPTS" > # process the standalone options > for var in $CONSOLIDATED_OPTS > do > case $var in > -Djboss.server.base.dir=*) > JBOSS_BASE_DIR=`readlink -m ${var#*=}` > ... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6392) standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/AS7-6392?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda commented on AS7-6392: ---------------------------------------- > remove the "if $linux" and matching "fi" I don't think it's good idea to remove it because readlink is not standard part of Solaris systems ++ RHEL 4 based readlink doesn't know option '-m' -- see JBPAPP-8372 readlink part is just helper to set JBOSS_BASE_DIR, JBOSS_LOG_DIR, JBOSS_CONFIG_DIR You can set these properties before executing standalone.sh as described for example in http://fedoraproject.org/wiki/Getting_started_with_JBossAS7_in_Fedora If you really want to have readlink support for Cygwin I would suggest to include $cygwin check in "if $linux" part ... but not sure how readlink is behaving in Cygwin. > standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN > --------------------------------------------------------------------------------------------------------- > > Key: AS7-6392 > URL: https://issues.jboss.org/browse/AS7-6392 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > > There is a check on linux, so a cygwin system will not execute this block: > if $linux; then > # consolidate the server and command line opts > CONSOLIDATED_OPTS="$JAVA_OPTS $SERVER_OPTS" > # process the standalone options > for var in $CONSOLIDATED_OPTS > do > case $var in > -Djboss.server.base.dir=*) > JBOSS_BASE_DIR=`readlink -m ${var#*=}` > ... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6436) ServerSetupTask.tearDown methods should be called in the reverse order

by Josef Cacek (JIRA)

Josef Cacek created AS7-6436: -------------------------------- Summary: ServerSetupTask.tearDown methods should be called in the reverse order Key: AS7-6436 URL: https://issues.jboss.org/browse/AS7-6436 Project: Application Server 7 Issue Type: Bug Components: Test Suite Reporter: Josef Cacek Assignee: Josef Cacek The ServerSetupObserver should call the {{tearDown()}} methods in the reverse order. Otherwise it breaks setup/service dependencies. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6392) standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/AS7-6392?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda updated AS7-6392: ----------------------------------- Assignee: Brian Stansberry (was: Rostislav Svoboda) Removing myself from assignee, sorry for confusion. Just JIRA shortcuts/pressed keys magic. > standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN > --------------------------------------------------------------------------------------------------------- > > Key: AS7-6392 > URL: https://issues.jboss.org/browse/AS7-6392 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > > There is a check on linux, so a cygwin system will not execute this block: > if $linux; then > # consolidate the server and command line opts > CONSOLIDATED_OPTS="$JAVA_OPTS $SERVER_OPTS" > # process the standalone options > for var in $CONSOLIDATED_OPTS > do > case $var in > -Djboss.server.base.dir=*) > JBOSS_BASE_DIR=`readlink -m ${var#*=}` > ... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6392) standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/AS7-6392?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda reassigned AS7-6392: -------------------------------------- Assignee: Rostislav Svoboda > standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN > --------------------------------------------------------------------------------------------------------- > > Key: AS7-6392 > URL: https://issues.jboss.org/browse/AS7-6392 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Rostislav Svoboda > > There is a check on linux, so a cygwin system will not execute this block: > if $linux; then > # consolidate the server and command line opts > CONSOLIDATED_OPTS="$JAVA_OPTS $SERVER_OPTS" > # process the standalone options > for var in $CONSOLIDATED_OPTS > do > case $var in > -Djboss.server.base.dir=*) > JBOSS_BASE_DIR=`readlink -m ${var#*=}` > ... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1578) UNICAST: lost ACK leads to endless retransmissions

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1578?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1578. ---------------------------- Resolution: Done Fixed according to suggest solution. Unit test is UNICAST_DroppedAckTest > UNICAST: lost ACK leads to endless retransmissions > -------------------------------------------------- > > Key: JGRP-1578 > URL: https://issues.jboss.org/browse/JGRP-1578 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.2.7, 3.3 > > > - B sends a unicast message M to A > - A drops the ACK(M) to B > - B sends no further messages to A > --> B will keep retransmitting M to A until it gets an ACK from A, or A leaves the cluster > --> However, A will not send an ACK(M) to B, as the logic for acking only sends an ack if we did receive a message from B and it was successfully added to the retransmit table > --> However, the retransmitted M will not get added to A's table, as M has already been received > SOLUTION: > - Always ack a message frpm B with the highest delivered seqno for B's table -- 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, 5 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 February 2013