January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2189) Revisit the jgroups management configuration

by Heiko Braun (Created) (JIRA)

Revisit the jgroups management configuration -------------------------------------------- Key: AS7-2189 URL: https://issues.jboss.org/browse/AS7-2189 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.0.CR1 This doesn't look very reasonable to me: {noformat} [domain@localhost:9999 /] /profile=ha/subsystem=jgroups/stack=tcp:read-resource { "outcome" => "success", "result" => { "protocol" => [ { "type" => "MPING", "socket-binding" => "jgroups-mping" }, {"type" => "MERGE2"}, { "type" => "FD_SOCK", "socket-binding" => "jgroups-tcp-fd" }, {"type" => "FD"}, {"type" => "VERIFY_SUSPECT"}, {"type" => "BARRIER"}, {"type" => "pbcast.NAKACK"}, {"type" => "UNICAST"}, {"type" => "pbcast.STABLE"}, {"type" => "VIEW_SYNC"}, {"type" => "pbcast.GMS"}, {"type" => "UFC"}, {"type" => "MFC"}, {"type" => "FRAG2"}, {"type" => "pbcast.STREAMING_STATE_TRANSFER"}, {"type" => "pbcast.FLUSH"} ], "transport" => { "type" => "TCP", "socket-binding" => "jgroups-tcp", "diagnostics-socket-binding" => "jgroups-diagnostics" } } } {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

7
7
0 / 0

