November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5991) It’s impossible to set a custom pattern for the handler’s formatter via CLI or native configuration API

by Radoslav Rangelov (JIRA)

Radoslav Rangelov created AS7-5991: -------------------------------------- Summary: It’s impossible to set a custom pattern for the handler’s formatter via CLI or native configuration API Key: AS7-5991 URL: https://issues.jboss.org/browse/AS7-5991 Project: Application Server 7 Issue Type: Bug Components: CLI, Logging Affects Versions: 7.1.2.Final (EAP) Reporter: Radoslav Rangelov Assignee: Alexey Loubyansky Fix For: 7.1.1.Final It’s impossible to set a custom pattern string for the handler’s formatter via CLI or native configuration API. The default value for the pattern is always used - not the specified one. The manual configuration of domain.xml file works fine during startup: <formatter> <pattern-formatter pattern="custom pattern string"/> </formatter> -- 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

3
9
0 / 0

[JBoss JIRA] (AS7-5987) EJB Deployment View

by Harald Pehl (JIRA)

Harald Pehl created AS7-5987: -------------------------------- Summary: EJB Deployment View Key: AS7-5987 URL: https://issues.jboss.org/browse/AS7-5987 Project: Application Server 7 Issue Type: Sub-task Components: Console Reporter: Harald Pehl Assignee: Heiko Braun Fix For: 7.2.0.CR1 -- 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
4
0 / 0

[JBoss JIRA] (AS7-5728) ClusteredSingleSignOn doesn't remove ssoId from sso cluster on Request.logout

by Stian Thorgersen (JIRA)

Stian Thorgersen created AS7-5728: ------------------------------------- Summary: ClusteredSingleSignOn doesn't remove ssoId from sso cluster on Request.logout Key: AS7-5728 URL: https://issues.jboss.org/browse/AS7-5728 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.3.Final (EAP) Reporter: Stian Thorgersen Logging out a user with Request.logout doesn't work with clustered SSO. This is caused by ClusteredSingleSignOn.deregister(String) not remove the ssoId from the SSO cluster. The ClusteredSingleSignOn.sessionEvent removes it from both the local cache and the SSO cluster, so a workaround is to call Session.invalidate() prior to calling Request.logout(). -- 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

4
8
0 / 0

[JBoss JIRA] (AS7-5992) Upgrade JGroups to 3.2.1

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-5992: --------------------------------- Summary: Upgrade JGroups to 3.2.1 Key: AS7-5992 URL: https://issues.jboss.org/browse/AS7-5992 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.2.0.Alpha1 -- 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-5980) HTTP connector has missing configuration

by Paul Hinds (JIRA)

Paul Hinds created AS7-5980: ------------------------------- Summary: HTTP connector has missing configuration Key: AS7-5980 URL: https://issues.jboss.org/browse/AS7-5980 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.1.2.Final (EAP) Reporter: Paul Hinds Assignee: Remy Maucherat We have an application that is using the JBoss HTTP connector without Apache in front. Because keep-alive timeout is not configurable we have to accept defaults which means for a request that takes 10ms to complete we seem to dedicate a thread for 15 seconds. It is impossible to balance performance with concurrency without this option. Other options are missing from JBossAs7 that are required for performance. max keep alive requests tcp no delay max http header size connection timeout compression These should be configurable in the connector XML having some parameters available via system properties is inconvenient. max header size and keep alive timeout are the showstoppers for our use of JBoss. -- 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

2
4
0 / 0

[JBoss JIRA] (AS7-5986) Add possibility to control settings of cache of stateful beans in EJB3 subsystem

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-5986: ------------------------------------- Summary: Add possibility to control settings of cache of stateful beans in EJB3 subsystem Key: AS7-5986 URL: https://issues.jboss.org/browse/AS7-5986 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.1.3.Final (EAP) Reporter: Ondřej Chaloupka Assignee: Heiko Braun Priority: Minor As it was mentioned in comments on JBPAPP6-1450 I'm creating upstream jira for this feature. It would be fine to have possibility to control settings of cache for stateful beans in EJB3 susbsystem. Currently there is possible to set up pool for stateless beans but there are no settings possibilities for SFSB. What I'm missing is the possibility how to define default cache for the stateful beans and how to create and manage things which cover tag <caches> from ejb3 subsystem. I mean that you can define cache-ref for SFSB and you can set up cache properties in EJB subsystem (eg. <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>) in standalone.xml or via cli (jboss-cli.sh) but this possibility is not accessible in web admin console. -- 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] (JBRULES-3279) Error message when using 2 patterns inside a single accumulate is not clear: Parser returned a null Package

