October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3637) Way to set JNDI properties for twiddle

by Owen Taylor (JIRA)

Way to set JNDI properties for twiddle -------------------------------------- Key: JBAS-3637 URL: http://jira.jboss.com/jira/browse/JBAS-3637 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Owen Taylor Priority: Minor It is frequently useful to be able to set JDNI properties when running twiddle - for example, you might want to set jnp.disableDiscovery when checking the status of a particular server that might not be running. Right now, this is difficult to do. You can export a JBOSS_CLASSPATH which contains a jndi.properties file before running twiddle.sh, but then you have to include all the standard jars in it, which is quite annoying. A pssible fixes would be one of: A) A way to prepend elements to JBOSS_CLASSPATH without disabling the default construction (also useful for getting a log4j.properties that doesn't drop twiddle.log in the cwd, perhaps) B) A command line option for specifying a particular properties file to load and pass to 'new InitialContext()' (slightly more convenient than A) C) A command line option to define particular properties: twiddle.sh -jnpProperty=jnp.disableDiscovery=true (Or some better syntax) The twiddle code actually does: Properties props = new Properties(System.getProperties()); props.put(Context.PROVIDER_URL, serverURL); ctx = new InitialContext(props); In the case where a server URL is set, so there may have been intention that twiddle.sh -Djnp.disableDiscovery=true would work, but AFAIK property inheritance doesn't work in that place - only the properties directly in props take effect, and system properties won't be looked at in the other code path either. -- 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

18 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-105) Refactor the VFS.isArchive and structural deployers

by Scott M Stark (JIRA)

Refactor the VFS.isArchive and structural deployers --------------------------------------------------- Key: JBMICROCONT-105 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-105 Project: JBoss MicroContainer Issue Type: Task Reporter: Scott M Stark We have been arguing about the ambiguity/utility of the vfs isArchive with regard to determing deployment strucutre. Proper separation of behavior would remove isArchive from the vfs and update the structural deployment spi to allow reuse of the structural parse without having to pull in jboss5/MainDeployer + all deployers. A related structure deployer discussion: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92529 VFS visiting: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92141 VFS isArchive removal: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92139 -- 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

18 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-759) Create a set of deadlock-detecting unit tests

by Manik Surtani (JIRA)

Create a set of deadlock-detecting unit tests --------------------------------------------- Key: JBCACHE-759 URL: http://jira.jboss.com/jira/browse/JBCACHE-759 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.4.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 >From email thread: "Okay, found out that jconsole also supports it: MBeans --> java.lang --> Threading --> Operations --> findMonitorDeadlockedThreads(). Of course, if we could integrate this into our test suites to regularly check for deadlocks..." Article from JavaSpecialists: http://www.javaspecialists.co.za/archive/newsletter.do?issue=130&locale=e... -- 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

18 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-697) First concurrent call doesn't throw exception

by Carlo de Wolf (JIRA)

First concurrent call doesn't throw exception --------------------------------------------- Key: EJBTHREE-697 URL: http://jira.jboss.com/jira/browse/EJBTHREE-697 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC10 - FD Concurrency check is in the server interceptor, while identity is established in the proxy after the first call. So if the first call is concurrent no exception is thrown. (see unit test concurrent) -- 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

18 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-479) Wizard for autopopulating a decision table

by Michael Neale (JIRA)

Wizard for autopopulating a decision table ------------------------------------------ Key: JBRULES-479 URL: http://jira.jboss.com/jira/browse/JBRULES-479 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Michael Neale Assigned To: Mark Proctor Priority: Minor This could be done quite easily by a contributor. Have a wizard (in the IDE) which takes information regarding the facts to be used, fields, actions (and the number of each) and generates a decision table based on that info capture (ie populates it). -- 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

18 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-297) Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation

by Bela Ban (JIRA)

Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation -------------------------------------------------------------------------------------------- Key: JGRP-297 URL: http://jira.jboss.com/jira/browse/JGRP-297 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 The java.lang.management.ThreadMXBean has a method to check for and (if found) enumerate deadlocked threads (only with simply synchronized locks, jav.util.concurrent locks currently not supported afaik). This can be run every N seconds, and is useful in both stress testing and possibly also during operation. -- 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

18 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-480) Change contract of Receiver

by Tim Fox (JIRA)

Change contract of Receiver --------------------------- Key: JBMESSAGING-480 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-480 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox -- 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

18 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-543) Use a file based transaction logger instead of logging in the database

by Tim Fox (JIRA)

Use a file based transaction logger instead of logging in the database ---------------------------------------------------------------------- Key: JBMESSAGING-543 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-543 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Currently we are logging prepared state transactions in the database. Instead, we should utilise a tried and tested transaction logger for performance reasons. We should evaluate both JBoss TS objectstore, and HOWL to take this role -- 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

18 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-576) Separate paging and persistence functionality

by Tim Fox (JIRA)

Separate paging and persistence functionality --------------------------------------------- Key: JBMESSAGING-576 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-576 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Alpha1, 1.0.1.CR5 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Reference management gets complex when we have to take into account messages and refs paged and not paged to storage especially if the database is shared, this means we end up having to do extra queries to work out if the ref is alredy in the database etc. We should separate the paging functionality out, so it doesn't page to the normal persistent store, but to a separate paging store which typically would be a local file based store using HOWL or some other fast logger. -- 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

18 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-608) Add a new compatibity and stress test layer based on JMS CTS

by Ovidiu Feodorov (JIRA)

Add a new compatibity and stress test layer based on JMS CTS ------------------------------------------------------------ Key: JBMESSAGING-608 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-608 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.1 http://jmscts.sourceforge.net/index.html The stress part is especially interesting. -- 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

18 years, 3 months

3
7
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 October 2006