February 2013 - jboss-jira - Jboss List Archives

[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

11 years, 3 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

11 years, 3 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

11 years, 3 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6431) Incorrectly evaluated expression when property is defined after the expression in xml

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/AS7-6431?page=com.atlassian.jira.plugin.s... ] Ondřej Chaloupka commented on AS7-6431: --------------------------------------- As workaround it could be used run :reload operation. Then the expression is evaluated correctly. The same problem occurs for redefinition of value. {code} <system-properties> <property name="qa.test.exp" value="expression.value"/> <property name="qa.test.property" value="${qa.test.exp:defaultValue}"/> </system-properties> {code} and run: {code} /system-property=qa.test.exp:write-attribute(name=value, value=something.else) {code} Then the {code} :resolve-expression(expression="${qa.test.property}" {code} is evaluated as "expression.value" and not as "something.else" The reload helps again. Maybe put info to user that reload is needed? Still I think that necessity of defining properties in exact order is not much user friendly. Not sure about this. > Incorrectly evaluated expression when property is defined after the expression in xml > ------------------------------------------------------------------------------------- > > Key: AS7-6431 > URL: https://issues.jboss.org/browse/AS7-6431 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.2.0.Alpha1 > Reporter: Ondřej Chaloupka > Assignee: Brian Stansberry > > There is problem in evaluation of expression in case that property for evaluation is defined after the expression. > In case of using DMR the order of property and expression definition is not taken in consideration and substitution works fine. > When you define system properties in xml like: > {code} > <system-properties> > <property name="qa.test.property" value="${qa.test.exp:defaultValue}"/> > <property name="qa.test.exp" value="expression.value"/> > </system-properties> > {code} > you start the container and then you can check the expression evaluation in jboss-cli.sh with command: > {code} > :resolve-expression(expression="${qa.test.property}") > {code} > The expression will be evaluated as "defaultValue" what is not correct because the "qa.test.exp" is defined. > When you switch definitions of properties (switch <property> tags) then the expression will be evaluated correctly (as "expression.value). -- 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

11 years, 3 months

1
0
0 / 0

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

by subh aym (JIRA)

subh aym created SECURITY-724: --------------------------------- Summary: 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: Anil Saldhana 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6349) Upgrade to Infinispan 5.2.0.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-6349?page=com.atlassian.jira.plugin.s... ] Radoslav Husar updated AS7-6349: -------------------------------- Description: http://www.dzone.com/links/infinispan_52final_is_out.html > Upgrade to Infinispan 5.2.0.Final > --------------------------------- > > Key: AS7-6349 > URL: https://issues.jboss.org/browse/AS7-6349 > Project: Application Server 7 > Issue Type: Component Upgrade > Components: Clustering > Reporter: Dimitris Andreadis > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 7.2.0.Alpha1 > > > http://www.dzone.com/links/infinispan_52final_is_out.html -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6432) Incorrect evaluation of system property for expression substitution

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/AS7-6432?page=com.atlassian.jira.plugin.s... ] Ondřej Chaloupka closed AS7-6432. --------------------------------- Resolution: Rejected Yes, you're perfectly correct. Sorry for this jira. The problem was in misconfiguration of test caused by the forgotten management action outcome check. The evaluation of system properties works nice. Thanks. > Incorrect evaluation of system property for expression substitution > ------------------------------------------------------------------- > > Key: AS7-6432 > URL: https://issues.jboss.org/browse/AS7-6432 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.2.0.Alpha1 > Reporter: Ondřej Chaloupka > Assignee: Brian Stansberry > > Finally I think that I've got a way how to resolve expressions on VM where container resides. > My test case: > https://github.com/ochaloup/jboss-as/blob/expression-substitution-run-in-... > From this I've found issues for system property evaluation. I mean the case when System.getProperty(someName) is called. > The application should get the evaluated value from expression but instead of it it gets the default value from expression. > The problematic test cases are > testSystemPropertyEvaluation - there is defined system property by calling System.setProperty and it's expected that the expression which uses this defined property will evaluate itself to the value of the System.setProperty. For the way of :resolve-expression it works fine but for getting value with System.getProperty the old default value is returned. > setInnerExpression - it defines two levels of evaluation of expression and it seems that then the System.getProperty on the second level of evaluation does not get the evaluated/substituted value > I hope that the test code will be more comprehensible than my explanation. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6435) XA datasources not automatically bound with enable=true

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6435?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6435: ----------------------------- Fix Version/s: 7.2.0.CR1 > XA datasources not automatically bound with enable=true > ------------------------------------------------------- > > Key: AS7-6435 > URL: https://issues.jboss.org/browse/AS7-6435 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.2.0.Alpha1 > Environment: Fedora 18 (x86_64) > JDK 7u11 > jboss-as-7.2.0.Alpha1-SNAPSHOT (built today) > Reporter: Frederico Francisco > Assignee: Stefano Maestri > Fix For: 7.2.0.CR1 > > Attachments: domain.xml > > > It seems that my xa-datasource is not started automatically and this causes my applications to fail with: > [Server:master-server-one] JBAS014775: New missing/unsatisfied dependencies: > [Server:master-server-one] service jboss.data-source.java:jboss/datasources/XADS (unavailable) dependents: [service jboss.deployment.subunit."myapp.ear"."myapp-ejb.jar".component.UserClass.jdbc.store-manager.INIT] > The webconsole shows that the datasource is enabled but when I try to disable it I get: > > Internal Server Error > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.", > "rolled-back" => true, > "server-groups" => {"cedsif-server-group" => {"host" => {"master" => {"master-server-one" => {"response" => { > "outcome" => "failed", > "failure-description" => "JBAS010455: Data-source service [XADS] is not enabled", > "rolled-back" => true > }}}}}} > } > The only way I got it to work was to use jboss-cli to start the datasource and then redeploying my applications. > Also, it works if I use a non-xa datasource. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6435) XA datasources not automatically bound with enable=true

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6435?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6435: ----------------------------- Component/s: Domain Management > XA datasources not automatically bound with enable=true > ------------------------------------------------------- > > Key: AS7-6435 > URL: https://issues.jboss.org/browse/AS7-6435 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 7.2.0.Alpha1 > Environment: Fedora 18 (x86_64) > JDK 7u11 > jboss-as-7.2.0.Alpha1-SNAPSHOT (built today) > Reporter: Frederico Francisco > Assignee: Stefano Maestri > Fix For: 7.2.0.CR1 > > Attachments: domain.xml > > > It seems that my xa-datasource is not started automatically and this causes my applications to fail with: > [Server:master-server-one] JBAS014775: New missing/unsatisfied dependencies: > [Server:master-server-one] service jboss.data-source.java:jboss/datasources/XADS (unavailable) dependents: [service jboss.deployment.subunit."myapp.ear"."myapp-ejb.jar".component.UserClass.jdbc.store-manager.INIT] > The webconsole shows that the datasource is enabled but when I try to disable it I get: > > Internal Server Error > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.", > "rolled-back" => true, > "server-groups" => {"cedsif-server-group" => {"host" => {"master" => {"master-server-one" => {"response" => { > "outcome" => "failed", > "failure-description" => "JBAS010455: Data-source service [XADS] is not enabled", > "rolled-back" => true > }}}}}} > } > The only way I got it to work was to use jboss-cli to start the datasource and then redeploying my applications. > Also, it works if I use a non-xa datasource. -- 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

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2013