October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-805) Channel is set to AUTO_GET_STATE even if cache doesn't want initial state transfer

by Brian Stansberry (JIRA)

Channel is set to AUTO_GET_STATE even if cache doesn't want initial state transfer ---------------------------------------------------------------------------------- Key: JBCACHE-805 URL: http://jira.jboss.com/jira/browse/JBCACHE-805 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani The channel should probably only be set to AUTO_GET_STATE if getFetchStateOnStartup() returns true. Otherwise if the node is shunned and reconnects, a full state transfer will occur. Presumably the cache can't or doesn't want to handle that, or getFetchStateOnStartup() would not have returned true. One problem is what if getFetchStateOnStartup() returns false because the config uses a shared cache loader (so no persistent state transfer) and a cold cache at startup is OK (so no in-memory state transfer). But, following reconnect the cache is no longer "cold" -- the in-memory tree now has potentially stale data. -- 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

16 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (SECURITY-8) LdapExtLoginModule should detect communication failures midstream

by Anil Saldhana (JIRA)

LdapExtLoginModule should detect communication failures midstream ------------------------------------------------------------------ Key: SECURITY-8 URL: http://jira.jboss.com/jira/browse/SECURITY-8 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 http://jira.jboss.com/jira/browse/JBAS-3661 There is a possibility of the context going stale due to communication exceptions with the ldap server when dealing with references etc. It may be useful for the LdapExtLoginModule to implement the: http://java.sun.com/j2se/1.3/docs/api/javax/naming/ldap/UnsolicitedNotifi... such that it can do graceful processing. -- 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

16 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3596) JNDI static cache

by Clebert Suconic (JIRA)

JNDI static cache ----------------- Key: JBAS-3596 URL: http://jira.jboss.com/jira/browse/JBAS-3596 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Clebert Suconic Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.CR1 Having a JNDI caching would improove performance on applications where JNDI is over used. -- 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

16 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-699) StackOverflowError in org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy

by Michael Grübsch (JIRA)

StackOverflowError in org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy ----------------------------------------------------------------------- Key: EJBTHREE-699 URL: http://jira.jboss.com/jira/browse/EJBTHREE-699 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC7 - FD Environment: Windows XP Reporter: Michael Grübsch Priority: Critical I refer to source version $Revision: 1.1.4.2 $ This is an excerpt from the stack trace: at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114) at $Proxy398.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114) at $Proxy398.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114) You may see, that invoke calls getProxyString which in turn on the proxy calls invoke! -- 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

16 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBFORUMS-129) Modify the schema being used from PHPBB

by Sohil Shah (JIRA)

Modify the schema being used from PHPBB --------------------------------------- Key: JBFORUMS-129 URL: http://jira.jboss.com/jira/browse/JBFORUMS-129 Project: JBoss Forums Issue Type: Sub-task Reporter: Sohil Shah Assigned To: Sohil Shah -- 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

16 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBFORUMS-127) Eliminate all GPL dependencies from the new forums

by Sohil Shah (JIRA)

Eliminate all GPL dependencies from the new forums -------------------------------------------------- Key: JBFORUMS-127 URL: http://jira.jboss.com/jira/browse/JBFORUMS-127 Project: JBoss Forums Issue Type: Task Affects Versions: 1.0.0 Alpha Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 1.1.0 Alpha Need to identify any GPL dependencies and convert to LGPL -- 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

16 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3511) JMS ASF integration and JMS Session Pools need resource management improvements

by Weston Price (JIRA)

JMS ASF integration and JMS Session Pools need resource management improvements ------------------------------------------------------------------------------- Key: JBAS-3511 URL: http://jira.jboss.com/jira/browse/JBAS-3511 Project: JBoss Application Server Issue Type: Support Patch Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.3 SP1 Reporter: Weston Price Assigned To: Weston Price Priority: Minor A client has requested that the JMS applications server integration facilities for resource management and JMS session pooling be improved primarily in two areas: 1) The ability to not create all JMS sessions on container startup. 2) The ability to recycle/release JMS sessions based on a configurable timeout. Both these features would need to be added to the existing JMSContainerInvoker as well as carried forward to the JBossJCA adapter prior to production release. -- 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

16 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3406) JMX Console throws 500 exception on regular expressions

by gregorypierce (JIRA)

JMX Console throws 500 exception on regular expressions ------------------------------------------------------- Key: JBAS-3406 URL: http://jira.jboss.com/jira/browse/JBAS-3406 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Environment: OSX 10.4.7 Reporter: gregorypierce When going through the Getting Started guide there is a note to search for service=JNDIView. After bringing up the JNDIView I entered a regular expression to search for all of the JNDI services and the server threw a 500 exception as opposed to saying that that format was not supported. -- 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

16 years, 9 months

4
5
0 / 0

[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

16 years, 9 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

16 years, 9 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006