July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1381) Make Schema and DTD downloadable

by Manik Surtani (JIRA)

Make Schema and DTD downloadable -------------------------------- Key: JBCACHE-1381 URL: http://jira.jboss.com/jira/browse/JBCACHE-1381 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Mircea Markus -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1379) Provide command-line converter scripts

by Manik Surtani (JIRA)

Provide command-line converter scripts -------------------------------------- Key: JBCACHE-1379 URL: http://jira.jboss.com/jira/browse/JBCACHE-1379 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Mircea Markus -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-511) FC: dynamically adjust credits

by Bela Ban (JIRA)

FC: dynamically adjust credits ------------------------------ Key: JGRP-511 URL: http://jira.jboss.com/jira/browse/JGRP-511 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 FC currently has a static number of credits (max_credits). It would be beneficial to implement something similar to TCP's exponential backoff and slow start, to take the message loss rate into account. Goal: when there is an overload, we reduce the credits in order to avoid compounding the overload by sending messages. On the other hand, we can send more messages when the receiver(s) have free capacity. To do this, each receiver sends the number of credits it can accept with its responses. By default, this would be the default number of credits (in TCP: size of the sliding window). DESIGN: NAKACK (and/or UNICAST) send the loss rate (rolling average of number of messages missing over number of messages received, per sender) when it exceeds a certain value (defined in NAKACK,UNICAST) up the stack. FC looks at the loss rate and slices the number of credits for that sender in half (exponential backoff). On the next response, it piggy backs the new number of credits, so that sender will block sending messages. When the loss rate drops below a certain (predefined) value, NAKACK sends another event up the stack. FC then increases the credits by a predefined value (slow start). Next time, it increases the value by the predefined value by 2 and so on, until the max number of credits have been reached again. -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1378) Update sample config files

by Manik Surtani (JIRA)

Update sample config files -------------------------- Key: JBCACHE-1378 URL: http://jira.jboss.com/jira/browse/JBCACHE-1378 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Mircea Markus -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Commented: (JBCACHE-552) Use "/" to replace "__DEFAULT__" in eviction policy

