January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2268) Domain member does startup instances

by Andreas Tauber (Created) (JIRA)

Domain member does startup instances ------------------------------------ Key: AS7-2268 URL: https://issues.jboss.org/browse/AS7-2268 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.2.Final Environment: SuSE Linux Domain Admin; Windows XP Domain Member; JBoss Web 7.0.2 on both sides Reporter: Andreas Tauber Assignee: Brian Stansberry After creating domain setup, resolved with ticket AS7-1431 individual instances defined with attribute autostart in host.xml of the domain member to not startup automatically when starting the domain.sh of this cluster member. Ok, at the moment the Admin Console is able to see my Windows XP Domain Member with three defined instances (they dont honor autostart). So I try to use Console to start those instances. Nothing really happens. AdminConsole shows green light, pressing another button goes back to red. ok, green, then red, the instances on xp domain member are not started. Starting server-four(xp) from my AdminConsole on domain controller(linux) brings one message on console: [Host Controller] 21:56:04,984 WARN [org.jboss.as.host.controller] (pool-4-thread-4) Existing server [Server:server-four] with state: STARTING But simply nothing happens. Looking forward to do full cluster deployment on "my" JBoss AS7. -- 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, 3 months

9
41
0 / 0

[JBoss JIRA] (AS7-3326) JDR Fails in Domain Mode

by Jesse Jaggars (JIRA)

Jesse Jaggars created AS7-3326: ---------------------------------- Summary: JDR Fails in Domain Mode Key: AS7-3326 URL: https://issues.jboss.org/browse/AS7-3326 Project: Application Server 7 Issue Type: Bug Components: JDR Affects Versions: 7.1.0.CR1b Environment: This issue should be present on any environment. Reporter: Jesse Jaggars Assignee: Jesse Jaggars JDR does not take into account host controller name or server name during operation and therefore fails to work correctly in domain mode. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3282) ResourceChangeScanner does not call listener.exception(throwable) if the scan method throws a RuntimeException or Error

by Geoffrey De Smet (Created) (JIRA)

ResourceChangeScanner does not call listener.exception(throwable) if the scan method throws a RuntimeException or Error ----------------------------------------------------------------------------------------------------------------------- Key: JBRULES-3282 URL: https://issues.jboss.org/browse/JBRULES-3282 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 5.4.0.Beta1 For example, ChangeSetTest succeeds, but in the system.out you get: {code} Exception in thread "Thread-9" java.lang.IllegalStateException: reader does have a modified date at org.drools.io.impl.ReaderResource.getLastModified(ReaderResource.java:64) at org.drools.io.impl.ResourceChangeScannerImpl.scan(ResourceChangeScannerImpl.java:166) at org.drools.io.impl.ResourceChangeScannerImpl$ProcessChangeSet.run(ResourceChangeScannerImpl.java:311) at java.lang.Thread.run(Thread.java:662) {code} -- 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, 3 months

5
13
0 / 0

[JBoss JIRA] (JBRULES-3287) Registering a SystemEventListener for a change set scanner does work. Therefor it's not possible to detect exceptions during scanning.

by Geoffrey De Smet (Created) (JIRA)

Registering a SystemEventListener for a change set scanner does work. Therefor it's not possible to detect exceptions during scanning. -------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-3287 URL: https://issues.jboss.org/browse/JBRULES-3287 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Mark Proctor I wrote a FailureDetectingSystemEventListener to retain the exceptions throw in the scanner, so I can fail my testcase if there are any exception is the off-threads of a testcase that should fail the test case (but currently don't). {code} FailureDetectingSystemEventListener systemEventListener = new FailureDetectingSystemEventListener(); SystemEventListenerFactory.setSystemEventListener(systemEventListener); {code} However, when I tried registering this on the agent: {code} KnowledgeAgent kagent = KnowledgeAgentFactory.newKnowledgeAgent("csv agent"); kagent.setSystemEventListener(systemEventListener); {code} It didn't work, the DoNothingSEL was still used. When I tried on the SystemEventListenerFactory: {code} SystemEventListenerFactory.setSystemEventListener(systemEventListener); {code} a StackOverflowException occurs, because ProcessChangeSet.listener is a DelegatingSEL pointing to itself. -- 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, 3 months

6
13
0 / 0

[JBoss JIRA] (AS7-2094) read-resource-description shows incorrect data types in Thread Pools

by Stan Silvert (Created) (JIRA)

read-resource-description shows incorrect data types in Thread Pools -------------------------------------------------------------------- Key: AS7-2094 URL: https://issues.jboss.org/browse/AS7-2094 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Alpha1 Reporter: Stan Silvert Assignee: Alexey Loubyansky Priority: Minor If you do :read-resource-description on a bounded-queue-thread-pool you will get several attributes with type of BigDecimal. From the xsd it looks none of them actually are of that type. I'm glad for this because the console can't handle BigDecimal right now. Also, keepalive timeout is shown as a Long when it is really an Integer. There are probably more of these as I have not checked throughout the subsystem. -- 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, 3 months

7
10
0 / 0