[JBoss JIRA] (AS7-3294) JSF Exception - Failed to parse the expression [#{cc.attrs.for}]

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created AS7-3294: --------------------------------------- Summary: JSF Exception - Failed to parse the expression [#{cc.attrs.for}] Key: AS7-3294 URL: https://issues.jboss.org/browse/AS7-3294 Project: Application Server 7 Issue Type: Bug Components: JSF Affects Versions: 7.1.0.CR1b Environment: Ubuntu Linux, Fedora, Java 6 Reporter: Lincoln Baxter III Assignee: Stan Silvert So I've run OCPsoft SocialPM ( https://github.com/ocpsoft/socialpm/ ) on both AS 7.1.0.CR1b and AS7 GitHub head, both of them get the following error when going to the signup page: (From Ken Finnigan) {code}21:53:35,494 WARN [org.jboss.solder.exception.control.log] (http--127.0.0.1-8080-2) No handlers found for exception javax.faces.view.facelets.TagAttributeException: /resources/ocpcommon/message.xhtml @46,61 for="#{cc.attrs.for}" Failed to parse the expression [#{cc.attrs.for}]{code} I've attached the entire server log for AS7 Head for reference. I've confirmed it worked with AS 7.0.2.Final, so it looks like a regression. I've taken a look at the JSF modules provided in AS7, 7.0.2 provides jsf-api-1.2_15-jbossorg-1.jar, whereas 7.1.0.CR1b and Head provides jsf-api-1.2_15-jbossorg-2.jar. I haven't had a chance to delve deeper into what discrepancies there might be between the two JSF versions yet. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1787) Fix JGroups description providers for the improved validation in jboss-as-subsystem-test

by Kabir Khan (JIRA)

Fix JGroups description providers for the improved validation in jboss-as-subsystem-test ---------------------------------------------------------------------------------------- Key: AS7-1787 URL: https://issues.jboss.org/browse/AS7-1787 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Reporter: Kabir Khan Assignee: Thomas Diesler Fix For: 7.1.0.Alpha1 I am adding some more validation of the model. This will be committed to upstream in the next few days. To make the security tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() as follows: {code} @Override protected ValidationConfiguration getModelValidationConfiguration() { return null; } {code} Returning null basically turns off validation of the providers. These are the errors that happen (this might change a bit before I commit the final version of the validation stuff): {code} VALIDATION ERRORS IN MODEL: Invalid key 'attributes' found for child type 'configuration' @[("subsystem" => "osgi")] No value-type for type=OBJECT {"description" => "The configuration data associated with the PID.","type" => OBJECT,"required" => true,"acces s-type" => "read-only","storage" => "configuration"} for attribute 'entries'[ ("subsystem" => "osgi"), ("configuration" => "*") ] No value-type for type=OBJECT {"description" => "The configuration data associated with the PID.","type" => OBJECT,"required" => true} for o peration parameter 'add.entries' @[ ("subsystem" => "osgi"), ("configuration" => "*") ] Invalid key 'attributes' found for child type 'property' @[("subsystem" => "osgi")] Invalid key 'attributes' found for child type 'module' @[("subsystem" => "osgi")] {code} The work in progress lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
8
0 / 0

[JBoss JIRA] Created: (AS7-1788) Fix Infinispan description providers for the improved validation in jboss-as-subsystem-test

by Kabir Khan (JIRA)

Fix Infinispan description providers for the improved validation in jboss-as-subsystem-test ------------------------------------------------------------------------------------------- Key: AS7-1788 URL: https://issues.jboss.org/browse/AS7-1788 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Kabir Khan Assignee: Paul Ferraro Fix For: 7.1.0.Alpha1 I added a test called JGroupsSubsystemTest which uses our subsystem testing framework which attempts to validate the description providers, this will be committed to upstream in the next few days. To make the tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() as follows: {code} @Override protected ValidationConfiguration getModelValidationConfiguration() { return null; } {code} Returning null basically turns off validation of the providers. What I have added is a minimum of what is required for subsystem testing, the test framework allows you to do a lot of other stuff, see the jmx subsystem test for some examples. The wip lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
8
0 / 0

[JBoss JIRA] Created: (LOGTOOL-24) Better support for Maven logging messages

by James Perkins (JIRA)

Better support for Maven logging messages ----------------------------------------- Key: LOGTOOL-24 URL: https://issues.jboss.org/browse/LOGTOOL-24 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: David Lloyd Maven only prints error and warning messages. Check for ways to print informational and possibly debug messages. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
5
0 / 0

[JBoss JIRA] (AS7-3278) rollout plan tab-completion

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-3278: -------------------------------------- Summary: rollout plan tab-completion Key: AS7-3278 URL: https://issues.jboss.org/browse/AS7-3278 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.0.Final Tab-completion isn't yet supported for rollout plans. -- 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

1
2
0 / 0

[JBoss JIRA] (AS7-3425) Allow setting of security properties via -S option on the command line

by Anil Saldhana (JIRA)

Anil Saldhana created AS7-3425: ---------------------------------- Summary: Allow setting of security properties via -S option on the command line Key: AS7-3425 URL: https://issues.jboss.org/browse/AS7-3425 Project: Application Server 7 Issue Type: Feature Request Components: Security, Server Affects Versions: 7.1.0.CR1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 7.1.0.Final It should be possible for users to set Security Properties via command line option -S http://docs.oracle.com/javase/6/docs/api/java/security/Security.html#setP... Previously it was part of Security subsystem configuration, but Jason thinks it is better to place it as a cmd line option. -- 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
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1330) EJB timer service should use a thread pool to avoid OOM

by Galder Zamarreno (JIRA)

EJB timer service should use a thread pool to avoid OOM ------------------------------------------------------- Key: EJBTHREE-1330 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1330 Project: EJB 3.0 Issue Type: Bug Components: pool Affects Versions: AS 4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor The default EJB timer service used by the EJB3 layer is based on org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory which delegates to the standard org.jboss.ejb.txtimer.EJBTimerService. For EJB3 beans using the EJB timer service the thread local pool should not be used. Since the current EJB timer service creates a new thread for each timer being created, the thread local pool will create a matching instance of the bean for that thread. Thus the number of active instances in total can effectively grow unchecked and thus an OOM will occur. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
8
0 / 0

[JBoss JIRA] (JBRULES-3355) Problems when writing rhs in Rule API

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3355: -------------------------------------- Summary: Problems when writing rhs in Rule API Key: JBRULES-3355 URL: https://issues.jboss.org/browse/JBRULES-3355 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.4.0.Beta1, 5.3.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.3.2.Final, 5.4.0.Beta2 Description of problem: There are several problems when writing rhs of a rule in Rule API: - if you omit rhs() you 'nullend' on the end of the rule which results in compile error - if you put comment in rhs() like rhs("//consequences") you get '//consequencesend' which result in compile error as well I think there should be line delimiter behind rhs and that if rhs is omitted it should result in empty string rather than "null". KnowledgeDescr descr = DescrFactory.newPackage().name("org.sample") .newRule().name("results in consequencesend") .rhs("//consequences") .end() .newRule().name("results in nullend") .lhs() .pattern("String").end() .end() .end() .getDescr(); -- 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
20
0 / 0

[JBoss JIRA] (AS7-3379) ResourceAdapterActivatorService never gets stopped

by Andy Taylor (JIRA)

Andy Taylor created AS7-3379: -------------------------------- Summary: ResourceAdapterActivatorService never gets stopped Key: AS7-3379 URL: https://issues.jboss.org/browse/AS7-3379 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.CR1b Reporter: Andy Taylor Assignee: Andy Taylor Priority: Critical Fix For: 7.1.0.Final This is because the stop method is over ridden but doesn't do anything meaning that resource adapters aren't closed properly leaving resources running. -- 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
3
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 January 2012