December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3767) Create a canonical "JndiServiceMBeanSupport" useful for binding objects to JNDI

by Elias Ross (JIRA)

Create a canonical "JndiServiceMBeanSupport" useful for binding objects to JNDI ------------------------------------------------------------------------------- Key: JBAS-3767 URL: http://jira.jboss.com/jira/browse/JBAS-3767 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Reporter: Elias Ross Assigned To: Scott M Stark A common application integration pattern is to create MBean services that bind objects (or themselves) to JNDI. These objects bound to JNDI are then used in EJBs. It seems generally useful to provide a class with JBoss, similar to ServiceMBeanSupport, which allows users to bind objects to the local JNDI. A lot of JBoss services do bind objects to JNDI and could probably extend from this base class. http://wiki.jboss.org/wiki/Wiki.jsp?page=BindMBeanToJNDI Additional ideas: Create an attribute "BindObject". Then users could do something like: <attribute name="BindObject" attributeClass="..." serialDataType="javaBean"> </attribute> -- 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

17 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1055) minimize/maximize causes portlet to return to initial state

by Johnny Healey (JIRA)

minimize/maximize causes portlet to return to initial state ----------------------------------------------------------- Key: JBPORTAL-1055 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1055 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Server Affects Versions: 2.4 Final Environment: CentOS release 4.4 (Final), jdk1.5.0_06 Reporter: Johnny Healey Assigned To: Julien Viet This has been noticed in a handful of custom portlets, but can be duplicated in the "event test" page that ships with the portal. "Test Event A" can change the color of the text in "Test Event B", but minimizing or maximizing "Test Event B" causes the text to return to the original color, black. -- 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

17 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1004) Jboss Portal to support virtual hosts

by Sverker Abrahamsson (JIRA)

Jboss Portal to support virtual hosts ------------------------------------- Key: JBPORTAL-1004 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1004 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sverker Abrahamsson JBoss Portal is today unable to support multiple virtual hosts, i.e. it's not possible to create a portal bound to the address www.foo.com and one that is bound to www.bar.com. This is a major problem for real world usage of JBoss Portal -- 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

17 years, 9 months

5
14
0 / 0

[JBoss JIRA] Created: (JGRP-376) TLS: use priority based queue rather than BoundedLinkedQueue for default thread pool

by Bela Ban (JIRA)

TLS: use priority based queue rather than BoundedLinkedQueue for default thread pool ------------------------------------------------------------------------------------ Key: JGRP-376 URL: http://jira.jboss.com/jira/browse/JGRP-376 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 This will allow us to dispatch incoming messages to threads from the pool based on criteria. - The impl implements interface BoundedChannel - It has N queues, 1 for each sender (possibly those are BoundedLinkedQueues) - There is a max size in bytes for the priority queue, each internal queue has max_size / N bytes where N = number of members. This is dynamically adjusted ADDITION - An internal queue maintains the number of bytes (Message.length()), an offer() or put() increases that amount by the size of the message, a take() or poll() decreases the amount. When a put() or offer() would exceed the max amount, it will block until a take() or poll() decreases it such that the new message can be added to the queue. We might also discard messages to full queues, or implement somthing akin to RED (random early detection), which starts discarding messages *before* the queue is full REMOVAL - Strategy pluggable, e.g. - Take from the fullest queue - Take from the least full queue - Round robin - Weighted round robin (weighted by capacity of each queue), e.g. take relative to capacity from each queue. Example: Queues A (2MB), B (2MB), C (6MB): we take 2 from A, 2 from B and 6 from C - Random robin etc -- 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

17 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JGRP-381) TLS: all queues for thread pools should use number of bytes rather than number of messages

by Bela Ban (JIRA)

TLS: all queues for thread pools should use number of bytes rather than number of messages ------------------------------------------------------------------------------------------ Key: JGRP-381 URL: http://jira.jboss.com/jira/browse/JGRP-381 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Instead of defining a max number of elements in a queue BoundedBlockingQueue (used by thread pool), we define a number of bytes. If that number is exceeded, we block on put()/offer(), and only unblock if a take() has removed N number of bytes so we can add our message without exceeding the limit -- 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

