February 2013 - jboss-jira - Jboss List Archives

by Bela Ban (JIRA)

Bela Ban created JGRP-1580: ------------------------------ Summary: BSH: remove Key: JGRP-1580 URL: https://issues.jboss.org/browse/JGRP-1580 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.3 Haven't heard of anyone using BSH. Remove BSH and bsh.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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6434) ResourceTransformationDescriptionBuilder needs a rejectChildResource(PathElement pathElement) method

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/AS7-6434?page=com.atlassian.jira.plugin.s... ] Emanuel Muckenhuber reopened AS7-6434: -------------------------------------- Assignee: Emanuel Muckenhuber (was: Kabir Khan) This needs to be changed a bit. Currently operations are only discarded and therefore will never get rejected. > ResourceTransformationDescriptionBuilder needs a rejectChildResource(PathElement pathElement) method > ---------------------------------------------------------------------------------------------------- > > Key: AS7-6434 > URL: https://issues.jboss.org/browse/AS7-6434 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: 7.2.0.Alpha1 > > > It has discardChildResource(PathElement pathElement) but in many, perhaps all cases using that is not correct. > Discarding is only valid if the legacy slave can produce a server without the discarded data and that server's running configuration will be consistent with newer version servers that see the data. > If that can't be done, or some conversion can't be made, a reject should happen to produce a more useful error message than what the slave will issue when it gets ops it can't understand. -- 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-6434) ResourceTransformationDescriptionBuilder needs a rejectChildResource(PathElement pathElement) method

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/AS7-6434?page=com.atlassian.jira.plugin.s... ] Emanuel Muckenhuber edited comment on AS7-6434 at 2/4/13 9:06 AM: ------------------------------------------------------------------ This needs to be changed a bit. Currently operations are discarded and therefore will never get rejected. was (Author: emuckenhuber): This needs to be changed a bit. Currently operations are only discarded and therefore will never get rejected. > ResourceTransformationDescriptionBuilder needs a rejectChildResource(PathElement pathElement) method > ---------------------------------------------------------------------------------------------------- > > Key: AS7-6434 > URL: https://issues.jboss.org/browse/AS7-6434 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: 7.2.0.Alpha1 > > > It has discardChildResource(PathElement pathElement) but in many, perhaps all cases using that is not correct. > Discarding is only valid if the legacy slave can produce a server without the discarded data and that server's running configuration will be consistent with newer version servers that see the data. > If that can't be done, or some conversion can't be made, a reject should happen to produce a more useful error message than what the slave will issue when it gets ops it can't understand. -- 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-6424) Web administration console does not handle values set with expressions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6424?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6424: --------------------------------------- Can we get a 1.5.1 into the AS in the next day or so? > Web administration console does not handle values set with expressions > ---------------------------------------------------------------------- > > Key: AS7-6424 > URL: https://issues.jboss.org/browse/AS7-6424 > Project: Application Server 7 > Issue Type: Bug > Components: Console > Affects Versions: 7.2.0.Alpha1 > Reporter: Ondřej Chaloupka > Assignee: Heiko Braun > Labels: console_1.5.1 > Fix For: 7.2.0.Alpha1 > > > In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response". > As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem. > This was hit on ejb subsystem. > You can try to set following tag like this > {code} > <strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/> > {code} > In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression. -- 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-4931) configuration history length and the number of days they are kept is hardcoded - this needs to be configurable

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4931?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-4931: --------------------------------------- Thanks. I don't want them in the standard standalone.xml file though. The existence of these can be a documentation issue until we add a regular configuration element in AS 8. The Integer.getInteger() calls need to be in in PrivilegedAction if there is a security manager present. > configuration history length and the number of days they are kept is hardcoded - this needs to be configurable > -------------------------------------------------------------------------------------------------------------- > > Key: AS7-4931 > URL: https://issues.jboss.org/browse/AS7-4931 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Ivo Studensky > Priority: Minor > > Currently 100 configuration settings are kept for 30 days. These settings are hard-coded in > org/ jboss/ as/ controller/ persistence/ ConfigurationFile.java > 057 private static final int CURRENT_HISTORY_LENGTH = 100; > 058 private static final int HISTORY_DAYS = 30; > As per PM: this is a bug/gap in the original requirements -- 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-26) Two if/else in a row on the same Pattern generate a compilation error

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-26?page=com.atlassian.jira.plugin.... ] Mario Fusco resolved DROOLS-26. ------------------------------- Fix Version/s: 5.6 6.0.0.Alpha1 Resolution: Done > Two if/else in a row on the same Pattern generate a compilation error > --------------------------------------------------------------------- > > Key: DROOLS-26 > URL: https://issues.jboss.org/browse/DROOLS-26 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 5.6, 6.0.0.Alpha1 > > > Two if/else in a rowon the same Pattern (as in the following example) generate a compilation error > {code} > rule "Car" when > $car: Car( abs == true ) > if ( colour == \"red\" ) do[red] > else if ( colour != \"red\" ) do[notRed] > if ( price < 1000 ) do[cheap] > else do[notCheap] > UnBlocker() > then > System.out.println( "The best Car is in " + $car ); > then[red] > System.out.println( ">>> Car is red " + $car ); > insert( new UnBlocker() ); > then[notRed] > System.out.println( ">>> Car is NOT red " + $car ); > then[cheap] > System.out.println( "*** Car is cheap " + $car ); > then[notCheap] > System.out.println( "*** Car is NOT cheap " + $car ); > end"; > {code} -- 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-5614) Reconfigure of JavaMail service on-the-fly

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-5614?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-5614: ----------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Reconfigure of JavaMail service on-the-fly > ------------------------------------------ > > Key: AS7-5614 > URL: https://issues.jboss.org/browse/AS7-5614 > Project: Application Server 7 > Issue Type: Bug > Components: Mail > Affects Versions: 7.1.1.Final > Reporter: Vadim Gusev > Assignee: Tomaz Cerar > Fix For: 7.3.0.Alpha1 > > > Since JavaMail implemented on Jboss AS7 we can't reconfigure JavaMail service on-the-fly. We always should reload the server to apply new configuration. -- 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-5942) Implement custom Stack resource for JGroups to maintain protocol order

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-5942?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar resolved AS7-5942. ------------------------------ Resolution: Done afaik, this was done... > Implement custom Stack resource for JGroups to maintain protocol order > ----------------------------------------------------------------------- > > Key: AS7-5942 > URL: https://issues.jboss.org/browse/AS7-5942 > Project: Application Server 7 > Issue Type: Task > Components: Clustering, Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Fix For: 7.2.0.Alpha1 > > > A JGroups stack is a transport together with an ordered list of protocols. The transport and the protocols are maintained as child resources. There is no direct way to maintain the order of a set of protocol child resources, so we need to implement a custom resource which does this. -- 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-6444) Physical Server Shutdown (SLAVE Host Controller) doesn't unregister JBOSS server from Domain Controller (MASTER)

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6444?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar closed AS7-6444. ---------------------------- Fix Version/s: 7.2.0.Alpha1 Resolution: Out of Date This has already been fixed in later releases. you can also verify by downloading nightly build of 7.2 from https://community.jboss.org/thread/167590 if you can still reproduce this problem, please reopen this issue. > Physical Server Shutdown (SLAVE Host Controller) doesn't unregister JBOSS server from Domain Controller (MASTER) > ---------------------------------------------------------------------------------------------------------------- > > Key: AS7-6444 > URL: https://issues.jboss.org/browse/AS7-6444 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final > Environment: JBOSS AS 7.1.1.Final > Reporter: Murtaza Ghodawala > Fix For: 7.2.0.Alpha1 > > > Hello Sir/Madam, > We have one master (domain controller) and one slave (host controller) jboss AS 7.1.1.Final setup. Whenever the physical server starts up, JBOSS service starts up automatically and same way on physical server reboot JBOSS gets shutdown and started along with the physical server startup. > Our problem is when we try to reboot slave machine and after reboot if we check the logs, it states ERROR message and because of which slave JBOSS server (host controller) doesn't get started up. > [Host Controller] 15:35:26,241 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: org.jboss.as.host.controller.RemoteDomainConnectionService$HostAlreadyExistsException: JBAS010832: There is already a registered host named 'slave' > The above problem is similar to the one raised in this JIRA BUG and hoping for a quick reply. > Thanks and Regards, > Murtaza Ghodawala > Email: murtaza_ghoda82(a)hotmail.com > Mobile: +965 97180549 -- 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-6444) Physical Server Shutdown (SLAVE Host Controller) doesn't unregister JBOSS server from Domain Controller (MASTER)

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6444?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6444: ----------------------------- Affects Version/s: 7.1.1.Final > Physical Server Shutdown (SLAVE Host Controller) doesn't unregister JBOSS server from Domain Controller (MASTER) > ---------------------------------------------------------------------------------------------------------------- > > Key: AS7-6444 > URL: https://issues.jboss.org/browse/AS7-6444 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Environment: JBOSS AS 7.1.1.Final > Reporter: Murtaza Ghodawala > > Hello Sir/Madam, > We have one master (domain controller) and one slave (host controller) jboss AS 7.1.1.Final setup. Whenever the physical server starts up, JBOSS service starts up automatically and same way on physical server reboot JBOSS gets shutdown and started along with the physical server startup. > Our problem is when we try to reboot slave machine and after reboot if we check the logs, it states ERROR message and because of which slave JBOSS server (host controller) doesn't get started up. > [Host Controller] 15:35:26,241 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: org.jboss.as.host.controller.RemoteDomainConnectionService$HostAlreadyExistsException: JBAS010832: There is already a registered host named 'slave' > The above problem is similar to the one raised in this JIRA BUG and hoping for a quick reply. > Thanks and Regards, > Murtaza Ghodawala > Email: murtaza_ghoda82(a)hotmail.com > Mobile: +965 97180549 -- 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