by Geoffrey De Smet (Created) (JIRA)

Error message when using 2 patterns inside a single accumulate is not clear: Parser returned a null Package ----------------------------------------------------------------------------------------------------------- Key: JBRULES-3279 URL: https://issues.jboss.org/browse/JBRULES-3279 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.3.0.Final Reporter: Geoffrey De Smet Assignee: Edson Tirelli I am trying to parse this rule: {code} rule "machineUsage" when $machineCapacity : MrMachineCapacity($machine : machine, $resource : resource) $usageTotal : Number() from accumulate( MrProcessRequirement(resource == $resource, $process : process, $usage : usage) MrProcessAssignment(machine == $machine, process == $process), sum($usage) ) then ... end {code} And I get this error message: {code} Exception in thread "main" java.lang.IllegalStateException: There are errors in the scoreDrl's:[47,77]: [ERR 102] Line 47:77 mismatched input ',' in rule "machineUsage" [0,0]: Parser returned a null Package {code} For this line: {code} MrProcessAssignment(machine == $machine, process == $process), {code} It clear that it's because I can't use 2 patterns inside a single accumulate, but the error message seems wrong? When I try this instead: {code} rule "machineUsage" when $machineCapacity : MrMachineCapacity($machine : machine, $resource : resource) $usageTotal : Number() from accumulate( (MrProcessRequirement(resource == $resource, $process : process, $usage : usage) and MrProcessAssignment(machine == $machine, process == $process)), sum($usage) ) then ... end {code} I get: {code} Exception in thread "main" org.drools.RuntimeDroolsException: BUG: Can't build a rete network with an inner OR group element {code} Don't really see the OR in there. -- 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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] (AS7-5823) Create class hierarchy

by Harald Pehl (JIRA)

Harald Pehl created AS7-5823: -------------------------------- Summary: Create class hierarchy Key: AS7-5823 URL: https://issues.jboss.org/browse/AS7-5823 Project: Application Server 7 Issue Type: Sub-task Reporter: Harald Pehl Seperate classes into two distinct packages: * org.jboss.mbui.aui: Contains classes for the abstract ui layer * org.jboss.mbui.cui: Contains classes for the concrete ui layer -- 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
1
0 / 0

[JBoss JIRA] (AS7-5964) Admin Console: Missing validation message for ListItem

by Harald Pehl (JIRA)

Harald Pehl created AS7-5964: -------------------------------- Summary: Admin Console: Missing validation message for ListItem Key: AS7-5964 URL: https://issues.jboss.org/browse/AS7-5964 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Harald Pehl Assignee: Harald Pehl Priority: Minor Fix For: 7.2.0.CR1 The ballrom widget {{org.jboss.ballroom.client.widgets.forms.ListItem}} does not show a validation icon / message in case of invalid values. In contrast other widgets like {{org.jboss.ballroom.client.widgets.forms.TextItem}} show a validation icon / message. Therefore an instance of {{org.jboss.ballroom.client.widgets.forms.InputElementWrapper}} is used. ListItem should also use this wrapper. -- 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
2
0 / 0

[JBoss JIRA] (AS7-5984) Determine whether a server is in sync with the domain model on reconnect

by Emanuel Muckenhuber (JIRA)

Emanuel Muckenhuber created AS7-5984: ---------------------------------------- Summary: Determine whether a server is in sync with the domain model on reconnect Key: AS7-5984 URL: https://issues.jboss.org/browse/AS7-5984 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Fix For: 7.2.0.CR1 When a server reconnects to the host-controller we would need to determine whether the server is still in sync with the domain model. Potentially the host-controller could also keep track of whether the server missed operations from the domain-controller. -- 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 November 2012