17 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-670) PreDestroy called multiple times

by Carlo de Wolf (JIRA)

PreDestroy called multiple times -------------------------------- Key: EJBTHREE-670 URL: http://jira.jboss.com/jira/browse/EJBTHREE-670 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf The PreDestroy callback is called multiple times. Once from the container and once from the pool. IMHO only the pool should call PreDestroy. Other callbacks are already handled by the pool. Unit test is in regression/ejbthree... -- 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

17 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBRULES-401) add ability to lock a node to prevent concurrent editing

by Michael Neale (JIRA)

add ability to lock a node to prevent concurrent editing -------------------------------------------------------- Key: JBRULES-401 URL: http://jira.jboss.com/jira/browse/JBRULES-401 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben -- 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

17 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3544) org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails bcasue service modules are unavailable

by Jaroslaw Kijanowski (JIRA)

org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails bcasue service modules are unavailable ------------------------------------------------------------------------------------------------------------ Key: JBAS-3544 URL: http://jira.jboss.com/jira/browse/JBAS-3544 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Environment: win xp Reporter: Jaroslaw Kijanowski Fix For: JBossAS-5.0.0.Beta org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails because the services jbossweb-tomcat55.sar and jboss-aop.deployer can't be registered, becasue in JB5.0 they changed their names to jbossweb-tomcat6.sar and jboss-aop-jdk50.deployer. FIX: change testsuite/src/main/org/jboss/test/management/test/DeploymentDescriptorUnitTestCase.java . . . public void testGetSarDescriptor() throws Exception { // String moduleName = "jbossweb-tomcat55.sar"; String moduleName = "jbossweb-tomcat6.sar"; . . . public void testGetDeployerDescriptor() throws Exception { // String moduleName = "jboss-aop.deployer"; String moduleName = "jboss-aop-jdk50.deployer"; -- 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

17 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1057) Create/update DTD/schemas for descriptors.

by Chris Laprun (JIRA)

Create/update DTD/schemas for descriptors. ------------------------------------------ Key: JBPORTAL-1057 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1057 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Roy Russo Priority: Minor Fix For: 2.4.1 Final -- 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

17 years, 10 months

7
11
0 / 0

[JBoss JIRA] Created: (JBAS-3918) jbossweb virtual-host processing not working

by Scott M Stark (JIRA)

jbossweb virtual-host processing not working -------------------------------------------- Key: JBAS-3918 URL: http://jira.jboss.com/jira/browse/JBAS-3918 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Scott M Stark Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.Beta2 Add a Host entry to the deployers/jbossweb.deployer/server.xml as described in the 4.0.x section of: http://wiki.jboss.org/wiki/Wiki.jsp?page=VirtualHosts for example: <Host name="succubus-vhost" autoDeploy="false" deployOnStartup="false" deployXML="false"> <Valve className="org.apache.catalina.valves.AccessLogValve" prefix="succubus-vhost" suffix=".log" pattern="common" directory="${jboss.server.home.dir}/log"/> </Host> add a virtual-host entry to the jmx-console.war/WEB-INF/jboss-web.xml: <jboss-web> <virtual-host>succubus-vhost</virtual-host> </jboss-web> and try to access the jmx-console using succubus-vhost: [starksm@succubus Security]$ wget http://succubus-vhost:8080/jmx-console/index.jsp --08:21:41-- http://succubus-vhost:8080/jmx-console/index.jsp => `index.jsp' Resolving succubus-vhost... 192.168.10.10 Connecting to succubus-vhost|192.168.10.10|:8080... connected. HTTP request sent, awaiting response... 400 No Host matches server name succubus-vhost 08:21:41 ERROR 400: No Host matches server name succubus-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

17 years, 10 months

7
10
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 December 2006