[JBoss JIRA] (AS7-3323) Apply properties to modules to distinguish public and non-public APIs

by David Lloyd (JIRA)

David Lloyd created AS7-3323: -------------------------------- Summary: Apply properties to modules to distinguish public and non-public APIs Key: AS7-3323 URL: https://issues.jboss.org/browse/AS7-3323 Project: Application Server 7 Issue Type: Task Components: Build System Reporter: David Lloyd Assignee: David Lloyd Priority: Blocker Fix For: 7.1.0.Final Add metainformation to each module which identifies it as one of the following: * Public - this module is intended to be available for user deployments to use * Unsupported - this module is unsupported and may change or disappear without any notice whatsoever * Private - this module is unsupported and internal and may change or disappear without any notice whatsoever -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-2494) Unable to put all configuration and logs outside AS7 distribution

by Rostislav Svoboda (Created) (JIRA)

Unable to put all configuration and logs outside AS7 distribution ----------------------------------------------------------------- Key: AS7-2494 URL: https://issues.jboss.org/browse/AS7-2494 Project: Application Server 7 Issue Type: Bug Components: Scripts Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.CR1 I'm not able to configure AS7 to use all configuration files from different location than standard $JBOSS_HOME/standalone/configuration or $JBOSS_HOME/domain/configuration. I'm using system properties described on confluence [1]. The same for log files. AS7 always requires logging.properties from $JBOSS_HOME and it writes boot.log into directories under $JBOSS_HOME depending whether standalone or domain is running. The root of this problem is in scripts: standalone.sh/.bat {code} -Dorg.jboss.boot.log.file=$JBOSS_HOME/standalone/log/boot.log -Dlogging.configuration=file:$JBOSS_HOME/standalone/configuration/logging.properties {code} domain.sh/.bat {code} -Dorg.jboss.boot.log.file=$JBOSS_HOME/domain/log/process-controller/boot.log -Dlogging.configuration=file:$JBOSS_HOME/domain/configuration/logging.properties -Dorg.jboss.boot.log.file=$JBOSS_HOME/domain/log/host-controller/boot.log -Dlogging.configuration=file:$JBOSS_HOME/domain/configuration/logging.properties {code} My idea: Introduce LOG_PATH + CONFIGURATION_PATH properties (similar to MODULEPATH property) in .sh/.bat files to have logs and configuration outside AS7/EAP6. Default LOG_PATH by default would be $JBOSS_HOME/domain/log or $JBOSS_HOME/standalone/log. Default CONFIGURATION_PATH would be $JBOSS_HOME/domain/configuration or $JBOSS_HOME/standalone/configuration. Definitions of -Dorg.jboss.boot.log.file= and -Dlogging.configuration= would be changed to use LOG_PATH + CONFIGURATION_PATH properties. Changes for server instances can be modified using system properties -- jboss.server.log.dir + jboss.server.config.dir OR jboss.domain.log.dir + jboss.domain.config.dir + jboss.domain.servers.dir. [1] https://docs.jboss.org/author/display/AS71/Command+line+parameters -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (SECURITY-641) Long running thread leaks SimpleRole objects

by Derek Horton (JIRA)

Derek Horton created SECURITY-641: ------------------------------------- Summary: Long running thread leaks SimpleRole objects Key: SECURITY-641 URL: https://issues.jboss.org/browse/SECURITY-641 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: Identity Affects Versions: PicketBox_v3_0_CR2 Environment: Tested on Mac OS X 10.6.7 with Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode) 1.6.0_24 Reporter: Derek Horton Assignee: Marcus Moyses Fix For: PicketBox_v4_0_final When invoking a long-running EJB method which makes a bunch of calls to some method in another EJB, then JBoss leaks SimpleRole objects. The SimpleRole objects are not removed by a manually triggered garbage collection. The SimpleRole object leakage seems to go away if I remove the security domain in jboss.xml. When running my jboss application during the night JBoss had 4GB of SimpleRole objects. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2323) All Quickstart readme files should include a link to the Getting Started Developing Applications Guide

by Sande Gilda (Created) (JIRA)

All Quickstart readme files should include a link to the Getting Started Developing Applications Guide ------------------------------------------------------------------------------------------------------ Key: AS7-2323 URL: https://issues.jboss.org/browse/AS7-2323 Project: Application Server 7 Issue Type: Enhancement Reporter: Sande Gilda -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-2883) Replace <alias> elemenst in infinispan subsystem with single <aliases> element

by Paul Ferraro (Created) (JIRA)

Replace <alias> elemenst in infinispan subsystem with single <aliases> element ------------------------------------------------------------------------------ Key: AS7-2883 URL: https://issues.jboss.org/browse/AS7-2883 Project: Application Server 7 Issue Type: Enhancement Components: Clustering Affects Versions: 7.1.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Minor Fix For: 7.1.0.CR1 To be consistent with domain configuration conventions, replace the sequence of string elements: <cache-container ...> <alias>alias1</alias> <alias>alias2</alias> </cache-container> with a list element: <cache-container ...> <aliases>alias1 alias2</aliases> </cache-container> -- 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, 3 months

4
9
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