January 2012 - jboss-jira - Jboss List Archives

[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

12 years, 5 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

12 years, 5 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

12 years, 5 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

12 years, 5 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

12 years, 5 months

4
9
0 / 0

[JBoss JIRA] (AS7-3274) Cancled recurring timer reactivated after server restart

by Wolf-Dieter Fink (Created) (JIRA)

Cancled recurring timer reactivated after server restart -------------------------------------------------------- Key: AS7-3274 URL: https://issues.jboss.org/browse/AS7-3274 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.2.Final Reporter: Wolf-Dieter Fink Assignee: Wolf-Dieter Fink If a timer should be cancled by invoking its cancel() method and this timer is current in timeout (method is processing) the cancelation is not complete successful. The scheduling is stopped imediately but after restarting the server this timer become active again. -- 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

12 years, 5 months

3
3
0 / 0

[JBoss JIRA] (AS7-3318) CLONE - ClassNotFoundException during start - org.jboss.as.messaging.jms.TransactionManagerLocator

by Miroslav Novak (JIRA)

Miroslav Novak created AS7-3318: ----------------------------------- Summary: CLONE - ClassNotFoundException during start - org.jboss.as.messaging.jms.TransactionManagerLocator Key: AS7-3318 URL: https://issues.jboss.org/browse/AS7-3318 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.CR1 Reporter: Miroslav Novak Assignee: Clebert Suconic Fix For: 7.1.0.Final When logging subsystem is set to DEBUG level for "org.hornetq" then ClassNotFoundException exception appears in console log: {code} 12:45:01,163 DEBUG [org.hornetq.ra.Util] (MSC service thread 1-4) org.jboss.as.messaging.jms.TransactionManagerLocator from [Module "org.hornetq.ra:main" from local module loader @6e811c88 (roots: /mnt/shared/test-eap6/server1/jboss-eap-6.0/modules)]: java.lang.ClassNotFoundException: org.jboss.as.messaging.jms.TransactionManagerLocator from [Module "org.hornetq.ra:main" from local module loader @6e811c88 (roots: /mnt/shared/test-eap6/server1/jboss-eap-6.0/modules)] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:473) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:461) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:403) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:125) at org.hornetq.ra.Util.locateTM(Util.java:261) [hornetq-ra-2.2.7.Final.jar:] at org.hornetq.ra.HornetQResourceAdapter.locateTM(HornetQResourceAdapter.java:1555) [hornetq-ra-2.2.7.Final.jar:] at org.hornetq.ra.HornetQResourceAdapter.start(HornetQResourceAdapter.java:210) [hornetq-ra-2.2.7.Final.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_22] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_22] at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_22] at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:345) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final] at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2127) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final] at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1030) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final] at org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator.doDeploy(ResourceAdapterActivatorService.java:148) [jboss-as-connector-7.1.0.CR1-redhat-1.jar:7.1.0.CR1-redhat-1] at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:94) [jboss-as-connector-7.1.0.CR1-redhat-1.jar:7.1.0.CR1-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] {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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1037) Ergonomics: size thread pools dynamically

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1037?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1037: --------------------------- Fix Version/s: 3.2 (was: 3.1) > Ergonomics: size thread pools dynamically > ----------------------------------------- > > Key: JGRP-1037 > URL: https://issues.jboss.org/browse/JGRP-1037 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.2 > > > Ergonomics are a step towards less configuration and more dynamic setting of values. Example: a thread pool's min and max sizes can be dynamically changed, based on observations. When we have a min size of 10, but the thread pool is always 75, then we should set the min size to 75 and possibly change the idle time too. > This is just a first step towards ergonomics and needs to be expanded on in 3.x releases -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1001) Use ByteMan / Metronome to inject faults for testing

by Bela Ban (JIRA)

Use ByteMan / Metronome to inject faults for testing ---------------------------------------------------- Key: JGRP-1001 URL: https://jira.jboss.org/jira/browse/JGRP-1001 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 Use ByteMan (jboss.org/byteman) to simulate issues that can happen at runtime: do this in unit tests. For example: crash of merge leader after initial round (who frees the locks ?) (same for FLUSH) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
7
0 / 0

[JBoss JIRA] (JGRP-1416) NAKACK / NAKACK2: shorten scope of seqno_lock

by Bela Ban (JIRA)

Bela Ban created JGRP-1416: ------------------------------ Summary: NAKACK / NAKACK2: shorten scope of seqno_lock Key: JGRP-1416 URL: https://issues.jboss.org/browse/JGRP-1416 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0.3, 3.1 The code in NAKACK/NAKACK2.send() acquires seqno_lock like this: {code:title=NAKACK.send()|borderStyle=solid} seqno_lock.lock(); try { try { // incrementing seqno and adding the msg to sent_msgs needs to be atomic msg_id=seqno +1; msg.putHeader(this.id, NakAckHeader.createMessageHeader(msg_id)); win.add(msg_id, msg); seqno=msg_id; } catch(Throwable t) { throw new RuntimeException("failure adding msg " + msg + " to the retransmit table for " + local_addr, t); } } finally { seqno_lock.unlock(); } {code} This slows concurrent sender threads down if add() takes a while. Method add() can take a while if we have many concurrent adds and removes. The reason we use seqno_lock is to prevent gaps in the sequence numbers, e.g. if we have an exception in add(). SOLUTION: - Assign a new msg_id by incrementing seqno *atomically* (seqno_lock is now de-scoped to only increment seqno, might replace this with an AtomicLong anyway) - In a loop: add the message (calling add()), until add() returns successfully, then break Example: {code} msg_id=seqno.incrementAndGet(); // uses an AtomicLong while(running) { // maybe bound with a counter try { msg.adddHeader(...); add(); break; } catch(Throwable t) { // log } } {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

12 years, 5 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012