by Mircea Markus (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-552?page=comments#action_12421377 ] Mircea Markus commented on JBCACHE-552: --------------------------------------- the _DEFAULT_ was removed from the configuration, should only be removed from the code > Use "/" to replace "__DEFAULT__" in eviction policy > --------------------------------------------------- > > Key: JBCACHE-552 > URL: http://jira.jboss.com/jira/browse/JBCACHE-552 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Eviction > Reporter: Ben Wang > Assigned To: Mircea Markus > Fix For: 3.0.0.GA > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Came up with a suggestion from Bela's training course. Currently since the region specification is order important, so use of "/" can be dangerours if not specified correctly. Btu can we order it internally during eviction policy specification such that user can order them randomly? What's the implication for troubleshooting? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1367) Eviction configuration too coarse grained - using seconds instead of milliseconds.

by Manik Surtani (JIRA)

Eviction configuration too coarse grained - using seconds instead of milliseconds. ---------------------------------------------------------------------------------- Key: JBCACHE-1367 URL: http://jira.jboss.com/jira/browse/JBCACHE-1367 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eviction Affects Versions: 2.1.1.GA, 2.1.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 3.0.0 Eviction configuration uses things like wakeUpIntervalSeconds, timeToLiveSeconds and maxAgeSeconds. Should provide similar attribs like wakeUpInterval, timeToLive and maxAge - which measure time in millis, which is more standard. Deprecate "Seconds" version, log a warning when they are 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, 2 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-645) Providing xml schema or dtd for configuration validation

by Mircea Markus (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-645?page=all ] Mircea Markus resolved JBCACHE-645. ----------------------------------- Fix Version/s: 3.0.0.ALPHA1 Resolution: Done Schema was created and uploaded here: http://www.jboss.org/jbosscache/jbosscache-config-3.0.xsd. (Most likely the url will change before the 3.0. GA to http://www.jbosscache.org/config/jbosscache-config-3.0.xsd). > Providing xml schema or dtd for configuration validation > -------------------------------------------------------- > > Key: JBCACHE-645 > URL: http://jira.jboss.com/jira/browse/JBCACHE-645 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.SP2 > Reporter: Galder Zamarreno > Assigned To: Mircea Markus > Fix For: 3.0.0.ALPHA1, 3.0.0.GA > > > It'd be nice if JBossCache could distribute an XML schema or dtd > that would allow for configuration to be validated before JBossCache > was actually deployed or started. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-89) Allow Specifying Custom Interceptors in XML Configuration

by Mircea Markus (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-89?page=all ] Mircea Markus resolved JBCACHE-89. ---------------------------------- Fix Version/s: 3.0.0.ALPHA1 Resolution: Done resolved all but the documentation (docs cannot be updated at this time as the layout is being changed for i18n). http://jira.jboss.com/jira/browse/JBCACHE-1391 was created to capture this. > Allow Specifying Custom Interceptors in XML Configuration > --------------------------------------------------------- > > Key: JBCACHE-89 > URL: http://jira.jboss.com/jira/browse/JBCACHE-89 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2 > Reporter: Daniel Gredler > Assigned To: Mircea Markus > Fix For: 3.0.0.ALPHA1, 3.0.0.GA > > Original Estimate: 1 day > Time Spent: 30 minutes > Remaining Estimate: 7 hours, 30 minutes > > It would be nice to be able to add interceptors via the XML configuration files. Indeed, in TreeCache.java the following comment exists, which may indicate that this feature is already planned: > // Create the interceptors in the correct order (later to be defined in XML file) > createInterceptorChain(); > A possible example configuration would be: > <server> > <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar" /> > <mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=TreeCache"> > ... > <attribute name="Interceptors"> > <interceptor>com.foo.project.MyInterceptor</interceptor> > </attribute> > ... > </mbean> > </server> > Something along the lines of the following method would then be able to add the custom interceptors (in TreeCache.java): > public void setInterceptors(Element interceptors) throws Exception { > NodeList list = interceptors.getChildNodes(); > for(int i = 0; i < list.getLength(); i++) { > org.w3c.dom.Node node = list.item(i); > if(node.getNodeType() != org.w3c.dom.Node.ELEMENT_NODE) > continue; > NodeList children = node.getChildNodes(); > if(children.getLength() != 1) > continue; > org.w3c.dom.Node childNode = list.item(0); > if(childNode.getNodeType() != org.w3c.dom.Node.TEXT_NODE) > continue; > String className = childNode.getNodeValue(); > if(className == null || className.length() == 0) > continue; > Interceptor interceptor = createInterceptor(className); > addInterceptor(interceptor_chain, interceptor); > } > } -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1283) Remove MBEAN tag from configuration files

by Manik Surtani (JIRA)

Remove MBEAN tag from configuration files ----------------------------------------- Key: JBCACHE-1283 URL: http://jira.jboss.com/jira/browse/JBCACHE-1283 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.1.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 3.0.0 Replace the <mbean ... /> container tag in config files with a <jbosscache ... /> tag. Would entail: 1) update all sample configs and docs to reflect this "new" element 2) document how the configuration will still accept old <mbean ... /> tags, but this is deprecated 3) document how the <mbean ... /> tag can cause problems with AS 5 (unintentional deployment), and how this can be done properly with the MC using the new <jbosscache ... /> tag Currently the XMLConfigurationParser looks for a <mbean ../> element, under which it pulls out more specific JBoss Cache elements. This could easily change so the parser to accept this, or on failing to do so, to pick up a <jbosscache ... /> container element. And log a deprecation warning when using the old <mbean ... /> container tag. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Resolved: (JBWEB-17) support mapping multiple Connectors to different vhosts

by Remy Maucherat (JIRA)

[ http://jira.jboss.com/jira/browse/JBWEB-17?page=all ] Remy Maucherat resolved JBWEB-17. --------------------------------- Resolution: Rejected The Tomcat architecture uses a hierachical view that is good for many things, including sensible configurability, but in return is not as flexible for mixing and matching connectors with hosts and individual webapps. Options include access restriction valves or "URL" rewriting using the JBoss Web rewrite valve, which will provide something transparent to your webapp. > support mapping multiple Connectors to different vhosts > ------------------------------------------------------- > > Key: JBWEB-17 > URL: http://jira.jboss.com/jira/browse/JBWEB-17 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Module > Reporter: Jan Hecking > Assigned To: Remy Maucherat > > See forum posting: > http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870728 > I'd like to deploy several web apps in a single JBoss server. Some of these apps are for internal use only. For security reasons it is required that the internal apps are not available on the same port as the external apps. Using regular vhosts is not sufficient as the vhost being accessed entirely depends on the Host: HTTP header sent by the client so requests to the "internal" vhosts cannot be blocked by the firewall on the TCP/IP layer but only by analyzing the HTTP request on the application layer. > As Scott Stark suggested in a reply to my forum posting it would be great if different Tomcat HTTP Connectors could be mapped to each vhost. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008